The scenario
A recruiting implementation needs to model how PeopleSoft HCM PS_JOB tables connect during hiring and assignment, from personal data through employment records to organizational job attributes.
What is in this drawing
Read the decisions behind it.
01
Used native erd with crowsfoot cardinality and FK columns to mirror PeopleSoft composite keys.
02
Added lookup tables for company, department, jobcode, location, and position to anchor PS_JOB assignment fields.
03
Included PS_EMPLOYMENT as the parent of PS_JOB based on shared emplid and empl_rcd keys.
Reuse this structure when documenting PeopleSoft HCM job data lineage for recruitment, onboarding, or HR data migration mapping.
More like this