The scenario
PeopleSoft HCM consultants need a reference ERD showing how PS_JOB connects to its core dimension and parent tables.
What is in this drawing
Read the decisions behind it.
01
Model PS_JOB with effective-dated composite key
02
Use native erd table/ref syntax for clear foreign-key mappings
03
Include PS_EMPLOYMENT as parent before PS_JOB to mirror PeopleSoft hierarchy
Reuse for documentation, data governance, or onboarding when mapping PeopleSoft HCM job data relationships.
More like this