The scenario
A PeopleSoft HCM implementation needs a normalized view of PS_JOB as an effective-dated employment history table linked to employees, departments, job codes, positions, locations, and benefits.
What is in this drawing
Read the decisions behind it.
01
Modeled PS_JOB with a composite effective-dated key (emplid, empl_rcd, effdt, effseq)
02
Separated current employee identity from employment rows using Employee and Employment tables
03
Linked benefits at employee level to capture plan elections independent of job history
Use when documenting PeopleSoft HCM data mappings, building integrations, or analyzing effective-dated job records and benefits enrollment.
More like this