ODS / Release Guide / 3.1

More documents

Recommendations

Info

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

Section 4 Problem Resolutions Student "Payroll Employee Position.POSITION_BEGIN_DATE = Employee Position.EFFECTIVE_DATE" Additionally, for the sake of ease of use, a new column should be added to EMPLOYEE_POSITION that indicates whether the position is a current position as of today's date. Resolution The function MPKFUNC.F_POSITION_CURRENT_IND was created to return an 'N' or 'Y' depending on whether the position is current based on the current date. In EMPLOYEE_POSITION reporting view, the column POSITION_CURRENT_IND was added to call the new function. The Employee Position was updated in the Employee, Faculty Assignment, Human Resource Faculty, Payroll, and Position business areas. The relationship was updated in the Payroll business view. Student 1-10G2J1 Impact REGISTRATION_STATUS, REGISTRATION_ERROR_FLAG and the other fields from SFRSTCR were not being updated in MST_STUDENT_COURSE where INSTITUTION_COURSE_IND = Y. Resolution A trigger on SFRSTCR was added for AS_STUDENT_COURSE_HISTORY to update changes to MST_STUDENT_COURSE. 1-10QHM8 Impact Composite views with a UNION in them can experience performance problems when they are joined to change tables within the UPDATE mappings. Resolution New composite view, MSVCURR, was created as a join of the existing AS_CURRICULUM select statement and the Banner change table SGRPCHG. The mapping UPDATE_MST_CURRICULUM was modified to use the new MSVCURR view. 1-11UA2L Impact A number of the values in MST_CURRICULUM originate from the Banner table SORLCUR. If no values exist on SORLCUR, then they will be retrieved from SGBSTDN. If there are no values in SORLCUR for the site information, admissions population, student population, student rate, leave reason and dates, or intended graduation academic period, year, and date, then these values in MST_CURRICULUM may not be synchronized with the SGBSTDN values. Operational Data Store Release 3.1 April 2007 38 Release Guide Confidential
Section 4 Problem Resolutions Student Resolution Added a call to the trigger ST_SGBSTDN_INSERT_ODS_CHANGE to track which curriculum records need to be refreshed. 1-15R5AX Impact The reporting views ADMISSIONS_APPLICATION, RECRUITMENT_INFORMATION, ACADEMIC_STUDY, ACADEMIC_OUTCOME and GOVERNMENT_ADMISSIONS can now be uniquely identified by the various curricula within an academic period for a person. The columns CURRICULUM_PRIORITY_NUMBER and CURRICULUM_ORDER or PROGRAM_NUMBER were added to each of these reporting views, and are the columns used to uniquely identify the priority of the curriculum for each student. Resolution Added the columns CURRICULUM_PRIORITY and CURRICULUM_ORDER to the following tables: MST_ADMISSIONS_APPLICATION MST_RECRUITMENT_INFORMATION MST_ACADEMIC_OUTCOME Added CURRICULUM_PRIORITY to MST_GENERAL_STUDENT. Added the columns CURRICULUM_PRIORITY_NUMBER and CURRICULUM_ORDER to the following reporting views: ADMISSIONS_APPLICATION RECRUITMENT_INFORMATION ACADEMIC_OUTCOME. Added CURRICULUM_ORDER to the view GOVERNMENT_ADMISSIONS. Added CURRICULUM_PRIORITY_NUMBER to view ACADEMIC_STUDY. Fixed Object Access views AR_USER_DEFINED_FIELDS, AS_ADMISSIONS_APPLICANT, MRVSTS1, AS_RECRUITING_DATA, and AS_RECRUITING_SOURCE_ANALYSIS to only display the primary curriculum if any exist. 1-17H2EH Impact There are specific situations where students have registered for classes (having rows defined in STUDENT_COURSE), and do not have corresponding records loaded into ACADEMIC_STUDY and ENROLLMENT (possibly other reporting views are also affected). April 2007 Operational Data Store Release 3.1 Confidential Release Guide 39
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 36 and 37: Section 4 Problem Resolutions Human
Page 40 and 41: 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 88 and 89:
Section 5 New, Changed, Removed Dat
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?