Loading, monitoring and the error report

Load, watch, and read the failure — and the failure names an OBJECT rather than a row, which is the difference from FBDI. The load is submitted as a process and produces a status and counts per business object: how many Worker records succeeded, how many Assignment records failed. Read the counts per object, not just the overall status, because a load where Workers succeeded and Assignments failed reports as a partial success and leaves the estate in the half-loaded state Lesson 3 warns about. The error report groups by object and message. A single underlying cause — one missing position — produces a rejection for every assignment referencing it, so a thousand errors are frequently one problem. Sort by message and count the distinct ones first; that number is how many problems you actually have. The message names the object and the attribute, and rarely the reason — the…

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