Why HCM has its own loader

HCM data is a different problem from an invoice, and three properties explain the whole loader. EFFECTIVE DATING. A worker record is not one row, it is a sequence of versions each valid over a date range. A salary change does not overwrite the salary; it creates a new version from a date, with the old one intact behind it. Every load is therefore a load AT A DATE, and the date is as much part of the data as the value. HIERARCHIES. Workers report to workers, positions sit under positions, organizations nest. A load has to resolve references to things it may be creating in the same file, which is why order inside the file matters as well as order between files. AND PERSON RECORDS THAT EXIST BEFORE THEY ARE EMPLOYED. A person, a work relationship, an assignment: three separate objects for what a spreadsheet thinks of as one…

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