...
- There are 160 tables from Peoplesoft; deltas go daily to replicator
- There are a number of impacted dms / mini marts stewarded by CIT that haven't surfaced as impacted by HR/Payroll until we saw Dave's daigram
- Some have extensive impact and other have minor impact
- In all cases shown in the diagrams data is moved/copied, transformed and inserted into those tables
- There is no clarity (written, definitive statements) from the Workday project on the representation of level 9s org data
- All suers users of the marts will have to be the ones to explain how the various org roll ups work and why they are needed.
- There are various possibilities of getting the representation done in Workday:
- custom fields
- 'containers'
- IN any case, the department tree is used broadly in the feeds from PS HR/Payroll
Big questions:
- what are the data conversion implications of org data?
- what are the implications of various Workday org representations and transformations from that to the pre-Workday org structures and representation?
Things to do:
- categorize the impact in terms of size and complexity and impact/risk
- decide who owns talking to campus about downstream impacts / campus extracts and uses and their own reports
- figure out if we need to and how to gauge the impact to models and reports
- dive into the diagram and illustrate the basic purpose, use, data extracts, transformations, and extracts in more detail
- map out the canned Workday jobs extract with the PS jobs table used for 80% of the right hand side of the diagram
- need to think hard about if we really want transaction systems fed from a warehouse and we have to think about timing of the systems;
- make sure time collection is included in reporting
- WORKDAY: Supply a meta data model (fields definitions,types, uses, examples of fields)
...