Lab briefing · Load a workforce, then correct it

Load twenty workers with assignments, then correct one salary the right way — and observe what the history looks like afterwards. Twenty is deliberate. Small enough to read every record, large enough that the load order matters and a manager hierarchy exists. Include at least three people who report to another person IN THE FILE, so the ordering problem from Lesson 3 is real rather than described. Before loading: check the source keys are unique. Count rows, count distinct keys, confirm. That is the query from Lesson 5 and it takes thirty seconds. After loading: read the counts per business object, not the overall status. Workers and Assignments should both be twenty. If Workers is twenty and Assignments is seventeen, you have the half-loaded estate, and finding that now rather than at the end is the point. Then the correction, and it is the real deliverable. Change one salary effective…

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