ODS / Release Guide / 3.1

More documents

Recommendations

Info

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

Section 4 Problem Resolutions General Miscellaneous Resolution The Purchasing Payable business model within COGNOS Report Studio was corrected by removing the relationship between the Purchase Order Item and Purchase Order Accounting, and then adding a new relationship between the Purchase Order and Purchase Order Accounting. To clarify the joins between the Purchase Order Item and Purchase Order Accounting, filters were added to define PO Document Level Accounting Record and PO Commodity Level Accounting Record. The old Document Level Accounting Record filter was renamed Invoice Document Level Accounting Record filter. A new Invoice Commodity Level Accounting Record filter was added. These assist in clarifying the joins between Item records and Accounting records when the document is utilizing Document Level Accounting versus Commodity Level Accounting. Additionally, the Invoice Payable business model within COGNOS Report Studio had its filter between the Invoice Item and Invoice Accounting record renamed for consistency. The Document Level Accounting Record filter was renamed Invoice Document Level Accounting Record and a new filter was added called Invoice Commodity Level Accounting Record filter. 1-IYRU7 Impact Several fields in various ODS views were inappropriately allowed to remain a length of varchar2(4000). This occurred when the columns were created via functions or calculations. The majority of these fields should have been a varchar2(1). Leaving these fields at varchar2(4000) created various problems when trying to report upon them. Resolution Added SUBSTR to all fields that were varchar2(4000) other than comments or text. 1-K25N5 Impact Cognos Changes: 1. The Government Student -> Government Financial Aid relationship needs to be removed in the Government Reporting business view. 2. Institution is missing from the Admissions Application and Recruitment Information business views. 3. Student (ORA-00904 "SITE_STREET_LINE4": invalid identifier") The Student view in the EUL and model has not been updated for 3.0 changes. 4. The join between Student and GPA By Level shouldn’t include ACADEMIC_PERIOD, only the PERSON_UID. ACADEMIC_PERIOD is NULL. See the BANINST1.AS_GPA_LEVEL view. 5. Join between TRANSACTION_HISTORY and OPERATING_LEDGER is incorrect. IT is missing the join between COMMITMENT_IND and the join between location and activity is incorrect. The problem will exist in both the Operational Data Store Release 3.1 April 2007 48 Release Guide Confidential
Section 4 Problem Resolutions General Miscellaneous OPERATING_LEDGER Business Concept and the TRANSACTION_HISTORY Business Concept. The following statement should be used in its entirety. OL = operating_leger, TH = TRANSACTION_HISTORY. join where OL.Chart_Of_Accounts = TH.Chart_Of_Accounts AND OL.Fiscal_Year = TH.Fiscal_Year and OL.Fiscal_Period = TH.Posting_Period and OL.Fund = TH.Fund and OL.Organization_Code = TH.Organization_Code and OL.Account = TH.Account and OL.Program = TH.Program and OL.Activity = NVL(TH.Activity,' ' ) OL.Location = NVL(TH.Location,' ') OL.Commitment_Type = TH.Commitment_Type Resolution Cognos Changes: 1. The Government Student -> Government Financial Aid relationship was removed in the Government Reporting business view. 2. Institution was added to the Admissions Application and Recruitment Information business views. 3. Student (ORA-00904 "SITE_STREET_LINE4": invalid identifier") The Student view in the EUL and model has been updated for 3.0 changes. 4. The join between Student and GPA By Level doesn't include ACADEMIC_PERIOD, only the PERSON_UID. ACADEMIC_PERIOD is NULL. See the BANINST1.AS_GPA_LEVEL view. 5. The join between TRANSACTION_HISTORY and OPERATING_LEDGER is corrected. It no longer is missing the join between COMMITMENT_TYPE and the join between location and activity is correct. The problem was fixed in both the Operating Ledger business concept and the TRANSACTION_HISTORY business concept. It was also fixed in the Grant Ledger business concept. The following statement was be used in its entirety. select * from operating_ledger ol, transaction_history th where OL.Chart_Of_Accounts = TH.Chart_Of_Accounts AND OL.Fiscal_Year = TH.Fiscal_Year and April 2007 Operational Data Store Release 3.1 Confidential Release Guide 49
Page 2 and 3: This documentation is proprietary i
Page 4 and 5: Table of Contents New Enrolled & Re
Page 6 and 7: Table of Contents This page intenti
Page 8 and 9: Introduction This page intentionall
Page 10 and 11: Section 1 Functional Enhancements A
Page 12 and 13: Section 1 Functional Enhancements A
Page 14 and 15: Section 1 Functional Enhancements F
Page 16 and 17: Section 1 Functional Enhancements H
Page 18 and 19: Section 1 Functional Enhancements S
Page 20 and 21: Section 1 Functional Enhancements N
Page 22 and 23: Section 2 Miscellaneous Enhancement
Page 24 and 25: Section 2 Miscellaneous Enhancement
Page 26 and 27: Section 3 Documentation Enhancement
Page 28 and 29: Section 4 Problem Resolutions Admin
Page 30 and 31: Section 4 Problem Resolutions Commo
Page 32 and 33: Section 4 Problem Resolutions Commo
Page 34 and 35: Section 4 Problem Resolutions Finan
Page 36 and 37: Section 4 Problem Resolutions Human
Page 38 and 39: Section 4 Problem Resolutions Stude
Page 50 and 51: Section 4 Problem Resolutions Gener
Page 52 and 53: Section 4 Problem Resolutions Gener
Page 54 and 55: Section 5 New, Changed, Removed Dat
Page 94: Section 5 New, Changed, Removed Dat

ODS / Release Guide / 3.1

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

Delete template?

Save as template?