Decision Support Release Notes. Release 2.0

Transcription

1 Decision Support Release Notes Release Financial Aid Budget Total Current Information Indicator Financial Aid Yearly Award & Gross Paid Amount Security for Person Records Student Recruiting & Admissions Administrative College Code and Name Objects Data Mart Security View Modification Security for Recruiting & Admissions Records... 4 DS_Release_Notes_ A.doc Page 1 of 5

2 1. Financial Aid 1.1 Budget Total Case Number: ProdLog #104 General Description: The Total Budget Amount object (found in the Budget Information subclass of the Financial Aid Needs Analysis class) previously pulled data from an incorrect table location. Reports using the Total Budget Amount object displayed a row for each Budget Component, instead of a single row for the Budget Total. The Total Budget Amount object has been modified to pull data from the correct source. Reports using the Total Budget Amount object will now return correct results. Technical Description: The Budget Total object incorrectly pulled the Budget Component amount data from the T_FA_STUDENT_BUDG_COMPNT.FA_STUDENT_BUDG_COMPNT_AMT table. The Budget Total object has been corrected to pull data from the T_FA_STUDENT_BUDG_TOT.FA_STUDENT_BUDG_TOT_AMT table. 1.2 Current Information Indicator Case Number: ProdLog #89 General Description: The Current Information Indicator object was inaccurately named. This object is in fact a Current Record Indicator. While a Current Information Indicator in the Data Warehouse is used to assist in record change tracking is used, the Current Record Indicator serves a different purpose. To avoid any confusion, this object has been renamed Current Record Indicator. Technical Description: Current Information Indicator object has been renamed to Current Record Indicator. The source table and column of this object remain unchanged. 1.3 Financial Aid Yearly Award Table & Gross Paid Amount Object Case Number: ProdLog #100 General Description: The Gross Paid Amount object is a value derived specifically for the EDW and is based on Banner data. This object also requires aggregation to the Year level. There was an error in the processing logic for the Data Warehouse yearly awards table, which excluded certain source system records when calculating this value. The excluded records were those records where there was no corresponding term record in the Banner source system. Approximately 600 records were not loaded from the Banner yearly award tables. These missing records therefore did not appear in reports based on Gross Paid Amount. The absence of these 600 records meant that the Gross Paid Amount object was not calculated correctly. The processing logic for the EDW has been modified to correct this problem, and the Data Warehouse now matches the Banner source system, as required by the Financial Aid Office and the UI-Integrate team. DS_Release_Notes_ A.doc Page 2 of 5

3 Please note, in accordance with business requirements identified by the Financial Aid Offices and UI-Integrate, the Financial Aid EDW has been designed to source Year- and Term-based Award records directly from the Banner source tables. The effect of this design is that any discrepancies between the Year- and Term-based Award records in the source system will be reflected in the EDW. In business terms, this means that Year data is not necessarily a true aggregate of Term data. Technical Description: An error in processing logic caused the T_FA_AWARD table to not be loaded with all records that existed in the Banner source system. This resulted in approximately 600 records not being loaded from the Banner yearly award tables. Certain records in the source system were excluded if there were no corresponding term records in the source system. Because the GROSS_PAID_AMT value relies on aggregated yearly award records, some records may have been excluded from reports based on GROSS_PAID_AMT. The ETL join logic has been modified to correct this problem, and the Data Warehouse now matches the Banner source system, as required by the Financial Aid Office and the UI-Integrate team. Please note, in accordance with business requirements identified by the Financial Aid Offices and UI-Integrate, the Financial Aid EDW has been designed to source Year- and Term-based Award records directly from the Banner source tables. The effect of this design is that any discrepancies between the Year- and Term-based Award records in the source system will be reflected in the EDW. In business terms, this means that Year data is not necessarily a true aggregate of Term data. 1.4 Security for Person Records Case Number: ProdLog #117 General Description: Previously, a security view did not exist on the Person History table for Financial Aid. Certain users could therefore view Person data that should have been restricted in accordance with University policy, specifically records for persons who were not students or financial aid applicants. Security has been applied to this table so that Financial Aid users will only be able to view Person records for students. Technical Description: Security was not previously applied to the T_PERS_HIST table in the Financial Aid universe. A new view (V_STU_PERS_HIST) has been created to ensure that all columns from T_PERS_HIST are included, while restricting rows to only those records that also have records in T_STUDENT_HIST. In addition, the Financial Aid user role has been modified to replace the access to T_PERS_HIST with access to V_STU_PERS_HIST in accordance with University policy. Users connecting via ODBC should ensure that they connect to this data using the new V_STU_PERS_HIST view. This change will not affect a user s ability to view Person records for students and financial aid applicants. DS_Release_Notes_ A.doc Page 3 of 5

4 2. Student Recruiting & Admissions 2.1 Administrative College Code and Name Objects EDW Current Applicant Case Number: Clarify _57 General Description: The Administrative College Code and Name objects were erroneously removed from the Current Applicant universe on 30 May When the omission was reported on 20 June 2003, they were immediately replaced. The objects have been re-added to the Current Applicant universe, and are now available for reporting and analysis purposes. Technical Description: Objects have been added to the Current Applicant universe. 2.2 Data Mart Security View Modification EDW - Undergrad Admissions Data Mart EDW - Grad Admissions Data Mart EDW - RA Contact Analysis Data Mart Case Number: Clarify _208 General Description: The security in the Recruiting & Admissions Data Marts erroneously restricted users from viewing application records for applicants who applied to multiple colleges in some cases. If the person applied for more than one college, only one of the colleges was able to see that application (the college that matched the application college). In other words, users with security restrictions to one college sometimes were unable to view application information for their college if the applicant had applied to more than one college. Security indicators have been changed to allow users to view application records for students who have applied to multiple colleges. This fix has been implemented in the Data Warehouse, and users are now able to view all application records to their college. Technical Description: While students may apply to multiple colleges, only a single college is listed per applicant on the T_DM_RECRUIT_APPLICANT table. The result is multiple application records with different colleges, but a single T_DM_RECRUIT_APPLICANT record which lists only one college. When this college differed from the one to which a user had security access, users were unable to view the application information. A new view of the T_DM_RECRUIT_APPLICANT table has been created and the Data Mart universes have been modified to use the view instead of the table itself. This fix has been implemented, and users are now able to access all application records to their college. 2.3 Security for Recruiting & Admissions Records EDW - Current Applicant EDW Current Recruit EDW Graduate Data Mart EDW Undergraduate Data Mart EDW RA Contact Analysis Data Mart Case Number: ProdLog #82 DS_Release_Notes_ A.doc Page 4 of 5

5 General Description: As originally designed, the Recruiting & Admissions security implementation applies person-level security, preventing one campus from seeing applicant or recruit records for another campus. However, for students who applied to more than one campus, each campus the students applied to was previously able to see certain information related to the students applications to other campuses, such as test scores and student attributes. Security on affected tables has been extended to the campus level to prevent this occurrence in the future. Technical Description: The following new security views have been created to apply campuslevel security to the underlying tables. These views prevent one campus from viewing applicant and recruit records for another campus. V_ADM_APPL_ATTR_HIST V_ADM_APPL_SRC_HIST V_ADM_CHKLST_ITEM_HIST V_ADM_DECN_HIST V_ADM_MAIL V_ADM_PRIOR_CUM_DEG_HIST V_ADM_RATING_HIST V_ADM_STD_HS_HIST V_ADM_STD_HS_SUBJ V_RECRUIT_ADM_STD_HS_HIST V_RECRUIT_ADM_STD_HS_SUBJ V_RECRUIT_ATTR V_RECRUIT_LEARN_OF_UI V_RECRUIT_MAIL V_RECRUIT_PRIOR_CUM_DEG_HIST V_RECRUIT_SRC V_RECRUIT_TEST_RESULT_HIST DS_Release_Notes_ A.doc Page 5 of 5