ODS / Release Guide / 3.1

More documents

Recommendations

Info

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

Section 4 Problem Resolutions Common being used. The change table was changed from AGRMCHG to the correct one, AGRGCHG. Resolution The triggers on AGBMGID and AGRMGIF were using the wrong change table, AGRMCHG. The triggers were changed to use AGRGCHG instead. 1-J60RF Impact The SPOUSE_IND in CONSTITUENT was not correctly being calculated. It needs to check for the cross reference records in MAT_RELATION (instead of the spouse records), and then also check that the MAT_RELATION.SPPOUSE_IND = Y. Resolution Create a new function which checks for an active spouse from MAT_RELATION and checks for a xref_code = X. This defect was corrected prior to the ODS 3.1 release. This fix was replaced because additional changes were made for the Relationship reporting view(RPE 1-EKBA1). 1-IYIUV Impact The wrong session was being selected when there were more than one SESSION_ID for a USER_ID for a given day. Resolution The TRUNC on the parameter date was removed. The AGBCSHR_START_DATE and AGBCSHR_END_DATE were removed so that the correct session is selected. Common 1-1GE4PX Impact The Communications process is currently designed to refresh based on the PIDM since the only database required fields are PIDM, System Code, and Activity Date. This means that every time a letter is processed (either update, insert or delete), all records for that PIDM are deleted and then all remaining records are re-inserted. Obviously, any school that fully utilizes Banner's letter process is going to have a lot of entries per person. So if an individual has, over the course of two years, 20 GURMAIL entries (even if they are from different systems like Advancement and Admissions), every time a new letter is added, all 20 letters are reprocessed. This creates a tremendous amount of unnecessary overhead for processing. Given the fact that a school may have thousands of students receiving mass mailings on a regular basis, you can see where the performance issues could start to creep in over time. Operational Data Store Release 3.1 April 2007 30 Release Guide Confidential
Section 4 Problem Resolutions Common Resolution A new change table was created to process GURMAIL changes (GURMCHG) - it's keys are GURMAIL_PIDM, GURMAIL_ACTIVITY_DATE. Modified the DELETE and UPDATE mappings to use the new change table and associated keys. 1-HEGFJ Impact Column naming was inconsistent in the following GOVERNEMENT_ACADEMIC_OUTCOME, GOVERNMENT_ADMISSIONS, GOVERNEMENT_FINANCIAL_AID, GOVERNMENT_STUDENT, PERSON, PERSON_DETAIL, PERSON_SENSITVE reporting views for the following columns names PRIMARY_ETHNICITY, PRIMARY_ETHNICITY_DESC, PRIMARY_ETHNICITY_CATEGORY and PRIMARY_ETHNICITY_CATEGORY_DESC. It was perceived as misspelled because the abbreviation in the initial reporting view was not consistently applied when these columns appear in a reporting view. This inconsistency was corrected. Resolution Consistent column naming was applied to the following reporting views: • GOVERNMENT_ACADEMIC_OUTCOME, GOVERNMENT_ADMISSIONS • OVERNMENT_FINANCIAL_AID • GOVERNMENT_STUDENT, • PERSON, PERSON_DETAIL • PERSON_SENSITIVE The column names are now: • PRIMARY_ETHNICITY, PRIMARY_ETHNICITY_DESC • PRIM_ETHNICITY_CATEGORY • PRIM_ETHNICITY_CATEGORY_DESC 1-HEIHH Impact Any code that had an apostrophe or any non-numeric, alphabetic symbol in it would error out on the loading of that data into the ODS. This was due to the F_GET_DESC function in GOKODSF. Resolution Added INCOMING_PARM_VALUE_REPLACE variable to replace INCOMING_PARAMETER_VALUE so that codes with apostrophes, etc. can be used. Used the REPLACE function to allow for these types of symbols. 1-OCJVG Impact The meta data for ORGANIZATION_ENTITY.TAX_ID was updated from NA to the proper source of SPBPERS_SSN. April 2007 Operational Data Store Release 3.1 Confidential Release Guide 31
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 32 and 33: Section 4 Problem Resolutions Commo
Page 34 and 35: Section 4 Problem Resolutions Finan
Page 36 and 37: Section 4 Problem Resolutions Human
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 80 and 81:
Section 5 New, Changed, Removed Dat
Page 82 and 83:
Page 84 and 85:
Page 86 and 87:
Page 88 and 89:
Page 90 and 91:
Page 92 and 93:
Page 94:
show all

ODS / Release Guide / 3.1

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?