Loading workers

Walk the worker object's components, then load person records, work relationships and assignments. Load a worker with two work relationships and a worker with concurrent assignments. Load supervisor relationships and show why they often come after the main load. Load seniority date overrides for acquired staff, then verify counts and spot-check the complex cases. Manager relationships frequently need a second pass, because a manager must exist before anyone can report to them. Load workers, then load the hierarchy — obvious once said, and one of the failure cases when it is not. Complex cases — dual relationships, concurrent assignments — are where loads break. Test those specifically, not just the simple majority. The simple majority always works. And seniority overrides at load time are how acquired service gets honoured, which closes the loop Module 12 left open: that module ended with exactly this gap as a failure case.

In this module: Module 16 · HCM Data Loader and Data Migration

1. 1Migration strategy: what to bringFree preview
2. 2The loading toolset
3. 3File structure and business objects
4. 4Your first load
5. 5The workforce structures load sequenceFree preview
6. 6Loading workers
7. 7Spreadsheet Data Loader
8. 8Diagnosing failures
9. 9Reconciliation and cutover
10. 10What breaks
11. 11Lab: migrate the workforce and reconcile it