EPM Common and global dimensions
EPM COMMON AND GLOBAL HASH FILE DESIGN
ETL DESIGN DOCUMENT VERSION 1.0 16 DECEMBER 2010
UT Dallas
Page 1
EPM Common and global dimensions
Document Revision InformationThe information below is to be included with all versions of this document.
Prepared By
Date
Version
Chris Ware Hardik Shah
16-Dec-2010
1.0
Revised By
Date
Revision Reason
Version
UT Dallas
Page 2
EPM Common and global dimensions
Document ApprovalThe signatures below indicate that all applicable parties have reviewed this document, have a common understanding of the document, and agree with its contents.
Project Manager
Name Title Signed Date
Application Delivery Manager
Name Title Signed Date
Data Architect
Name Title Signed Date
QA Lead
Name Title Signed Date
Project Lead
Name Title Signed Date
ETL Developer
Name
Chris Ware Hardik Shah
Title Signed Date
UT Dallas
Page 3
EPM Common and global dimensions Table of ContentsDocument Revision Information .............................................................................................................. 2 Document Approval ................................................................................................................................ 3 1 Introduction................................................................................................................................. 10 1.1 Purpose ....................................................................................................................................... 10 1.2 Source ......................................................................................................................................... 10 1.3 Naming Standard ......................................................................................................................... 10 1.4 Assumptions ................................................................................................................................ 10 1.5 Risks ............................................................................................................................................ 11 2 Technical Design ...................................................................................................................... 12 2.1 High Level Design ......................................................................................................................... 12 2.2 High Level Data Flow.................................................................................................................... 14 3 Global Dimensions.................................................................................................................... 16 3.1 PS_D_ACCOUNT :......................................................................................................................... 16 3.1.1 Prerequisites ......................................................................................................................... 16 3.1.2 Assumptions ......................................................................................................................... 16 3.1.3 Source ................................................................................................................................... 16 3.1.4 Process Flow Overview.......................................................................................................... 17 3.1.5 Process Description ............................................................................................................... 17 3.1.6 Risks...................................................................................................................................... 17 3.2 PS_D_CLASS_FIELD: ..................................................................................................................... 18 3.2.1 Prerequisites ......................................................................................................................... 18 3.2.2 Assumptions ......................................................................................................................... 18 3.2.3 Source ................................................................................................................................... 18 3.2.4 Process Flow Overview.......................................................................................................... 18 3.2.5 Process Description ............................................................................................................... 18 3.2.6 Risks...................................................................................................................................... 19 3.3 PS_D_CUSTOMER: ....................................................................................................................... 19 3.3.1 Prerequisites ......................................................................................................................... 19 3.3.2 Assumptions ......................................................................................................................... 19 UT Dallas Page 4
EPM Common and global dimensions3.3.3 Source ................................................................................................................................... 19 3.3.4 Process Flow Overview.......................................................................................................... 20 3.3.5 Process Description ............................................................................................................... 20 3.3.6 Risks...................................................................................................................................... 20 3.4 PS_D_FUND: ................................................................................................................................ 21 3.4.1 Prerequisites ......................................................................................................................... 21 3.4.2 Assumptions ......................................................................................................................... 21 3.4.3 Source ................................................................................................................................... 21 3.4.4 Process Flow Overview.......................................................................................................... 21 3.4.5 Process Description ............................................................................................................... 21 3.4.6 Risks...................................................................................................................................... 22 3.5 PS_D_LOCATION: ......................................................................................................................... 22 3.5.1 Prerequisites ......................................................................................................................... 22 3.5.2 Assumptions ......................................................................................................................... 22 3.5.3 Source ................................................................................................................................... 22 3.5.4 Process Flow Overview.......................................................................................................... 23 3.5.5 Process Description ............................................................................................................... 23 3.5.6 Risks...................................................................................................................................... 23 3.6 PS_D_PRJ: .................................................................................................................................... 24 3.6.1 Prerequisites ......................................................................................................................... 24 3.6.2 Assumptions ......................................................................................................................... 24 3.6.3 Source ................................................................................................................................... 24 3.6.4 Process Flow Overview.......................................................................................................... 25 3.6.5 Process Description ............................................................................................................... 25 3.6.6 Risks...................................................................................................................................... 25 3.7 PS_D_PRJ_RSRC: .......................................................................................................................... 26 3.7.1 Prerequisites ......................................................................................................................... 26 3.7.2 Assumptions ......................................................................................................................... 26 3.7.3 Source ................................................................................................................................... 26 3.7.4 Process Flow Overview.......................................................................................................... 26 3.7.5 Process Description ............................................................................................................... 27 UT Dallas Page 5
EPM Common and global dimensions3.7.6 Risks...................................................................................................................................... 27 3.8 PS_D_SUPPLIER: .......................................................................................................................... 27 3.8.1 Prerequisites ......................................................................................................................... 27 3.8.2 Assumptions ......................................................................................................................... 28 3.8.3 Source ................................................................................................................................... 28 3.8.4 Process Flow Overview.......................................................................................................... 28 3.8.5 Process Description ............................................................................................................... 28 3.8.6 Risks...................................................................................................................................... 29 3.9 PS_D_JOBCODE:........................................................................................................................... 29 3.9.1 Prerequisites ......................................................................................................................... 29 3.9.2 Assumptions ......................................................................................................................... 29 3.9.3 Source ................................................................................................................................... 29 3.9.4 Process Flow Overview.......................................................................................................... 30 3.9.5 Process Description ............................................................................................................... 30 3.9.6 Risks...................................................................................................................................... 30 3.10 PS_D_PERSON:........................................................................................................................... 31 3.10.1 Prerequisites ....................................................................................................................... 31 3.10.2 Assumptions ....................................................................................................................... 31 3.10.3 Source ................................................................................................................................. 31 3.10.4 Process Flow Overview........................................................................................................ 32 3.10.5 Process Description ............................................................................................................. 33 3.10.6 Risks.................................................................................................................................... 34 3.11 PS_D_CHARTFIELD1: .................................................................................................................. 35 3.11.1 Prerequisites ....................................................................................................................... 35 3.11.2 Assumptions ....................................................................................................................... 35 3.11.3 Source ................................................................................................................................. 35 3.11.4 Process Flow Overview........................................................................................................ 35 3.11.5 Process Description ............................................................................................................. 35 3.11.6 Risks.................................................................................................................................... 36 3.12 PS_D_CMPNY:............................................................................................................................ 37 3.12.1 Prerequisites ....................................................................................................................... 37 UT Dallas Page 6
EPM Common and global dimensions3.12.2 Assumptions ....................................................................................................................... 37 3.12.3 Source ................................................................................................................................. 37 3.12.4 Process Flow Overview........................................................................................................ 37 3.12.5 Process Description ............................................................................................................. 38 3.12.6 Risks.................................................................................................................................... 38 3.13 PS_D_DEPT: ............................................................................................................................... 38 3.13.1 Prerequisites ....................................................................................................................... 38 3.13.2 Assumptions ....................................................................................................................... 39 3.13.3 Source ................................................................................................................................. 39 3.13.4 Process Flow Overview........................................................................................................ 39 3.13.5 Process Description ............................................................................................................. 39 3.13.6 Risks.................................................................................................................................... 40 3.14 PS_D_ESTAB: ............................................................................................................................. 40 3.14.1 Prerequisites ....................................................................................................................... 40 3.14.2 Assumptions ....................................................................................................................... 40 3.14.3 Source ................................................................................................................................. 40 3.14.4 Process Flow Overview........................................................................................................ 41 3.14.5 Process Description ............................................................................................................. 41 3.14.6 Risks.................................................................................................................................... 41 3.15 PS_D_GOV_SUBAG: ................................................................................................................... 42 3.15.1 Prerequisites ....................................................................................................................... 42 3.15.2 Assumptions ....................................................................................................................... 42 3.15.3 Source ................................................................................................................................. 42 3.15.4 Process Flow Overview........................................................................................................ 42 3.15.5 Process Description ............................................................................................................. 42 3.15.6 Risks.................................................................................................................................... 43 3.16 PS_D_LEDGER: ........................................................................................................................... 43 3.16.1 Prerequisites ....................................................................................................................... 43 3.16.2 Assumptions ....................................................................................................................... 43 3.16.3 Source ................................................................................................................................. 43 3.16.4 Process Flow Overview........................................................................................................ 44 UT Dallas Page 7
EPM Common and global dimensions3.16.5 Process Description ............................................................................................................. 44 3.16.6 Risks.................................................................................................................................... 44 3.17 PS_D_OPER_UNIT: ..................................................................................................................... 45 3.17.1 Prerequisites ....................................................................................................................... 45 3.17.2 Assumptions ....................................................................................................................... 45 3.17.3 Source ................................................................................................................................. 45 3.17.4 Process Flow Overview........................................................................................................ 45 3.17.5 Process Description ............................................................................................................. 46 3.17.6 Risks.................................................................................................................................... 46 3.18 PS_D_PRJ_AC: ............................................................................................................................ 46 3.18.1 Prerequisites ....................................................................................................................... 46 3.18.2 Assumptions ....................................................................................................................... 47 3.18.3 Source ................................................................................................................................. 47 3.18.4 Process Flow Overview........................................................................................................ 47 3.18.5 Process Description ............................................................................................................. 47 3.18.6 Risks.................................................................................................................................... 48 3.19 PS_D_REG_RGN: ........................................................................................................................ 48 3.19.1 Prerequisites ....................................................................................................................... 48 3.19.2 Assumptions ....................................................................................................................... 48 3.19.3 Source ................................................................................................................................. 48 3.19.4 Process Flow Overview........................................................................................................ 49 3.19.5 Process Description ............................................................................................................. 49 3.19.6 Risks.................................................................................................................................... 49 3.20 PS_D_TRC: ................................................................................................................................. 50 3.20.1 Prerequisites ....................................................................................................................... 50 3.20.2 Assumptions ....................................................................................................................... 50 3.20.3 Source ................................................................................................................................. 50 3.20.4 Process Flow Overview........................................................................................................ 50 3.20.5 Process Description ............................................................................................................. 50 3.20.6 Risks.................................................................................................................................... 51
UT Dallas
Page 8
EPM Common and global dimensions4 Common Dimensions............................................................................................................... 52 4.1 PS_D_DET_PERIOD: ..................................................................................................................... 52 4.1.1 Prerequisites ......................................................................................................................... 52 4.1.2 Assumptions ......................................................................................................................... 52 4.1.3 Source ................................................................................................................................... 52 4.1.4 Process Flow Overview.......................................................................................................... 53 4.1.5 Process Description ............................................................................................................... 54 4.1.6 Risks...................................................................................................................................... 55 4.2 PS_D_DT_PATTERN: ..................................................................................................................... 55 4.2.1 Prerequisites ......................................................................................................................... 55 4.2.2 Assumptions ......................................................................................................................... 55 4.2.3 Source ................................................................................................................................... 55 4.2.4 Process Flow Overview.......................................................................................................... 56 4.2.5 Process Description ............................................................................................................... 56 4.2.6 Risks...................................................................................................................................... 57 4.3 PS_D_BUS_UNIT_COMP :............................................................................................................. 58 4.3.1 Prerequisites ......................................................................................................................... 58 4.3.2 Assumptions ......................................................................................................................... 58 4.3.3 Source ................................................................................................................................... 58 4.3.4 Process Flow Overview.......................................................................................................... 58 4.3.5 Process Description ............................................................................................................... 59 4.3.6 Risks...................................................................................................................................... 59 5 Supporting Information and Sources ............................................................................... 64
UT Dallas
Page 9
EPM Common and global dimensions
1
Introduction
1.1 PurposeThe scope of this document is to define the ETL approach taken to load data from single or multiple sources for each of the identified common and global dimension table.
1.2 SourceSource data is fetched from PeopleSoft tables into EPM warehouse for all the common and global dimension tables.
1.3 Naming StandardNaming standard used for job modifications will be same as defined for CS module by ARDC team.
1.4 Assumptions1) Four different types of dimensions were identified during the analysis process i.e., a. Dimension having _D in the naming convention i.e. PS_D_ACCOUNT b. Dimension having _L in the naming convention i.e. PS_L_ACCOUNT c. Dimension having _O in the naming convention i.e. PS_O_ACCOUNT d. Dimension having _R in the naming convention i.e. PS_R_ACCOUNT Out of the above 4 dimension types this design document caters to only _D type of dimension tables. Assumption is that other types of dimension tables do not require modifications to their existing design. 2) This design document caters to only OWS to MDW jobs. No changes will be made to OWE to MDW jobs.
UT Dallas
Page 10
EPM Common and global dimensions1.5 RisksETL Design is based on the inputs received from UTD regarding the true owner of each dimension. Any deviation on true source will impact ETL design and subsequently will impact ETL development.
UT Dallas
Page 11
EPM Common and global dimensions
2
Technical Design
2.1 High Level DesignObjective of this process is to store golden master record in dimension table. Currently EPM is designed to load from each of the 3 sources i.e. FSCM (Finance and Supply chain management), HCM (Human capital management) and CS (Campus solution). Since these dimensions are common or global they are shared across all the modules and hence should have only one record for each dimension. As of now ETL team have identified following common and global dimension for which UTD has determined true source or correct order of load,
Sr. No. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 UT Dallas
Dimension Type Common Common Common Common Common Common Common Common Common Common Common Global Global Global Global Global Global Global
Name PS_D_BUSINESS_UNIT PS_D_BUS_UNIT_COMP PS_D_DET_PERIOD PS_D_DT_PATTERN PS_D_CURRENCY PS_D_DET_BUDGET PS_D_LANGUAGE PS_D_PATTERN_DAY PS_D_SUM_BUDGET PS_D_SUM_PERIOD PS_D_UOM PS_D_ACCOUNT PS_D_CHARTFIELD1 PS_D_CLASS_FIELD PS_D_CMPNY PS_D_CUSTOMER PS_D_DEPT PS_D_ESTAB
Owner/Load Order FSCM, HCM & CS FSCM FSCM, HCM & CS FSCM, HCM & CS FSCM FSCM FSCM FSCM FSCM FSCM FSCM FSCM FSCM FSCM HCM FSCM HCM HCM Page 12
EPM Common and global dimensionsSr. No. 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 Global Global Global Global Global Global Global Global Global Global Global Global Global Global Global Global Global Global Global Global Global Global Global PS_D_PRJ PS_D_PRJ_AC PS_D_PRJ_RSRC PS_D_REG_RGN PS_D_SUPPLIER PS_D_TRC PS_D_ALTACCT PS_D_ANLYS_TYPE PS_D_BUDGET_REF PS_D_CA PS_D_CHANNEL PS_D_CUST_ORG PS_D_ETHNIC_GRP PS_D_FREQ PS_D_GOV_POI PS_D_LRNG_ENV PS_D_MATCH_RULE PS_D_ORD_CAPTURE PS_D_POS PS_D_PRODUCT PS_D_PROGRAM_FDM PS_D_SALPLN PS_D_STAT_CODE Dimension Type Global Global Global Global Global Global Global Name PS_D_FUND PS_D_GOV_SUBAG PS_D_JOBCODE PS_D_LEDGER PS_D_LOCATION PS_D_OPER_UNIT PS_D_PERSON Owner/Load Order FSCM CS HCM FSCM FSCM FSCM Load from CS & HCM FSCM FSCM FSCM HCM FSCM HCM FSCM FSCM FSCM FSCM UNKNOWN FSCM CS HCM HCM HCM FSCM FSCM HCM FSCM FSCM\CS HCM FSCM
UT Dallas
Page 13
EPM Common and global dimensions2.2 High Level Data FlowCurrent Flow:
Proposed Design: Below diagrams depicts dimension having single owner. For the dimension having multiple owners please refer to the detail design for the ETL approach.
UT Dallas
Page 14
EPM Common and global dimensionsScenario: FSCM is the true owner for the dimension. Solution: In this scenario jobs loading data from PS to OWS for CS and HCM warehouse will not run rather only FSCM version of the job will load data from PeopleSoft table to OWS staging dimension table. Once the data is loaded into OWS table, MDW version of the job will load data from OWS to MDW dimension. Modification will be made to MDW job to replicate one dimension record of FSCM source into 3 dimension records in hash file for each source. For e.g.,
FSCM ACCT# SETID 123 DAL01
HCM ACCT# SETID 123 DAL01
OWS ACCT# SETID SRC_SYS_ID 123 DAL01 FSCM
MDW ACCOUNT_SID ACCT# SETID SRC_SYS_ID 1 123 DAL01 FSCM
CS ACCT# SETID 123 DAL01
Hash File ACCOUNT_SID ACCT# SETID 1 1 1
SRC_SYS_ID
123 DAL01 FSCM 123 DAL01 HCM 123 DAL01 CS
UT Dallas
Page 15
EPM Common and global dimensions
3
Global Dimensions
3.1 PS_D_ACCOUNT :
3.1.1 P r e r e q u i s i t e s The prerequisites to this ETL process are as follows: 1) Following 2 lookup tables needs to be prepopulated, a. PS_S_ACCT_TYPE_TBL (J_Stage_PS_S_ACCT_TYPE_TBL_FSCM91_EPM91) b. PS_PF_SETID_LOOKUP (Control table) 3.1.2 A s s u m p t i o n s An account for a given business unit will have same SETID across all sources.
3.1.3 S o u r c e True source of ACCOUNT information will come from FSCM warehouse.
UT Dallas
Page 16
EPM Common and global dimensions3.1.4 P r o c e s s F l o w O v e r v i e w
3.1.5 P r o c e s s D e s c r i p t i o n 1) Source (PeopleSoft) to Staging (OWS), a. Only FSCM version of the job will load data into OWS table. i. Job Name: J_Stage_PS_S_GL_ACCT_TBL_FSCM91_EPM91 b. Modify master sequence to call only FSCM version of job to load OWS ACCOUNT table. 2) Staging (OWS) to MDW a. No changes will be made to hash file creation jobs. b. Modify MDW job to replicate 3 records into hash file for each source i. Job Name: J_Dim_PS_D_ACCOUNT_OWS c. Make sure above mentioned MDW job is called in master sequence.
3.1.6 R i s k s NA
UT Dallas
Page 17
EPM Common and global dimensions
3.2 PS_D_CLASS_FIELD:
3.2.1 P r e r e q u i s i t e s The prerequisites to this ETL process are as follows: 1) Following lookup table needs to be prepopulated, a. PS_PF_SETID_LOOKUP (Control table) 3.2.2 A s s u m p t i o n s NA.
3.2.3 S o u r c e True source of CLASS_FIELD information will come from FSCM warehouse. 3.2.4 P r o c e s s F l o w O v e r v i e w
3.2.5 P r o c e s s D e s c r i p t i o n 1) Source (PeopleSoft) to Staging (OWS), UT Dallas Page 18
EPM Common and global dimensionsa. Only FSCM version of the job will load data into OWS table. i. Job Name: J_Stage_PS_S_CLASS_CF_TBL_FSCM91_EPM91 b. Modify master sequence to call only FSCM version of job to load OWS table. 2) Staging (OWS) to MDW a. No changes will be made to hash file creation jobs. b. Modify MDW job to replicate 3 records into hash file for each source i. Job Name: J_Dim_PS_D_CLASS_FIELD c. Make sure above mentioned MDW job is called in master sequence.
3.2.6 R i s k s NA
3.3 PS_D_CU STOMER:
3.3.1 P r e r e q u i s i t e s The prerequisites to this ETL process are as follows: 1) Following lookup table needs to be prepopulated, a. PS_D_CUST_ORG i. Job Name: J_Dim_PS_D_CUST_ORG_SCM b. PS_CUST_ADDRESS i. Job Name: J_Stage_PS_CUST_ADDRESS_FMS_FSCM91_EPM91 c. PS_PF_SETID_LOOKUP (Control table) 3.3.2 A s s u m p t i o n s NA
3.3.3 S o u r c e True source of CUSTOMER information will come from FSCM warehouse. UT Dallas Page 19
EPM Common and global dimensions3.3.4 P r o c e s s F l o w O v e r v i e w
3.3.5 P r o c e s s D e s c r i p t i o n 1) Source (PeopleSoft) to Staging (OWS), a. Only FSCM version of the job will load data into OWS table. i. Job Name: J_Stage_PS_CUSTOMER_FMS_FSCM91_EPM91 b. Modify master sequence to call only FSCM version of job to load OWS table. 2) Staging (OWS) to MDW a. No changes will be made to hash file creation jobs. b. Modify MDW job to replicate 3 records into hash file for each source i. Job Name: J_Dim_PS_D_CUSTOMER_SCM c. Make sure above mentioned MDW job is called in master sequence.
3.3.6 R i s k s NA
UT Dallas
Page 20
EPM Common and global dimensions3.4 PS_D_FUND:
3.4.1 P r e r e q u i s i t e s The prerequisites to this ETL process are as follows: 1) Following lookup table needs to be prepopulated, a. PS_PF_SETID_LOOKUP (Control table) 3.4.2 A s s u m p t i o n s NA
3.4.3 S o u r c e True source of FUND information will come from FSCM warehouse. 3.4.4 P r o c e s s F l o w O v e r v i e w
3.4.5 P r o c e s s D e s c r i p t i o n 1) Source (PeopleSoft) to Staging (OWS), a. Only FSCM version of the job will load data into OWS table. UT Dallas Page 21
EPM Common and global dimensionsi. Job Name: J_Stage_PS_S_FUND_TBL_FSCM91_EPM91 b. Modify master sequence to call only FSCM version of job to load OWS table. 2) Staging (OWS) to MDW a. No changes will be made to hash file creation jobs. b. Modify MDW job to replicate 3 records into hash file for each source i. Job Name: J_Dim_PS_D_FUND c. Make sure above mentioned MDW job is called in master sequence.
3.4.6 R i s k s NA
3.5 PS_D_LOCATION:
3.5.1 P r e r e q u i s i t e s The prerequisites to this ETL process are as follows: 1) Following lookup tables needs to be prepopulated, a. PS_WA_LOCN_MAP_DFN (Job not found loading this table. Seems to be configuration table.) b. PS_D_REG_RGN c. PS_D_ESTAB 3.5.2 A s s u m p t i o n s NA
3.5.3 S o u r c e True source of Location information will come from FSCM warehouse.
UT Dallas
Page 22
EPM Common and global dimensions3.5.4 P r o c e s s F l o w O v e r v i e w
3.5.5 P r o c e s s D e s c r i p t i o n 1) Source (PeopleSoft) to Staging (OWS), a. Only FSCM version of the job will load data into OWS table. i. Job Name: J_Stage_PS_LOCATION_TBL_FMS_FSCM91_EPM91 b. Modify master sequence to call only FSCM version of job to load OWS table. 2) Staging (OWS) to MDW a. No changes will be made to hash file creation jobs. b. Modify MDW job to replicate 3 records into hash file for each source i. Job Name: J_Dim_PS_D_LOCATION c. Make sure above mentioned MDW job is called in master sequence.
3.5.6 R i s k s NA
UT Dallas
Page 23
EPM Common and global dimensions3.6 PS_D_PRJ:
3.6.1 P r e r e q u i s i t e s The prerequisites to this ETL process are as follows: 1) Following lookup tables needs to be prepopulated, a. PS_D_BUSINESS_UNIT b. PS_PPK_DISC_RT_TBL c. PS_PROJ_TYPE_TBL d. PS_S_BC_PROJ_RQST e. PS_S_PC_INT_TMPL f. PS_S_PPK_INITP_TBL
g. PS_S_SET_CNTRL_REC h. PS_S_XLATITEM_VW 3.6.2 A s s u m p t i o n s NA
3.6.3 S o u r c e True source of PRJ information will come from FSCM warehouse.
UT Dallas
Page 24
EPM Common and global dimensions3.6.4 P r o c e s s F l o w O v e r v i e w
3.6.5 P r o c e s s D e s c r i p t i o n 1) Source (PeopleSoft) to Staging (OWS), a. Only FSCM version of the job will load data into OWS table. i. Job Name: J_Stage_PS_PROJECT_FSCM91_EPM91 b. Modify master sequence to call only FSCM version of job to load OWS table. 2) Staging (OWS) to MDW a. No changes will be made to hash file creation jobs. b. Modify MDW job to replicate 3 records into hash file for each source i. Job Name: J_Dim_PS_D_PRJ c. Make sure above mentioned MDW job is called in master sequence.
3.6.6 R i s k s NA
UT Dallas
Page 25
EPM Common and global dimensions3.7 PS_D_PRJ_RSRC:
3.7.1 P r e r e q u i s i t e s The prerequisites to this ETL process are as follows: 1) Following lookup tables needs to be prepopulated, a. PS_S_PROJ_CATG_TBL b. PS_S_PROJ_RES_TYPE c. PS_S_PROJ_SCAT_TBL d. PS_S_SET_CNTRL_REC 3.7.2 A s s u m p t i o n s NA
3.7.3 S o u r c e True source of PRJ_RSRC information will come from FSCM warehouse. 3.7.4 P r o c e s s F l o w O v e r v i e w
UT Dallas
Page 26
EPM Common and global dimensions3.7.5 P r o c e s s D e s c r i p t i o n 1) Source (PeopleSoft) to Staging (OWS), a. Only FSCM version of the job will load data into OWS table. i. Job Name: J_Stage_PS_PROJ_RESOURCE_FSCM91_EPM91 b. Modify master sequence to call only FSCM version of job to load OWS table. 2) Staging (OWS) to MDW a. No changes will be made to hash file creation jobs. b. Modify MDW job to replicate 3 records into hash file for each source i. Job Name: J_Dim_PS_D_PRJ_RSRC c. Make sure above mentioned MDW job is called in master sequence.
3.7.6 R i s k s NA
3.8 PS_D_SUPPLIER:
3.8.1 P r e r e q u i s i t e s The prerequisites to this ETL process are as follows: 1) Following lookup tables needs to be prepopulated, a. PS_VENDOR_ADDR i. As per analysis this table is only loaded from HR source. If this is the case then need to modify OWS job to replicate entry for finance source in hash file as MDW job looks up this table with SRC as part of the key. 1. Job Name: J_Stage_PS_VENDOR_ADDR_HCM_HCM91_EPM91 b. PS_VENDOR_ID_NBRS i. As per analysis this is loaded from FIN source. In this scenario there should not be any change to its OWS job. c. PS_PF_SETID_LOOKUP
UT Dallas
Page 27
EPM Common and global dimensions3.8.2 A s s u m p t i o n s NA
3.8.3 S o u r c e True source of SUPPLIER information will come from FSCM warehouse. 3.8.4 P r o c e s s F l o w O v e r v i e w
3.8.5 P r o c e s s D e s c r i p t i o n 1) Source (PeopleSoft) to Staging (OWS), a. Only FSCM version of the job will load data into OWS table. i. Job Name: J_Stage_PS_VENDOR_FMS_FSCM91_EPM91 b. Modify master sequence to call only FSCM version of job to load OWS table. 2) Staging (OWS) to MDW a. No changes will be made to hash file creation jobs. b. Modify MDW job to replicate 3 records into hash file for each source i. Job Name: J_Dim_PS_D_SUPPLIER c. Make sure above mentioned MDW job is called in master sequence. UT Dallas Page 28
EPM Common and global dimensions
3.8.6 R i s k s NA
3.9 PS_D_JOBCODE:
3.9.1 P r e r e q u i s i t e s The prerequisites to this ETL process are as follows: 1) Following lookup tables needs to be prepopulated, a. PS_PF_SETID_LOOKUP 3.9.2 A s s u m p t i o n s NA
3.9.3 S o u r c e True source of PS_D_JOBCODE information will come from HCM warehouse.
UT Dallas
Page 29
EPM Common and global dimensions3.9.4 P r o c e s s F l o w O v e r v i e w
3.9.5 P r o c e s s D e s c r i p t i o n 1) Source (PeopleSoft) to Staging (OWS), a. Only HCM version of the job will load data into OWS table. i. Job Name: J_Stage_PS_JOBCODE_TBL_HCM91_EPM91 b. Modify master sequence to call only HCM version of job to load OWS table. 2) Staging (OWS) to MDW a. No changes will be made to hash file creation jobs. b. Modify MDW job to replicate 3 records into hash file for each source i. Job Name: J_Dim_PS_D_JOBCODE c. Make sure above mentioned MDW job is called in master sequence.
3.9.6 R i s k s NA
UT Dallas
Page 30
EPM Common and global dimensions3.10 PS_D_PERSON:
3.10.1 P r e r e q u i s i t e s The prerequisites to this ETL process are as follows: 1) Following lookup tables needs to be prepopulated, a. PS_ADDRESSES b. PS_BN_PERSON c. PS_DIVERS_ETHNIC d. PS_D_REG_RGN e. PS_EMAIL_ADDRESSES f. PS_EMERGENCY_CNTCT
g. PS_HRS_APP_PROFILE h. PS_PERSONAL_PHONE i. j. PS_PERS_APPL_INFO PS_PERS_DATA_EFFDT
k. PS_PERS_DATA_USA l. PS_PERS_DATA_USF
m. PS_PERS_NID n. PS_PRIORWORK_SUM o. PS_S_NAMES p. PS_S_XLATITEM_VW 3.10.2 A s s u m p t i o n s NA
3.10.3 S o u r c e PERSON data is loaded from both the source HCM and CS. Source which has more updated image of the PERSON takes precedence into MDW.
UT Dallas
Page 31
EPM Common and global dimensions3.10.4 P r o c e s s F l o w O v e r v i e w
Loads
PS_PERSON(HCM)
OWS / Control tables
PS_PERSON (OWS)
Lookup all the child tables and fetch all the required attributes for PS_D_PERSON table
A
Loads
PS_PERSON(CS)
Relational Hash File
MDW person hash file
Writes updated record back to hash file
A
Lookup relational hash file on EMPLID and SRC
If Found
Lookup MDW record in hash file to see if incoming record is updated record compared what is stored in DB using UPDT_TMS
Updated record
PS_D_PERSON(MDW)
If Not Found B
UT Dallas
Page 32
EPM Common and global dimensions
3.10.5 P r o c e s s D e s c r i p t i o n 1) Source (PeopleSoft) to Staging (OWS), a. No change to CS and HR OWS job, i. CS Job Name: J_Stage_PS_PERSON_HCM91_EPM91 ii. HR Job Name: J_Stage_PS_PERSON_HCM91_EPM91 b. Modify master sequence to call only HCM version of job to load OWS table. 2) Staging (OWS) to MDW a. Create 2 hash file create job for following lookup files, i. Relational Hash file lookup ii. MDW hash file b. Modify MDW job to propagate new field LAST_UPDT_TMS from OWS table. i. Job Name: J_Dim_PS_D_PERSON c. Modify design of MDW job as per below rules, i. Lookup relational hash file on EMPLID and SRC_SYS_ID, UT Dallas Page 33
EPM Common and global dimensions1. If found then lookup MDW hash file on SID value to check whether incoming record is updated record compared to stored record i.e. compare LAST_UPD_TIME on record, a. If incoming record is updated record i.e. new image of the dimension then update all dimensional attributes in MDW table and Write a record to MDW hash file. b. If incoming record is not updated record then do nothing. 2. If not found, a. Lookup MDW hash file based on the business rules provided by UTD to identify whether that person already exist in MDW, i. If Exists, 1. Use the SID value and append a record to relational hash file with SRC_SYS_ID, EMPLID and PERSON_SID. 2. Check whether incoming record is updated image compared to stored record, a. If yes then update all dimensional attributes in MDW table and Write a record to MDW hash file. b. If no then update EMPLID field in dimension table. 3. If Not EXISTs, a. Generate SID value, b. Append a record to relational hash file with PERSON_SID, EMPLID and SRC_SYS_ID, c. Append record to MDW hash file, d. Insert record to MDW table. d. Make sure above mentioned MDW job is called in master sequence.
3.10.6 R i s k s NA
UT Dallas
Page 34
EPM Common and global dimensions3.11 PS_D_CHARTFIELD1:
3.11.1 P r e r e q u i s i t e s The prerequisites to this ETL process are as follows: 1) Following lookup tables are pre-populated, a. PS_D_CHARTFIELD1 (J_Hash_PS_D_CHARTFIELD1) b. PS_PF_SETID_LOOKUP (Control table) 3.11.2 A s s u m p t i o n s Chartfield1 will have the same SETID across all sources.
3.11.3 S o u r c e The true source of Chartfield1 information will come from FSCM warehouse. 3.11.4 P r o c e s s F l o w O v e r v i e w
3.11.5 P r o c e s s D e s c r i p t i o n 1) Source (PeopleSoft) to Staging (OWS), UT Dallas Page 35
EPM Common and global dimensionsa. Only FSCM version of the job will load data into OWS table. i. Job Name: J_Stage_PS_S_CF1_TBL_FSCM91_EPM91 b. Modify master sequence to call only FSCM version of job to load OWS Chartfield1 table. 2) Staging (OWS) to MDW a. No changes will be made to hash file creation jobs. b. Modify MDW job to replicate 3 records into hash file for each source i. Job Name: J_Dim_PS_D_CHARTFIELD1 c. Make sure above mentioned MDW job is called in master sequence.
3.11.6 R i s k s NA
UT Dallas
Page 36
EPM Common and global dimensions3.12 PS_D_CMPNY:
3.12.1 P r e r e q u i s i t e s The prerequisites to this ETL process are as follows: 1) Following lookup tables are pre-populated, a. PS_PF_SETID_LOOKUP (Control table) b. PS_LEGAL_TYPE_TBL (J_Stage_PS_LEGAL_TYPE_TBL_HCM91_EPM91) c. PS_S_XLATITEM_VW d. PS_D_LOCATION e. PS_D_REG_RGN 3.12.2 A s s u m p t i o n s A company will have same SETID across all sources.
3.12.3 S o u r c e True source of company information will come from HR warehouse. 3.12.4 P r o c e s s F l o w O v e r v i e w
UT Dallas
Page 37
EPM Common and global dimensions3.12.5 P r o c e s s D e s c r i p t i o n 1) Source (PeopleSoft) to Staging (OWS), a. Only HCM version of the job will load data into OWS table. i. Job Name: J_Stage_PS_S_COMPANY_TBL_HCM91_EPM91 b. Modify master sequence to call only HCM version of job to load OWS Company table. 2) Staging (OWS) to MDW a. No changes will be made to hash file creation jobs. b. Modify MDW job to replicate 3 records into hash file for each source i. Job Name: J_Dim_PS_D_CMPNY c. Make sure above mentioned MDW job is called in master sequence.
3.12.6 R i s k s NA
3.13 PS_D_DEPT:
3.13.1 P r e r e q u i s i t e s The prerequisites to this ETL process are as follows: 1) Following lookup tables are pre-populated, a. PS_PF_SETID_LOOKUP (Control table) b. PS_S_XLATITEM_VW c. PS_D_LOCATION d. PS_D_CMPNY e. PS_D_GOV_SUBAG f. PS_D_PERSON
g. PS_PF_SETID_LOOKUP
UT Dallas
Page 38
EPM Common and global dimensions3.13.2 A s s u m p t i o n s A department will have same SETID across all sources.
3.13.3 S o u r c e True source of department information will come from HCM warehouse. 3.13.4 P r o c e s s F l o w O v e r v i e w
3.13.5 P r o c e s s D e s c r i p t i o n 1) Source (PeopleSoft) to Staging (OWS), a. Only HCM version of the job will load data into OWS table. i. Job Name: J_Stage_PS_DEPT_TBL_FMS_FSCM91_EPM91 b. Modify master sequence to call only HCM version of job to load OWS department table. 2) Staging (OWS) to MDW a. No changes will be made to hash file creation jobs. b. Modify MDW job to replicate 3 records into hash file for each source i. Job Name: J_Dim_PS_D_DEPT1 c. Make sure above mentioned MDW job is called in master sequence. UT Dallas Page 39
EPM Common and global dimensions
3.13.6 R i s k s NA
3.14 PS_D_ESTAB:
3.14.1 P r e r e q u i s i t e s The prerequisites to this ETL process are as follows: 1) Following lookup tables are pre-populated, a. n/a 3.14.2 A s s u m p t i o n s An ESTAB will have same SETID across all sources.
3.14.3 S o u r c e True source of ESTAB information will come from HCM warehouse.
UT Dallas
Page 40
EPM Common and global dimensions3.14.4 P r o c e s s F l o w O v e r v i e w
3.14.5 P r o c e s s D e s c r i p t i o n 1) Source (PeopleSoft) to Staging (OWS), a. Only HCM version of the job will load data into OWS table. i. Job Name: J_Stage_PS_ESTAB_TBL_HCM91_EPM91 b. Modify master sequence to call only HCM version of job to load OWS ESTAB table. 2) Staging (OWS) to MDW a. No changes will be made to hash file creation jobs. b. Modify MDW job to replicate 3 records into hash file for each source i. Job Name: J_Dim_PS_D_ESTAB c. Make sure above mentioned MDW job is called in master sequence.
3.14.6 R i s k s NA
UT Dallas
Page 41
EPM Common and global dimensions3.15 PS_D_GOV_SUBAG:
3.15.1 P r e r e q u i s i t e s The prerequisites to this ETL process are as follows: 1) Following lookup tables are pre-populated, a. PS_PF_SETID_LOOKUP (Control table) b. PS_D_CMPNY 3.15.2 A s s u m p t i o n s A gov_subag will have same SETID across all sources.
3.15.3 S o u r c e True source of gov_subag information will come from CS warehouse. 3.15.4 P r o c e s s F l o w O v e r v i e w
3.15.5 P r o c e s s D e s c r i p t i o n 1) Source (PeopleSoft) to Staging (OWS), UT Dallas Page 42
EPM Common and global dimensionsa. Only CS version of the job will load data into OWS table. i. Job Name: J_Stage_PS_GVT_SUBAGCY_TBL_CS b. Modify master sequence to call only CS version of job to load OWS GVT_SUBAGCY table. 2) Staging (OWS) to MDW a. No changes will be made to hash file creation jobs. b. Modify MDW job to replicate 3 records into hash file for each source c. Job Name: J_Dim_PS_D_GOV_SUBAG Make sure above mentioned MDW job is called in master sequence.
3.15.6 R i s k s NA
3.16 PS_D_LEDG ER:
3.16.1 P r e r e q u i s i t e s The prerequisites to this ETL process are as follows: 1) Following lookup tables are pre-populated, a. PS_PF_SETID_LOOKUP (Control table) 3.16.2 A s s u m p t i o n s A Ledger will have same SETID across all sources.
3.16.3 S o u r c e True source of Ledger information will come from FSCM warehouse.
UT Dallas
Page 43
EPM Common and global dimensions3.16.4 P r o c e s s F l o w O v e r v i e w
3.16.5 P r o c e s s D e s c r i p t i o n 1) Source (PeopleSoft) to Staging (OWS), a. Only FSCM version of the job will load data into OWS table. i. Job Name: J_Stage_PS_S_LEDGRPLEDTBL_FSCM91_EPM91 ii. Job Name: J_Stage_PS_S_LED_DEFN_TBL_FSCM91_EPM91 iii. Job Name: J_Stage_PS_S_LED_GRP_TBL_FSCM91_EPM91 b. Modify master sequence to call only FSCM version of job to load OWS Ledger table. 2) Staging (OWS) to MDW a. No changes will be made to hash file creation jobs. b. Modify MDW job to replicate 3 records into hash file for each source i. Job Name: J_Dim_PS_D_LEDGER_E c. Make sure above mentioned MDW job is called in master sequence.
3.16.6 R i s k s NA
UT Dallas
Page 44
EPM Common and global dimensions
3.17 PS_D_O PER_UN IT:
3.17.1 P r e r e q u i s i t e s The prerequisites to this ETL process are as follows: 1) Following lookup tables are pre-populated, a. PS_PF_SETID_LOOKUP (Control table) 3.17.2 A s s u m p t i o n s A Ledger will have same SETID across all sources.
3.17.3 S o u r c e True source of Ledger information will come from FSCM warehouse. 3.17.4 P r o c e s s F l o w O v e r v i e w
UT Dallas
Page 45
EPM Common and global dimensions3.17.5 P r o c e s s D e s c r i p t i o n 1) Source (PeopleSoft) to Staging (OWS), a. Only FSCM version of the job will load data into OWS table. i. Job Name: J_Stage_PS_OPER_UNIT_TBL_FSCM91_EPM91 b. Modify master sequence to call only FSCM version of job to load OWS Oper_Unit table. 2) Staging (OWS) to MDW a. No changes will be made to hash file creation jobs. b. Modify MDW job to replicate 3 records into hash file for each source i. Job Name: J_Dim_PS_D_OPER_UNIT c. Make sure above mentioned MDW job is called in master sequence.
3.17.6 R i s k s NA
3.18 PS_D_PRJ_AC:
3.18.1 P r e r e q u i s i t e s The prerequisites to this ETL process are as follows: 2) Following lookup tables are pre-populated, a. PS_PF_SETID_LOOKUP (Control table) b. PS_S_PPK_INITP_TBL c. PS_PROJ_TYPE_TBL d. PS_PPK_DISC_RT_TBL e. PS_D_BUSINESS_UNIT f. PS_S_BC_PROJ_RQST
g. PS_S_PC_INT_TMPL h. PS_S_XLATITEM_VW UT Dallas Page 46
EPM Common and global dimensionsi. PS_S_SET_CNTRL_REC
3.18.2 A s s u m p t i o n s A project will have same SETID across all sources.
3.18.3 S o u r c e True source of project information will come from FSCM warehouse. 3.18.4 P r o c e s s F l o w O v e r v i e w
3.18.5 P r o c e s s D e s c r i p t i o n 1) Source (PeopleSoft) to Staging (OWS), a. Only FSCM version of the job will load data into OWS table. i. Job Name: J_Stage_PS_PROJECT_FSCM91_EPM91 b. Modify master sequence to call only FSCM version of job to load OWS Project table. 2) Staging (OWS) to MDW a. No changes will be made to hash file creation jobs. b. Modify MDW job to replicate 3 records into hash file for each source UT Dallas Page 47
EPM Common and global dimensionsi. Job Name: J_Dim_PS_D_PRJ_AC_PS_PROJECT c. Make sure above mentioned MDW job is called in master sequence.
3.18.6 R i s k s NA
3.19 PS_D_REG_RGN:
3.19.1 P r e r e q u i s i t e s The prerequisites to this ETL process are as follows: 1) Following lookup tables are pre-populated, a. PS_D_REG_RGN 3.19.2 A s s u m p t i o n s A REG_RGN will have same SETID across all sources.
3.19.3 S o u r c e True source of REG_RGN information will come from HCM warehouse.
UT Dallas
Page 48
EPM Common and global dimensions3.19.4 P r o c e s s F l o w O v e r v i e w
3.19.5 P r o c e s s D e s c r i p t i o n 1) Source (PeopleSoft) to Staging (OWS), a. Only HCM version of the job will load data into OWS table. i. Job Name: J_Stage_PS_REG_REGION_TBL_HCM91_EPM91 b. Modify master sequence to call only HCM version of job to load OWS ACCOUNT table. 2) Staging (OWS) to MDW a. No changes will be made to hash file creation jobs. b. Modify MDW job to replicate 3 records into hash file for each source i. Job Name: J_Dim_PS_D_REG_RGN c. Make sure above mentioned MDW job is called in master sequence.
3.19.6 R i s k s NA
UT Dallas
Page 49
EPM Common and global dimensions3.20 PS_D_TRC:
3.20.1 P r e r e q u i s i t e s The prerequisites to this ETL process are as follows: 1) Following lookup tables are pre-populated, a. PS_S_XLATITEM_VW 3.20.2 A s s u m p t i o n s A TRC will have same SETID across all sources.
3.20.3 S o u r c e True source of TRC information will come from HCM warehouse. 3.20.4 P r o c e s s F l o w O v e r v i e w
3.20.5 P r o c e s s D e s c r i p t i o n 1) Source (PeopleSoft) to Staging (OWS), a. Only FSCM version of the job will load data into OWS table. UT Dallas Page 50
EPM Common and global dimensionsi. Job Name: J_Stage_PS_TL_TRC_TBL_HCM_HCM91_EPM91 b. Modify master sequence to call only FSCM version of job to load OWS ACCOUNT table. 2) Staging (OWS) to MDW a. No changes will be made to hash file creation jobs. b. Modify MDW job to replicate 3 records into hash file for each source i. Job Name: J_Dim_PS_D_TRC c. Make sure above mentioned MDW job is called in master sequence.
3.20.6 R i s k s NA
UT Dallas
Page 51
EPM Common and global dimensions
4
Common Dimensions
4.1 PS_D_DET_PERIOD:
4.1.1 P r e r e q u i s i t e s The prerequisites to this ETL process are as follows: 1) Following lookup tables needs to be prepopulated, a. PS_D_YEAR b. PS_PF_SETID_LOOKUP c. PS_D_DT_PATTERN
4.1.2 A s s u m p t i o n s 1. NA
4.1.3 S o u r c e This table is populated from all 3 sources. Following is the load order, 1) Load all the calendars from FSCM source into OWS table. 2) Load all the calendars from HCM source which are not already loaded by FSCM into OWS table. 3) Load all the calendars from CS source which are not loaded by either FSCM or HCM into OWS table.
UT Dallas
Page 52
EPM Common and global dimensions4.1.4 P r o c e s s F l o w O v e r v i e w
UT Dallas
Page 53
EPM Common and global dimensions
4.1.5 P r o c e s s D e s c r i p t i o n 1) Source (PeopleSoft) to Staging (OWS), a. No change to FSCM OWS job i. Job Name: J_Stage_PS_S_CAL_DETP_TBL_FSCM_FSCM91_EPM91 b. Modify HR OWS job as per following rules, i. Job Name: J_Stage_PS_S_CAL_DETP_TBL_HCM_HCM91_EPM91 ii. Rules: 1. If incoming record exist in OWS table and source is FSCM then it is skipped, 2. If incoming record exist in OWS table and source is not FSCM then it is updated in OWS, 3. If incoming record does not exist in OWS table then it is inserted. c. Modify CS OWS job as per following rules, i. Job Name: J_Stage_PS_S_CAL_DETP_TBL_CS ii. Rules: 1. If incoming record exist in OWS table and source is FSCM or HCM then it is skipped, 2. If incoming record exist in OWS table and source is not FSCM or HCM then it is updated in OWS, 3. If incoming record does not exist in OWS table then it is inserted. 2) Staging (OWS) to MDW a. No changes will be made to hash file creation jobs. b. Modify MDW job to replicate 3 records into hash file for each source i. Job Name: J_Dim_PS_D_DET_PERIOD_E c. Make sure above mentioned MDW job is called in master sequence.
UT Dallas
Page 54
EPM Common and global dimensions
4.1.6 R i s k s NA
4.2 PS_D_DT_PATTERN:
4.2.1 P r e r e q u i s i t e s The prerequisites to this ETL process are as follows: 1) Following lookup tables needs to be pre-populated, a. PS_PF_SETID_LOOKUP 4.2.2 A s s u m p t i o n s NA
4.2.3 S o u r c e This table is populated from all 3 sources. Following is the load order, 1) Load all the patterns from FSCM source into OWS table. 2) Load all the patterns from HCM source which are not already loaded by FSCM into OWS table. 3) Load all the patterns from CS source which are not loaded by either FSCM or HCM into OWS table.
UT Dallas
Page 55
EPM Common and global dimensions4.2.4 P r o c e s s F l o w O v e r v i e w
4.2.5 P r o c e s s D e s c r i p t i o n 1) Source (PeopleSoft) to Staging (OWS), UT Dallas Page 56
EPM Common and global dimensionsa. No change to FSCM OWS job i. J_Stage_PS_S_CAL_DEFN_TBL_FSCM_FSCM91_EPM91 b. Modify HR OWS job as per following rules, i. Job Name: J_Stage_PS_S_CAL_DEFN_TBL_HCM_HCM91_EPM91 ii. Rules: 1. If incoming record exist in OWS table and source is FSCM then it is skipped, 2. If incoming record exist in OWS table and source is not FSCM then it is updated in OWS, 3. If incoming record does not exist in OWS table then it is inserted. c. Modify CS OWS job as per following rules, i. Job Name: J_Stage_PS_S_CAL_DEFN_TBL_CS ii. Rules: 1. If incoming record exist in OWS table and source is FSCM or HCM then it is skipped, 2. If incoming record exist in OWS table and source is not FSCM or HCM then it is updated in OWS, 3. If incoming record does not exist in OWS table then it is inserted. 2) Staging (OWS) to MDW a. No changes will be made to hash file creation jobs. b. Modify MDW job to replicate 3 records into hash file for each source i. Job Name: J_Dim_PS_D_DT_PATTERN_E c. Make sure above mentioned MDW job is called in master sequence.
4.2.6 R i s k s NA
UT Dallas
Page 57
EPM Common and global dimensions4.3 PS_D_BU S_UNIT_CO MP :
4.3.1 P r e r e q u i s i t e s The prerequisites to this ETL process are as follows: 1) Following lookup tables needs to be pre-populated, a. PS_S_BUS_UNIT_FS b. PS_CURRENCY_CD_TBL c. PS_S_BUS_UNIT_FS d. PS_D_DT_PATTERN e. PS_S_SET_CNTRL_REC 4.3.2 A s s u m p t i o n s A BUS_UNIT_COMP for a given business unit will have same SETID across all sources.
4.3.3 S o u r c e True source of BUS_UNIT_COMP information will come from FSCM warehouse. 4.3.4 P r o c e s s F l o w O v e r v i e w
UT Dallas
Page 58
EPM Common and global dimensions4.3.5 P r o c e s s D e s c r i p t i o n 1) Source (PeopleSoft) to Staging (OWS), a. Only FSCM version of the job will load data into OWS table. i. Job Name: J_Stage_PS_S_BUS_UNIT_GL_FSCM_FSCM91_EPM91 b. Modify master sequence to call only FSCM version of job to load OWS BUS_UNIT_COMP table. 2) Staging (OWS) to MDW a. No changes will be made to hash file creation jobs. b. Modify MDW job to replicate 3 records into hash file for each source i. Job Name: J_Dim_PS_D_BUS_UNIT_COMP_E c. Make sure above mentioned MDW job is called in master sequence.
4.3.6 R i s k s NA
4.4 PS_D_BU SIN ESS_UNIT :
4.4.1 P r e r e q u i s i t e s The prerequisites to this ETL process are as follows: 1) Following lookup tables needs to be pre-populated, a. PS_S_BUS_UNIT_FS b. PS_D_BUS_UNIT_PF c. PS_PF_BUS_UNIT_MAP d. PS_D_BUS_UNIT_COMP e. PS_CURRENCY_CD_TBL f. PS_D_DT_PATTERN
g. PS_S_SET_CNTRL_REC
UT Dallas
Page 59
EPM Common and global dimensions4.4.2 A s s u m p t i o n s A BUSINESS_UNIT for a given business unit will have same SETID across all sources. 4.4.3 S o u r c e There are 25 different jobs categorized by business type across all 3 sources i.e. FSCM, HCM and CS loading into BUSINESS_UNIT dimension table. Sr. No. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 Source FSCM FSCM FSCM FSCM FSCM FSCM FSCM FSCM FSCM FSCM FSCM FSCM CS FSCM FSCM FSCM (Loaded by 16 J_Dim_PS_D_BUSINESS_UNIT_PC HCM too) FSCM (Loaded by 17 J_Dim_PS_D_BUSINESS_UNIT_GL HCM too) HCM (Loaded by 18 J_Dim_PS_D_BUSINESS_UNIT_HR FSCM too) 19 J_Dim_PS_D_BUSINESS_UNIT_DM Not Found 20 J_Dim_PS_D_BUSINESS_UNIT_RA Not Found 21 J_Dim_PS_D_BUSINESS_UNIT_RC Not Found 22 J_Dim_PS_D_BUSINESS_UNIT_RF Not Found 23 J_Dim_PS_D_BUSINESS_UNIT_RO Not Found 24 J_Dim_PS_D_BUSINESS_UNIT_RSF Not Found 25 J_Dim_PS_D_BUSINESS_UNIT_RY Not Found Job Name J_Dim_PS_D_BUSINESS_UNIT_AM J_Dim_PS_D_BUSINESS_UNIT_AP J_Dim_PS_D_BUSINESS_UNIT_AR J_Dim_PS_D_BUSINESS_UNIT_BI J_Dim_PS_D_BUSINESS_UNIT_CA J_Dim_PS_D_BUSINESS_UNIT_EX J_Dim_PS_D_BUSINESS_UNIT_IN J_Dim_PS_D_BUSINESS_UNIT_MG J_Dim_PS_D_BUSINESS_UNIT_OM J_Dim_PS_D_BUSINESS_UNIT_PM J_Dim_PS_D_BUSINESS_UNIT_QC J_Dim_PS_D_BUSINESS_UNIT_RS J_Dim_PS_D_BUSINESS_UNIT_SF J_Dim_PS_D_BUSINESS_UNIT_SP J_Dim_PS_D_BUSINESS_UNIT_TD
UT Dallas
Page 60
EPM Common and global dimensions
4.4.4 P r o c e s s F l o w O v e r v i e w
4.4.5 P r o c e s s D e s c r i p t i o n 1) Source (PeopleSoft) to Staging (OWS), a. Mentioned below are job name and owner by business type,
Sr. Job Name No. 1 J_Dim_PS_D_BUSINESS_UNIT_AM 2 J_Dim_PS_D_BUSINESS_UNIT_AP 3 J_Dim_PS_D_BUSINESS_UNIT_AR 4 J_Dim_PS_D_BUSINESS_UNIT_BI 5 J_Dim_PS_D_BUSINESS_UNIT_CA 6 J_Dim_PS_D_BUSINESS_UNIT_EX 7 J_Dim_PS_D_BUSINESS_UNIT_IN
Source FSCM FSCM FSCM FSCM FSCM FSCM FSCM
8 J_Dim_PS_D_BUSINESS_UNIT_MG FSCM 9 J_Dim_PS_D_BUSINESS_UNIT_OM FSCM 10 J_Dim_PS_D_BUSINESS_UNIT_PM 11 J_Dim_PS_D_BUSINESS_UNIT_QC 12 J_Dim_PS_D_BUSINESS_UNIT_RS UT Dallas FSCM FSCM FSCM Page 61
EPM Common and global dimensionsSr. Job Name No. 13 J_Dim_PS_D_BUSINESS_UNIT_SF 14 J_Dim_PS_D_BUSINESS_UNIT_SP 15 J_Dim_PS_D_BUSINESS_UNIT_TD 16 J_Dim_PS_D_BUSINESS_UNIT_PC 17 J_Dim_PS_D_BUSINESS_UNIT_GL 18 J_Dim_PS_D_BUSINESS_UNIT_HR Source CS FSCM FSCM FSCM (Loaded by HCM too) FSCM (Loaded by HCM too) HCM (Loaded by FSCM too)
b. Modify master sequence to call above mentioned jobs to load OWS table. 2) Staging (OWS) to MDW a. No changes will be made to hash file creation jobs. b. Modify MDW job to replicate 3 records into hash file for each source. Modify all 25 jobs.
Sr. Job Name No. 1 J_Dim_PS_D_BUSINESS_UNIT_AM 2 J_Dim_PS_D_BUSINESS_UNIT_AP 3 J_Dim_PS_D_BUSINESS_UNIT_AR 4 J_Dim_PS_D_BUSINESS_UNIT_BI 5 J_Dim_PS_D_BUSINESS_UNIT_CA 6 J_Dim_PS_D_BUSINESS_UNIT_EX 7 J_Dim_PS_D_BUSINESS_UNIT_IN 8 J_Dim_PS_D_BUSINESS_UNIT_MG 9 J_Dim_PS_D_BUSINESS_UNIT_OM 10 J_Dim_PS_D_BUSINESS_UNIT_PM 11 J_Dim_PS_D_BUSINESS_UNIT_QC 12 J_Dim_PS_D_BUSINESS_UNIT_RS 13 J_Dim_PS_D_BUSINESS_UNIT_SF 14 J_Dim_PS_D_BUSINESS_UNIT_SP 15 J_Dim_PS_D_BUSINESS_UNIT_TD 16 J_Dim_PS_D_BUSINESS_UNIT_PC 17 J_Dim_PS_D_BUSINESS_UNIT_GL UT Dallas Page 62
EPM Common and global dimensionsSr. Job Name No. 18 J_Dim_PS_D_BUSINESS_UNIT_HR 19 J_Dim_PS_D_BUSINESS_UNIT_DM 20 J_Dim_PS_D_BUSINESS_UNIT_RA 21 J_Dim_PS_D_BUSINESS_UNIT_RC 22 J_Dim_PS_D_BUSINESS_UNIT_RF 23 J_Dim_PS_D_BUSINESS_UNIT_RO 24 J_Dim_PS_D_BUSINESS_UNIT_RSF 25 J_Dim_PS_D_BUSINESS_UNIT_RY
c. Make sure above mentioned MDW job is called in master sequence.
4.4.6 R i s k s NA
UT Dallas
Page 63
EPM Common and global dimensions
5Sr. No. 1. 2.
Supporting Information and Sources
File Name Customization naming conventions.xlsx EPM Common and Global Dimension Owners New Common and Global Dimensions
File Description Naming convention for Job Modifications
File
Customization naming conventions.xlsx
Spreadsheet identifying true owner for each dimension.
EPM Common Dimensions Owners.xlsx
3
Email confirmation from UTD on some of the dimensions for true owner.
New Common and Global Dimensions.msg
UT Dallas
Page 64