Decision Support Release Notes. Release 7.0

Save this PDF as:
 WORD  PNG  TXT  JPG

Size: px
Start display at page:

Download "Decision Support Release Notes. Release 7.0"

Transcription

1 Decision Support Release Notes Release General Modifications Telephone Number Presentation Citizen Type Code Change Catalog & Schedule Course Description Text & Course Description Effective Date Objects Added Building County Name Addition Section Fee Detail Code Finance Three New Finance Universes Grant Payment Application Tables and Objects New Finance Purchasing Column Additions Human Resources / Payroll Modification to Benefits Deductions Tables Payroll Accounting Detail Category Code Column and Object Added Predefined Condition Code Object Removed Predefined Condition Code Objects Added Employee Birth Date Objects Added Current Hire Date, Position Class Description, Position Class Code Objects Added Accounting Detail Sub-class Access Added to HR Security Roles Current Information Indicator... 9 DS_Release_Notes_ doc Page 1 of 9

2 1. General Modifications 1.1 Telephone Number Presentation Business Objects Universes in multiple data collections EDW Current Applicant EDW Current Recruit EDW HR Deduction Administration EDW HR Employee Administration EDW HR Position and Job Hierarchy Case Number: _388 General Description: Telephone numbers were previously displayed in multiple EDW Universes as straight seven-digit numbers with no breaks (i.e., ). Telephone numbers are now displayed in EDW Universes with hyphen breaks for number prefixes (i.e., ). Area codes are included in a separate data field and are not affected by this change. This change affects the display of historical and current information. Users connecting to the Data Warehouse via an ODBC connection will not be affected by this change. Telephone numbers in EDW tables and columns will continue to be displayed with no breaks (i.e., ). 1.2 Citizen Type Code Change Products Affected: Data Warehouse Tables in multiple data collections Business Objects Universes in multiple data collections Data Mart Graduate Admissions Data Mart Recruiting & Admissions Contact Analysis Data Mart Undergraduate Admissions EDW Current Applicant EDW Current Recruit EDW Current Employee EDW Financial Aid EDW Finance Accounts Receivable EDW Finance Comprehensive EDW Finance Grants EDW Finance Purchasing EDW HR Employee Administration EDW HR Deduction Administration EDW HR Time & Attendance / Payroll HR EDW (Bio-Demo) Case Number: _147 Description: A Person Citizenship Type Code value has been changed from Foreign to International. This change was implemented in the Person History (T_PERS_HIST) table, and in the Citizenship Type Code (T_LKP_CITIZEN_TYPE_CD) table. DS_Release_Notes_ doc Page 2 of 9

3 2. Catalog & Schedule 2.1 Course Description Text & Course Description Effective Date Objects Added Catalog & Schedule Business Objects Universes EDW STU Course Catalog Case Number: _504 Description: Two new objects have been added to the EDW Course Catalog universe. Objects for Course Description and Course Description Effective Date are now available in the Course Listing class. The data for these objects are sourced from the Course Description Text (CRS_DESC_TXT) column and Course Description Effective Date (CRS_DESC_TXT_EFF_DT) column in the Course Description Text (T_CRS_DESC_TXT) table. This data was previously available in the EDW tables and could be accessed through an ODBC connection. The data has now also been included as an object in the Course Catalog universe for use through the Business Objects reporting tools. 2.2 Building County Name Addition Catalog & Schedule EDW Tables None Case Number: _160 Description: A new column for Building County Name (BLDG_COUNTY_NAME) has been added to the Building Definition table (T_BLDG_DEFN) in the Catalog & Schedule EDW. Users connecting to the EDW via an ODBC connection are now able to use Building County Name for reporting and analysis purposes. 2.3 Section Fee Detail Code Catalog & Schedule EDW Tables Catalog & Schedule Business Objects Universes EDW STU Course Schedule Case Number: _481 Description: Previously, when using the Course Schedule universe to perform reporting on sections and their associated section fee details, the results erroneously excluded records with no fees associated (i.e., null values). This exclusion was the result of a combination of factors: 1) an improper join existed between the Section Base table and the Section Fee Detail Code table and 2) some CRN records were missing from the Section Fee table (T_SEC_FEE). The missing CRN values have been added to the Section Fee table (T_SEC_FEE) and are available for use in the universes and through ODBC connections. In addition, the join between the Section Base table and the Section Fee table has been corrected, and reporting on sections and fees will now correctly return results for all sections, including those with no fee associated (null values). DS_Release_Notes_ doc Page 3 of 9

4 3. Finance 3.1 Three New Finance Universes Case Numbers: Finance Business Objects Universes EDW Finance Comprehensive EDW Finance C-FOAPAL EDW Finance Ledgers OL/GL EDW Finance Posted Transaction _328, _339, _353, _385, _391, _1089, _362, _138, _328, _335, _193, _314-1, _210, _218, _222, _226 Description: Decision Support is pleased to announce the availability of 3 new Finance universes. There are now separate universes for C-FOAPAL information, Operating Ledger/General Ledger information, and Posted Transaction information. These universes provide a more targeted subset of the existing Finance-Comprehensive universe, and were developed to provide you with a simplified environment to develop your Finance reports. Testing has revealed that many of the errors and data relationship issues found in the existing Finance-Comprehensive universe have been corrected in these new universes. Additional detailed information, including universe descriptions and mappings, is available on the Universe Information page of the DS Metadata. The Finance Comprehensive universe will continue to be available. Existing reports against the Finance Comprehensive universe will continue to work as before. However, given the improvements these new universes offer, Decision Support strongly recommend that users utilize these new universes for any new reports or queries, and that they redevelop existing reports to work against these new universes as soon as it is convenient. 3.2 Grant Payment Application Tables and Objects Products Affected: Finance EDW Tables Finance Business Objects Universes EDW Finance Grants Case Number: _ _402 Description: The Grant Payment Application table was developed using preliminary information regarding data usage and entry. The Grant Payment Application data is entered into Banner by the Grants and Contracts office, and the intent of the table in the EDW is to allow users to match grant payments to grant billings. Prior to implementation, Decision Support attempted to define a primary key (to define unique rows) based on Banner business rules. However, the usage of this table and related data since Finance go-live has revealed there is no such mechanism to define a unique row in this table. Therefore, the data in this table does not accurately reflect the payments that are applied to sponsor billings. DS_Release_Notes_ doc Page 4 of 9

5 Because of the high potential for inaccurate results using data from this table, the table has been dropped from the EDW. In addition, the Grant Payment Application object class and its two objects have been deleted from the Finance Grants universe have been deleted. This change will affect users using either Business Objects or ODBC connections. 3.3 New Finance Purchasing Column Additions Products Affected: Finance EDW Tables None Case Number: _187 General Description: Two new columns relating to Purchasing have been added to tables in the Finance EDW. The additional columns contain information on Purchase Order Print Date and Requestor Phone Number sourced from the Banner system. Columns have been added to the tables as indicated in the chart below. Users connecting to the EDW via ODBC can begin using this new data for reporting and analysis purposes. Logical Column name Physical Column Name Added to Table Purchase Order Print Date PO_PRINT_DT T_PO Requester Phone Number RQSTR_TELE_AREA_CD RQSTR_TELE_NMR RQSTR_TELE_EXT T_REQ DS_Release_Notes_ doc Page 5 of 9

6 4. Human Resources / Payroll 4.1 Modification to Benefits Deductions Tables HR/Pay EDW Tables None Case Number: Internal Tracking Number 15 Description: The Miscellaneous Deduction History (T_MISC_DED_HIST) table and the Life & Disability Deduction History table (T_LIFE_DISBL_DED_HIST) were not populated with data in the EDW when HR/Pay was implemented on 30 December The tables were unable to be populated due to errors in the Data Warehouse processing logic. The Benefit Deduction Tables are sourced from one main and several adjunct tables from the Banner source system. The Benefits and Payroll offices manually divide these deduction entries into 9 distinct categories. Within each category, there are often several calculation rules that define how data is to be populated in the EDW. To correctly calculate the values to be entered into these tables, the following changes have been implemented to the tables in the EDW. Miscellaneous Deductions: (T_MISC_DED_HIST) Remove Columns Employer Amount (MISC_DED_EMPLR_AMT) Employer Annual Limit (MISC_DED_EMPLR_ANNL_LIMIT) Add Column Lifetime Limit (MISC_DED_EMPEE_LIFETIME_LIMIT) Life Disability Deductions: (T_LIFE_DISBL_DED_HIST) Add Columns Employee Calculated Amount (LIFE_DISBL_EMPEE_CALC_AMT) Employer Calculated Amount (LIFE_DISBL_EMPLR_CALC_AMT) Users with an ODBC connection can now use data from the Miscellaneous Deduction History table and the Life & Disability Deduction History table for reporting and analysis. The HR/Pay universes have not been modified to include this new data availability. Modifications to affected Universes are scheduled for a later release (2/27/04). 4.2 Payroll Accounting Detail Category Code Column and Object Added Products Affected: HR/Pay Business Objects Universes HR/Pay EDW Tables EDW HR Payroll/Time & Attendance Case Number: Internal Tracking Number 14 Description: An Accounting Detail Category Code object has been added to the Accounting Detail subclass of the Payroll class. The object is sourced from a new column PAYR_ACCTG_CATGRY_CD in the V_PAYR_ACCTG_DETL_PUB view. The column was also added to the Payroll Accounting Detail (T_PAYR_ACCTG_DETAIL) table. DS_Release_Notes_ doc Page 6 of 9

7 4.3 Predefined Condition Code Object Removed HR/Pay Business Objects Universe Case Number: Internal Tracking Number 36 Description: The Payroll/Time & Attendance universe erroneously included a pre-defined condition for Accrued Leave. This pre-defined condition has been removed from this universe to eliminate the potential for misuse and incorrect results. 4.4 Predefined Condition Code Objects Added HR/Pay Business Objects Universes EDW HR Deduction Administration EDW HR Employee Administration EDW HR Position and Job Hierarchy Case Number: Internal Tracking Number 38 Description: When reporting on data in tables on which history is tracked, the potential for Cartesian Product Errors exists. A Cartesian product is encountered when there is a many-to manyrelationship, and such a query will result in a large number of unneeded rows of data. Several classes in the HR/Pay universes relate to data on which history is tracked. Pre-defined condition objects have been added to these universes to eliminate the potential for Cartesian Product Errors. Below is a list of all pre-defined condition code objects added to each universe: Predefined Conditions Universe EA DA PJH PTA Exclude One Time Payment X X X Payroll Campus X X X X Active Employee X X X X Current Information X X X X Date Range Conditions X X X X Objects Head Count X X X X Time Dimension Academic Year X X X X Users can utilize these pre-defined conditions in the Condition panel of either WebIntelligence or BusinessObjects 5i DS_Release_Notes_ doc Page 7 of 9

8 4.5 Employee Birth Date Objects Added HR/Pay Business Objects Universes EDW HR Deduction Administration EDW HR Employee Administration EDW HR Position and Job Hierarchy Case Number: _504 (Internal Tracking Number 50) Description: Users with the Personnel Manager security role have expressed a requirement to include information on Employee Birth Date in their reporting and analysis. An employee birth date object has been added to each of the HR/Pay universes, in the Payroll class to support this requirement. Because of the sensitive nature of this data, the new Employee Birth Data objects have restricted access and are not available to all users. 4.6 Current Hire Date, Position Class Description, Position Class Code Objects Added HR/Pay Business Objects Universe Case Number: Internal Tracking Number 53 Description: Three new objects have been added to the Payroll/Time & Attendance universe to support reporting requirements. The new objects are Current Hire Date, Position Class Description, and Position Class code. Object Name Current Hire Date Position Class Description Position Class Code In Class Employee Position Position 4.7 Accounting Detail Sub-class Access Added to HR Security Roles HR/Pay Oracle Security Roles Case Number: Internal Tracking Number 33 Description: The Accounting Detail sub-class and its associated objects were erroneously restricted by HR/Pay Oracle security roles. Access to this sub-class and objects has been enabled in all HR/Pay security roles. DS_Release_Notes_ doc Page 8 of 9

9 4.8 Current Information Indicator HR/Pay EDW Tables None Case Number: Internal Tracking Number 9 Description: When the HR/Pay EDW was implemented on 30 December, the Current Information Indicator columns (found in many tables) were defined in various ways. Because of the varying definitions, users were not able to use this data in any meaningful way. These columns have been re-released and standardized to reflect the current database record. Columns have been modified according to the chart below. Users with ODBC connections may begin using the data in these columns to define current database records. This fixes issue 5.6 on the HR/Pay Advisory 3.0. TABLE COLUMN T_JOB_HIST JOB_CUR_INFO_IND T_LOA_HIST LOA_CUR_INFO_IND T_PERS_ENDRS_HIST PERS_ENDRS_CUR_INFO_IND T_PERS_LIC_CERT_HIST PERS_LIC_CERT_CUR_INFO_IND T_PERS_MEDICAL_COND_HIST PERS_MEDICAL_COND_CUR_INFO_IND T_PERS_SKILL_HIST PERS_SKILL_CUR_INFO_IND T_POSN_HIST POSN_HIST_CUR_INFO_IND T_PREM_PAYRT_HIST PREM_PAYRT_CUR_INFO_IND T_SNRTY_BAL_HIST SNRTY_BAL_CUR_INFO_IND T_POSN_CLS_HIST POSN_CLS_CUR_INFO_IND T_UNION_CNTRCT_HIST UNION_CNTRCT_CUR_INFO_IND T_BNFT_COVG_HIST BNFT_COVG_CUR_INFO_IND T_CNTRCT_HIST CNTRCT_CUR_INFO_IND T_EMPEE_CLS_HIST EMPEE_CLS_CUR_INFO_IND T_WORK_SCHED_HIST WORK_SCHED_CUR_INFO_IND T_ACCR_LEAVE_BAL_HIST ACCR_LEAVE_BAL_CUR_INFO_IND T_BNFT_LBR_DISTR_HIST BNFT_LBR_DISTR_CUR_INFO_IND T_BNFT_PERS_HIST BNFT_PERS_CUR_INFO_IND T_CNTRCT_PARM_HIST CNTRCT_PARM_CUR_INFO_IND T_EARNS_CD_HIST EARNS_CD_CUR_INFO_IND T_EMPEE_HIST EMPEE_CUR_INFO_IND T_EMPEE_INTL_INFO_HIST_3 INTL_INFO_CUR_INFO_IND T_FAC_HIST FAC_CUR_INFO_IND T_FAC_LOA_APPEAL_HIST FAC_LOA_APPEAL_CUR_INFO_IND T_FAC_LOA_APRV_HIST FAC_LOA_APRV_CUR_INFO_IND T_FAC_RANK_HIST FAC_RANK_CUR_INFO_IND T_FAC_TENURE_HIST FAC_TENURE_CUR_INFO_IND T_JOB_DETL_HIST JOB_DETL_CUR_INFO_IND T_JOB_DETL_HIST_5 JOB_DETL_CUR_INFO_IND T_EMPEE_HIST_5 EMPEE_CUR_INFO_IND DS_Release_Notes_ doc Page 9 of 9