How SAP SuccessFactors accepts data
Load order and mechanism apply across every object on this platform.
- 1Foundation Objects firstLegal Entity, Business Unit, Division, Department, Location, Job Classification, Pay Group and Cost Center. Everything else references these and nothing downstream succeeds until they are correct.
- 2PositionsWhere position management is in scope, positions exist before a worker can be assigned to one, and position-to-position reporting is established here.
- 3Basic user informationPerson ID External and User ID — where the legacy employee number is either retained or cross-referenced. That decision determines whether history stays traceable to the source.
- 4Biographical and personal informationName, date of birth, national identifiers, addresses, contacts, dependants, with country-specific field requirements applying here.
- 5Employment informationHire, rehire and termination dates and employment status, which anchor every dated record that follows.
- 6Job history (job_info)The effective-dated heart of Employee Central. Every job, transfer, position, manager and status change is a dated row, chronologically sequenced and non-overlapping, each referencing Foundation Objects that already exist.
- 7Manager assignmentSelf-referential — a worker's manager is another worker — so either the hierarchy loads in dependency order or managers are assigned in a second pass.
- 8CompensationBase salary, salary basis, pay frequency, pay components and allowances, effective-dated and validated against the Pay Group Foundation Object.
Employee Central rejects a worker whose department, position, job classification or manager does not already exist, which makes load order part of the design rather than an implementation detail.