ODS / Release Guide / 3.1

More documents

Recommendations

Info

$Math 152 - Lecture Notes # 3 - David Maslanka THE CATENARY A ...$

Section 4 Problem Resolutions Human Resources 1-1430LW Impact When calculating deduction amounts, the current process obtains amounts from the PDRDEDN table. There are certain deductions that need to be retrieved from the PTRBDPL table as well which were missed in the design of benefit deductions. Resolution The existing function to get the deduction amounts was going against the PDRDEDN table. There are cases where the deduction amounts should be retrieved from the PTRBDPL table. This logic was added to POKODSF in order to properly account for all deductions for the columns in the BENEFIT_DEDUCTION reporting view. 1-1DLLIA Impact The ODS table MPT_EMPL_EARN_CY is keyed upon PERSON_UID, CALENDAR_YEAR, EMPLOYER, POSITION, SUFFIX, EARNINGS, MONTH. So, a PERJTOT change does trigger an update for any row based on that key. However the function POKODSF.F_CALC_EARNING_TOTALS_YTD (used to calculate total hours and total earning year-to-date) does so based on PERSON_UID only and not PERSON_UID and Position. Resolution The PERYCHG change table was modified to refresh based on PIDM and YEAR. This was done because the composite views use functions that calculate amounts based on a parameter of PIDM & Year. So, all rows must be refreshed for a PIDM and YEAR in order to calculate them correctly. 1-1DY3E1 Impact The NBBFISC_COAS code is a NULL column in Banner. As a result, this column should not be used during the incremental refresh. The trigger will fail on NBBFISC if a record is inserted in NBBFISC without the COAS code. Resolution The change table NBRFCHG was modified to refresh only on the fiscal year. The chart of accounts was removed and the necessary objects were modified to reflect this change. 1-1JNL2E Impact The TOTAL_HOURS_FISCAL_YEAR & TOTAL_EARNINGS_FISCAL_YEAR columns in the AP_EARNING_TOTALS_FY composite view are calculated incorrectly. The Fiscal Year is passed to a function that is not taking into account the start and end dates of that particular fiscal year. As a result, these calculations are being done for the calendar year. Resolution A new function was added to POKODSF to calculate the amounts for the months within a fiscal year. Operational Data Store Release 3.1 April 2007 36 Release Guide Confidential
Section 4 Problem Resolutions Human Resources 1-1JNWO9 Impact The join to YEARLY_DEDUCTION in the BENEFIT_DEDUCTION reporting view causes a performance issue in this view due to the aggregations being calculated in YEARLY_DEDUCTION. Resolution A new table to house the YEARLY_DEDUCTION data was created in the ODS. This will become part of the ODS ETL and will significantly increase the performance of the reporting views that use the YEARLOY_DEDUCTION reporting view. 1-IAJNC Impact The fields, PROFILE_DATE and PROFILE_YEAR, were not returning data because of a typo. EMPLOYEE_PROLILE needed to be changed to EMPLOYEE_PROFILE. Resolution The parameter for the functions, F_YEAR and F_PROFILE_DATE were changed to EMPLOYEE_PROFILE. 1-MFS0N Impact Records were being excluded from the BENEFICIARY_DEPENDENT reporting view due to an incorrect join in the view. If a beneficiary does not have a PIDM it causes the BENEFICIARY_DEPENDENT view to exclude that person. Resolution An outer join from MST_PERSON join to MPT_BENEFICIARY was added on the BENEFICIARY_UID so that all records from MPT_BENEFICIARY would be retrieved regardless of a BENEFICIARY_UID having a record in the MST_PERSON table. 1-NNWZA Impact When Finance is partitioned, it results in a mapping error when scheduled in the Administrative UI: Error Purging Change Table - no DELETE mapping found for: LOAD_MFT_TRANS_HISTORY_1_PART. All five partitions fail with a similar error. The same holds true for the payroll distribution partition exchange mappings. Resolution The script to install the partition exchange option for transaction history and payroll history were modified to add the records to TMTVPARM. This creates records in MTVPARM so that the mapping knows which change table to purge prior to loading these tables. 1-QAJXX Impact The join in Cognos between PAYROLL_EMPLOYEE_POSITION and EMPLOYEE_POSITION had an incorrect join: April 2007 Operational Data Store Release 3.1 Confidential Release Guide 37
Page 2 and 3: This documentation is proprietary i
Page 4 and 5: Table of Contents New Enrolled & Re
Page 6 and 7: Table of Contents This page intenti
Page 8 and 9: Introduction This page intentionall
Page 10 and 11: Section 1 Functional Enhancements A
Page 12 and 13: Section 1 Functional Enhancements A
Page 14 and 15: Section 1 Functional Enhancements F
Page 16 and 17: Section 1 Functional Enhancements H
Page 18 and 19: Section 1 Functional Enhancements S
Page 20 and 21: Section 1 Functional Enhancements N
Page 22 and 23: Section 2 Miscellaneous Enhancement
Page 24 and 25: Section 2 Miscellaneous Enhancement
Page 26 and 27: Section 3 Documentation Enhancement
Page 28 and 29: Section 4 Problem Resolutions Admin
Page 30 and 31: Section 4 Problem Resolutions Commo
Page 32 and 33: Section 4 Problem Resolutions Commo
Page 34 and 35: Section 4 Problem Resolutions Finan
Page 38 and 39: Section 4 Problem Resolutions Stude
Page 48 and 49: Section 4 Problem Resolutions Gener
Page 54 and 55: Section 5 New, Changed, Removed Dat
Page 86 and 87:
Section 5 New, Changed, Removed Dat
Page 88 and 89:
Page 90 and 91:
Page 92 and 93:
Page 94:
show all

ODS / Release Guide / 3.1

Create successful ePaper yourself

Delete template?

Save as template?