ODS / Release Guide / 3.1
ODS / Release Guide / 3.1
ODS / Release Guide / 3.1
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Section 4 Problem Resolutions<br />
Finance<br />
data might be recorded in SHRTRIT without have any data in the SORPCOL. The<br />
ETL processing will be modified to consider this possible occurrence of related data.<br />
Resolution<br />
Added SHRTRCE_COUNT_IND_GPA_IND to the function named<br />
F_CALC_TRANSFER_CREDITS. This modified function was used to create both of<br />
the above mentioned <strong>ODS</strong> reporting views. Code was written (SOVPCL0.sql) to<br />
include data from both the SHRTRIT/SHRTRAM and the SORPCOL/SORDEGR<br />
Banner database tables. The reporting view, PREVIOUS_EDUCATION, was<br />
modified to retrieve only one record for each combination of PERSON_UID<br />
(PIDM) and INSTITUTION (STVSBGI_CODE). A new view was created to be used<br />
with the update mapping, MSVPCOL.sql.<br />
Finance<br />
1-1A2CII<br />
Impact<br />
The UPDATE_MFT_CHECKS mapping is not performing optimally. There is a very<br />
low record per second rate during this process.<br />
Resolution<br />
The reason the performance on this mapping was slow is because we were not using<br />
the primary key when trying to do the refresh. A new change table was created so<br />
that both the BANK_CODE and CHECK_NUMBER are used while refreshing the<br />
MFT_CHECKS table.<br />
1-1E2L1T<br />
Impact<br />
There are two parts to this defect. The first part is the fact that a script that creates<br />
two Banner table indexes for the ETL of MFT_TRANSACTION_HISTORY never<br />
was included as part of the <strong>ODS</strong> 3.0 install. The second part is that the original index<br />
FGBTRND_FROM_TRNH_<strong>ODS</strong> referenced the wrong column and could cause<br />
performance issues.<br />
Resolution<br />
The index was corrected and put into a patch that creates both indexes for those<br />
clients that were a fresh <strong>ODS</strong> 3.0 install. The actual correction in the index itself was<br />
to change column FGBTRND_ENCD_ITEM_NUM to FGBTRND_ITEM_NUM.<br />
The install script was also updated for the <strong>ODS</strong> <strong>3.1</strong> release so that this will not be a<br />
problem in the future.<br />
1-17WV00<br />
Impact<br />
The AF_FUND_HIERARCHY and AF_ACCOUNT_HIEARCHY views are returning<br />
limited records in an Oracle 10g database where the Optimizer is set to CHOOSE.<br />
Resolution<br />
The OPTIMIZER MODE of CHOOSE was causing this view to return a limited<br />
April 2007 Operational Data Store <strong>Release</strong> <strong>3.1</strong><br />
Confidential <strong>Release</strong> <strong>Guide</strong> 33