What breaks: four HCM load failures

Four failures, and the last two are the ones that reach production. One. A worker loaded before their position exists. The assignment is rejected naming the position attribute. Visible, cheap, and the fix is the load order from Lesson 3. Two. An effective date a day early. Usually a spreadsheet or time-zone artefact. It does not fail: it creates a one-day version, and the record afterwards shows a change nobody made. Payroll will find it before you do. Three. A source key reused across two people. The second load updates the first person instead of creating the second. The count is one short, no error is raised, and a real employee's record now carries somebody else's details. The uniqueness check in Lesson 5 is one query and prevents it entirely. Four. A load that succeeded into a FUTURE-DATED version nobody can see today. The screen shows the current version, which…

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