Beruflich Dokumente
Kultur Dokumente
ETL DESIGN
16 DECEMBER 2010
UT Dallas Page 1
EPM Common and global dimensions
UT Dallas Page 2
EPM Common and global dimensions
Document Approval
The signatures below indicate that all applicable parties have reviewed this document, have a
common understanding of the document, and agree with its contents.
Title
Signed Date
Application Name
Delivery Manager
Title
Signed Date
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 Contents
Document 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
UT Dallas Page 4
EPM Common and global dimensions
UT Dallas Page 5
EPM Common and global dimensions
3.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 dimensions
UT Dallas Page 7
EPM Common and global dimensions
UT Dallas Page 8
EPM Common and global dimensions
4 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 Purpose
The 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 Source
Source data is fetched from PeopleSoft tables into EPM warehouse for all the common
and global dimension tables.
Naming standard used for job modifications will be same as defined for CS module by
ARDC team.
1.4 Assumptions
1) 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 dimensions
1.5 Risks
ETL 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
Objective 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. Dimension
No. Type Name Owner/Load Order
1 Common PS_D_BUSINESS_UNIT FSCM, HCM & CS
2 Common PS_D_BUS_UNIT_COMP FSCM
3 Common PS_D_DET_PERIOD FSCM, HCM & CS
4 Common PS_D_DT_PATTERN FSCM, HCM & CS
5 Common PS_D_CURRENCY FSCM
6 Common PS_D_DET_BUDGET FSCM
7 Common PS_D_LANGUAGE FSCM
8 Common PS_D_PATTERN_DAY FSCM
9 Common PS_D_SUM_BUDGET FSCM
10 Common PS_D_SUM_PERIOD FSCM
11 Common PS_D_UOM FSCM
12 Global PS_D_ACCOUNT FSCM
13 Global PS_D_CHARTFIELD1 FSCM
14 Global PS_D_CLASS_FIELD FSCM
15 Global PS_D_CMPNY HCM
16 Global PS_D_CUSTOMER FSCM
17 Global PS_D_DEPT HCM
18 Global PS_D_ESTAB HCM
UT Dallas Page 12
EPM Common and global dimensions
Sr. Dimension
No. Type Name Owner/Load Order
19 Global PS_D_FUND FSCM
20 Global PS_D_GOV_SUBAG CS
21 Global PS_D_JOBCODE HCM
22 Global PS_D_LEDGER FSCM
23 Global PS_D_LOCATION FSCM
24 Global PS_D_OPER_UNIT FSCM
Global PS_D_PERSON Load from CS &
25 HCM
26 Global PS_D_PRJ FSCM
27 Global PS_D_PRJ_AC FSCM
28 Global PS_D_PRJ_RSRC FSCM
29 Global PS_D_REG_RGN HCM
30 Global PS_D_SUPPLIER FSCM
31 Global PS_D_TRC HCM
32 Global PS_D_ALTACCT FSCM
33 Global PS_D_ANLYS_TYPE FSCM
34 Global PS_D_BUDGET_REF FSCM
35 Global PS_D_CA FSCM
36 Global PS_D_CHANNEL UNKNOWN
37 Global PS_D_CUST_ORG FSCM
38 Global PS_D_ETHNIC_GRP CS
39 Global PS_D_FREQ HCM
40 Global PS_D_GOV_POI HCM
41 Global PS_D_LRNG_ENV HCM
42 Global PS_D_MATCH_RULE FSCM
43 Global PS_D_ORD_CAPTURE FSCM
Global PS_D_POS HCM
44
45 Global PS_D_PRODUCT FSCM
46 Global PS_D_PROGRAM_FDM FSCM\CS
47 Global PS_D_SALPLN HCM
48 Global PS_D_STAT_CODE FSCM
UT Dallas Page 13
EPM Common and global dimensions
Current 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 dimensions
Scenario:
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
CS Hash File
ACCT# SETID ACCOUNT_SID ACCT# SETID SRC_SYS_ID
123 DAL01 1 123 DAL01 FSCM
1 123 DAL01 HCM
1 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
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
UT Dallas Page 16
EPM Common and global dimensions
3.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
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
3.2.2 A s s u m p t i o n s
NA.
3.2.3 S o u r c e
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
UT Dallas Page 18
EPM Common and global dimensions
a. 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.1 P r e r e q u i s i t e s
3.3.2 A s s u m p t i o n s
NA
3.3.3 S o u r c e
UT Dallas Page 19
EPM Common and global dimensions
3.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
3.3.6 R i s k s
NA
UT Dallas Page 20
EPM Common and global dimensions
3.4 PS_D_FUND:
3.4.1 P r e r e q u i s i t e s
3.4.2 A s s u m p t i o n s
NA
3.4.3 S o u r c e
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
UT Dallas Page 21
EPM Common and global dimensions
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
3.5.2 A s s u m p t i o n s
NA
3.5.3 S o u r c e
UT Dallas Page 22
EPM Common and global dimensions
3.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
3.5.6 R i s k s
NA
UT Dallas Page 23
EPM Common and global dimensions
3.6 PS_D_PRJ:
3.6.1 P r e r e q u i s i t e s
3.6.2 A s s u m p t i o n s
NA
3.6.3 S o u r c e
UT Dallas Page 24
EPM Common and global dimensions
3.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
3.6.6 R i s k s
NA
UT Dallas Page 25
EPM Common and global dimensions
3.7 PS_D_PRJ_RSRC:
3.7.1 P r e r e q u i s i t e s
3.7.2 A s s u m p t i o n s
NA
3.7.3 S o u r c e
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 dimensions
3.7.5 P r o c e s s D e s c r i p t i o n
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
UT Dallas Page 27
EPM Common and global dimensions
3.8.2 A s s u m p t i o n s
NA
3.8.3 S o u r c e
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
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
3.9.2 A s s u m p t i o n s
NA
3.9.3 S o u r c e
UT Dallas Page 29
EPM Common and global dimensions
3.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
3.9.6 R i s k s
NA
UT Dallas Page 30
EPM Common and global dimensions
3.10 PS_D_PERSON:
3.10.1 P r e r e q u i s i t e s
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 dimensions
3.10.4 P r o c e s s F l o w O v e r v i e w
Loads
PS_PERSON
(CS)
If Not
Found
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
UT Dallas Page 33
EPM Common and global dimensions
1. 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.
3.10.6 R i s k s
NA
UT Dallas Page 34
EPM Common and global dimensions
3.11 PS_D_CHARTFIELD1:
3.11.1 P r e r e q u i s i t e s
3.11.2 A s s u m p t i o n s
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
UT Dallas Page 35
EPM Common and global dimensions
a. 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 dimensions
3.12 PS_D_CMPNY:
3.12.1 P r e r e q u i s i t e s
3.12.2 A s s u m p t i o n s
3.12.3 S o u r c e
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 dimensions
3.12.5 P r o c e s s D e s c r i p t i o n
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
UT Dallas Page 38
EPM Common and global dimensions
3.13.2 A s s u m p t i o n s
3.13.3 S o u r c e
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
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
3.14.2 A s s u m p t i o n s
3.14.3 S o u r c e
UT Dallas Page 40
EPM Common and global dimensions
3.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
3.14.6 R i s k s
NA
UT Dallas Page 41
EPM Common and global dimensions
3.15 PS_D_GOV_SUBAG:
3.15.1 P r e r e q u i s i t e s
3.15.2 A s s u m p t i o n s
3.15.3 S o u r c e
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
UT Dallas Page 42
EPM Common and global dimensions
a. 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.1 P r e r e q u i s i t e s
3.16.2 A s s u m p t i o n s
3.16.3 S o u r c e
UT Dallas Page 43
EPM Common and global dimensions
3.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
3.16.6 R i s k s
NA
UT Dallas Page 44
EPM Common and global dimensions
3.17.1 P r e r e q u i s i t e s
3.17.2 A s s u m p t i o n s
3.17.3 S o u r c e
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 dimensions
3.17.5 P r o c e s s D e s c r i p t i o n
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
UT Dallas Page 46
EPM Common and global dimensions
i. PS_S_SET_CNTRL_REC
3.18.2 A s s u m p t i o n s
3.18.3 S o u r c e
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
UT Dallas Page 47
EPM Common and global dimensions
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
3.19.2 A s s u m p t i o n s
3.19.3 S o u r c e
UT Dallas Page 48
EPM Common and global dimensions
3.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
3.19.6 R i s k s
NA
UT Dallas Page 49
EPM Common and global dimensions
3.20 PS_D_TRC:
3.20.1 P r e r e q u i s i t e s
3.20.2 A s s u m p t i o n s
3.20.3 S o u r c e
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
UT Dallas Page 50
EPM Common and global dimensions
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
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 dimensions
4.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
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
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 dimensions
4.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
UT Dallas Page 56
EPM Common and global dimensions
4.2.6 R i s k s
NA
UT Dallas Page 57
EPM Common and global dimensions
4.3.1 P r e r e q u i s i t e s
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
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 dimensions
4.3.5 P r o c e s s D e s c r i p t i o n
4.3.6 R i s k s
NA
4.4.1 P r e r e q u i s i t e s
UT Dallas Page 59
EPM Common and global dimensions
4.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. Job Name Source
1 J_Dim_PS_D_BUSINESS_UNIT_AM
FSCM
2 J_Dim_PS_D_BUSINESS_UNIT_AP
FSCM
3 J_Dim_PS_D_BUSINESS_UNIT_AR
FSCM
4 J_Dim_PS_D_BUSINESS_UNIT_BI
FSCM
5 J_Dim_PS_D_BUSINESS_UNIT_CA
FSCM
6 J_Dim_PS_D_BUSINESS_UNIT_EX
FSCM
7 J_Dim_PS_D_BUSINESS_UNIT_IN
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
FSCM
11 J_Dim_PS_D_BUSINESS_UNIT_QC
FSCM
12 J_Dim_PS_D_BUSINESS_UNIT_RS
FSCM
13 J_Dim_PS_D_BUSINESS_UNIT_SF
CS
14 J_Dim_PS_D_BUSINESS_UNIT_SP
FSCM
15 J_Dim_PS_D_BUSINESS_UNIT_TD
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
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
Sr.
Job Name Source
No.
1 J_Dim_PS_D_BUSINESS_UNIT_AM FSCM
2 J_Dim_PS_D_BUSINESS_UNIT_AP FSCM
3 J_Dim_PS_D_BUSINESS_UNIT_AR FSCM
4 J_Dim_PS_D_BUSINESS_UNIT_BI FSCM
5 J_Dim_PS_D_BUSINESS_UNIT_CA FSCM
6 J_Dim_PS_D_BUSINESS_UNIT_EX FSCM
7 J_Dim_PS_D_BUSINESS_UNIT_IN 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 FSCM
11 J_Dim_PS_D_BUSINESS_UNIT_QC FSCM
12 J_Dim_PS_D_BUSINESS_UNIT_RS FSCM
UT Dallas Page 61
EPM Common and global dimensions
Sr.
Job Name Source
No.
13 J_Dim_PS_D_BUSINESS_UNIT_SF CS
14 J_Dim_PS_D_BUSINESS_UNIT_SP FSCM
15 J_Dim_PS_D_BUSINESS_UNIT_TD FSCM
FSCM (Loaded by HCM
16 J_Dim_PS_D_BUSINESS_UNIT_PC
too)
FSCM (Loaded by HCM
17 J_Dim_PS_D_BUSINESS_UNIT_GL
too)
HCM (Loaded by FSCM
18 J_Dim_PS_D_BUSINESS_UNIT_HR
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 dimensions
Sr.
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
4.4.6 R i s k s
NA
UT Dallas Page 63
EPM Common and global dimensions
UT Dallas Page 64