ODS / Release Guide / 3.1
ODS / Release Guide / 3.1
ODS / Release Guide / 3.1
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
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