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.
This documentation is proprietary information of SunGard Higher Education and is not to be copied, reproduced, lent or disposed of,<br />
nor used for any purpose other than that for which it is specifically provided without the written permission of SunGard Higher<br />
Education.<br />
SunGard Higher Education<br />
4 Country View Road<br />
Malvern, Pennsylvania 19355<br />
United States of America<br />
(800) 522 - 4827<br />
Customer Support Center website<br />
http://connect.sungardhe.com<br />
Distribution Services e-mail address<br />
distserv@sungardhe.com<br />
Other services<br />
In preparing and providing this publication, SunGard Higher Education is not rendering legal, accounting, or other similar professional<br />
services. SunGard Higher Education makes no claims that an institution's use of this publication or the software for which it is provided<br />
will insure compliance with applicable federal or state laws, rules, or regulations. Each organization should seek legal, accounting and<br />
other similar professional services from competent providers of the organization's own choosing.<br />
Trademark<br />
Without limitation, SunGard, the SunGard logo, Banner, Campus Pipeline, Luminis, PowerCAMPUS, Matrix, and Plus are trademarks<br />
or registered trademarks of SunGard Data Systems Inc. or its subsidiaries in the U.S. and other countries. Third-party names and marks<br />
referenced herein are trademarks or registered trademarks of their respective owners.<br />
Notice of rights<br />
Copyright © SunGard Higher Education 2007. This document is proprietary and confidential information of SunGard Higher Education<br />
Inc. and is not to be copied, reproduced, lent, displayed or distributed, nor used for any purpose other than that for which it is<br />
specifically provided without the express written permission of SunGard Higher Education Inc.
<strong>Release</strong> <strong>Guide</strong><br />
Operational Data Store<br />
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7<br />
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7<br />
Section 1 Functional Enhancements . . . . . . . . . . . . . . . . . . . . . . 9<br />
Accounts Receivable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9<br />
Changed RECEIVABLE_ACCOUNTING Reporting View . . . . . . . . . . . . . . . . . 9<br />
Changed Accounts Receivable Views . . . . . . . . . . . . . . . . . . . . . . . . . . 9<br />
Administrative User Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10<br />
Email Notification Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10<br />
Freeze Data Maintenance Enhancements . . . . . . . . . . . . . . . . . . . . . . . . 10<br />
Miscellaneous Administrative UI Enhancements . . . . . . . . . . . . . . . . . . . . . 11<br />
Advancement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12<br />
Changed CONSTITUTUENT Reporting View . . . . . . . . . . . . . . . . . . . . . . 12<br />
Removed Views and Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12<br />
Common . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13<br />
New F_GET_PERSON_INFO function . . . . . . . . . . . . . . . . . . . . . . . . . . 13<br />
Changed PREFERRED_ADDRESS Reporting View . . . . . . . . . . . . . . . . . . . . 13<br />
Changed Relationship Reporting View. . . . . . . . . . . . . . . . . . . . . . . . . . 13<br />
Finance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14<br />
New Financial Manager and Principal Investigator Names . . . . . . . . . . . . . . . 14<br />
Changed TRANSACTION_HISTORY Reporting View . . . . . . . . . . . . . . . . . . 15<br />
Financial Aid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15<br />
New and Changed Indexes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15<br />
Human Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16<br />
Changed LEAVE_BALANCE View . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16<br />
Student . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16<br />
New Fourth Minor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16<br />
New Enrollment View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16<br />
3
Table of Contents<br />
New Enrolled & Registered Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . 16<br />
Changed STUDENT_COURSE Reporting View. . . . . . . . . . . . . . . . . . . . . . 17<br />
Changed Academic Standing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17<br />
Changed STUDENT_COURSE_ATTRIBUTE Reporting View . . . . . . . . . . . . . . . 18<br />
Changed ADMISSIONS_APPLICATION Reporting and Composite Views . . . . . . . . 19<br />
New Baselined Concurrent Curriculum. . . . . . . . . . . . . . . . . . . . . . . . . . 19<br />
Section 2 Miscellaneous Enhancements . . . . . . . . . . . . . . . . . . . . 21<br />
New List of Values Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21<br />
New Self-Service Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21<br />
Changed Data Model ERD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22<br />
Changed Discoverer EUL and Cognos Report Studio. . . . . . . . . . . . . . . . . . 23<br />
Section 3 Documentation Enhancements . . . . . . . . . . . . . . . . . . . 25<br />
New Third Party Reporting Tool Chapter . . . . . . . . . . . . . . . . . . . . . . . . . 25<br />
New List of Values Views to Data Model Chapter . . . . . . . . . . . . . . . . . . . 25<br />
New Appendix A for Report Relationship Diagrams . . . . . . . . . . . . . . . . . . 25<br />
Combined Banner to <strong>ODS</strong> <strong>Guide</strong> with <strong>ODS</strong> Handbook. . . . . . . . . . . . . . . . 25<br />
Removed the Preface from the Handbook . . . . . . . . . . . . . . . . . . . . . . . . 26<br />
Section 4 Problem Resolutions . . . . . . . . . . . . . . . . . . . . . . . . . . 27<br />
Accounts Receivable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27<br />
Administrative User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27<br />
Advancement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29<br />
Common . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30<br />
Finance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33<br />
Financial Aid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
4 <strong>Release</strong> <strong>Guide</strong> Confidential
Table of Contents<br />
Human Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35<br />
Student . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38<br />
General Miscellaneous . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47<br />
Section 5 New, Changed, Removed Database Columns . . . . . . . . 53<br />
Reporting View Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53<br />
Composite Table Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73<br />
April 2007 Operational Data Store <strong>Release</strong> <strong>3.1</strong><br />
Confidential <strong>Release</strong> <strong>Guide</strong> 5
Table of Contents<br />
This page intentionally left blank<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
6 <strong>Release</strong> <strong>Guide</strong> Confidential
Introduction<br />
Introduction<br />
This document describes the functional and technical enhancements, problem<br />
resolutions and objects included in <strong>Release</strong> <strong>3.1</strong> of the Operational Data Store<br />
(<strong>ODS</strong>).<br />
Prerequisites<br />
The following is required for this release:<br />
• <strong>ODS</strong> <strong>Release</strong> 3.0 must be installed before you can upgrade to <strong>ODS</strong> <strong>Release</strong> <strong>3.1</strong>,<br />
or perform a fresh<strong>3.1</strong> install.<br />
• Oracle 9.2.0.6/10.2.0.2<br />
• OWB 10.2.0.2<br />
• (optional install) Self-Service Reporting - Oracle Application Express 2.2.1<br />
At the minimum, the following Banner releases must be installed:<br />
• Advancement - 7.2<br />
• Finance - 7.2<br />
• Accounts Receivable - 7.2<br />
• Financial Aid - 7.3<br />
• General - 7.3<br />
• Human Resources - 7.2<br />
• Position Control- 7.2<br />
• Student - 7.3<br />
April 2007 Operational Data Store <strong>Release</strong> <strong>3.1</strong><br />
Confidential <strong>Release</strong> <strong>Guide</strong> 7
Introduction<br />
This page intentionally left blank<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
8 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 1 Functional Enhancements<br />
Accounts Receivable<br />
Section 1<br />
Functional Enhancements<br />
This section contains a brief description of all enhancements included in this<br />
release, and the associated RPE number. For detailed information, refer to the<br />
“Operational Data Store Handbook” for <strong>Release</strong> <strong>3.1</strong>.<br />
Accounts Receivable<br />
Changed RECEIVABLE_ACCOUNTING Reporting View<br />
1-J36RV<br />
The RECEIVABLE_ACCOUNTING reporting view was modified to list all rule class<br />
codes associated with the A and B accounting distributions on each detail code. The<br />
rule class codes assist in reconciling between Finance and Accounts Receivable in<br />
determining year end journal entries that may be necessary for corrections. The<br />
following columns were added:<br />
A_RULE_CLASS1, A_RULE_CLASS_DESC1<br />
A_RULE_CLASS2, A_RULE_CLASS_DESC2<br />
A_RULE_CLASS3, A_RULE_CLASS_DESC3<br />
B_RULE_CLASS1, B_RULE_CLASS_DESC1<br />
B_RULE_CLASS2, B_RULE_CLASS_DESC2<br />
B_RULE_CLASS3, B_RULE_CLASS_DESC3<br />
Changed Accounts Receivable Views<br />
1-PU2LF<br />
The APPLICATION_OF_PAYMENT reporting view was modified to list detail codes<br />
used as payment and charges and the actual type of detail code it was. The operating<br />
designator was also added. The following fields were added to support the build for<br />
accounting lines in the new reporting view:<br />
• APPL_OF_PAY_DETAIL_ACCOUNTING<br />
• PAY_DETAIL_CODE, PAY_DETAIL_CODE_DESC<br />
• PAY_DETAIL_CODE_TYPE<br />
• PAY_OPERATING_DESIGNATOR<br />
• CHARGE_DETAIL_CODE<br />
• CHARGE_DETAIL_CODE_DESC<br />
April 2007 Operational Data Store <strong>Release</strong> <strong>3.1</strong><br />
Confidential <strong>Release</strong> <strong>Guide</strong> 9
Section 1 Functional Enhancements<br />
Administrative User Interface<br />
• CHARGE_DETAIL_CODE_TYPE<br />
• CHARGE_OPERATING_DESIGNATOR.<br />
The APPL_OF_PAY_DETAIL_ACCOUNTING reporting view was created to list the<br />
default accounting distributions used for payments and default accounting<br />
distributions used for charges that had payments applied against them as well as the<br />
rule class code used in the transaction. Multiple records may exist as the accounting<br />
distributions can be split.<br />
Administrative User Interface<br />
Email Notification Enhancements<br />
Added Information in Notification Email Message<br />
1-1KMHAB<br />
The email messages sent out for job notification now contains more detailed<br />
information about the job as well as details about any errors encountered. For the<br />
Change Table Counter job, any tables with record counts greater than the threshold<br />
are reported.<br />
Changed Default for Email Job Notification<br />
1-1KMHAJ<br />
Job notification via email used to be set up on a "mass" basis. Anyone configured to<br />
be notified received emails for all jobs that ran. The default has been changed so<br />
that users only receive notifications for jobs that they submitted. However, there is<br />
still an option to configure an account to receive messages for all jobs.<br />
Freeze Data Maintenance Enhancements<br />
New Freeze Process Delete<br />
RPE 1-VCTDX<br />
When running a freeze process, you can elect to insert or replace an event, as well<br />
as to delete one.<br />
Changed Freeze Columns<br />
1-R96GF<br />
A subset of columns to freeze can now be selected.<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
10 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 1 Functional Enhancements<br />
Administrative User Interface<br />
Changed Freeze Data List Definitions<br />
1-VCTE3<br />
Freeze list definitions can now be renamed, deleted, and duplicated.<br />
Changed Freeze List Page<br />
1-VDEAR<br />
The following navigational links have been added to the Freeze List definition<br />
screens:<br />
• Links between the Create and Update screens<br />
• A link to display existing freeze list names when creating a new list<br />
• Also the limit on the number of records has been removed<br />
Miscellaneous Administrative UI Enhancements<br />
New Ability to Edit/Clone Submitted Jobs<br />
1-1KMHID<br />
This enhancement allows you to "edit" a job in the queue, by either changing its<br />
values and resubmitting it, or by actually submitting it again as a.<br />
New Select / Deselect Option to Control Report Page<br />
1-VCSSH<br />
Links for "Select All" and "Deselect All" were added to the Filter Report dialog to<br />
make using the dialog easier.<br />
New Termination Wizard<br />
1-XV7P5<br />
Long-running jobs can now be terminated using a Process Termination Wizard<br />
screen that is accessed from the Control Report for a running job. The wizard either<br />
automatically kills the job directly at the operating system level, or generates a list of<br />
Oracle commands that terminate the job manually using Oracle.<br />
New Composite View Meta Data Maintenance<br />
1-XV7PB<br />
Composite view meta data can now be added, edited or deleted using the<br />
Administrative User Interface.<br />
April 2007 Operational Data Store <strong>Release</strong> <strong>3.1</strong><br />
Confidential <strong>Release</strong> <strong>Guide</strong> 11
Section 1 Functional Enhancements<br />
Advancement<br />
New <strong>Release</strong> Numbers Added to Administrative UI<br />
CMS-RPE41920<br />
The release number on all screens/pages within the Administrative UI now display<br />
the current WebTailor module number for the product, both <strong>ODS</strong> and EDW. The<br />
version number of the code module (package) that was previously displayed is also<br />
available within the HTML for the screen itself, as an HTML comment field, at the<br />
bottom of the HTML code.<br />
New Slotted Table Name in Control Report for Single Slot Process<br />
CMS-RPE47440<br />
The name of the slotted table now appears in the process name as it is listed in the<br />
Control Report display for the "Load A Single Slot" process.<br />
Changed Security to Enable/Disable PINs<br />
1-1JNJYP<br />
The Security screens now include a checkbox for enabling/disabling PINs for an<br />
Administrative account. This is useful for accounts that become disabled after<br />
exceeding the maximum number of login attempts.<br />
Advancement<br />
Changed CONSTITUTUENT Reporting View<br />
RPE 1-UHZTF<br />
As part of the overall Self-Service Reporting enhancement, four new columns were<br />
added to the CONSTITUENT reporting view to further facilitate reporting<br />
opportunities. The added columns are:<br />
• CURRENT_AGE<br />
• EMAIL_PREFERRED_ADDRESS<br />
• GENDER<br />
• GENDER_DESC.<br />
Removed Views and Table<br />
17SHMV<br />
Performance of a few Advancement reporting views was improved in defect G31AG.<br />
Therefore, the obsolete work view, MAVCONE, and obsolete composite tables,<br />
MAT_CONSTITUENT and MAT_ORGANIZATIONAL_CONSTITUENT were<br />
removed from baseline code tree and the <strong>ODS</strong> environment.<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
12 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 1 Functional Enhancements<br />
Common<br />
Common<br />
New F_GET_PERSON_INFO function<br />
1-SSIDA<br />
In release 3.0 the MST_PERSON table was joined to a number of reporting views to<br />
retrieve the Name and ID fields so that clients would not be required to join in<br />
MST_PERSON in their reporting tools. In doing so, a performance decrease could<br />
result when joining multiple reporting views together that all have a join to<br />
MST_PERSON.<br />
In release <strong>3.1</strong> the hard joins to MST_PERSON were removed from the reporting<br />
view scripts, and a function called F_GET_PERSON_INFO in the MGKFUNC<br />
package was added in their place to retrieve the Name and ID information. The<br />
result is that the MST_PERSON table is only accessed when trying to retrieve these<br />
two columns from a reporting view instead of being accessed anytime the reporting<br />
view is accessed. This new function can also be used to return a select number of<br />
other columns from the MST_PERSON table.<br />
Changed PREFERRED_ADDRESS Reporting View<br />
1-12ZOQH<br />
The TELEPHONE_PREFERRED reporting view contained one active, primary<br />
telephone for each address in the ADDRESS_PREFERRED reporting view (if an<br />
active, primary telephone exists for that address).<br />
Since the data in TELEPHONE_PREFERRED is, for all intents and purposes, an<br />
attribute of preferred addresses, we have added the telephone related columns from<br />
this reporting view to the ADDRESS_PREFERRED reporting view. Doing so will<br />
simplify reporting by eliminating the need for users to join these views to retrieve<br />
the corresponding telephone information.<br />
In making this change, we have in turn made the TELEPHONE_PREFERRED<br />
reporting view obsolete or redundant, since the same information can now be<br />
retrieved from ADDRESS_PREFERRED, as necessary. Therefore, we have removed<br />
the TELEPHONE_PREFERRED reporting view from the <strong>ODS</strong>.<br />
Changed Relationship Reporting View<br />
1-EKBA1<br />
The Relationship reporting view was enhanced to combine a person’s distinct<br />
spousal or child records with a corresponding cross reference record to the<br />
respective spouse or child, as applicable. This ensures the most accurate<br />
presentation of these relationships by eliminating duplicate or redundant spousal<br />
or child records when both sources exist.<br />
April 2007 Operational Data Store <strong>Release</strong> <strong>3.1</strong><br />
Confidential <strong>Release</strong> <strong>Guide</strong> 13
Section 1 Functional Enhancements<br />
Finance<br />
Also, various column names were changed and meta data business definitions were<br />
rewritten to more accurately describe the data presented. Additional data columns,<br />
including descriptions, entity indicators, household indicator and matching gift<br />
UID were also added to supplement reporting opportunities.<br />
Finance<br />
New Financial Manager and Principal Investigator Names<br />
1-THZI9<br />
The GENERAL_LEDGER reporting view now displays the financial manager in a<br />
last name, first name, middle initial format.<br />
The OPERATING_LEDGER reporting view now displays the financial manager in a<br />
last name, first name, middle initial format.<br />
The BUDGET_AVAILABILITY_LEDGER reporting view now displays the financial<br />
managers for both fund and organization in a last name, first name, middle initial<br />
format.<br />
The BUDGET_DETAIL reporting view now displays the financial managers for both<br />
fund and organization in a last name, first name, middle initial format.<br />
The FIXED_ASSET_ACCOUNTING_SOURCE reporting view now displays the<br />
financial managers for both fund and organization in a last name, first name,<br />
middle initial format.<br />
The FIXED_ASSET_FUNDING_SOURCE reporting view now displays the financial<br />
managers for both fund and organization in a last name, first name, middle initial<br />
format.<br />
The INVOICE_ACCOUNTING reporting view now displays the financial managers<br />
for both fund and organization in a last name, first name, middle initial format. The<br />
financial manager UID and ID were also added.<br />
The PURCHASE_ORDER_ACCOUNTING reporting view now displays the<br />
financial managers for both fund and organization in a last name, first name,<br />
middle initial format. The financial manager UID and ID were also added.<br />
The ENDOWMENT_UNITS reporting view now displays the entity name in a last<br />
name, first name, middle initial format.<br />
The GRANT_VIEW reporting view now displays the principal investigator name in<br />
a last name, first name, middle initial format as well as organization financial<br />
manager name.<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
14 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 1 Functional Enhancements<br />
Financial Aid<br />
The GRANT_FUND reporting view now displays the principal investigator name in<br />
a last name, first name, middle initial format as well as fund financial manager<br />
name.<br />
Changed TRANSACTION_HISTORY Reporting View<br />
1-TC9MJ<br />
The ORGANIZATION_HIERARCHY reporting view was enhanced to display the<br />
financial manager in a last name, first name, middle initial format as<br />
FINANCIAL_MANAGER_NAME.<br />
The TRANSACTION_HISTORY reporting view was enhanced to display the<br />
NORMAL_BALANCE, INTERNAL_ACCOUNT_TYPE, and<br />
INTERNAL_ACCOUNT_TYPE_DESC, and to use them to categorize accounting<br />
transactions for various report templates. ACCOUNT_POOL and<br />
ACCOUNT_POOL_DESC were added to support budget checking.<br />
The INTERNAL_FUND_TYPE and INTERNAL_FUND_TYPE_DESC were also<br />
added in anticipation of being able to report by fund category. Financial manager<br />
information for both the fund and organization was added to give the ability to<br />
report transactions by financial manager. The fields are<br />
FUND_FINANCIAL_MANAGER_UID, FUND_FINANCIAL_MANAGER_ID,<br />
FUND_FINANCIAL_MANAGER_NAME, ORGN_FINANCIAL_MANAGER_UID,<br />
ORGN_FINANCIAL_MANAGER_ID, and<br />
FUND_FINANCIAL_MANAGER_NAME.<br />
FUND_POOL was enhanced to default the FUND_POOL from the<br />
FUND_HIERARCHY if the FUND_POOL was not populated on<br />
TRANSACTION_HISTORY.<br />
GRANT_ID, GRANT_DESC, and GRANT_STATUS were added to assist in grant<br />
reporting.<br />
Financial Aid<br />
New and Changed Indexes<br />
RPE 1-ZRKO8<br />
A number of indexes were added to the Financial Aid MRT composite tables in the<br />
<strong>ODS</strong> to aid in performance of queries off of the reporting views. Also, system<br />
generated index names were replaced with static names in order to track them in<br />
the health check job.<br />
April 2007 Operational Data Store <strong>Release</strong> <strong>3.1</strong><br />
Confidential <strong>Release</strong> <strong>Guide</strong> 15
Section 1 Functional Enhancements<br />
Human Resources<br />
Human Resources<br />
Changed LEAVE_BALANCE View<br />
1-19CLOJ<br />
The LEAVE_BALANCE view was enhanced to include leave information when an<br />
institution elects to track leave by employee position. The LEAVE_BALANCE view<br />
now includes records from the PERJLEV table as well as the PERLEAV table.<br />
Student<br />
New Fourth Minor<br />
1-O6L5F<br />
Fourth minor and description columns were added to composite views<br />
AS_CURRICULUM_FOS and AS_LEARNER_CURRICULUM_FOS, composite<br />
tables MST_ADMISSIONS_APPLICATION, MST_ACADEMIC_OUTCOME,<br />
MST_GENERAL_STUDENT, and MST_RECRUITMENT_INFORMATION, and<br />
reporting views ACADEMIC_OUTCOME, ACADEMIC_STUDY,<br />
ADMISSIONS_APPLICATION, RECRUITMENT_INFORMATION,<br />
GOVERNMENT_ACADEMIC_OUTCOME, and GOVERNMENT_STUDENT.<br />
(EDW clients also see EDW RPE 1-S0SX1).<br />
New Enrollment View<br />
1-ZR2DF<br />
The AS_ENROLLMENT_HISTORY composite view was added to extract<br />
enrollment data for students after their grades have been rolled to history. Since the<br />
Banner process SFPREGS.pc can purge registration data, this enhancement ensures<br />
that historical enrollment data will be extracted and loaded into the Operational<br />
Data Store.<br />
New Enrolled & Registered Indicators<br />
1-ZRKOZ<br />
The system determines Enrolled and Registered students differently for different<br />
areas of administrative processing. A standard procedure has been written to set<br />
each of these indicators to yes or no.<br />
Within the <strong>ODS</strong>, the ENROLLED_IND is set to Y when the student has either<br />
current enrollment details or institutional history for an academic period. Likewise,<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
16 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 1 Functional Enhancements<br />
Student<br />
within the <strong>ODS</strong>, the REGISTERED_IND is set to Y when the student has either<br />
enrolled course or institutional history courses for an academic period.<br />
Changed STUDENT_COURSE Reporting View<br />
1-5KUKD<br />
The STUDENT COURSE reporting view has a START_DATE and END_DATE that<br />
was thought to meet the expectation of tracking the last date of attendance. The<br />
STUDENT COURSE Start Date will first look at the SFRAREG_START_DATE and if<br />
no value then it will use the SSBSECT_START_DATE. The data for the End Date will<br />
now look at the SFRSTCR_LAST_DATE_ATTENDED first and then the<br />
SFRAREG_COMPLETION_DATE and if no value then the currently used<br />
SSBSECT_END_DATE. Remember the STUDENT COURSE Start Date and End<br />
Date is for the student in this course. If you need to report on the SCHEDULE<br />
OFFERING Start and End Date, you should use that reporting view.<br />
In addition to the change in how the START_DATE and END_DATE are populated,<br />
the LAST_ATTEND_DATE from SFRSTCR_LAST_DATE_ATTENDED was added<br />
as a new column on the STUDENT_COURSE reporting view.<br />
Changed Academic Standing<br />
1-MJSHZ<br />
The following academic standing columns were removed from composite view<br />
AS_GENERAL_STUDENT and table MST_GENERAL_STUDENT because all<br />
academic standing columns are now in MST_ACADEMIC_STANDING:<br />
ACAD_STANDING_ACAD_PERIOD_DESC<br />
ACADEMIC_STANDING<br />
ACADEMIC_STANDING_ACAD_PERIOD<br />
ACADEMIC_STANDING_DESC<br />
COMB_ACAD_STANDING_TERM_DESC<br />
COMBINED_ACAD_STANDING_DESC<br />
COMBINED_ACAD_STANDING_TERM<br />
COMBINED_ACADEMIC_STANDING<br />
PROGRESS_EVALUATION<br />
PROGRESS_EVALUATION_DESC<br />
The following columns were moved from composite view<br />
AS_ACADEMIC_STANDING and table MST_ACADEMIC_STANDING to<br />
composite view AS_ENROLLMENT and table MST_ENROLLMENT, since<br />
MST_ENROLLMENT will now contain history enrollment data:<br />
DEANS_LIST_DATE<br />
DEANS_LIST_DESC<br />
DEANS_LIST_VALUE<br />
ENROLLMENT_EXISTS_IND<br />
GRADE_MAILER_CHG_DATE<br />
GRADE_MAILER_DUP<br />
April 2007 Operational Data Store <strong>Release</strong> <strong>3.1</strong><br />
Confidential <strong>Release</strong> <strong>Guide</strong> 17
Section 1 Functional Enhancements<br />
Student<br />
GRADE_MAILER_DUP_DATE<br />
GRADE_MAILING_DATE<br />
PRE_CATALOG_IND<br />
RECORD_SOURCE_IND<br />
RECORD_STATUS_DATE<br />
RECORD_STATUS_IND<br />
SPECIAL_EXAM_CREDIT<br />
SPECIAL_EXAM_DESC<br />
TRANSFER_TO_INSTITUTION<br />
TRANSFER_TO_INSTITUTION_DESC<br />
WITHDRAWAL_REASON<br />
WITHDRAWAL_REASON_DESC<br />
The following columns were added to composite view AS_ACADEMIC_STANDING<br />
and table MST_ACADEMIC_STANDING:<br />
STUDENT_LEVEL<br />
STUDENT_LEVEL_DESC<br />
ACADEMIC_STAND_OVERRIDE<br />
ACADEMIC_STAND_OVERRIDE_DESC<br />
ACADEMIC_STANDING<br />
ACADEMIC_STANDING_DESC<br />
ACADEMIC_STANDING_DATE<br />
PROGRESS_EVAL_OVERRIDE<br />
PROGRESS_EVAL_OVERRIDE_DESC<br />
PROGRESS_EVALUATION_END<br />
PROGRESS_EVALUATION_END_DESC<br />
PROGRESS_EVALUATION_END_DATE<br />
COMB_ACAD_STAND_OVERRIDE<br />
COMB_ACAD_STAND_OVERRIDE_DESC<br />
COMBINED_ACAD_STAND_END<br />
COMBINED_ACAD_STAND_END_DESC<br />
COMBINED_ACAD_STAND_END_DATE<br />
The AS_ACADEMIC_STANDING composite view was rewritten to extract overrides,<br />
beginning of academic period, and ends of academic period values for academic<br />
standing, progress evaluation, and combined academic standing.<br />
Changed STUDENT_COURSE_ATTRIBUTE Reporting View<br />
1-OBZY9<br />
The course reference number column was added to the reporting views<br />
STUDENT_COURSE_GRADE_CHANGE, STUDENT_COURSE_ATTRIBUTE,<br />
and STUDENT_COURSE_ATT_SLOT.<br />
Transfer courses were given a unique course reference number by combining the<br />
transfer institution, attendance period, course, and institutional equivalency<br />
sequence numbers.<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
18 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 1 Functional Enhancements<br />
New Baselined Concurrent Curriculum<br />
The STUDENT_COURSE_ATTRIBUTE reporting view was modified to report on<br />
all attributes assigned to the student first. If none exist, then the attributes assigned<br />
at the section level are reported.<br />
Changed ADMISSIONS_APPLICATION Reporting and Composite<br />
Views<br />
CMS-RPE47387<br />
The AS_ADMISSIONS_APPLICATION composite view was altered to map the<br />
SABSUPL columns SABSUPL_INST_DATA1 through SABSUPL_INST_DATA5 to<br />
bring that data into the <strong>ODS</strong> MST_ADMISSIONS_APPLICATION. Now the<br />
reporting view ADMISSIONS_APPLICATION will have these columns populated<br />
when data is available.<br />
New Baselined Concurrent Curriculum<br />
1-11HW59<br />
The <strong>ODS</strong> <strong>3.1</strong> release requires Banner release 7.3 at the minimum. This requires that<br />
Concurrent Curriculum, optionally provided with <strong>ODS</strong> 3.0, be baselined in the<br />
source directories and that the upgrade and install scripts for the <strong>3.1</strong> release are<br />
updated accordingly.<br />
All Concurrent Curriculum scripts and objects from <strong>ODS</strong> 3.0 were baselined for <strong>3.1</strong>.<br />
Objects include:<br />
• MST_CURR_ADMISSIONS_APPL MST_CURRICULUM_FOS<br />
• MST_CURR_ACADEMIC_OUTCOME MST_CURR_RECRUITMENT_INFO<br />
MST_CURR_STUDENT<br />
• MST_CURRICULUM<br />
• MST_FIELD_OF_STUDY<br />
• MST_STUDENT_TERM_STAGE<br />
• FIELD_OF_STUDY<br />
• LOAD_MST_CURRICULUM_BATCH : Combines load of:<br />
• MST_ACADEMIC_OUTCOME<br />
• MST_ADMISSIONS_APPLICATION<br />
• MST_GENERAL_STUDENT<br />
• MST_RECRUITMENT_INFORMATION<br />
April 2007 Operational Data Store <strong>Release</strong> <strong>3.1</strong><br />
Confidential <strong>Release</strong> <strong>Guide</strong> 19
Section 1 Functional Enhancements<br />
New Baselined Concurrent Curriculum<br />
This page intentionally left blank<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
20 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 2 Miscellaneous Enhancements<br />
New List of Values Views<br />
Section 2<br />
Miscellaneous Enhancements<br />
New List of Values Views<br />
RPE 1-1CFEYR<br />
The <strong>ODS</strong> has a database schema called <strong>ODS</strong>LOV that owns the list of value views.<br />
Most, but not all, of the views are based on the MGT_VALIDATION composite table.<br />
(At least one view is based on an MGRSDAX rule.) MGT_VALIDATION is loaded<br />
using Oracle Warehouse Builder (OWB) from validation tables (or in some cases<br />
static lists of values) in Banner. Validation tables loaded into MGT_VALIDATION<br />
from Banner have been identified as lists of values that have views assigned to them.<br />
(Not all the MGT_VALIDATION validation tables have been created as LOV views.)<br />
Each view has the columns TABLE_NAME, VALUE, and VALUE_DESC.<br />
TABLE_NAME is the name of the Banner validation table. VALUE and<br />
VALUE_DESC are values, or codes, and descriptions for the values. Some of the<br />
views also have QUALIFIER, and QUALIFIER_DESC. QUALIFIER is used to group<br />
values by a common attribute. For example, it can be Chart of Accounts, Academic<br />
Period or a Banner PIDM. QUALIFIER_DESC is a description for the QUALIFIER.<br />
Qualifier description is only populated when the qualifier is an Academic Period.<br />
The Cognos ReportNet model and Oracle Discoverer End User Layer have been<br />
updated to reference the list of value views for parameters and conditions. Self-<br />
Service Reporting also uses the list of value views for search criteria.<br />
New Self-Service Reporting<br />
RPE 1-UHZTF<br />
The Self-Service Reporting (SSR) enhancement provides simple, ad hoc access to<br />
information within the <strong>ODS</strong>.<br />
SSR is delivered with report templates that provide examples of various common<br />
data retrieval needs across your institution. Each report template is based on the<br />
functional data relationships set forth in the Business Concept Diagrams found in<br />
the <strong>ODS</strong> published meta data. The template design for SSR uses a Filter - List - Detail<br />
approach. This approach includes a Search Criteria page where you select the<br />
various filters to execute a query, a List page that displays the results of that query,<br />
and a Detail Reports page where you access additional information specific to any<br />
individual result on the List page.<br />
The information on the List and Detail Reports pages can be viewed online or<br />
exported to a CSV file (Microsoft Excel format) or XML file for printing or<br />
additional manipulation. For some templates, you can also save the unique primary<br />
April 2007 Operational Data Store <strong>Release</strong> <strong>3.1</strong><br />
Confidential <strong>Release</strong> <strong>Guide</strong> 21
Section 2 Miscellaneous Enhancements<br />
Changed Data Model ERD<br />
identifier(s) for your List page results to the <strong>ODS</strong> for use in custom reports<br />
developed with your reporting tool. The Email icon enables you to send email to<br />
everyone on the List page. If you select an individual address from the List page, you<br />
can send email to that individual.<br />
Changed Data Model ERD<br />
RPE 1-NZE5T<br />
Data Model (Entity Relationship Diagram - ERD) changes reflect newly identified<br />
and new logical relationships between views in the <strong>ODS</strong> database for <strong>ODS</strong> <strong>Release</strong><br />
<strong>3.1</strong>. Those changes are reflected in the Cognos Report Studio model and the Oracle<br />
Discoverer End User Layer to correctly join new views in the reporting tools and to<br />
reflect the new business concepts.<br />
1. There is a new Oracle Discoverer End User Layer written for <strong>ODS</strong> <strong>3.1</strong>. Please<br />
refer to RPE 1-PDHUL for details regarding the new EUL.<br />
2. The Operating Ledger data model was enhanced to add a GRANT_VIEW<br />
relationship to the OPERATION_LEDGER reporting view using GRANT_ID<br />
similar to the way it was done in the GENERAL_LEDGER data model. The<br />
index order was corrected on the OPERATING_LEDGER reporting view by<br />
moving the ORGANIZATION_CODE after Fund. Additionally information<br />
was added to assist in identifying a source financial transaction for the<br />
TRANSACTION_HISTORY reporting view.<br />
3. The Advancement Prospect data model was enhanced to modify the key/<br />
frequency for the CONSTITUENT_PLAN reporting view as follows: Multiple<br />
rows per PERSON_UID per Project per Move or UNPLANNED_MOVE. The<br />
cardinality/relationship from PROSPECT_INFO reporting view to the<br />
CONSTITUENT_PLAN reporting view is now one to zero or many.<br />
4. The Constituent business view within the Cognos Report Studio model was<br />
enhanced by correcting the relationship between CONSTITUENT and<br />
CONSTITUENT_PLAN. Now the relationship is between PROSPECT_INFO<br />
and CONSTITUENT_PLAN.<br />
5. The Receivable Account data model was renamed to Receivable Revenue and<br />
was enhanced to add the new reporting view<br />
APPL_OF_PAY_DETAIL_ACCOUNTING. The cardinality/relationship<br />
between RECEIVABLE_ACCOUNT and<br />
APPL_OF_PAY_DETAIL_ACCOUNTING is 1 to many.<br />
6. A new Receivable Customer data model was added to allow reporting from a<br />
student or organization perspective.<br />
7. The TELEPHONE_PREFERRED reporting view was removed from all data<br />
models.<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
22 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 2 Miscellaneous Enhancements<br />
Changed Discoverer EUL and Cognos Report Studio<br />
8. A Constituent Entity data model was added to allow reporting on both<br />
constituents and organization constituents together.<br />
9. The Employee data model was enhanced by adding the<br />
ORGANIZATION_HIERARCHY reporting view joining to both EMPLOYEE<br />
and EMPLOYEE_POSITION reporting views.<br />
10. The Employee business view within the Cognos Report Studio model was<br />
enhanced by adding the ORGANIZATION_HIERARCHY with a joining<br />
relationship to EMPLOYEE using the HOME_ORGANIZATION_CHART and<br />
HOME_ORGANIZATION.<br />
11. The Position data model was enhanced to by adding the<br />
ORGANIZATION_HIERARCHY reporting view joining to both EMPLOYEE<br />
and EMPLOYEE_POSITION reporting views.<br />
12. The Position business view within the Cognos Report Studio model was<br />
enhanced by adding the ORGANIZATION_HIERARCHY with a joining<br />
relationship to EMPLOYEE_POSITION using the<br />
TIMESHEET_CHART_OF_ACCOUNTS and<br />
TIMESHEET_ORGANIZATION.<br />
13. The Endowment Distribution, Fixed Asset, Grant Ledger, Grant and Project,<br />
Purchasing Payable, Invoice Payable, Grant and Project, and Transaction<br />
History data models were enhanced by adding information to assist in<br />
identifying a source financial transaction for the TRANSACTION_HISTORY<br />
reporting view.<br />
14. Filters on TRANSACTION_HISTORY were added using LEDGER_IND and<br />
DOCUMENT_TYPE.<br />
15. The General Ledger data model was enhanced by adding the GRANT_VIEW<br />
reporting view and by adding information to assist in identifying a source<br />
financial transaction for the TRANSACTION_HISTORY reporting view.<br />
16. The Residential Life data model was enhanced to add the ACADEMIC_STUDY<br />
reporting view.<br />
17. Supervisor model query subject was added to Cognos Report Studio.<br />
Constituent Spouse custom folder was added to Oracle Discoverer.<br />
Changed Discoverer EUL and Cognos Report Studio<br />
1-PDHUL<br />
The Discoverer End User Layer (EUL) for <strong>ODS</strong> <strong>3.1</strong> was enhanced by adding 51 new<br />
functional business areas. The business areas are based upon the Business Concept<br />
ERDs. These now reflect the same relationships as the Cognos Report Studio<br />
business views.<br />
April 2007 Operational Data Store <strong>Release</strong> <strong>3.1</strong><br />
Confidential <strong>Release</strong> <strong>Guide</strong> 23
Section 2 Miscellaneous Enhancements<br />
Changed Discoverer EUL and Cognos Report Studio<br />
The default date hierarchies were removed due to performance issues and replaced<br />
with new date hierarchy folders for each different date identified that we want to<br />
break down by year, month and day.<br />
All underscores from the folder names in the EUL were removed to make them<br />
more like business names and to allow for column header wrapping capabilities.<br />
However, the underscore was kept in the UID names because UID is an Oracle<br />
keyword.<br />
All item names were replaced with the column business names from the meta data<br />
repository. This was to make the names more like the English language.<br />
Additionally, all true number items were identified as data point numbers and<br />
changed to aggregate as sums or averages. This was to ensure that the number items<br />
were aggregated the same way assuring you that numbers are accurate by not mixing<br />
details with sums. Consequently, all ID fields were redefined as non-data point items<br />
to make sure that joins between two folders would work correctly.<br />
Due to major changes that have been made to the <strong>ODS</strong> <strong>3.1</strong> EUL, clients will have to<br />
continue to use the existing <strong>ODS</strong> 3.0 EUL for workbooks that have already been<br />
written. The only enhancements to the <strong>ODS</strong> 3.0 EUL are those necessary to stay<br />
synchronized with the <strong>ODS</strong> <strong>3.1</strong> reporting views. In order for clients to take<br />
advantage of the new <strong>ODS</strong> <strong>3.1</strong> EUL features, they will have to write their workbooks<br />
against the new EUL.<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
24 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 3 Documentation Enhancements<br />
New Third Party Reporting Tool Chapter<br />
Section 3<br />
Documentation Enhancements<br />
All enhancements in the current release are documented in either the Banner to<br />
<strong>ODS</strong> User <strong>Guide</strong> or the Operational Data Store Handbook. Documentation-specific<br />
changes are described below:<br />
New Third Party Reporting Tool Chapter<br />
All reporting tool documentation has been combined into the Third Party<br />
Reporting Tools chapter, Chapter 3.<br />
Report Relationship Diagrams were added to Appendix A. The diagrams are<br />
arranged by subject area.<br />
New List of Values Views to Data Model Chapter<br />
The list of value views in the <strong>ODS</strong>LOV schema were added to the Data Model<br />
chapter of the <strong>ODS</strong> Handbook.<br />
New Appendix A for Report Relationship Diagrams<br />
The relationships in the reporting meta data for Cognos ReportNet and Oracle<br />
Discoverer are the same. The relationship diagrams in Appendix A show the<br />
relationships between <strong>ODS</strong> reporting views that are used to generate Structured<br />
Query Language (SQL) which, in turn, are used in reports. There is one diagram<br />
for each business concept. The diagrams are grouped by subject areas such as<br />
Accounts Receivable, Advancement, etc.<br />
Combined Banner to <strong>ODS</strong> <strong>Guide</strong> with <strong>ODS</strong> Handbook<br />
The information in the Banner to <strong>ODS</strong> User <strong>Guide</strong> is now its own chapter in the<br />
<strong>ODS</strong> Handbook. The chapter is called “Banner to the <strong>ODS</strong>.” The books were<br />
combined because, currently, Banner is the only source for the <strong>ODS</strong>.<br />
April 2007 Operational Data Store <strong>Release</strong> <strong>3.1</strong><br />
Confidential <strong>Release</strong> <strong>Guide</strong> 25
Section 3 Documentation Enhancements<br />
Removed the Preface from the Handbook<br />
Removed the Preface from the Handbook<br />
The Preface chapter from the <strong>ODS</strong> Handbook was removed. The information was<br />
combined with the Overview chapter.<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
26 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 4 Problem Resolutions<br />
Accounts Receivable<br />
Section 4<br />
Problem Resolutions<br />
This section contains the impact and resolution for all defects included in this<br />
release. Defects and their resolutions can also be accessed through the Customer<br />
Support Center.<br />
Accounts Receivable<br />
1-1D02G9<br />
Impact<br />
The AN_PAYROLL_DISTRIBUTION composite view on the Banner side errors if<br />
Banner Finance is not installed. There is a call to a Banner Finance delivered<br />
function that errors because the function has not been installed on the Banner side.<br />
Resolution<br />
The call to build dynamic sql from the TOK<strong>ODS</strong>F package was removed into the<br />
GOK<strong>ODS</strong>F package so that it can be used by all product scripts. Also added the<br />
F_GET_FINANCE_DESC and F_GET_FINANCE_STATUS functions into<br />
FOK<strong>ODS</strong>F. There were some tables missing that retrieve descriptions and statuses<br />
for the <strong>ODS</strong>.<br />
1-THYQI<br />
Impact<br />
If neither the Name nor Address were entered into Banner 4x through 6x, the<br />
TBBMISC record was not created by the TFA/TSAMISC forms. Thus, an outer join<br />
is needed between the two records to accommodate old Banner data. Otherwise all<br />
miscellaneous charges will not be pulled into the<br />
AT_MISCELLANEOUS_TRANSACTION view.<br />
Resolution<br />
An outer join was added to TBBMISC_RECEIPT_NUMBER so that if there was no<br />
corresponding record in TBBMISC, the TBRMISD record would still be returned.<br />
Administrative User Interface<br />
1-13CPZA<br />
Impact<br />
Because a comma was being used to delimit the parameter stream for a Job, if a<br />
WHERE clause for a Single Freeze table job contained a comma-delimited list (like<br />
using the IN operator for example), the parameter string was not interpreted<br />
April 2007 Operational Data Store <strong>Release</strong> <strong>3.1</strong><br />
Confidential <strong>Release</strong> <strong>Guide</strong> 27
Section 4 Problem Resolutions<br />
Administrative User Interface<br />
correctly. Hence, the resulting usage of the WHERE clause could wind up with<br />
incorrect or invalid SQL.<br />
Note: This only impacted users of the Freeze Single table function. The Freeze<br />
Multiple tables function uses different logic entirely and was NOT<br />
impacted by this particular defect.<br />
Resolution<br />
The method of delimiting data in parameter lists for JOB streams was changed to<br />
account for commas being used inside parameter values.<br />
1-191CCV<br />
Impact<br />
When the Health Check job is run, row count warnings are reported for meta data,<br />
as well as warnings that indexes are missing.<br />
Resolution<br />
Corrected the reported meta data numbers in MGK<strong>ODS</strong>U. Obsolete system<br />
generated indexes were removed from MGBINDX.<br />
1-1ABGHL<br />
Impact<br />
The Javascript code behind the Delete button had a bug in it, limiting the number<br />
of control reports that could be selected.<br />
Resolution<br />
The technique used to identify records to be deleted was changed.<br />
1-1EJL1X<br />
Impact<br />
The ability to only assign the WebTailor role of 'Information Access Meta Data'<br />
would not work. Users get an error when logging in.<br />
Resolution<br />
Missing rows were added for the bmenu.P_MainMenu to the TWGRMENU table.<br />
1-10XGUN<br />
Impact<br />
If using combinatorial "OR" logic in a WHERE clause with a Freeze Table definition,<br />
not wrapping the condition(s) with parenthesis can cause unexpected results.<br />
Resolution<br />
Supplied WHERE clause conditions in Freeze Table definitions are now wrapped<br />
automatically with parentheses when the WHERE clause combined with the<br />
automatic EVENT conditions when processing a Freeze.<br />
1-N7FXD<br />
Impact<br />
If more than one DB link exists in the <strong>ODS</strong> instance with a naming like<br />
'%SOURCE_DB%', this error would occur, causing the Health Check job to abort.<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
28 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 4 Problem Resolutions<br />
Advancement<br />
Resolution<br />
The MGK<strong>ODS</strong>U package has been updated to issue an explicit error message if<br />
multiple DB links with that name are detected.<br />
1-NFT81<br />
Impact<br />
The WebTailor menu items for the Administrative User Interface overlap the<br />
Banner image and are difficult to read.<br />
Resolution<br />
New cascading style sheets were added for WEB_DEFAULTMENU.CSS,<br />
WEB_DEFAULTAPP.CSS, WEB_DEFAULTHELP.CSS, and<br />
WEB_DEFAULTHOME.CSS.<br />
1-OSHSJ<br />
Impact<br />
The loading of MTVPARM, MGRSDAX and MGRUSER fail during the install of the<br />
EDW and <strong>ODS</strong> due to unique key violations on the sequence number in these tables.<br />
Resolution<br />
Running the script associated with this defect resets the sequence numbers to match<br />
the number of records in the tables and, therefore, resynchronize the tables and<br />
sequences.<br />
1-P5UFV<br />
Impact<br />
The following error "mgkfgac.P_listelemFGA ORA-01031: insufficient privileges"<br />
displays when you click on "Set Up Security Rule" in Administration UI after an<br />
<strong>ODS</strong> 3.0 New Install.<br />
Resolution<br />
The missing CONTEXT is created with the mgkfgac package specification. Recreate<br />
the mgkfgac package.<br />
1-PSOIY<br />
Impact<br />
In the control report for jobs submitted, the work "successfully" is incorrect spelled<br />
as "succesfully". The word successfully was misspelled on the Administrative<br />
interface control report.<br />
Resolution<br />
Corrected misspelling from 'successfully' to 'successfully' to print on the control<br />
report.<br />
Advancement<br />
1-16XK0A<br />
Impact<br />
The table, MAT_GIFT, was not being updated because the wrong change table was<br />
April 2007 Operational Data Store <strong>Release</strong> <strong>3.1</strong><br />
Confidential <strong>Release</strong> <strong>Guide</strong> 29
Section 4 Problem Resolutions<br />
Common<br />
being used. The change table was changed from AGRMCHG to the correct one,<br />
AGRGCHG.<br />
Resolution<br />
The triggers on AGBMGID and AGRMGIF were using the wrong change table,<br />
AGRMCHG. The triggers were changed to use AGRGCHG instead.<br />
1-J60RF<br />
Impact<br />
The SPOUSE_IND in CONSTITUENT was not correctly being calculated. It needs<br />
to check for the cross reference records in MAT_RELATION (instead of the spouse<br />
records), and then also check that the MAT_RELATION.SPPOUSE_IND = Y.<br />
Resolution<br />
Create a new function which checks for an active spouse from MAT_RELATION and<br />
checks for a xref_code = X.<br />
This defect was corrected prior to the <strong>ODS</strong> <strong>3.1</strong> release. This fix was replaced because<br />
additional changes were made for the Relationship reporting view(RPE 1-EKBA1).<br />
1-IYIUV<br />
Impact<br />
The wrong session was being selected when there were more than one SESSION_ID<br />
for a USER_ID for a given day.<br />
Resolution<br />
The TRUNC on the parameter date was removed. The AGBCSHR_START_DATE<br />
and AGBCSHR_END_DATE were removed so that the correct session is selected.<br />
Common<br />
1-1GE4PX<br />
Impact<br />
The Communications process is currently designed to refresh based on the PIDM<br />
since the only database required fields are PIDM, System Code, and Activity Date.<br />
This means that every time a letter is processed (either update, insert or delete), all<br />
records for that PIDM are deleted and then all remaining records are re-inserted.<br />
Obviously, any school that fully utilizes Banner's letter process is going to have a lot<br />
of entries per person. So if an individual has, over the course of two years, 20<br />
GURMAIL entries (even if they are from different systems like Advancement and<br />
Admissions), every time a new letter is added, all 20 letters are reprocessed. This<br />
creates a tremendous amount of unnecessary overhead for processing.<br />
Given the fact that a school may have thousands of students receiving mass mailings<br />
on a regular basis, you can see where the performance issues could start to creep in<br />
over time.<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
30 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 4 Problem Resolutions<br />
Common<br />
Resolution<br />
A new change table was created to process GURMAIL changes (GURMCHG) - it's<br />
keys are GURMAIL_PIDM, GURMAIL_ACTIVITY_DATE. Modified the DELETE<br />
and UPDATE mappings to use the new change table and associated keys.<br />
1-HEGFJ<br />
Impact<br />
Column naming was inconsistent in the following<br />
GOVERNEMENT_ACADEMIC_OUTCOME, GOVERNMENT_ADMISSIONS,<br />
GOVERNEMENT_FINANCIAL_AID, GOVERNMENT_STUDENT, PERSON,<br />
PERSON_DETAIL, PERSON_SENSITVE reporting views for the following columns<br />
names PRIMARY_ETHNICITY, PRIMARY_ETHNICITY_DESC,<br />
PRIMARY_ETHNICITY_CATEGORY and<br />
PRIMARY_ETHNICITY_CATEGORY_DESC.<br />
It was perceived as misspelled because the abbreviation in the initial reporting view<br />
was not consistently applied when these columns appear in a reporting view. This<br />
inconsistency was corrected.<br />
Resolution<br />
Consistent column naming was applied to the following reporting views:<br />
• GOVERNMENT_ACADEMIC_OUTCOME, GOVERNMENT_ADMISSIONS<br />
• OVERNMENT_FINANCIAL_AID<br />
• GOVERNMENT_STUDENT,<br />
• PERSON, PERSON_DETAIL<br />
• PERSON_SENSITIVE<br />
The column names are now:<br />
• PRIMARY_ETHNICITY, PRIMARY_ETHNICITY_DESC<br />
• PRIM_ETHNICITY_CATEGORY<br />
• PRIM_ETHNICITY_CATEGORY_DESC<br />
1-HEIHH<br />
Impact<br />
Any code that had an apostrophe or any non-numeric, alphabetic symbol in it<br />
would error out on the loading of that data into the <strong>ODS</strong>. This was due to the<br />
F_GET_DESC function in GOK<strong>ODS</strong>F.<br />
Resolution<br />
Added INCOMING_PARM_VALUE_REPLACE variable to replace<br />
INCOMING_PARAMETER_VALUE so that codes with apostrophes, etc. can be<br />
used. Used the REPLACE function to allow for these types of symbols.<br />
1-OCJVG<br />
Impact<br />
The meta data for ORGANIZATION_ENTITY.TAX_ID was updated from NA to the<br />
proper source of SPBPERS_SSN.<br />
April 2007 Operational Data Store <strong>Release</strong> <strong>3.1</strong><br />
Confidential <strong>Release</strong> <strong>Guide</strong> 31
Section 4 Problem Resolutions<br />
Common<br />
Resolution<br />
The source name, SPBPERS_SSN was added to the meta data for<br />
ORGANIZATION_ENTITY.TAX_ID.<br />
1-ONW6V<br />
Impact<br />
The public synonym and grant were commented out and were not being created in<br />
the last upgrade. These have been uncommented out.<br />
Resolution<br />
The public synonym and grant were uncommented out.<br />
1-P5V9I<br />
Impact<br />
NATION_OF_BIRTH was used to populate NATION_OF_CITIZENSHIP. This was<br />
changed to use NATION_OF_CITIZENSHIP to populate<br />
NATION_OF_CITZENSHIP.<br />
Resolution<br />
NATION_OF_BIRTH was replaced with NATION_OF_CITIZENSHIP and<br />
NATION_OF_BIRTH_DESC with NATION_OF_CITZENSHIP_DESC.<br />
1-Y6B7U<br />
Impact<br />
Data was incorrectly brought into the MST_PREVIOUS_EDUCATION_SLOT <strong>ODS</strong><br />
composite table due to an error in the package MSKPRED.<br />
MSKPRED was incorrectly updating the SS_GRAD_DATE in<br />
MST_PREVIOUS_EDUCATION composite table so when the data was moved into<br />
MST_PREVIOUS_EDUCATION_SLOT, the data was not correctly being stored.<br />
Resolution<br />
The package, MSKPRED, was corrected and is now updating the SS_GRAD_DATE<br />
properly in both MST_PREVIOUS_EDUCATION and<br />
MST_PREVIOUS_EDUCATION_SLOT. In all the slotted packages, it was necessary<br />
to add an NVL check on the LAST_DML_DATE to ensure it is updating properly.<br />
1-YLPB7<br />
Impact<br />
On the PREVIOUS_EDUCATION and PREVIOUS_EDUCATION_SLOT reporting<br />
views the column TOTAL_TRANSFER_CREDITS (which is a sum of the<br />
SHRTRCE_CREDIT_HOURS), is not taking into account the source<br />
SHRTRCE_COUNT_IN_GPA_IND. This source column is the field which indicates<br />
whether these transfer credits are 'accepted' credits and adds the credits to the GPA<br />
calculations in Banner. So, only the transfer credits that are transferred to count in<br />
GPA should be added to the TOTAL_TRANSFER_CREDITS on the<br />
PREVIOUS_EDUCATION and PREVIOUS_EDUCATION_SLOT reporting views.<br />
While testing the resolution for this defect, it was uncovered that some data is not<br />
being considered in the extract of data to load into the <strong>ODS</strong><br />
MGT_PREVIOUS_EDUCATION composite table. Data is being driven by entries on<br />
the Banner SORPCOL table, but depending on the procedures of the institution,<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
32 <strong>Release</strong> <strong>Guide</strong> Confidential
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
Section 4 Problem Resolutions<br />
Finance<br />
number of records because of the way it is handling the ORDER BY clause with the<br />
PRIOR statement. This was removed and an order by on the _PRED column was<br />
used instead of the PRIOR FTVATYP_ATYP_CODE for<br />
AF_ACCOUNT_HIERARCHY and PRIOR FTVFTYP_FTYP_CODE for<br />
AF_FUND_HIERARCHY.<br />
1-H6QST<br />
Impact<br />
The function to calculate TOTAL_APPROVED_ITEM_AMOUNT was causing '0'<br />
values to be returned in the composite view AF_PURCHASE_ORDER. The<br />
TOTAL_APPROVED_ITEM_AMOUNT was 0 when it should have had a value<br />
greater than 0.<br />
Resolution<br />
Fixed 0 amounts by putting NVL around each amount field and then doing the<br />
operation and summation.<br />
1-NNWZA<br />
Impact<br />
When Finance is partitioned, it results in a mapping error when scheduled in the<br />
Administrative UI: Error Purging Change Table - no DELETE mapping found for:<br />
LOAD_MFT_TRANS_HISTORY_1_PART.<br />
All five partitions fail with a similar error. The same holds true for the payroll<br />
distribution partition exchange mappings.<br />
Resolution<br />
The script to install the partition exchange option for transaction history and<br />
payroll history were modified to add the records to TMTVPARM. This creates<br />
records in MTVPARM so that the mapping knows which change table to purge prior<br />
to loading these tables.<br />
1-R3A4F<br />
Impact<br />
The data from Banner is incorrectly mapped in the LOAD_MST_INSTITIUTION<br />
process so the columns from the composite view are not being loaded into the<br />
correct <strong>ODS</strong> composite table columns for MST_INSTITUTION. Therefore, the<br />
data is not being retrieved correctly when using the INSTITUTION reporting view.<br />
Also some the columns are being populated with a NULL and they should be<br />
retrieving data from Banner database table SORBCNT.<br />
Resolution<br />
Fixed the mapping LOAD_MST_INSTITUTION so source columns are correctly<br />
mapped to target columns.<br />
1-Y010Q<br />
Impact<br />
An intermediate view was used to create ENDOWMENT_ATTRIBUTES. This is not<br />
necessary.<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
34 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 4 Problem Resolutions<br />
Financial Aid<br />
Resolution<br />
The SELECT statement was changed to select from<br />
MFT_ENDOWMENT_ATTRIBUTES instead of ENDW_ATTRIBUTES.<br />
Financial Aid<br />
1-1430KN<br />
Impact<br />
The 16 Disbursement amounts used for Government reporting are being calculated<br />
incorrectly. They are not on the correct data model which causes the numbers to be<br />
incorrect when reporting from the Government reporting view<br />
GOVERNMENT_FA_FUND.<br />
Resolution<br />
The 16 disbursement amount fields were removed from the<br />
AWARD_DISBURSEMENT model to the FINAID_FUND data model. Then,<br />
modified the reporting views to go against the new <strong>ODS</strong> tables where these columns<br />
now reside.<br />
Human Resources<br />
1-11OADR<br />
Impact<br />
NOK<strong>ODS</strong>F.F_GET_SUPERVISOR does not pick up the most recent PIDM.<br />
Resolution<br />
The function, NOK<strong>ODS</strong>F.F_GET_SUPERVISOR needed an ORDER BY<br />
NBRJOBS_EFFECTIVE_DATE added to the queries in order to obtain the latest job<br />
record.<br />
1-1352AL<br />
Impact<br />
The AP_PAST_EMPLOYMENT uses information from the<br />
PPREXPE_SUPER_COMMENT field. The database field definition has changed<br />
from a LONG to a CLOB. This data is "processed" by the<br />
GOK<strong>ODS</strong>.F_TRIM_LONGS function in the AP_PAST_EMPLOYMENT view. Since<br />
the column is now a CLOB, the trim doesn't work correctly and causes the LOAD to<br />
fail with an error.<br />
Resolution<br />
The F_TRIM_LONGS function was removed and replaced with an Oracle function<br />
to convert CLOB fields to VARCHAR.<br />
April 2007 Operational Data Store <strong>Release</strong> <strong>3.1</strong><br />
Confidential <strong>Release</strong> <strong>Guide</strong> 35
Section 4 Problem Resolutions<br />
Human Resources<br />
1-1430LW<br />
Impact<br />
When calculating deduction amounts, the current process obtains amounts from<br />
the PDRDEDN table. There are certain deductions that need to be retrieved from<br />
the PTRBDPL table as well which were missed in the design of benefit deductions.<br />
Resolution<br />
The existing function to get the deduction amounts was going against the<br />
PDRDEDN table. There are cases where the deduction amounts should be retrieved<br />
from the PTRBDPL table. This logic was added to POK<strong>ODS</strong>F in order to properly<br />
account for all deductions for the columns in the BENEFIT_DEDUCTION<br />
reporting view.<br />
1-1DLLIA<br />
Impact<br />
The <strong>ODS</strong> table MPT_EMPL_EARN_CY is keyed upon PERSON_UID,<br />
CALENDAR_YEAR, EMPLOYER, POSITION, SUFFIX, EARNINGS, MONTH. So, a<br />
PERJTOT change does trigger an update for any row based on that key. However the<br />
function POK<strong>ODS</strong>F.F_CALC_EARNING_TOTALS_YTD (used to calculate total<br />
hours and total earning year-to-date) does so based on PERSON_UID only and not<br />
PERSON_UID and Position.<br />
Resolution<br />
The PERYCHG change table was modified to refresh based on PIDM and YEAR.<br />
This was done because the composite views use functions that calculate amounts<br />
based on a parameter of PIDM & Year. So, all rows must be refreshed for a PIDM and<br />
YEAR in order to calculate them correctly.<br />
1-1DY3E1<br />
Impact<br />
The NBBFISC_COAS code is a NULL column in Banner. As a result, this column<br />
should not be used during the incremental refresh. The trigger will fail on NBBFISC<br />
if a record is inserted in NBBFISC without the COAS code.<br />
Resolution<br />
The change table NBRFCHG was modified to refresh only on the fiscal year. The<br />
chart of accounts was removed and the necessary objects were modified to reflect<br />
this change.<br />
1-1JNL2E<br />
Impact<br />
The TOTAL_HOURS_FISCAL_YEAR & TOTAL_EARNINGS_FISCAL_YEAR<br />
columns in the AP_EARNING_TOTALS_FY composite view are calculated<br />
incorrectly. The Fiscal Year is passed to a function that is not taking into account the<br />
start and end dates of that particular fiscal year. As a result, these calculations are<br />
being done for the calendar year.<br />
Resolution<br />
A new function was added to POK<strong>ODS</strong>F to calculate the amounts for the months<br />
within a fiscal year.<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
36 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 4 Problem Resolutions<br />
Human Resources<br />
1-1JNWO9<br />
Impact<br />
The join to YEARLY_DEDUCTION in the BENEFIT_DEDUCTION reporting view<br />
causes a performance issue in this view due to the aggregations being calculated in<br />
YEARLY_DEDUCTION.<br />
Resolution<br />
A new table to house the YEARLY_DEDUCTION data was created in the <strong>ODS</strong>. This<br />
will become part of the <strong>ODS</strong> ETL and will significantly increase the performance of<br />
the reporting views that use the YEARLOY_DEDUCTION reporting view.<br />
1-IAJNC<br />
Impact<br />
The fields, PROFILE_DATE and PROFILE_YEAR, were not returning data because<br />
of a typo. EMPLOYEE_PROLILE needed to be changed to EMPLOYEE_PROFILE.<br />
Resolution<br />
The parameter for the functions, F_YEAR and F_PROFILE_DATE were changed to<br />
EMPLOYEE_PROFILE.<br />
1-MFS0N<br />
Impact<br />
Records were being excluded from the BENEFICIARY_DEPENDENT reporting<br />
view due to an incorrect join in the view. If a beneficiary does not have a PIDM it<br />
causes the BENEFICIARY_DEPENDENT view to exclude that person.<br />
Resolution<br />
An outer join from MST_PERSON join to MPT_BENEFICIARY was added on the<br />
BENEFICIARY_UID so that all records from MPT_BENEFICIARY would be<br />
retrieved regardless of a BENEFICIARY_UID having a record in the MST_PERSON<br />
table.<br />
1-NNWZA<br />
Impact<br />
When Finance is partitioned, it results in a mapping error when scheduled in the<br />
Administrative UI: Error Purging Change Table - no DELETE mapping found for:<br />
LOAD_MFT_TRANS_HISTORY_1_PART.<br />
All five partitions fail with a similar error. The same holds true for the payroll<br />
distribution partition exchange mappings.<br />
Resolution<br />
The script to install the partition exchange option for transaction history and<br />
payroll history were modified to add the records to TMTVPARM. This creates<br />
records in MTVPARM so that the mapping knows which change table to purge prior<br />
to loading these tables.<br />
1-QAJXX<br />
Impact<br />
The join in Cognos between PAYROLL_EMPLOYEE_POSITION and<br />
EMPLOYEE_POSITION had an incorrect join:<br />
April 2007 Operational Data Store <strong>Release</strong> <strong>3.1</strong><br />
Confidential <strong>Release</strong> <strong>Guide</strong> 37
Section 4 Problem Resolutions<br />
Student<br />
"Payroll Employee Position.POSITION_BEGIN_DATE = Employee<br />
Position.EFFECTIVE_DATE"<br />
Additionally, for the sake of ease of use, a new column should be added to<br />
EMPLOYEE_POSITION that indicates whether the position is a current position as<br />
of today's date.<br />
Resolution<br />
The function MPKFUNC.F_POSITION_CURRENT_IND was created to return an<br />
'N' or 'Y' depending on whether the position is current based on the current date.<br />
In EMPLOYEE_POSITION reporting view, the column<br />
POSITION_CURRENT_IND was added to call the new function.<br />
The Employee Position was updated in the Employee, Faculty Assignment, Human<br />
Resource Faculty, Payroll, and Position business areas. The relationship was updated<br />
in the Payroll business view.<br />
Student<br />
1-10G2J1<br />
Impact<br />
REGISTRATION_STATUS, REGISTRATION_ERROR_FLAG and the other fields<br />
from SFRSTCR were not being updated in MST_STUDENT_COURSE where<br />
INSTITUTION_COURSE_IND = Y.<br />
Resolution<br />
A trigger on SFRSTCR was added for AS_STUDENT_COURSE_HISTORY to<br />
update changes to MST_STUDENT_COURSE.<br />
1-10QHM8<br />
Impact<br />
Composite views with a UNION in them can experience performance problems<br />
when they are joined to change tables within the UPDATE mappings.<br />
Resolution<br />
New composite view, MSVCURR, was created as a join of the existing<br />
AS_CURRICULUM select statement and the Banner change table SGRPCHG. The<br />
mapping UPDATE_MST_CURRICULUM was modified to use the new MSVCURR<br />
view.<br />
1-11UA2L<br />
Impact<br />
A number of the values in MST_CURRICULUM originate from the Banner table<br />
SORLCUR. If no values exist on SORLCUR, then they will be retrieved from<br />
SGBSTDN. If there are no values in SORLCUR for the site information, admissions<br />
population, student population, student rate, leave reason and dates, or intended<br />
graduation academic period, year, and date, then these values in<br />
MST_CURRICULUM may not be synchronized with the SGBSTDN values.<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
38 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 4 Problem Resolutions<br />
Student<br />
Resolution<br />
Added a call to the trigger ST_SGBSTDN_INSERT_<strong>ODS</strong>_CHANGE to track which<br />
curriculum records need to be refreshed.<br />
1-15R5AX<br />
Impact<br />
The reporting views ADMISSIONS_APPLICATION,<br />
RECRUITMENT_INFORMATION, ACADEMIC_STUDY, ACADEMIC_OUTCOME<br />
and GOVERNMENT_ADMISSIONS can now be uniquely identified by the various<br />
curricula within an academic period for a person. The columns<br />
CURRICULUM_PRIORITY_NUMBER and CURRICULUM_ORDER or<br />
PROGRAM_NUMBER were added to each of these reporting views, and are the<br />
columns used to uniquely identify the priority of the curriculum for each student.<br />
Resolution<br />
Added the columns CURRICULUM_PRIORITY and CURRICULUM_ORDER to<br />
the following tables:<br />
MST_ADMISSIONS_APPLICATION<br />
MST_RECRUITMENT_INFORMATION<br />
MST_ACADEMIC_OUTCOME<br />
Added CURRICULUM_PRIORITY to MST_GENERAL_STUDENT.<br />
Added the columns CURRICULUM_PRIORITY_NUMBER and<br />
CURRICULUM_ORDER to the following reporting views:<br />
ADMISSIONS_APPLICATION<br />
RECRUITMENT_INFORMATION<br />
ACADEMIC_OUTCOME.<br />
Added CURRICULUM_ORDER to the view GOVERNMENT_ADMISSIONS.<br />
Added CURRICULUM_PRIORITY_NUMBER to view ACADEMIC_STUDY.<br />
Fixed Object Access views AR_USER_DEFINED_FIELDS,<br />
AS_ADMISSIONS_APPLICANT, MRVSTS1, AS_RECRUITING_DATA, and<br />
AS_RECRUITING_SOURCE_ANALYSIS to only display the primary curriculum if<br />
any exist.<br />
1-17H2EH<br />
Impact<br />
There are specific situations where students have registered for classes (having rows<br />
defined in STUDENT_COURSE), and do not have corresponding records loaded<br />
into ACADEMIC_STUDY and ENROLLMENT (possibly other reporting views are<br />
also affected).<br />
April 2007 Operational Data Store <strong>Release</strong> <strong>3.1</strong><br />
Confidential <strong>Release</strong> <strong>Guide</strong> 39
Section 4 Problem Resolutions<br />
Student<br />
The effected students have Banner SGBSTDN rows with effective term codes<br />
(effectivity date), where multiple curriculums can exist for a term, but do not have<br />
rows in SORLCUR for all subsequent effective terms (effectivity date) of SGBSTDN.<br />
Example:<br />
SGBSTDN may have rows with effective term codes 200610, 200620, 200630. A<br />
first curriculum exists in SORLCUR for 200610. Then a second curriculum was<br />
added for the second term of 200620. The first curriculum only displays in<br />
ACADEMIC_STUDY for the first term. It should display for the second and<br />
third term. For those cases where students are not getting the appropriate<br />
records loaded into ACADEMIC_STUDY and ENROLLMENT, EDW daily<br />
extracts and Cognos reports are under-reporting the number of students who<br />
are actually registered for classes.<br />
Resolution<br />
ACADEMIC_PERIOD_END was added to composite view<br />
AS_LEARNER_CURRICULUM_FOS and table MST_CURR_STUDENT. The join<br />
of SGBSTDN to SORLCUR was made to be on PIDM only in<br />
AS_LEARNER_CURRICULUM_FOS in order to get all current curricula data for<br />
each effective term. The joins between MST_STUDENT_TERM_STAGE and<br />
MST_CURR_STUDENT were fixed in the mappings<br />
LOAD_MST_CURRICULUM_BATCH, UPDATE_MST_GENERAL_STUDENT,<br />
and UPDATE_MST_GENERAL_STUDENT_TRM.<br />
1-19FMIO<br />
Impact<br />
The column mapped to the CENSUS_ENROLLMENT_DATE2 field in the<br />
MSVGVC1 view is incorrect. As a result, the SSBSECT_CENSUS_ENRL_DATE is<br />
being populated into this column instead of SSBSECT_CENSUS_2_DATE.<br />
Resolution<br />
CENSUS_ENROLLMENT_DATE1 was replaced with<br />
CENSUS_ENROLLMENT_DATE2 for field<br />
MSVGVC1.CENSUS_ENROLLMENT_DATE2.<br />
1-7AJ6X<br />
Impact<br />
The field COMPLETED_IND was null. This was populated with a Y when the<br />
checklist received date is not null otherwise set to N.<br />
Resolution<br />
The field COMPLETED_IND was null. It is now populated with the following:<br />
DECODE (SARCHKL_RECEIVE_DATE, NULL,'N','Y')<br />
1-7EQHZ<br />
Impact<br />
The field, SEC_TRANSCRIPT_RECEIVED_DATE was being populated by NULL.<br />
This was changed to populate from the High School Receive Date.<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
40 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 4 Problem Resolutions<br />
Student<br />
Resolution<br />
The field, SEC_TRANSCRIPT_RECEIVED_DATE was being populated with a null.<br />
This has been changed to populate with SORHSCH_TRANS_RECV_DATE.<br />
1-IA70O<br />
Impact<br />
The ACADEMIC_OUTCOME_ENROLLED_INDICATOR in the reporting views for<br />
Student and Enrollment was not resetting properly when changes occurred to the<br />
degree in the table SGBSTDN. The function in Banner,<br />
Sokodsf.F_DEGR_ENROLLED_IND used the SGBSTDN table which does not have<br />
a trigger to re-extract enrollment information. There was nothing to re-extract<br />
enrollment information also in the Student Concurrent Curriculum add-on.<br />
Resolution<br />
The logic to determine the ACADEMIC_OUTCOME_ENROLLED_IND is now<br />
determined in the <strong>ODS</strong>. Function F_DEGR_ENROLLED_IND was removed from<br />
package SOK<strong>ODS</strong>F. Column ACADEMIC_OUTCOME_ENROLLED_IND was<br />
removed from composite views AS_ACADEMIC_STANDING, AS_ENROLLMENT,<br />
as well as composite tables MST_ACADEMIC_STANDING and<br />
MST_ENROLLMENT. Function F_DEGR_ENROLLED_IND was added and<br />
function F_GET_OUTCOME_ENROLLED_IND was removed from package<br />
MSKFUNC. Mapping value for column<br />
ACADEMIC_OUTCOME_ENROLLED_IND was modified for reporting views<br />
enrollment and student.<br />
1-1DY19X<br />
Impact<br />
Performance has been improved for the mappings LOAD_MST_STUDENT_CLASS<br />
and UPDATE_MST_STUDENT_CLASS.<br />
Resolution<br />
The student classification driver logic was moved from<br />
AS_STUDENT_CLASS_DRIVER to AS_STUDENT_CLASSIFICATION. The view<br />
AS_STUDENT_CLASS_DRIVER and function<br />
SOK<strong>ODS</strong>F.F_CHECK_FOR_CLASS_TERM were removed. A new view MSVCLS0<br />
was created to improve performance of the UPDATE_MST_STUDENT_CLASS<br />
mapping. LOAD_MST_STUDENT_CLASS and UPDATE_MST_STUDENT_CLASS<br />
mappings were updated to use the updated views.<br />
1-1DYFKN<br />
Impact<br />
The <strong>ODS</strong> data is not correctly reflecting the Banner current and active indicators on<br />
some curriculum field of study rows. Because of this, they are being displayed with<br />
the student curriculum in the Academic Study reporting view. Corrections need to<br />
be made so only current and active field of study appears in the various reporting<br />
views that display the student curriculum.<br />
Resolution<br />
Changes were made to permit the correct indicator to be associated with each Field<br />
of Study for a student in Academic Study reporting view rows.<br />
The following triggers were altered:<br />
April 2007 Operational Data Store <strong>Release</strong> <strong>3.1</strong><br />
Confidential <strong>Release</strong> <strong>Guide</strong> 41
Section 4 Problem Resolutions<br />
Student<br />
• ST_SORLCUR_INSERT_<strong>ODS</strong>_CHANGE and<br />
ST_SORLFOS_INSERT_<strong>ODS</strong>_CHANGE to insert change records into<br />
SGRPCHG with a SGRPCHG_TABLE_NAME of 'FIELD_OF_STUDY'.<br />
• Updated the DELETE_MST_FIELD_OF_STUDY and<br />
UPDATE_MST_FIELD_OF_STUDY mappings to use SGRPCHG instead of<br />
SHRDCHG.<br />
1-EDE2X<br />
Impact<br />
The Instructional Assignment view was returning the wrong results when a person<br />
had multiple academic periods with the same academic year.<br />
Resolution<br />
The WHERE statement was joining ACADEMIC_YEAR instead of<br />
ACADEMIC_PERIOD.<br />
1-H6ZQR<br />
Impact<br />
Item 1 - Joining the STUDENT to the STUDENT_COHORT_SLOT is cumbersome<br />
since the STUDENT_COHORT_SLOT is not built by ACADEMIC_PERIOD. This is<br />
inconsistent and confusing since it does not follow the same pattern as the other<br />
reporting views in the <strong>ODS</strong>.<br />
Ease of use for the end user would expect the change to the<br />
STUDENT_COHORT_SLOT:<br />
REMOVE the columns ACADEMIC_PERIOD_START and<br />
ACADEMIC_PERIOD_END.<br />
ADD the columns ACADEMIC_PERIOD and ACADEMIC_PERIOD_DESC.<br />
Modify the data load for the MST_STUDENT_COHORT_SLOT to use the display<br />
rules from MGRSDAX with an INTERNAL_GROUP = COHORT and<br />
INTERNAL_CODE = STDNCHRT and load the cohort values by these rules.<br />
Modify the reporting view STUDENT_COHORT_SLOT to display the cohort1,<br />
cohort2, cohort3, etc. by ACADEMIC_PERIOD.<br />
Update the Cognos Packages as appropriate.<br />
Update the Discoverer EUL as appropriate.<br />
Resolution<br />
Item 1: Added academic period and description, and removed academic period<br />
start and end columns from MST_STUDENT_COHORT_SLOT table and<br />
STUDENT_COHORT_SLOT view. Modified package MSKCHRT to populate<br />
MST_STUDENT_COHORT_SLOT by academic period instead of a range of<br />
academic periods. Updated reporting views AS_STUDENT_DATA,<br />
GOVERNMENT_ACADEMIC_OUTCOME, and<br />
GOVERNMENT_FINANCIAL_AID to use the new ACADEMIC_PERIOD column in<br />
the join conditions.<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
42 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 4 Problem Resolutions<br />
Student<br />
The Report Studio model was updated to include changes to Student Cohort Slot.<br />
The Student Cohort Slot was added to the Advisor Student List business view.<br />
Student relates to Student Cohort Slot by Person UID and Academic Period.<br />
1-HRL6J<br />
Impact<br />
Meta data for some columns in AS_CURRICULUM and AS_FIELD_OF_STUDY<br />
composite views as well as FIELD_OF_STUDY reporting view had incorrect source<br />
mappings.<br />
Resolution<br />
The meta data mapping source was corrected for several columns composite views<br />
AS_CURRICULUM and AS_FIELD_OF_STUDY, as well as the reporting view<br />
FIELD_OF_STUDY.<br />
1-JK92W<br />
Impact<br />
Information in the <strong>ODS</strong> was not being updated on the Enrollment reporting view<br />
since the existing triggers for the housing and veteran data were not impacting<br />
AS_ENROLLMENT. The HOUSING_IND and VETERAN_TYPE columns in<br />
AS_ENROLLMENT composite view were not being updated since there was not a<br />
trigger on the Banner database tables SLRRASG and SGRVETN for this view.<br />
Resolution<br />
Triggers were added to support the changes to the AS_ENROLLMENT composite<br />
view. The added triggers were ST_SLRRASG_INSERT_<strong>ODS</strong>_CHANGE and<br />
ST_SGRVETN_INSERT_<strong>ODS</strong>_CHANGE. Now both the Housing Ind and the<br />
veteran's information are being correctly brought into the <strong>ODS</strong> -<br />
MST_ENROLLMENT composite table.<br />
1-JQL7X<br />
Impact<br />
The additional source of SHRTRCE.SHRTRCE_COUNT_IN_GPA_IND was missing<br />
for the field STUDENT_COURSE.COUNT_IN_GPA_IND in the meta data.<br />
Resolution<br />
Another source (SHRTRCE_COUNT_IND_GPA_IND) was added in the meta data<br />
for the column STUDENT_COURSE.COUNT_IN_GPA_IND.<br />
1-K7WW5<br />
Impact<br />
Repeat indicator was only being set for institutional courses and not for transfer<br />
courses. This information is available in Banner for both institutional and transfer<br />
courses. This column can be set on the AS_STUDENT_COURSE_IN_PROGRESS<br />
from the SFRSTCR_REPT_OVER. On the AS_STUDENT_COURSE_TRANSFER<br />
this column can be set from the SHRTRCE_REPEAT_COURSE. Currently the<br />
AS_STUDENT_COURSE_HISTORY is being set from<br />
SHRTCKN_REPEAT_COURSE_IND.<br />
Resolution<br />
In AS_STUDENT_COURSE_TRANSFER, SHRTRCE_REPEAT_COURSE as value<br />
for REPEAT_COURSE_IND was added.<br />
April 2007 Operational Data Store <strong>Release</strong> <strong>3.1</strong><br />
Confidential <strong>Release</strong> <strong>Guide</strong> 43
Section 4 Problem Resolutions<br />
Student<br />
1-L9EGU<br />
Impact<br />
Data in AS_PRE_STUDENT.PS_ATTEND_TO_DATE comes from the<br />
SORDEGR.SORDEGR_ATTEND_TO column, when<br />
SORDEGR.SORDEGR_ATTEND_TO is updated. This change is not seen in the<br />
<strong>ODS</strong> when the UPDATE_MST_PRE_STUDENT mapping is run. However it is seen<br />
when the LOAD process is run. There should be a trigger that permits both the<br />
MST_PRE_STUDENT or the MST_PREVIOUS_EDUCATION to recognize and<br />
update with this change in Banner.<br />
Resolution<br />
Added logic to the <strong>ODS</strong> trigger on SORDEGR so that changes will be refreshed into<br />
MST_PRE_STUDENT if changes occur on SORDEGR.<br />
1-LU645<br />
Impact<br />
The package body SOK<strong>ODS</strong>F. F_GET_FIELDSTUDY_ROWID was populating<br />
CONCENTRATIONS for a major that was not current. This function is supposed to<br />
only populate active and current majors, minors and concentrations. This affected<br />
both Banner composite views AS_CURRICULUM_FOS and<br />
AS_LEARNER_CURRICULUM_FOS, which impacts the creation of<br />
ACADEMIC_STUDY, RECRUITMENT_INFORMATION, ADMISSIONS, and<br />
ACADEMIC_OUTCOME.<br />
Resolution<br />
In the package body SOK<strong>ODS</strong>F, the following line was removed from function<br />
F_GET_FIELDSTUDY_ROWID:<br />
AND NVL(B.SORLFOS_MAJR_CODE_ATTACH,'#') =<br />
NVL(A.SORLFOS_MAJR_CODE_ATTACH,'#')<br />
1-M1QUH<br />
Impact<br />
The STUDENT reporting view in the Student Concurrent Curriculum add-on for<br />
release 3.0 was using an old method that incorrectly calculated the number of<br />
matriculations in a given academic period. There is no longer a limitation of two<br />
curriculums that can be matriculated in a given academic period.<br />
Resolution<br />
The STUDENT reporting view (MSVSTDN.SQL) was corrected by modifying the<br />
value of column ACADEMIC_STUDY_MATRIC_IN_COUNT to call the function<br />
MSKFUNC.F_ACAD_STUDY_MATRIC_IN_COUNT.<br />
1-M8TYX<br />
Impact<br />
Reporting view column comments were added to all reporting views in the <strong>ODS</strong>, but<br />
they were missing for the columns added for the <strong>ODS</strong> 3.0 post Banner 7.3 added<br />
concurrent curriculum columns. Missing meta data information needed to be<br />
corrected.<br />
Resolution<br />
The student concurrent curriculum was included if the client is using Banner<br />
Student 7.3. The script ADD_REPVIEW_COMMENTS.SQL was included with the<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
44 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 4 Problem Resolutions<br />
Student<br />
<strong>ODS</strong> 3.0 release, but was not called from the concurrent curriculum meta data<br />
upgrade driver script. The student concurrent curriculum for Banner 7.3 will now<br />
be included in baseline for the <strong>ODS</strong> <strong>3.1</strong> release.<br />
1-MWD0J<br />
Impact<br />
Student has incorrect classification due to AS_STUDENT_CLASS_ATTR looking<br />
for the existence of a student attribute for a term greater than the maximum<br />
SHRTGPA_TERM_CODE.<br />
Resolution<br />
The process to determine student classification was rewritten to use a driver view<br />
(AS_STUDENT_CLASS_DRIVER) to control the creation of all records that track<br />
the student's classification. The process is used when the SGRATT – Student<br />
Attribute table is used and when it is not used to display the student classification on<br />
the SGBSTDN – General Student record. When combined with the records created<br />
for academic history occurrences that had matching student levels, the driver results<br />
were combined with the re-written AS_STUDENT_CLASSIFICATION view to either<br />
load the table or refresh it.<br />
As a result of the re-architecture, the views MSVCLAS, MSVCLSA, and<br />
AS_STUDENT_CLASS_ATTR are no longer needed, as well as the<br />
DELETE_STUDENT_ATTR_CLASS and UPDATE_STUDENT_ATTR_CLASS<br />
mappings.<br />
1-MX3M1<br />
Impact<br />
The script error from ADD_REPVIEW_COMMENTS.SQL occurred because an old<br />
version of the STUDENT_COURSE_ATTRIBTUE view exists in the database. The<br />
script was not included in the <strong>ODS</strong>2.2 upgrade (<strong>ODS</strong>_UPGRADE.SQL).<br />
Resolution<br />
The student view script MSVSCAT.SQL was changed in version 2.2 to include new<br />
columns INSTITUTION_COURSE_IND, TRANSFER_COURSE_IND, ID, NAME.<br />
Recreate the STUDENT_COURSE_ATTRIBUTE view, and rerun the<br />
ADD_REPVIEW_COMMENTS.SQL script.<br />
1-OGNE8<br />
Impact<br />
The view ACADEMIC_OUTCOME was not being updated when changes were made<br />
to SHRTCKG. Therefore, ACADEMIC_OUTCOME was added to the SHRTCKG<br />
trigger.<br />
Resolution<br />
The view AS_ACADEMIC_OUTCOME needed to be added to the trigger for<br />
SHRTCKG.<br />
1-PP8C9<br />
Impact<br />
Data in the <strong>ODS</strong> needs to reflect the same information as the data displayed in<br />
Banner. On the AS_ENROLLMENT reporting view the Y/N indicator<br />
(ACADEMIC_HISTORY_EXISTS_IND) reflects whether or not Academic History<br />
April 2007 Operational Data Store <strong>Release</strong> <strong>3.1</strong><br />
Confidential <strong>Release</strong> <strong>Guide</strong> 45
Section 4 Problem Resolutions<br />
Student<br />
(SHRTTRM) data exists for specified PIDM and Term Code. Confirm this is using<br />
the trigger ST_SHRTGPA_INSERT_<strong>ODS</strong>_CHANGE to track any changes made.<br />
Resolution<br />
The call was moved to insert ENROLLMENT change records from trigger<br />
ST_SHRTTRM_INSERT_<strong>ODS</strong>_CHANGE to trigger<br />
ST_SHRTGPA_INSERT_<strong>ODS</strong>_CHANGE.<br />
1-Q4DPP<br />
Impact<br />
The table MST_INSTRUCTIONAL_ASSIGNMENT was not being updated for<br />
changes in SPRIDEN because the name MST_INSTRUCTIONAL_ASSIGNMENT<br />
was used instead of INSTRUCTIONAL_ASSIGNMENT.<br />
Resolution<br />
The name MST_INSTRUCTIONAL_ASSIGNMENT was being used in the trigger to<br />
pick up changes from SPRIDEN. The mapping uses<br />
INSTRUCTIONAL_ASSIGNMENT so the updates were not happening.<br />
1-QGK6A<br />
Impact<br />
In the 3.0 release, the change table used to refresh the<br />
MST_ACADEMIC_OUTCOME table in the <strong>ODS</strong> was changed from SHRDCHG to<br />
SPRPCHG. The change was reflected in the OWB mappings. However, the changes<br />
were not reflected in the triggers on two of the tables. Thus, records were being<br />
inserted into the incorrect change table and were not being processed for the<br />
refresh.<br />
Resolution<br />
The triggers ST_SHBDIPL_INSERT_<strong>ODS</strong>_CHANGE and<br />
ST_SHRTCKD_INSERT_<strong>ODS</strong>_CHANGE were modified to insert<br />
ACADEMIC_OUTCOME change records into SPRPCHG.<br />
1-S4D8S<br />
Impact<br />
The name changes in SPRIDEN are not reflected in MST_ADVISOR fields,<br />
ADVISOR_ID, ADVISOR_FIRST_NAME, ADVISOR_LAST_NAME,<br />
ADVISOR_NAME_FLMI, ADVISOR_NAME_LFMI. These fields have been replaced<br />
with a new function, MSKFUNC.F_GET_MST_PERSON_INFO.<br />
Resolution<br />
Created new function, MSKFUNC.F_GET_MST_PERSON_INFO which retrieves<br />
the ID, FIRST_NAME, LAST_NAME, LFMI_NAME, FLMI_NAME for the<br />
ADVISOR_UID for the ADVISOR view.<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
46 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 4 Problem Resolutions<br />
General Miscellaneous<br />
General Miscellaneous<br />
1-10GY3R<br />
Impact<br />
The client is not able to import the Oracle Discoverer workbooks.<br />
Resolution<br />
There was a workbook in the EUL that had an apostrophe in the document<br />
description (description of the AF33 workbook). The character was showing up as<br />
an upside down "?." It is evidently an unprintable character in the database. The<br />
character was removed and the workbooks were re-exported. This made it possible<br />
to import the workbooks into Discoverer.<br />
1-1A27V5<br />
Impact<br />
The document Report Studio8_<strong>ODS</strong>_Install_Instructions.doc in the<br />
ods30000i\reports\Cognos_Report Studio\Cognos8 folder is missing one step in the<br />
page 5 of the document.<br />
I think it would be necessary to tell the person responsible for the install to copy over<br />
the file "crn_ods_templates.zip" in the directory /Development.<br />
This will make the template appear in the content administration page.<br />
On the page 13 of the document "Report Studio8_<strong>ODS</strong>_Install_Instructions.doc" of<br />
the folder "ods30000i\reports\Cognos_Report Studio\Cognos8" I receive an error<br />
"This portlet cannot be displayed because it is disabled.”<br />
This error is happening when the page is disabled and it would be a good thing to<br />
show the client on how to enable the page so that he can continue in the installation.<br />
To enable the page you have to click on edit on the top right, click on the general<br />
tab and then uncheck the box "Disable this entry". Sometime you have to go on the<br />
folder on the public tab and change it there because the check box is disabled and<br />
don’t permit a check or uncheck.<br />
Resolution<br />
The documentation was updated to tell clients to copy the deployment archive to<br />
the Cognos deployment directory. Instructions were also added to remove the<br />
disabling of the packages after an import.<br />
1-1CU1IU<br />
Impact<br />
The business model for Purchase Payable within the COGNOS Report Studio model<br />
now retrieves document level accounting records as well as the commodity level<br />
accounting records for reports. This was accomplished by creating a new<br />
relationship between the Purchase Order and Purchase Order Accounting and<br />
removing the old relationship between Purchase Order Item and Purchase Order<br />
Accounting.<br />
April 2007 Operational Data Store <strong>Release</strong> <strong>3.1</strong><br />
Confidential <strong>Release</strong> <strong>Guide</strong> 47
Section 4 Problem Resolutions<br />
General Miscellaneous<br />
Resolution<br />
The Purchasing Payable business model within COGNOS Report Studio was<br />
corrected by removing the relationship between the Purchase Order Item and<br />
Purchase Order Accounting, and then adding a new relationship between the<br />
Purchase Order and Purchase Order Accounting. To clarify the joins between the<br />
Purchase Order Item and Purchase Order Accounting, filters were added to define<br />
PO Document Level Accounting Record and PO Commodity Level Accounting<br />
Record.<br />
The old Document Level Accounting Record filter was renamed Invoice Document<br />
Level Accounting Record filter. A new Invoice Commodity Level Accounting Record<br />
filter was added. These assist in clarifying the joins between Item records and<br />
Accounting records when the document is utilizing Document Level Accounting<br />
versus Commodity Level Accounting. Additionally, the Invoice Payable business<br />
model within COGNOS Report Studio had its filter between the Invoice Item and<br />
Invoice Accounting record renamed for consistency. The Document Level<br />
Accounting Record filter was renamed Invoice Document Level Accounting Record<br />
and a new filter was added called Invoice Commodity Level Accounting Record<br />
filter.<br />
1-IYRU7<br />
Impact<br />
Several fields in various <strong>ODS</strong> views were inappropriately allowed to remain a length<br />
of varchar2(4000). This occurred when the columns were created via functions or<br />
calculations. The majority of these fields should have been a varchar2(1). Leaving<br />
these fields at varchar2(4000) created various problems when trying to report upon<br />
them.<br />
Resolution<br />
Added SUBSTR to all fields that were varchar2(4000) other than comments or text.<br />
1-K25N5<br />
Impact<br />
Cognos Changes:<br />
1. The Government Student -> Government Financial Aid relationship needs to<br />
be removed in the Government Reporting business view.<br />
2. Institution is missing from the Admissions Application and Recruitment<br />
Information business views.<br />
3. Student (ORA-00904 "SITE_STREET_LINE4": invalid identifier") The Student<br />
view in the EUL and model has not been updated for 3.0 changes.<br />
4. The join between Student and GPA By Level shouldn’t include<br />
ACADEMIC_PERIOD, only the PERSON_UID. ACADEMIC_PERIOD is<br />
NULL. See the BANINST1.AS_GPA_LEVEL view.<br />
5. Join between TRANSACTION_HISTORY and OPERATING_LEDGER is<br />
incorrect. IT is missing the join between COMMITMENT_IND and the join<br />
between location and activity is incorrect. The problem will exist in both the<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
48 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 4 Problem Resolutions<br />
General Miscellaneous<br />
OPERATING_LEDGER Business Concept and the<br />
TRANSACTION_HISTORY Business Concept. The following statement<br />
should be used in its entirety. OL = operating_leger, TH =<br />
TRANSACTION_HISTORY. join where<br />
OL.Chart_Of_Accounts = TH.Chart_Of_Accounts<br />
AND<br />
OL.Fiscal_Year = TH.Fiscal_Year and<br />
OL.Fiscal_Period = TH.Posting_Period and<br />
OL.Fund = TH.Fund and<br />
OL.Organization_Code = TH.Organization_Code and<br />
OL.Account = TH.Account and<br />
OL.Program = TH.Program and<br />
OL.Activity = NVL(TH.Activity,' ' )<br />
OL.Location = NVL(TH.Location,' ')<br />
OL.Commitment_Type = TH.Commitment_Type<br />
Resolution<br />
Cognos Changes:<br />
1. The Government Student -> Government Financial Aid relationship was<br />
removed in the Government Reporting business view.<br />
2. Institution was added to the Admissions Application and Recruitment<br />
Information business views.<br />
3. Student (ORA-00904 "SITE_STREET_LINE4": invalid identifier") The<br />
Student view in the EUL and model has been updated for 3.0 changes.<br />
4. The join between Student and GPA By Level doesn't include<br />
ACADEMIC_PERIOD, only the PERSON_UID. ACADEMIC_PERIOD is<br />
NULL. See the BANINST1.AS_GPA_LEVEL view.<br />
5. The join between TRANSACTION_HISTORY and OPERATING_LEDGER is<br />
corrected. It no longer is missing the join between COMMITMENT_TYPE and<br />
the join between location and activity is correct. The problem was fixed in both<br />
the Operating Ledger business concept and the TRANSACTION_HISTORY<br />
business concept. It was also fixed in the Grant Ledger business concept. The<br />
following statement was be used in its entirety.<br />
select *<br />
from operating_ledger ol, transaction_history th<br />
where OL.Chart_Of_Accounts = TH.Chart_Of_Accounts<br />
AND<br />
OL.Fiscal_Year = TH.Fiscal_Year and<br />
April 2007 Operational Data Store <strong>Release</strong> <strong>3.1</strong><br />
Confidential <strong>Release</strong> <strong>Guide</strong> 49
Section 4 Problem Resolutions<br />
General Miscellaneous<br />
OL.Fiscal_Period = TH.Posting_Period and<br />
OL.Fund = TH.Fund and<br />
OL.Organization_Code = TH.Organization_Code and<br />
OL.Account = TH.Account and<br />
OL.Program = TH.Program and<br />
OL.Activity = NVL(TH.Activity,' ' ) and<br />
OL.Location = NVL(TH.Location,' ') and<br />
OL.Commitment_Type = TH.Commit_Type<br />
The joins in Operating Ledger and Grant Ledger were changed to inner joins. Also,<br />
because Grant Ledger had nulls in Fiscal Year and Fiscal Period, the report used to<br />
test the joins needed to filter on Fiscal Year and Fiscal Period so that it returned only<br />
those rows from Grant Ledger where they were not null.<br />
1-M2R19<br />
Impact<br />
Published meta data pages still showed SCT in the title.<br />
Resolution<br />
Updated the MGKPUBL package to include SGHE in titles. Updated data in<br />
WMT_IA_SYSTEM table for <strong>ODS</strong> and EDW to include SGHE in system description.<br />
1-NV6ID<br />
Impact<br />
Discoverer and Report Studio meta data will not contain additional columns that<br />
were added for the Concurrent Curriculum reporting views.<br />
Resolution<br />
Added the additional columns for the Banner 7.3 concurrent curriculum views.<br />
1-OMVEG<br />
Impact<br />
The CC_UPGRADE.SQL script calls the ods/IA_ADMIN/dbscripts/metadata/7.3/<br />
metadata_upgrade_cc.sql which has lines like this<br />
@&home_dir/ods/dbscripts/metadata/7.3/metadata/<br />
md_ods_source_insert_30_cc.sql<br />
The lines need to include the IA_ADMIN directory in the path.<br />
@&home_dir/ods/IA_ADMIN/dbscripts/metadata/7.3/metadata/<br />
md_ods_source_insert_30_cc.sql<br />
W/a: Edit script and add IA_ADMIN to path directory.<br />
Resolution<br />
No action to be taken. Path is correct in baseline code. Script will not be used going<br />
forward, as it was a 3.0 specific optional upgrade piece.<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
50 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 4 Problem Resolutions<br />
General Miscellaneous<br />
1-PFGAM<br />
Impact<br />
Error messages occur when running the <strong>ODS</strong>_PARTITIONING.SQL script for the<br />
<strong>ODS</strong> 3.0 upgrade.<br />
Resolution<br />
No action to be taken. Baseline script is correct.<br />
1-R3A2D<br />
Impact<br />
The first three view errors are from incorrect synonyms as you described.<br />
1. SPECIAL_ACTIVITY_SLOT : errors are caused by the creation of an invalid<br />
synonym in #2 below. To correct this error, connect as <strong>ODS</strong>MGR and execute<br />
the statement below....<br />
CREATE OR REPLACE PUBLIC SYNONYM SPECIAL_ACTIVITY_SLOT FOR<br />
SPECIAL_ACTIVITY_SLOT;<br />
2. SPECIAL_ACTIVITY_YEAR_SLOT : errors are due to a missing synonym. To<br />
correct this error, connect as <strong>ODS</strong>MGR and execute the statement below...<br />
CREATE OR REPLACE PUBLIC SYNONYM<br />
SPECIAL_ACTIVITY_YEAR_SLOT FOR SPECIAL_ACTIVITY_YEAR_SLOT;<br />
Change the create synonym statement in the script <strong>ODS</strong>/SLOTTED_VIEWS/<br />
SPECIAL_ACTIVITY_YEAR_SLOT.SQL.<br />
3. GRANT_APPLIED_PAYMENTS :error due to the creation of an incorrect<br />
synonym. To correct this error, connect as <strong>ODS</strong>MGR and execute the<br />
statements below...<br />
DROP PUBLIC SYNONYM GRANT_APPLIED_PAYMENT;<br />
CREATE OR REPLACE PUBLIC SYNONYM GRANT_APPLIED_PAYMENTS<br />
FOR GRANT_APPLIED_PAYMENTS;<br />
Change the create synonym statement in the script <strong>ODS</strong>/FINANCE/VIEWS/<br />
MFVGAP0.SQL<br />
4. STUDENT_COURSE_ATTRIBUTE : could you please rerun the script <strong>ODS</strong>/<br />
STUDENT/VIEW/MSVSCAT.SQL to recreate this view. The columns that<br />
show up in the error log were added in 2.2....<br />
Resolution<br />
The errors generated in the meta data upgrade process were from the<br />
ADD_REPVIEW_COMMENTS.SQL script that uses meta data to add comment on<br />
reporting views. For these errors, the meta data existed, but view columns could not<br />
be found in the database due to incorrect synonyms.<br />
April 2007 Operational Data Store <strong>Release</strong> <strong>3.1</strong><br />
Confidential <strong>Release</strong> <strong>Guide</strong> 51
Section 4 Problem Resolutions<br />
General Miscellaneous<br />
This page intentionally left blank<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
52 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 5 New, Changed, Removed Database Columns<br />
Reporting View Columns<br />
Section 5 New, Changed, Removed Database Columns<br />
The following table contains a list of new, changed and removed reporting view columns and composite table columns.<br />
Reporting View Columns<br />
Reporting View Action Dropped/Renamed Column - Old Name Added/Renamed Column - New Name<br />
ACADEMIC_OUTCOME Added CURRICULUM_ORDER<br />
ACADEMIC_OUTCOME Added CURRICULUM_PRIORITY_NUMBER<br />
ACADEMIC_OUTCOME Added FOURTH_MINOR<br />
ACADEMIC_OUTCOME Added FOURTH_MINOR_DESC<br />
ACADEMIC_STUDY Added CURRICULUM_PRIORITY_NUMBER<br />
ACADEMIC_STUDY Added FOURTH_MINOR<br />
ACADEMIC_STUDY Added FOURTH_MINOR_DESC<br />
ADDRESS_PREFERRED Added PHONE_AREA<br />
ADDRESS_PREFERRED Added PHONE_COMMENT<br />
ADDRESS_PREFERRED Added PHONE_EXT<br />
ADDRESS_PREFERRED Added PHONE_INTL_ACCESS<br />
ADDRESS_PREFERRED Added PHONE_NUMBER<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
53 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 5 New, Changed, Removed Database Columns<br />
Reporting View Columns<br />
Reporting View Action Dropped/Renamed Column - Old Name Added/Renamed Column - New Name<br />
ADDRESS_PREFERRED Added PHONE_NUMBER_COMBINED<br />
ADDRESS_PREFERRED Added PHONE_PRIMARY_IND<br />
ADDRESS_PREFERRED Added PHONE_SEQ_NUMBER<br />
ADDRESS_PREFERRED Added PHONE_STATUS_IND<br />
ADDRESS_PREFERRED Added PHONE_TYPE<br />
ADDRESS_PREFERRED Added PHONE_TYPE_DESC<br />
ADDRESS_PREFERRED Added PHONE_UNLIST_IND<br />
ADMISSIONS_APPLICATION Added CURRICULUM_ORDER<br />
ADMISSIONS_APPLICATION Added CURRICULUM_PRIORITY_NUMBER<br />
ADMISSIONS_APPLICATION Added FOURTH_MINOR<br />
ADMISSIONS_APPLICATION Added FOURTH_MINOR_DESC<br />
APPL_OF_PAY_DETAIL_ACCOUNTING<br />
APPL_OF_PAY_DETAIL_ACCOUNTING<br />
APPL_OF_PAY_DETAIL_ACCOUNTING<br />
APPL_OF_PAY_DETAIL_ACCOUNTING<br />
Added<br />
View<br />
Added<br />
View<br />
Added<br />
View<br />
Added<br />
View<br />
ACCOUNT_POSTING_STATUS<br />
ACCOUNT_UID<br />
ADMINISTRATIVE_GROUP<br />
APPLIED_AMOUNT<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
54 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 5 New, Changed, Removed Database Columns<br />
Reporting View Columns<br />
Reporting View Action Dropped/Renamed Column - Old Name Added/Renamed Column - New Name<br />
APPL_OF_PAY_DETAIL_ACCOUNTING<br />
APPL_OF_PAY_DETAIL_ACCOUNTING<br />
APPL_OF_PAY_DETAIL_ACCOUNTING<br />
APPL_OF_PAY_DETAIL_ACCOUNTING<br />
APPL_OF_PAY_DETAIL_ACCOUNTING<br />
APPL_OF_PAY_DETAIL_ACCOUNTING<br />
APPL_OF_PAY_DETAIL_ACCOUNTING<br />
APPL_OF_PAY_DETAIL_ACCOUNTING<br />
APPL_OF_PAY_DETAIL_ACCOUNTING<br />
APPL_OF_PAY_DETAIL_ACCOUNTING<br />
APPL_OF_PAY_DETAIL_ACCOUNTING<br />
Added<br />
View<br />
Added<br />
View<br />
Added<br />
View<br />
Added<br />
View<br />
Added<br />
View<br />
Added<br />
View<br />
Added<br />
View<br />
Added<br />
View<br />
Added<br />
View<br />
Added<br />
View<br />
Added<br />
View<br />
APPLIED_DATE<br />
CHARGE_ACCOUNT<br />
CHARGE_ACCOUNT_DESC<br />
CHARGE_ACCOUNT_EXTERNAL<br />
CHARGE_ACTIVITY<br />
CHARGE_ACTIVITY_DESC<br />
CHARGE_CHART_OF_ACCOUNTS<br />
CHARGE_CHART_OF_ACCOUNTS_DES<br />
C<br />
CHARGE_DETAIL_CODE<br />
CHARGE_DETAIL_CODE_DESC<br />
CHARGE_DETAIL_CODE_TYPE<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
55 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 5 New, Changed, Removed Database Columns<br />
Reporting View Columns<br />
Reporting View Action Dropped/Renamed Column - Old Name Added/Renamed Column - New Name<br />
APPL_OF_PAY_DETAIL_ACCOUNTING<br />
APPL_OF_PAY_DETAIL_ACCOUNTING<br />
APPL_OF_PAY_DETAIL_ACCOUNTING<br />
APPL_OF_PAY_DETAIL_ACCOUNTING<br />
APPL_OF_PAY_DETAIL_ACCOUNTING<br />
APPL_OF_PAY_DETAIL_ACCOUNTING<br />
APPL_OF_PAY_DETAIL_ACCOUNTING<br />
APPL_OF_PAY_DETAIL_ACCOUNTING<br />
APPL_OF_PAY_DETAIL_ACCOUNTING<br />
APPL_OF_PAY_DETAIL_ACCOUNTING<br />
APPL_OF_PAY_DETAIL_ACCOUNTING<br />
Added<br />
View<br />
Added<br />
View<br />
Added<br />
View<br />
Added<br />
View<br />
Added<br />
View<br />
Added<br />
View<br />
Added<br />
View<br />
Added<br />
View<br />
Added<br />
View<br />
Added<br />
View<br />
Added<br />
View<br />
CHARGE_FUND<br />
CHARGE_FUND_DESC<br />
CHARGE_LOCATION<br />
CHARGE_LOCATION_DESC<br />
CHARGE_OPERATING_DESIGNATOR<br />
CHARGE_ORGANIZATION<br />
CHARGE_ORGANIZATION_DESC<br />
CHARGE_PERCENT<br />
CHARGE_PROGRAM<br />
CHARGE_PROGRAM_DESC<br />
CHARGE_RULE_CLASS<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
56 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 5 New, Changed, Removed Database Columns<br />
Reporting View Columns<br />
Reporting View Action Dropped/Renamed Column - Old Name Added/Renamed Column - New Name<br />
APPL_OF_PAY_DETAIL_ACCOUNTING<br />
APPL_OF_PAY_DETAIL_ACCOUNTING<br />
APPL_OF_PAY_DETAIL_ACCOUNTING<br />
APPL_OF_PAY_DETAIL_ACCOUNTING<br />
APPL_OF_PAY_DETAIL_ACCOUNTING<br />
APPL_OF_PAY_DETAIL_ACCOUNTING<br />
APPL_OF_PAY_DETAIL_ACCOUNTING<br />
APPL_OF_PAY_DETAIL_ACCOUNTING<br />
APPL_OF_PAY_DETAIL_ACCOUNTING<br />
APPL_OF_PAY_DETAIL_ACCOUNTING<br />
APPL_OF_PAY_DETAIL_ACCOUNTING<br />
Added<br />
View<br />
Added<br />
View<br />
Added<br />
View<br />
Added<br />
View<br />
Added<br />
View<br />
Added<br />
View<br />
Added<br />
View<br />
Added<br />
View<br />
Added<br />
View<br />
Added<br />
View<br />
Added<br />
View<br />
CHARGE_RULE_CLASS_DESC<br />
CHARGE_TRAN_NUMBER<br />
DIRECT_PAY_IND<br />
ID<br />
MULTI_SOURCE<br />
MULTI_SOURCE_DESC<br />
NAME<br />
PAY_ACCOUNT<br />
PAY_ACCOUNT_DESC<br />
PAY_ACCOUNT_EXTERNAL<br />
PAY_ACTIVITY<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
57 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 5 New, Changed, Removed Database Columns<br />
Reporting View Columns<br />
Reporting View Action Dropped/Renamed Column - Old Name Added/Renamed Column - New Name<br />
APPL_OF_PAY_DETAIL_ACCOUNTING<br />
APPL_OF_PAY_DETAIL_ACCOUNTING<br />
APPL_OF_PAY_DETAIL_ACCOUNTING<br />
APPL_OF_PAY_DETAIL_ACCOUNTING<br />
APPL_OF_PAY_DETAIL_ACCOUNTING<br />
APPL_OF_PAY_DETAIL_ACCOUNTING<br />
APPL_OF_PAY_DETAIL_ACCOUNTING<br />
APPL_OF_PAY_DETAIL_ACCOUNTING<br />
APPL_OF_PAY_DETAIL_ACCOUNTING<br />
APPL_OF_PAY_DETAIL_ACCOUNTING<br />
APPL_OF_PAY_DETAIL_ACCOUNTING<br />
Added<br />
View<br />
Added<br />
View<br />
Added<br />
View<br />
Added<br />
View<br />
Added<br />
View<br />
Added<br />
View<br />
Added<br />
View<br />
Added<br />
View<br />
Added<br />
View<br />
Added<br />
View<br />
Added<br />
View<br />
PAY_ACTIVITY_DESC<br />
PAY_CHART_OF_ACCOUNTS<br />
PAY_CHART_OF_ACCOUNTS_DESC<br />
PAY_DETAIL_CODE<br />
PAY_DETAIL_CODE_DESC<br />
PAY_DETAIL_CODE_TYPE<br />
PAY_FUND<br />
PAY_FUND_DESC<br />
PAY_LOCATION<br />
PAY_LOCATION_DESC<br />
PAY_OPERATING_DESIGNATOR<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
58 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 5 New, Changed, Removed Database Columns<br />
Reporting View Columns<br />
Reporting View Action Dropped/Renamed Column - Old Name Added/Renamed Column - New Name<br />
APPL_OF_PAY_DETAIL_ACCOUNTING<br />
APPL_OF_PAY_DETAIL_ACCOUNTING<br />
APPL_OF_PAY_DETAIL_ACCOUNTING<br />
APPL_OF_PAY_DETAIL_ACCOUNTING<br />
APPL_OF_PAY_DETAIL_ACCOUNTING<br />
APPL_OF_PAY_DETAIL_ACCOUNTING<br />
APPL_OF_PAY_DETAIL_ACCOUNTING<br />
APPL_OF_PAY_DETAIL_ACCOUNTING<br />
APPL_OF_PAY_DETAIL_ACCOUNTING<br />
APPL_OF_PAY_DETAIL_ACCOUNTING<br />
APPL_OF_PAY_DETAIL_ACCOUNTING<br />
Added<br />
View<br />
Added<br />
View<br />
Added<br />
View<br />
Added<br />
View<br />
Added<br />
View<br />
Added<br />
View<br />
Added<br />
View<br />
Added<br />
View<br />
Added<br />
View<br />
Added<br />
View<br />
Added<br />
View<br />
PAY_ORGANIZATION<br />
PAY_ORGANIZATION_DESC<br />
PAY_PERCENT<br />
PAY_PROGRAM<br />
PAY_PROGRAM_DESC<br />
PAY_RULE_CLASS<br />
PAY_RULE_CLASS_DESC<br />
PAY_TRAN_NUMBER<br />
POSTING_DATE<br />
POSTING_DOCUMENT<br />
PROCESS_GROUP<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
59 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 5 New, Changed, Removed Database Columns<br />
Reporting View Columns<br />
Reporting View Action Dropped/Renamed Column - Old Name Added/Renamed Column - New Name<br />
APPL_OF_PAY_DETAIL_ACCOUNTING<br />
Added<br />
View<br />
REAPPLICATION_IND<br />
APPLICATION_OF_PAYMENT Added CHARGE_DETAIL_CODE<br />
APPLICATION_OF_PAYMENT Added CHARGE_DETAIL_CODE_DESC<br />
APPLICATION_OF_PAYMENT Added CHARGE_DETAIL_CODE_TYPE<br />
APPLICATION_OF_PAYMENT Added CHARGE_OPERATING_DESIGNATOR<br />
APPLICATION_OF_PAYMENT Added PAY_DETAIL_CODE<br />
APPLICATION_OF_PAYMENT Added PAY_DETAIL_CODE_DESC<br />
APPLICATION_OF_PAYMENT Added PAY_DETAIL_CODE_TYPE<br />
APPLICATION_OF_PAYMENT Added PAY_OPERATING_DESIGNATOR<br />
AWARD_DISBURSEMENT Dropped FEDERAL_GRANT_DISBURSED<br />
AWARD_DISBURSEMENT Dropped FEDERAL_LOAN_DISBURSED<br />
AWARD_DISBURSEMENT Dropped FEDERAL_SCHOLARSHIP_DISBURSED<br />
AWARD_DISBURSEMENT Dropped FEDERAL_WORK_DISBURSED<br />
AWARD_DISBURSEMENT Dropped INST_GRANT_DISBURSED<br />
AWARD_DISBURSEMENT Dropped INST_LOAN_DISBURSED<br />
AWARD_DISBURSEMENT Dropped INST_SCHOLARSHIP_DISBURSED<br />
AWARD_DISBURSEMENT Dropped INST_WORK_DISBURSED<br />
AWARD_DISBURSEMENT Dropped OTHER_GRANT_DISBURSED<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
60 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 5 New, Changed, Removed Database Columns<br />
Reporting View Columns<br />
Reporting View Action Dropped/Renamed Column - Old Name Added/Renamed Column - New Name<br />
AWARD_DISBURSEMENT Dropped OTHER_LOAN_DISBURSED<br />
AWARD_DISBURSEMENT Dropped OTHER_SCHOLARSHIP_DISBURSED<br />
AWARD_DISBURSEMENT Dropped OTHER_WORK_DISBURSED<br />
AWARD_DISBURSEMENT Dropped STATE_GRANT_DISBURSED<br />
AWARD_DISBURSEMENT Dropped STATE_LOAN_DISBURSED<br />
AWARD_DISBURSEMENT Dropped STATE_SCHOLARSHIP_DISBURSED<br />
AWARD_DISBURSEMENT Dropped STATE_WORK_DISBURSED<br />
BUDGET_AVAILABILITY_LEDGER Added FUND_FINANCIAL_MANAGER_NAME<br />
BUDGET_AVAILABILITY_LEDGER Added ORGN_FINANCIAL_MANAGER_NAME<br />
BUDGET_DETAIL Added FUND_FINANCIAL_MANAGER_NAME<br />
BUDGET_DETAIL Added ORGN_FINANCIAL_MANAGER_NAME<br />
CALENDAR_DATE_HIERARCHY<br />
CALENDAR_DATE_HIERARCHY<br />
CALENDAR_DATE_HIERARCHY<br />
CALENDAR_DATE_HIERARCHY<br />
Added<br />
View<br />
Added<br />
View<br />
Added<br />
View<br />
Added<br />
View<br />
ADMINISTRATIVE_GROUP<br />
CALENDAR_DATE<br />
CALENDAR_DAY<br />
CALENDAR_DAY_OF_WEEK<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
61 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 5 New, Changed, Removed Database Columns<br />
Reporting View Columns<br />
Reporting View Action Dropped/Renamed Column - Old Name Added/Renamed Column - New Name<br />
CALENDAR_DATE_HIERARCHY<br />
CALENDAR_DATE_HIERARCHY<br />
CALENDAR_DATE_HIERARCHY<br />
CALENDAR_DATE_HIERARCHY<br />
CALENDAR_DATE_HIERARCHY<br />
CALENDAR_DATE_HIERARCHY<br />
CALENDAR_DATE_HIERARCHY<br />
Added<br />
View<br />
Added<br />
View<br />
Added<br />
View<br />
Added<br />
View<br />
Added<br />
View<br />
Added<br />
View<br />
Added<br />
View<br />
CALENDAR_MONTH<br />
CALENDAR_MONTH_ABBREV<br />
CALENDAR_MONTH_DESC<br />
CALENDAR_YEAR<br />
MULTI_SOURCE<br />
MULTI_SOURCE_DESC<br />
PROCESS_GROUP<br />
COMMUNICATION Added ACTIVITY_DATE<br />
CONSTITUENT Added CURRENT_AGE<br />
CONSTITUENT Added EMAIL_PREFERRED_ADDRESS<br />
CONSTITUENT Added GENDER<br />
CONSTITUENT Added GENDER_DESC<br />
EMPLOYEE_POSITION Added POSITION_CURRENT_IND<br />
ENDOWMENT_SUMMARY<br />
Dropped<br />
View<br />
ACCOUNT<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
62 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 5 New, Changed, Removed Database Columns<br />
Reporting View Columns<br />
Reporting View Action Dropped/Renamed Column - Old Name Added/Renamed Column - New Name<br />
ENDOWMENT_SUMMARY<br />
ENDOWMENT_SUMMARY<br />
ENDOWMENT_SUMMARY<br />
ENDOWMENT_SUMMARY<br />
ENDOWMENT_SUMMARY<br />
ENDOWMENT_SUMMARY<br />
ENDOWMENT_SUMMARY<br />
ENDOWMENT_SUMMARY<br />
ENDOWMENT_SUMMARY<br />
ENDOWMENT_SUMMARY<br />
ENDOWMENT_SUMMARY<br />
Dropped<br />
View<br />
Dropped<br />
View<br />
Dropped<br />
View<br />
Dropped<br />
View<br />
Dropped<br />
View<br />
Dropped<br />
View<br />
Dropped<br />
View<br />
Dropped<br />
View<br />
Dropped<br />
View<br />
Dropped<br />
View<br />
Dropped<br />
View<br />
ACCOUNT_DESC<br />
ADMINISTRATIVE_GROUP<br />
BOOK_AMOUNT<br />
CHART_OF_ACCOUNTS<br />
CHART_OF_ACCOUNTS_DESC<br />
ENDOWMENT_FUND_LD<br />
ENDOWMENT_POOL<br />
ENDOWMENT_POOL_DESC<br />
FUND<br />
FUND_DESC<br />
MULTI_SOURCE<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
63 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 5 New, Changed, Removed Database Columns<br />
Reporting View Columns<br />
Reporting View Action Dropped/Renamed Column - Old Name Added/Renamed Column - New Name<br />
ENDOWMENT_SUMMARY<br />
ENDOWMENT_SUMMARY<br />
ENDOWMENT_SUMMARY<br />
ENDOWMENT_SUMMARY<br />
ENDOWMENT_SUMMARY<br />
ENDOWMENT_SUMMARY<br />
ENDOWMENT_SUMMARY<br />
ENDOWMENT_SUMMARY<br />
Dropped<br />
View<br />
Dropped<br />
View<br />
Dropped<br />
View<br />
Dropped<br />
View<br />
Dropped<br />
View<br />
Dropped<br />
View<br />
Dropped<br />
View<br />
Dropped<br />
View<br />
MULTI_SOURCE_DESC<br />
ORGANIZATION_CODE<br />
ORGANIZATION_DESC<br />
PROCESS_GROUP<br />
PROGRAM<br />
PROGRAM_DESC<br />
UNITIZATION_PERIOD_END_DATE<br />
UNITS_PURCHASED<br />
ENDOWMENT_UNITS Added ENTITY_NAME<br />
FINAID_FUND Added FEDERAL_GRANT_DISBURSED<br />
FINAID_FUND Added FEDERAL_LOAN_DISBURSED<br />
FINAID_FUND Added FEDERAL_SCHOLARSHIP_DISBURSED<br />
FINAID_FUND Added FEDERAL_WORK_DISBURSED<br />
FINAID_FUND Added INST_GRANT_DISBURSED<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
64 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 5 New, Changed, Removed Database Columns<br />
Reporting View Columns<br />
Reporting View Action Dropped/Renamed Column - Old Name Added/Renamed Column - New Name<br />
FINAID_FUND Added INST_LOAN_DISBURSED<br />
FINAID_FUND Added INST_SCHOLARSHIP_DISBURSED<br />
FINAID_FUND Added INST_WORK_DISBURSED<br />
FINAID_FUND Added OTHER_GRANT_DISBURSED<br />
FINAID_FUND Added OTHER_LOAN_DISBURSED<br />
FINAID_FUND Added OTHER_SCHOLARSHIP_DISBURSED<br />
FINAID_FUND Added OTHER_WORK_DISBURSED<br />
FINAID_FUND Added STATE_GRANT_DISBURSED<br />
FINAID_FUND Added STATE_LOAN_DISBURSED<br />
FINAID_FUND Added STATE_SCHOLARSHIP_DISBURSED<br />
FINAID_FUND Added STATE_WORK_DISBURSED<br />
FIXED_ASSET_ACCOUNTING_SOURCE Added FUND_FINANCIAL_MANAGER_NAME<br />
FIXED_ASSET_ACCOUNTING_SOURCE Added ORGN_FINANCIAL_MANAGER_NAME<br />
FIXED_ASSET_FUNDING_SOURCE Added FUND_FINANCIAL_MANAGER_NAME<br />
FIXED_ASSET_FUNDING_SOURCE Added ORGN_FINANCIAL_MANAGER_NAME<br />
GENERAL_LEDGER Added FUND_FINANCIAL_MANAGER_NAME<br />
GOVERNMENT_ACADEMIC_OUTCOME Renamed PRIMARY_ETHNCITY PRIMARY_ETHNICITY<br />
GOVERNMENT_ACADEMIC_OUTCOME Renamed PRIMARY_ETHNCITY_CATEGORY PRIM_ETHNICITY_CATEGORY<br />
GOVERNMENT_ACADEMIC_OUTCOME Renamed PRIMARY_ETHNCITY_CATEGORY_DESC PRIM_ETHNICITY_CATEGORY_DESC<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
65 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 5 New, Changed, Removed Database Columns<br />
Reporting View Columns<br />
Reporting View Action Dropped/Renamed Column - Old Name Added/Renamed Column - New Name<br />
GOVERNMENT_ACADEMIC_OUTCOME Added FOURTH_MINOR<br />
GOVERNMENT_ACADEMIC_OUTCOME Added FOURTH_MINOR_DESC<br />
GOVERNMENT_ADMISSIONS Renamed PRIMARY_ETHNCITY PRIMARY_ETHNICITY<br />
GOVERNMENT_ADMISSIONS Renamed PRIMARY_ETHNCITY_CATEGORY PRIM_ETHNICITY_CATEGORY<br />
GOVERNMENT_ADMISSIONS Renamed PRIMARY_ETHNCITY_CATEGORY_DESC PRIM_ETHNICITY_CATEGORY_DESC<br />
GOVERNMENT_ADMISSIONS Added CURRICULUM_ORDER<br />
GOVERNMENT_FINANCIAL_AID Renamed PRIMARY_ETHNCITY PRIMARY_ETHNICITY<br />
GOVERNMENT_FINANCIAL_AID Renamed PRIMARY_ETHNCITY_CATEGORY PRIM_ETHNICITY_CATEGORY<br />
GOVERNMENT_FINANCIAL_AID Renamed PRIMARY_ETHNCITY_CATEGORY_DESC PRIM_ETHNICITY_CATEGORY_DESC<br />
GOVERNMENT_STUDENT Renamed PRIMARY_ETHNCITY PRIMARY_ETHNICITY<br />
GOVERNMENT_STUDENT Renamed PRIMARY_ETHNCITY_CATEGORY PRIM_ETHNICITY_CATEGORY<br />
GOVERNMENT_STUDENT Renamed PRIMARY_ETHNCITY_CATEGORY_DESC PRIM_ETHNICITY_CATEGORY_DESC<br />
GOVERNMENT_STUDENT Added FOURTH_MINOR<br />
GOVERNMENT_STUDENT Added FOURTH_MINOR_DESC<br />
GRANT_FUND Added FUND_FINANCIAL_MANAGER_NAME<br />
GRANT_FUND Added PRINCIPAL_INVESTIGATOR_NAME<br />
GRANT_VIEW Added ORGN_FINANCIAL_MANAGER_NAME<br />
GRANT_VIEW Added PRINCIPAL_INVESTIGATOR_NAME<br />
INVOICE_ACCOUNTING Added FUND_FINANCIAL_MANAGER_ID<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
66 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 5 New, Changed, Removed Database Columns<br />
Reporting View Columns<br />
Reporting View Action Dropped/Renamed Column - Old Name Added/Renamed Column - New Name<br />
INVOICE_ACCOUNTING Added FUND_FINANCIAL_MANAGER_NAME<br />
INVOICE_ACCOUNTING Added FUND_FINANCIAL_MANAGER_UID<br />
INVOICE_ACCOUNTING Added ORGN_FINANCIAL_MANAGER_ID<br />
INVOICE_ACCOUNTING Added ORGN_FINANCIAL_MANAGER_NAME<br />
INVOICE_ACCOUNTING Added ORGN_FINANCIAL_MANAGER_UID<br />
LEAVE_BALANCE Added POSITION<br />
LEAVE_BALANCE Added POSITION_TITLE<br />
LEAVE_BALANCE Added SUFFIX<br />
OPERATING_LEDGER Added FUND_FINANCIAL_MANAGER_NAME<br />
OPERATING_LEDGER Added ORGN_FINANCIAL_MANAGER_NAME<br />
ORGANIZATION_HIERARCHY Added FINANCIAL_MANAGER_NAME<br />
PERSON_DETAIL Renamed PRIMARY_ETHNCITY_CATEGORY PRIM_ETHNICITY_CATEGORY<br />
PERSON_DETAIL Renamed PRIMARY_ETHNCITY_CATEGORY_DESC PRIM_ETHNICITY_CATEGORY_DESC<br />
PURCHASE_ORDER_ACCOUNTING Added FUND_FINANCIAL_MANAGER_ID<br />
PURCHASE_ORDER_ACCOUNTING Added FUND_FINANCIAL_MANAGER_NAME<br />
PURCHASE_ORDER_ACCOUNTING Added FUND_FINANCIAL_MANAGER_UID<br />
PURCHASE_ORDER_ACCOUNTING Added ORGN_FINANCIAL_MANAGER_ID<br />
PURCHASE_ORDER_ACCOUNTING Added ORGN_FINANCIAL_MANAGER_NAME<br />
PURCHASE_ORDER_ACCOUNTING Added ORGN_FINANCIAL_MANAGER_UID<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
67 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 5 New, Changed, Removed Database Columns<br />
Reporting View Columns<br />
Reporting View Action Dropped/Renamed Column - Old Name Added/Renamed Column - New Name<br />
RECEIVABLE_ACCOUNTING Added A_RULE_CLASS_DESC1<br />
RECEIVABLE_ACCOUNTING Added A_RULE_CLASS_DESC2<br />
RECEIVABLE_ACCOUNTING Added A_RULE_CLASS_DESC3<br />
RECEIVABLE_ACCOUNTING Added A_RULE_CLASS1<br />
RECEIVABLE_ACCOUNTING Added A_RULE_CLASS2<br />
RECEIVABLE_ACCOUNTING Added A_RULE_CLASS3<br />
RECEIVABLE_ACCOUNTING Added B_RULE_CLASS_DESC1<br />
RECEIVABLE_ACCOUNTING Added B_RULE_CLASS_DESC2<br />
RECEIVABLE_ACCOUNTING Added B_RULE_CLASS_DESC3<br />
RECEIVABLE_ACCOUNTING Added B_RULE_CLASS1<br />
RECEIVABLE_ACCOUNTING Added B_RULE_CLASS2<br />
RECEIVABLE_ACCOUNTING Added B_RULE_CLASS3<br />
RECRUITMENT_INFORMATION Added CURRICULUM_ORDER<br />
RECRUITMENT_INFORMATION Added CURRICULUM_PRIORITY_NUMBER<br />
RECRUITMENT_INFORMATION Added FOURTH_MINOR<br />
RECRUITMENT_INFORMATION Added FOURTH_MINOR_DESC<br />
RELATIONSHIP Renamed MARRIAGE_STATUS_IND SPOUSE_STATUS<br />
RELATIONSHIP Renamed PRIMARY_IND COMBINED_MAILING_PRIORITY<br />
RELATIONSHIP Renamed RELATED_ADDRESS_TYPE RELATED_CHILD_ADDR_TYPE<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
68 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 5 New, Changed, Removed Database Columns<br />
Reporting View Columns<br />
Reporting View Action Dropped/Renamed Column - Old Name Added/Renamed Column - New Name<br />
RELATIONSHIP Renamed RELATED_ADDRESS_TYPE_DESC RELATED_CHILD_ADDR_TYPE_DESC<br />
RELATIONSHIP Renamed RELATED_TAX_ID RELATED_CHILD_TAX_ID<br />
RELATIONSHIP Renamed RELATION_TYPE_IND RELATION_SOURCE<br />
RELATIONSHIP Added COMBINED_MAILING_PRIORITY_DESC<br />
RELATIONSHIP Added ENTITY_IND<br />
RELATIONSHIP Added HOUSEHOLD_IND<br />
RELATIONSHIP Added RELATED_ENTITY_IND<br />
RELATIONSHIP Added RELATED_MATCHING_GIFT_ID<br />
RELATIONSHIP Added RELATED_MATCHING_GIFT_NAME<br />
RELATIONSHIP Added RELATED_MATCHING_GIFT_UID<br />
RELATIONSHIP Added RELATION_SOURCE_DESC<br />
RELATIONSHIP Added SPOUSE_STATUS_DESC<br />
STUDENT_COHORT_SLOT Dropped ACADEMIC_PERIOD_END<br />
STUDENT_COHORT_SLOT Dropped ACADEMIC_PERIOD_START<br />
STUDENT_COHORT_SLOT Added ACADEMIC_PERIOD<br />
STUDENT_COHORT_SLOT Added ACADEMIC_PERIOD_DESC<br />
STUDENT_COURSE Added LAST_ATTEND_DATE<br />
STUDENT_COURSE_ATT_SLOT Added COURSE_REFERENCE_NUMBER<br />
STUDENT_COURSE_ATTRIBUTE Added COURSE_REFERENCE_NUMBER<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
69 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 5 New, Changed, Removed Database Columns<br />
Reporting View Columns<br />
Reporting View Action Dropped/Renamed Column - Old Name Added/Renamed Column - New Name<br />
STUDENT_COURSE_GRADE_CHANGE Added COURSE_REFERENCE_NUMBER<br />
TELEPHONE_PREFERRED<br />
TELEPHONE_PREFERRED<br />
TELEPHONE_PREFERRED<br />
TELEPHONE_PREFERRED<br />
TELEPHONE_PREFERRED<br />
TELEPHONE_PREFERRED<br />
TELEPHONE_PREFERRED<br />
TELEPHONE_PREFERRED<br />
TELEPHONE_PREFERRED<br />
TELEPHONE_PREFERRED<br />
TELEPHONE_PREFERRED<br />
Dropped<br />
View<br />
Dropped<br />
View<br />
Dropped<br />
View<br />
Dropped<br />
View<br />
Dropped<br />
View<br />
Dropped<br />
View<br />
Dropped<br />
View<br />
Dropped<br />
View<br />
Dropped<br />
View<br />
Dropped<br />
View<br />
Dropped<br />
View<br />
ADDRESS_NUMBER<br />
ADDRESS_TYPE<br />
ADDRESS_TYPE_DESC<br />
ADMINISTRATIVE_GROUP<br />
ENTITY_UID<br />
ID<br />
MULTI_SOURCE<br />
MULTI_SOURCE_DESC<br />
NAME<br />
PHONE_AREA<br />
PHONE_COMMENT<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
70 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 5 New, Changed, Removed Database Columns<br />
Reporting View Columns<br />
Reporting View Action Dropped/Renamed Column - Old Name Added/Renamed Column - New Name<br />
TELEPHONE_PREFERRED<br />
TELEPHONE_PREFERRED<br />
TELEPHONE_PREFERRED<br />
TELEPHONE_PREFERRED<br />
TELEPHONE_PREFERRED<br />
TELEPHONE_PREFERRED<br />
TELEPHONE_PREFERRED<br />
TELEPHONE_PREFERRED<br />
TELEPHONE_PREFERRED<br />
TELEPHONE_PREFERRED<br />
TELEPHONE_PREFERRED<br />
Dropped<br />
View<br />
Dropped<br />
View<br />
Dropped<br />
View<br />
Dropped<br />
View<br />
Dropped<br />
View<br />
Dropped<br />
View<br />
Dropped<br />
View<br />
Dropped<br />
View<br />
Dropped<br />
View<br />
Dropped<br />
View<br />
Dropped<br />
View<br />
PHONE_EXT<br />
PHONE_INTL_ACCESS<br />
PHONE_NUMBER<br />
PHONE_NUMBER_COMBINED<br />
PHONE_PRIMARY_IND<br />
PHONE_SEQ_NUMBER<br />
PHONE_STATUS_IND<br />
PHONE_TYPE<br />
PHONE_TYPE_DESC<br />
PHONE_UNLIST_IND<br />
PROCESS_GROUP<br />
TRANSACTION_HISTORY Added ACCOUNT_POOL<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
71 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 5 New, Changed, Removed Database Columns<br />
Reporting View Columns<br />
Reporting View Action Dropped/Renamed Column - Old Name Added/Renamed Column - New Name<br />
TRANSACTION_HISTORY Added ACCOUNT_POOL_DESC<br />
TRANSACTION_HISTORY Added FUND_FINANCIAL_MANAGER_ID<br />
TRANSACTION_HISTORY Added FUND_FINANCIAL_MANAGER_NAME<br />
TRANSACTION_HISTORY Added FUND_FINANCIAL_MANAGER_UID<br />
TRANSACTION_HISTORY Added GRANT_DESC<br />
TRANSACTION_HISTORY Added GRANT_ID<br />
TRANSACTION_HISTORY Added GRANT_STATUS<br />
TRANSACTION_HISTORY Added INTERNAL_ACCOUNT_TYPE<br />
TRANSACTION_HISTORY Added INTERNAL_ACCOUNT_TYPE_DESC<br />
TRANSACTION_HISTORY Added INTERNAL_FUND_TYPE<br />
TRANSACTION_HISTORY Added INTERNAL_FUND_TYPE_DESC<br />
TRANSACTION_HISTORY Added NORMAL_BALANCE<br />
TRANSACTION_HISTORY Added ORGN_FINANCIAL_MANAGER_ID<br />
TRANSACTION_HISTORY Added ORGN_FINANCIAL_MANAGER_NAME<br />
TRANSACTION_HISTORY Added ORGN_FINANCIAL_MANAGER_UID<br />
VALIDATION Added DATA_ENTRY_IND<br />
VALIDATION Added EFFECTIVE_DATE<br />
VALIDATION Added NEXT_CHANGE_DATE<br />
VALIDATION Added QUALIFIER<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
72 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 5 New, Changed, Removed Database Columns<br />
Composite Table Columns<br />
Reporting View Action Dropped/Renamed Column - Old Name Added/Renamed Column - New Name<br />
VALIDATION Added QUALIFIER_DESCRIPTION<br />
VALIDATION Added STATUS<br />
VALIDATION Added STATUS_DESCRIPTION<br />
VALIDATION Added TERMINATION_DATE<br />
Composite Table Columns<br />
Composite Table Action Dropped/Renamed Column - Old Name Added/Renamed Column - New Name<br />
MAT_CONSTITUENT<br />
MAT_CONSTITUENT<br />
MAT_CONSTITUENT<br />
MAT_CONSTITUENT<br />
MAT_CONSTITUENT<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
PERSON_UID<br />
DONOR_IND<br />
PROSPECT_IND<br />
LOST_ALUMNUS_IND<br />
PREF_LAST_NAME<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
73 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 5 New, Changed, Removed Database Columns<br />
Composite Table Columns<br />
Composite Table Action Dropped/Renamed Column - Old Name Added/Renamed Column - New Name<br />
MAT_CONSTITUENT<br />
MAT_CONSTITUENT<br />
MAT_CONSTITUENT<br />
MAT_CONSTITUENT<br />
MAT_CONSTITUENT<br />
MAT_CONSTITUENT<br />
MAT_CONSTITUENT<br />
MAT_CONSTITUENT<br />
MAT_CONSTITUENT<br />
MAT_CONSTITUENT<br />
MAT_CONSTITUENT<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
PREF_FIRST_NAME<br />
PREF_MIDDLE_INITIAL<br />
NICKNAME<br />
GRADUATION_NAME<br />
PARENTS_NAME<br />
MAIDEN_LAST_NAME<br />
PREF_CLASS<br />
PREF_CLASS_DESC<br />
PREF_COLLEGE<br />
PREF_COLLEGE_DESC<br />
PREF_DONOR_CATEGORY<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
74 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 5 New, Changed, Removed Database Columns<br />
Composite Table Columns<br />
Composite Table Action Dropped/Renamed Column - Old Name Added/Renamed Column - New Name<br />
MAT_CONSTITUENT<br />
MAT_CONSTITUENT<br />
MAT_CONSTITUENT<br />
MAT_CONSTITUENT<br />
MAT_CONSTITUENT<br />
MAT_CONSTITUENT<br />
MAT_CONSTITUENT<br />
MAT_CONSTITUENT<br />
MAT_CONSTITUENT<br />
MAT_CONSTITUENT<br />
MAT_CONSTITUENT<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
PREF_DONOR_CATEGORY_DESC<br />
HOMETOWN<br />
HOMETOWN_STATE<br />
HOMETOWN_STATE_DESC<br />
HOMETOWN_NATION<br />
HOMETOWN_NATION_DESC<br />
OCCUPATIONAL_TITLE<br />
OCCUPATIONAL_TITLE_DESC<br />
INCOME_LEVEL<br />
INCOME_LEVEL_DESC<br />
SOCIETY_NAME<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
75 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 5 New, Changed, Removed Database Columns<br />
Composite Table Columns<br />
Composite Table Action Dropped/Renamed Column - Old Name Added/Renamed Column - New Name<br />
MAT_CONSTITUENT<br />
MAT_CONSTITUENT<br />
MAT_CONSTITUENT<br />
MAT_CONSTITUENT<br />
MAT_CONSTITUENT<br />
MAT_CONSTITUENT<br />
MAT_CONSTITUENT<br />
MAT_CONSTITUENT<br />
MAT_CONSTITUENT<br />
MAT_CONSTITUENT<br />
MAT_CONSTITUENT<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
COMBINED_MAILING_NAME<br />
COMB_MAILING_ADDR_TYPE<br />
COMB_MAILING_ADDR_TYPE_DESC<br />
ADDRESS_NAME<br />
PREF_ADDR_TYPE<br />
PREF_ADDR_TYPE_DESC<br />
PREF_ADDR_TYPE_GEOR<br />
PREF_ADDR_TYPE_GEOR_DESC<br />
LIFE_TOTAL_GIVING<br />
MOST_RECENT_GIFT_NUMBER<br />
MOST_RECENT_GIFT_DATE<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
76 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 5 New, Changed, Removed Database Columns<br />
Composite Table Columns<br />
Composite Table Action Dropped/Renamed Column - Old Name Added/Renamed Column - New Name<br />
MAT_CONSTITUENT<br />
MAT_CONSTITUENT<br />
MAT_CONSTITUENT<br />
MAT_CONSTITUENT<br />
MAT_CONSTITUENT<br />
MAT_CONSTITUENT<br />
MAT_CONSTITUENT<br />
MAT_CONSTITUENT<br />
MAT_CONSTITUENT<br />
MAT_CONSTITUENT<br />
MAT_CONSTITUENT<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
MOST_RECENT_GIFT_AMT<br />
LIFE_TOTAL_PLEDGE_AMT<br />
MOST_RECENT_PLEDGE_NUMBER<br />
MOST_RECENT_PLEDGE_DATE<br />
MOST_RECENT_PLEDGE_AMT<br />
LIFE_TOTAL_PLEDGE_PAY<br />
LIFE_GIFT_SOCIETY_TYPE<br />
LIFE_GIFT_SOCIETY_TYPE_DESC<br />
LIFE_GIFT_SOCIETY<br />
LIFE_GIFT_SOCIETY_DESC<br />
LIFE_TOTAL_COMMITMENT<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
77 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 5 New, Changed, Removed Database Columns<br />
Composite Table Columns<br />
Composite Table Action Dropped/Renamed Column - Old Name Added/Renamed Column - New Name<br />
MAT_CONSTITUENT<br />
MAT_CONSTITUENT<br />
MAT_CONSTITUENT<br />
MAT_CONSTITUENT<br />
MAT_CONSTITUENT<br />
MAT_CONSTITUENT<br />
MAT_CONSTITUENT<br />
MAT_CONSTITUENT<br />
MAT_CONSTITUENT<br />
MAT_CONSTITUENT<br />
MAT_CONSTITUENT<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
HIGHEST_GIFT_NUMBER<br />
HIGHEST_GIFT_AMOUNT<br />
HIGHEST_GIFT_DATE<br />
HIGHEST_GIFT_FISCAL_YEAR<br />
HIGHEST_GIFT_FISCAL_YEAR_DESC<br />
MIF_VALUE<br />
MIF_DESC<br />
ZONE_VALUE<br />
DOMAIN_VALUE<br />
LAST_ACTIVITY_DATE<br />
LAST_DML_DATE<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
78 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 5 New, Changed, Removed Database Columns<br />
Composite Table Columns<br />
Composite Table Action Dropped/Renamed Column - Old Name Added/Renamed Column - New Name<br />
MAT_CONSTITUENT<br />
MAT_ORGANIZATIONAL_CONSTITUENT<br />
MAT_ORGANIZATIONAL_CONSTITUENT<br />
MAT_ORGANIZATIONAL_CONSTITUENT<br />
MAT_ORGANIZATIONAL_CONSTITUENT<br />
MAT_ORGANIZATIONAL_CONSTITUENT<br />
MAT_ORGANIZATIONAL_CONSTITUENT<br />
MAT_ORGANIZATIONAL_CONSTITUENT<br />
MAT_ORGANIZATIONAL_CONSTITUENT<br />
MAT_ORGANIZATIONAL_CONSTITUENT<br />
MAT_ORGANIZATIONAL_CONSTITUENT<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
LAST_ACTIVITY_DML<br />
ENTITY_UID<br />
DONOR_IND<br />
PROSPECT_IND<br />
FEDERAL_IDENTIFICATION<br />
BUSINESS<br />
STANDARD_INDUSTRY<br />
STANDARD_INDUSTRY_DESC<br />
MATCHING_GIFT_PERCENT<br />
MAX_YEAR_DONATE_AMOUNT<br />
MAX_PERSON_MATCH_AMOUNT<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
79 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 5 New, Changed, Removed Database Columns<br />
Composite Table Columns<br />
Composite Table Action Dropped/Renamed Column - Old Name Added/Renamed Column - New Name<br />
MAT_ORGANIZATIONAL_CONSTITUENT<br />
MAT_ORGANIZATIONAL_CONSTITUENT<br />
MAT_ORGANIZATIONAL_CONSTITUENT<br />
MAT_ORGANIZATIONAL_CONSTITUENT<br />
MAT_ORGANIZATIONAL_CONSTITUENT<br />
MAT_ORGANIZATIONAL_CONSTITUENT<br />
MAT_ORGANIZATIONAL_CONSTITUENT<br />
MAT_ORGANIZATIONAL_CONSTITUENT<br />
MAT_ORGANIZATIONAL_CONSTITUENT<br />
MAT_ORGANIZATIONAL_CONSTITUENT<br />
MAT_ORGANIZATIONAL_CONSTITUENT<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
PREF_ADDRESS_TYPE<br />
PREF_ADDRESS_TYPE_DESC<br />
JOB_CATEGORY<br />
JOB_CATEGORY_DESC<br />
MATCHING_GIFT_UID<br />
MATCH_MINIMUM<br />
MATCH_MAXIMUM<br />
MAX_MATCH_ORG_EMPL_YEAR<br />
MULTIPLE_RATIOS_IND<br />
PRIMARY_DONOR_CATEGORY<br />
PRIMARY_DONOR_CATEGORY_DESC<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
80 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 5 New, Changed, Removed Database Columns<br />
Composite Table Columns<br />
Composite Table Action Dropped/Renamed Column - Old Name Added/Renamed Column - New Name<br />
MAT_ORGANIZATIONAL_CONSTITUENT<br />
MAT_ORGANIZATIONAL_CONSTITUENT<br />
MAT_ORGANIZATIONAL_CONSTITUENT<br />
MAT_ORGANIZATIONAL_CONSTITUENT<br />
MAT_ORGANIZATIONAL_CONSTITUENT<br />
MAT_ORGANIZATIONAL_CONSTITUENT<br />
MAT_ORGANIZATIONAL_CONSTITUENT<br />
MAT_ORGANIZATIONAL_CONSTITUENT<br />
MAT_ORGANIZATIONAL_CONSTITUENT<br />
MAT_ORGANIZATIONAL_CONSTITUENT<br />
MAT_ORGANIZATIONAL_CONSTITUENT<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
LIFE_TOTAL_GIVING<br />
MOST_RECENT_GIFT_NUMBER<br />
MOST_RECENT_GIFT_DATE<br />
MOST_RECENT_GIFT_AMT<br />
LIFE_TOTAL_PLEDGE_AMT<br />
MOST_RECENT_PLEDGE_NUMBER<br />
MOST_RECENT_PLEDGE_DATE<br />
MOST_RECENT_PLEDGE_AMT<br />
LIFE_TOTAL_PLEDGE_PAY<br />
LIFE_GIFT_SOCIETY_TYPE<br />
LIFE_GIFT_SOCIETY_TYPE_DESC<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
81 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 5 New, Changed, Removed Database Columns<br />
Composite Table Columns<br />
Composite Table Action Dropped/Renamed Column - Old Name Added/Renamed Column - New Name<br />
MAT_ORGANIZATIONAL_CONSTITUENT<br />
MAT_ORGANIZATIONAL_CONSTITUENT<br />
MAT_ORGANIZATIONAL_CONSTITUENT<br />
MAT_ORGANIZATIONAL_CONSTITUENT<br />
MAT_ORGANIZATIONAL_CONSTITUENT<br />
MAT_ORGANIZATIONAL_CONSTITUENT<br />
MAT_ORGANIZATIONAL_CONSTITUENT<br />
MAT_ORGANIZATIONAL_CONSTITUENT<br />
MAT_ORGANIZATIONAL_CONSTITUENT<br />
MAT_ORGANIZATIONAL_CONSTITUENT<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
Dropped<br />
Table<br />
LIFE_GIFT_SOCIETY<br />
LIFE_GIFT_SOCIETY_DESC<br />
LIFE_TOTAL_COMMITMENT<br />
MIF_VALUE<br />
MIF_DESC<br />
ZONE_VALUE<br />
DOMAIN_VALUE<br />
LAST_ACTIVITY_DATE<br />
LAST_DML_DATE<br />
LAST_ACTIVITY_DML<br />
MAT_RELATION Renamed MARRIAGE_STATUS_IND SPOUSE_STATUS<br />
MAT_RELATION Renamed PRIMARY_IND COMBINED_MAILING_PRIORITY<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
82 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 5 New, Changed, Removed Database Columns<br />
Composite Table Columns<br />
Composite Table Action Dropped/Renamed Column - Old Name Added/Renamed Column - New Name<br />
MAT_RELATION Renamed RELATED_ADDRESS_DESC RELATED_CHILD_ADDR_TYPE_DESC<br />
MAT_RELATION Renamed RELATED_ADDRESS_TYPE RELATED_CHILD_ADDR_TYPE<br />
MAT_RELATION Renamed RELATED_TAX_ID RELATED_CHILD_TAX_ID<br />
MAT_RELATION Renamed RELATION_TYPE RELATION_SOURCE<br />
MAT_RELATION Added COMBINED_MAILING_PRIORITY_DESC<br />
MAT_RELATION Added HOUSEHOLD_IND<br />
MAT_RELATION Added RELATION_SOURCE_DESC<br />
MAT_RELATION Added SPOUSE_STATUS_DESC<br />
MGT_CALENDAR_DATE_HIERARCHY<br />
MGT_CALENDAR_DATE_HIERARCHY<br />
MGT_CALENDAR_DATE_HIERARCHY<br />
MGT_CALENDAR_DATE_HIERARCHY<br />
MGT_CALENDAR_DATE_HIERARCHY<br />
MGT_CALENDAR_DATE_HIERARCHY<br />
Added<br />
Table<br />
Added<br />
Table<br />
Added<br />
Table<br />
Added<br />
Table<br />
Added<br />
Table<br />
Added<br />
Table<br />
CALENDAR_DATE<br />
CALENDAR_YEAR<br />
CALENDAR_MONTH<br />
CALENDAR_MONTH_ABBREV<br />
CALENDAR_MONTH_DESC<br />
CALENDAR_DAY<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
83 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 5 New, Changed, Removed Database Columns<br />
Composite Table Columns<br />
Composite Table Action Dropped/Renamed Column - Old Name Added/Renamed Column - New Name<br />
MGT_CALENDAR_DATE_HIERARCHY<br />
MGT_CALENDAR_DATE_HIERARCHY<br />
MGT_CALENDAR_DATE_HIERARCHY<br />
MGT_CALENDAR_DATE_HIERARCHY<br />
MGT_CALENDAR_DATE_HIERARCHY<br />
MGT_CALENDAR_DATE_HIERARCHY<br />
MGT_CALENDAR_DATE_HIERARCHY<br />
MGT_CALENDAR_DATE_HIERARCHY<br />
Added<br />
Table<br />
Added<br />
Table<br />
Added<br />
Table<br />
Added<br />
Table<br />
Added<br />
Table<br />
Added<br />
Table<br />
Added<br />
Table<br />
Added<br />
Table<br />
CALENDAR_DAY_OF_WEEK<br />
MIF_VALUE<br />
MIF_DESC<br />
ZONE_VALUE<br />
DOMAIN_VALUE<br />
LAST_ACTIVITY_DATE<br />
LAST_DML_DATE<br />
LAST_ACTIVITY_DML<br />
MGT_VALIDATION Added DATA_ENTRY_IND<br />
MGT_VALIDATION Added EFFECTIVE_DATE<br />
MGT_VALIDATION Added NEXT_CHANGE_DATE<br />
MGT_VALIDATION Added QUALIFIER<br />
MGT_VALIDATION Added QUALIFIER_DESCRIPTION<br />
MGT_VALIDATION Added STATUS<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
84 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 5 New, Changed, Removed Database Columns<br />
Composite Table Columns<br />
Composite Table Action Dropped/Renamed Column - Old Name Added/Renamed Column - New Name<br />
MGT_VALIDATION Added STATUS_DESCRIPTION<br />
MGT_VALIDATION Added TERMINATION_DATE<br />
MPT_LEAVE_BALANCE Added POSITION<br />
MPT_LEAVE_BALANCE Added SUFFIX<br />
MPT_YEARLY_DEDUCT<br />
MPT_YEARLY_DEDUCT<br />
MPT_YEARLY_DEDUCT<br />
MPT_YEARLY_DEDUCT<br />
MPT_YEARLY_DEDUCT<br />
MPT_YEARLY_DEDUCT<br />
MPT_YEARLY_DEDUCT<br />
MPT_YEARLY_DEDUCT<br />
MPT_YEARLY_DEDUCT<br />
Added<br />
Table<br />
Added<br />
Table<br />
Added<br />
Table<br />
Added<br />
Table<br />
Added<br />
Table<br />
Added<br />
Table<br />
Added<br />
Table<br />
Added<br />
Table<br />
Added<br />
Table<br />
APPLICABLE_GROSS_QTR1<br />
APPLICABLE_GROSS_QTR2<br />
APPLICABLE_GROSS_QTR3<br />
APPLICABLE_GROSS_QTR4<br />
CARRIER<br />
CARRIER_DESC<br />
DOMAIN_VALUE<br />
EMPLOYEE_CONTRIBUTION_QTR1<br />
EMPLOYEE_CONTRIBUTION_QTR2<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
85 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 5 New, Changed, Removed Database Columns<br />
Composite Table Columns<br />
Composite Table Action Dropped/Renamed Column - Old Name Added/Renamed Column - New Name<br />
MPT_YEARLY_DEDUCT<br />
MPT_YEARLY_DEDUCT<br />
MPT_YEARLY_DEDUCT<br />
MPT_YEARLY_DEDUCT<br />
MPT_YEARLY_DEDUCT<br />
MPT_YEARLY_DEDUCT<br />
MPT_YEARLY_DEDUCT<br />
MPT_YEARLY_DEDUCT<br />
MPT_YEARLY_DEDUCT<br />
MPT_YEARLY_DEDUCT<br />
MPT_YEARLY_DEDUCT<br />
Added<br />
Table<br />
Added<br />
Table<br />
Added<br />
Table<br />
Added<br />
Table<br />
Added<br />
Table<br />
Added<br />
Table<br />
Added<br />
Table<br />
Added<br />
Table<br />
Added<br />
Table<br />
Added<br />
Table<br />
Added<br />
Table<br />
EMPLOYEE_CONTRIBUTION_QTR3<br />
EMPLOYEE_CONTRIBUTION_QTR4<br />
EMPLOYEE_CONTRIBUTION_YTD<br />
EMPLOYER_CONTRIBUTION_QTR1<br />
EMPLOYER_CONTRIBUTION_QTR2<br />
EMPLOYER_CONTRIBUTION_QTR3<br />
EMPLOYER_CONTRIBUTION_QTR4<br />
EMPLOYER_CONTRIBUTION_YTD<br />
GROSS_COMPENSATION_YTD<br />
MIF_DESC<br />
MIF_VALUE<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
86 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 5 New, Changed, Removed Database Columns<br />
Composite Table Columns<br />
Composite Table Action Dropped/Renamed Column - Old Name Added/Renamed Column - New Name<br />
MPT_YEARLY_DEDUCT<br />
MPT_YEARLY_DEDUCT<br />
MPT_YEARLY_DEDUCT<br />
Added<br />
Table<br />
Added<br />
Table<br />
Added<br />
Table<br />
PAYROLL_DEDUCTION_YEAR<br />
PERSON_UID<br />
ZONE_VALUE<br />
MRT_AWARD_DISBURSEMENT Dropped FEDERAL_GRANT_DISBURSED<br />
MRT_AWARD_DISBURSEMENT Dropped FEDERAL_LOAN_DISBURSED<br />
MRT_AWARD_DISBURSEMENT Dropped FEDERAL_SCHOLARSHIP_DISBURSED<br />
MRT_AWARD_DISBURSEMENT Dropped FEDERAL_WORK_DISBURSED<br />
MRT_AWARD_DISBURSEMENT Dropped INST_GRANT_DISBURSED<br />
MRT_AWARD_DISBURSEMENT Dropped INST_LOAN_DISBURSED<br />
MRT_AWARD_DISBURSEMENT Dropped INST_SCHOLARSHIP_DISBURSED<br />
MRT_AWARD_DISBURSEMENT Dropped INST_WORK_DISBURSED<br />
MRT_AWARD_DISBURSEMENT Dropped OTHER_GRANT_DISBURSED<br />
MRT_AWARD_DISBURSEMENT Dropped OTHER_LOAN_DISBURSED<br />
MRT_AWARD_DISBURSEMENT Dropped OTHER_SCHOLARSHIP_DISBURSED<br />
MRT_AWARD_DISBURSEMENT Dropped OTHER_WORK_DISBURSED<br />
MRT_AWARD_DISBURSEMENT Dropped STATE_GRANT_DISBURSED<br />
MRT_AWARD_DISBURSEMENT Dropped STATE_LOAN_DISBURSED<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
87 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 5 New, Changed, Removed Database Columns<br />
Composite Table Columns<br />
Composite Table Action Dropped/Renamed Column - Old Name Added/Renamed Column - New Name<br />
MRT_AWARD_DISBURSEMENT Dropped STATE_SCHOLARSHIP_DISBURSED<br />
MRT_AWARD_DISBURSEMENT Dropped STATE_WORK_DISBURSED<br />
MRT_FINAID_FUND Added FEDERAL_GRANT_DISBURSED<br />
MRT_FINAID_FUND Added FEDERAL_LOAN_DISBURSED<br />
MRT_FINAID_FUND Added FEDERAL_SCHOLARSHIP_DISBURSED<br />
MRT_FINAID_FUND Added FEDERAL_WORK_DISBURSED<br />
MRT_FINAID_FUND Added INST_GRANT_DISBURSED<br />
MRT_FINAID_FUND Added INST_LOAN_DISBURSED<br />
MRT_FINAID_FUND Added INST_SCHOLARSHIP_DISBURSED<br />
MRT_FINAID_FUND Added INST_WORK_DISBURSED<br />
MRT_FINAID_FUND Added OTHER_GRANT_DISBURSED<br />
MRT_FINAID_FUND Added OTHER_LOAN_DISBURSED<br />
MRT_FINAID_FUND Added OTHER_SCHOLARSHIP_DISBURSED<br />
MRT_FINAID_FUND Added OTHER_WORK_DISBURSED<br />
MRT_FINAID_FUND Added STATE_GRANT_DISBURSED<br />
MRT_FINAID_FUND Added STATE_LOAN_DISBURSED<br />
MRT_FINAID_FUND Added STATE_SCHOLARSHIP_DISBURSED<br />
MRT_FINAID_FUND Added STATE_WORK_DISBURSED<br />
MST_ACADEMIC_OUTCOME Added CURRICULUM_ORDER<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
88 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 5 New, Changed, Removed Database Columns<br />
Composite Table Columns<br />
Composite Table Action Dropped/Renamed Column - Old Name Added/Renamed Column - New Name<br />
MST_ACADEMIC_OUTCOME Added CURRICULUM_PRIORITY<br />
MST_ACADEMIC_OUTCOME Added FOURTH_MINOR<br />
MST_ACADEMIC_OUTCOME Added FOURTH_MINOR_DESC<br />
MST_ACADEMIC_STANDING Dropped CURRENT_DATE<br />
MST_ACADEMIC_STANDING Dropped DEANS_LIST_DATE<br />
MST_ACADEMIC_STANDING Dropped DEANS_LIST_DESC<br />
MST_ACADEMIC_STANDING Dropped DEANS_LIST_VALUE<br />
MST_ACADEMIC_STANDING Dropped ENROLLMENT_EXISTS_IND<br />
MST_ACADEMIC_STANDING Dropped GRADE_MAILER_CHG_DATE<br />
MST_ACADEMIC_STANDING Dropped GRADE_MAILER_DUP<br />
MST_ACADEMIC_STANDING Dropped GRADE_MAILER_DUP_DATE<br />
MST_ACADEMIC_STANDING Dropped GRADE_MAILING_DATE<br />
MST_ACADEMIC_STANDING Dropped PRE_CATALOG_IND<br />
MST_ACADEMIC_STANDING Dropped RECORD_SOURCE_IND<br />
MST_ACADEMIC_STANDING Dropped RECORD_STATUS_DATE<br />
MST_ACADEMIC_STANDING Dropped RECORD_STATUS_IND<br />
MST_ACADEMIC_STANDING Dropped SPECIAL_EXAM_CREDIT<br />
MST_ACADEMIC_STANDING Dropped SPECIAL_EXAM_DESC<br />
MST_ACADEMIC_STANDING Dropped TRANSFER_TO_INSTITUTION<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
89 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 5 New, Changed, Removed Database Columns<br />
Composite Table Columns<br />
Composite Table Action Dropped/Renamed Column - Old Name Added/Renamed Column - New Name<br />
MST_ACADEMIC_STANDING Dropped TRANSFER_TO_INSTITUTION_DESC<br />
MST_ACADEMIC_STANDING Dropped WITHDRAWAL_REASON<br />
MST_ACADEMIC_STANDING Dropped WITHDRAWAL_REASON_DESC<br />
MST_ACADEMIC_STANDING Added STUDENT_LEVEL<br />
MST_ACADEMIC_STANDING Added STUDENT_LEVEL_DESC<br />
MST_ACADEMIC_STANDING Added ACADEMIC_STAND_OVERRIDE<br />
MST_ACADEMIC_STANDING Added ACADEMIC_STAND_OVERRIDE_DESC<br />
MST_ACADEMIC_STANDING Added ACADEMIC_STANDING<br />
MST_ACADEMIC_STANDING Added ACADEMIC_STANDING_DATE<br />
MST_ACADEMIC_STANDING Added ACADEMIC_STANDING_DESC<br />
MST_ACADEMIC_STANDING Added PROGRESS_EVAL_OVERRIDE<br />
MST_ACADEMIC_STANDING Added PROGRESS_EVAL_OVERRIDE_DESC<br />
MST_ACADEMIC_STANDING Added PROGRESS_EVALUATION_END<br />
MST_ACADEMIC_STANDING Added PROGRESS_EVALUATION_END_DESC<br />
MST_ACADEMIC_STANDING Added PROGRESS_EVALUATION_END_DATE<br />
MST_ACADEMIC_STANDING Added COMB_ACAD_STAND_OVERRIDE<br />
MST_ACADEMIC_STANDING Added COMB_ACAD_STAND_OVERRIDE_DESC<br />
MST_ACADEMIC_STANDING Added COMBINED_ACAD_STAND_END<br />
MST_ACADEMIC_STANDING Added COMBINED_ACAD_STAND_END_DATE<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
90 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 5 New, Changed, Removed Database Columns<br />
Composite Table Columns<br />
Composite Table Action Dropped/Renamed Column - Old Name Added/Renamed Column - New Name<br />
MST_ACADEMIC_STANDING Added COMBINED_ACAD_STAND_END_DESC<br />
MST_ACADEMIC_STANDING Added LAST_ACTIVITY_DATE<br />
MST_ACADEMIC_STANDING Added LAST_DML_DATE<br />
MST_ACADEMIC_STANDING Added LAST_ACTIVITY_DML<br />
MST_ADMISSIONS_APPLICATION Added CURRICULUM_ORDER<br />
MST_ADMISSIONS_APPLICATION Added CURRICULUM_PRIORITY<br />
MST_ADMISSIONS_APPLICATION Added FOURTH_MINOR<br />
MST_ADMISSIONS_APPLICATION Added FOURTH_MINOR_DESC<br />
MST_ENROLLMENT Dropped ACADEMIC_OUTCOME_ENROLLED_IN<br />
D<br />
MST_ENROLLMENT Added DEANS_LIST_DATE<br />
MST_ENROLLMENT Added DEANS_LIST_DESC<br />
MST_ENROLLMENT Added DEANS_LIST_VALUE<br />
MST_ENROLLMENT Added ENROLLMENT_EXISTS_IND<br />
MST_ENROLLMENT Added GRADE_MAILER_CHG_DATE<br />
MST_ENROLLMENT Added GRADE_MAILER_DUP<br />
MST_ENROLLMENT Added GRADE_MAILER_DUP_DATE<br />
MST_ENROLLMENT Added GRADE_MAILING_DATE<br />
MST_ENROLLMENT Added PRE_CATALOG_IND<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
91 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 5 New, Changed, Removed Database Columns<br />
Composite Table Columns<br />
Composite Table Action Dropped/Renamed Column - Old Name Added/Renamed Column - New Name<br />
MST_ENROLLMENT Added RECORD_SOURCE_IND<br />
MST_ENROLLMENT Added RECORD_STATUS_DATE<br />
MST_ENROLLMENT Added RECORD_STATUS_IND<br />
MST_ENROLLMENT Added SPECIAL_EXAM_CREDIT<br />
MST_ENROLLMENT Added SPECIAL_EXAM_DESC<br />
MST_ENROLLMENT Added TRANSFER_TO_INSTITUTION<br />
MST_ENROLLMENT Added TRANSFER_TO_INSTITUTION_DESC<br />
MST_ENROLLMENT Added WITHDRAWAL_REASON<br />
MST_ENROLLMENT Added WITHDRAWAL_REASON_DESC<br />
MST_GENERAL_STUDENT Dropped ACAD_STANDING_ACAD_PERIOD_DESC<br />
MST_GENERAL_STUDENT Dropped ACADEMIC_STANDING<br />
MST_GENERAL_STUDENT Dropped ACADEMIC_STANDING_ACAD_PERIOD<br />
MST_GENERAL_STUDENT Dropped ACADEMIC_STANDING_DESC<br />
MST_GENERAL_STUDENT Dropped COMB_ACAD_STANDING_TERM_DESC<br />
MST_GENERAL_STUDENT Dropped COMBINED_ACAD_STANDING_DESC<br />
MST_GENERAL_STUDENT Dropped COMBINED_ACAD_STANDING_TERM<br />
MST_GENERAL_STUDENT Dropped COMBINED_ACADEMIC_STANDING<br />
MST_GENERAL_STUDENT Dropped PROGRESS_EVALUATION<br />
MST_GENERAL_STUDENT Dropped PROGRESS_EVALUATION_DESC<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
92 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 5 New, Changed, Removed Database Columns<br />
Composite Table Columns<br />
Composite Table Action Dropped/Renamed Column - Old Name Added/Renamed Column - New Name<br />
MST_GENERAL_STUDENT Dropped STUDENT_CLASS_FIRST_DESC<br />
MST_GENERAL_STUDENT Dropped STUDENT_CLASSIFICATION_FIRST<br />
MST_GENERAL_STUDENT Added CURRICULUM_PRIORITY<br />
MST_GENERAL_STUDENT Added FOURTH_MINOR<br />
MST_GENERAL_STUDENT Added FOURTH_MINOR_DESC<br />
MST_RECRUITMENT_INFORMATION Added CURRICULUM_PRIORITY<br />
MST_RECRUITMENT_INFORMATION Added FOURTH_MINOR<br />
MST_RECRUITMENT_INFORMATION Added FOURTH_MINOR_DESC<br />
MST_STUDENT_COURSE Added LAST_ATTEND_DATE<br />
MST_STUDENT_COHORT_SLOT Dropped ACADEMIC_PERIOD_END<br />
MST_STUDENT_COHORT_SLOT Dropped ACADEMIC_PERIOD_START<br />
MST_STUDENT_COHORT_SLOT Added ACADEMIC_PERIOD<br />
MST_STUDENT_COHORT_SLOT Added ACADEMIC_PERIOD_DESC<br />
MST_STUDENT_COURSE_ATT_SLOT Added COURSE_REFERENCE_NUMBER<br />
MST_STUDENT_COURSE_ATTRIBUTE Added COURSE_REFERENCE_NUMBER<br />
MST_STUDENT_COURSE_GRADE_CHG Added COURSE_REFERENCE_NUMBER<br />
MTT_LEDGER_ACCOUNTING Added A_RULE_CLASS_DESC1<br />
MTT_LEDGER_ACCOUNTING Added A_RULE_CLASS_DESC2<br />
MTT_LEDGER_ACCOUNTING Added A_RULE_CLASS_DESC3<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
93 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 5 New, Changed, Removed Database Columns<br />
Composite Table Columns<br />
Composite Table Action Dropped/Renamed Column - Old Name Added/Renamed Column - New Name<br />
MTT_LEDGER_ACCOUNTING Added A_RULE_CLASS1<br />
MTT_LEDGER_ACCOUNTING Added A_RULE_CLASS2<br />
MTT_LEDGER_ACCOUNTING Added A_RULE_CLASS3<br />
MTT_LEDGER_ACCOUNTING Added B_RULE_CLASS_DESC1<br />
MTT_LEDGER_ACCOUNTING Added B_RULE_CLASS_DESC2<br />
MTT_LEDGER_ACCOUNTING Added B_RULE_CLASS_DESC3<br />
MTT_LEDGER_ACCOUNTING Added B_RULE_CLASS1<br />
MTT_LEDGER_ACCOUNTING Added B_RULE_CLASS2<br />
MTT_LEDGER_ACCOUNTING Added B_RULE_CLASS3<br />
Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />
94 <strong>Release</strong> <strong>Guide</strong> Confidential