Business objects and their dependencies

Worker, Assignment, Position, Job — and the load order is not in any error message. The structural objects come first: Jobs and Positions, along with the Organizations and Locations they reference, because an assignment names them and cannot be created against something that does not exist. Then Worker, which creates the person and the work relationship. Then Assignment, which connects the person to the job, position, organization and manager. MANAGER HIERARCHIES ARE THE ONE THAT BITES. An assignment naming a manager needs that manager's assignment to exist already — so a file loaded in a random order fails on roughly half its rows for a reason that reads as a data problem. Load top-down where you can, or load assignments without managers first and add the reporting relationship in a second pass. The second approach is usually easier and always more diagnosable. And within one file, order matters too, because…

In this module: Module 8 · HDL for HCM data

1. 1Why HCM has its own loader
2. 2The .dat file format
3. 3Business objects and their dependencies
4. 4Effective dates: the part that catches everyone
5. 5Source keys and matching existing records
6. 6Loading, monitoring and the error report
7. 7Corrections and the delete you cannot do
8. 8HDL versus HSDL, and when to use each
9. 9What breaks: four HCM load failures
10. 10Lab briefing · Load a workforce, then correct it