Oracle Fusion · HCM · Master data
Migrate workers into Oracle Fusion HCM, covering person records, work relationships, assignments, effective-dated history and the dependencies that gate the load.
Oracle Fusion separates the person from the employment. A person record describes the human being; a work relationship describes their relationship with a legal employer; an assignment describes the job they do within it. Someone rehired twice with a concurrent second job is one person, several work relationships and several assignments.
Everything is effective-dated with explicit start and end dates, and HDL rejects gaps and overlaps outright. Reconstructing a legacy history as a clean, contiguous set of dated rows is the bulk of the work on this object.
Scope is agreed in discovery; this is the shape of the object.
| Data area | Typical information |
|---|---|
| Person | Name, date of birth, gender, national identifiers, person number |
| Contact information | Addresses, phones, emails, emergency contacts |
| Work relationship | Legal employer, hire date, worker type, termination date |
| Assignment | Job, position, grade, department, location, manager, FTE, working hours |
| Assignment history | Effective-dated rows for every job, transfer and status change |
| Salary | Salary basis, amount, effective dates |
| Documents | Document records and attachments where in scope |
Dependency drives load sequence: a child cannot exist before its parent.
Confirm each of these before the first migration cycle.
Production-proven means we have delivered this object from that source. Supported and custom-mapping describe capability, not delivery history.
Object-level equivalence. Field-level mapping is produced per engagement.
| Source system | Source entity | Target object |
|---|---|---|
| PeopleSoft | PERSONAL_DATA + JOB | Fusion Person + Work Relationship + Assignment |
| Paycom | Employee + job records | Fusion Person + Assignment |
| SuccessFactors | Person + Employment + job_info | Fusion Person + Work Relationship + Assignment |
| JD Edwards | Address Book + Employee Master (F060116) | Fusion Person + Assignment |
HCM Data Loader (HDL) — pipe-delimited .dat files per business object, zipped
HCM Spreadsheet Data Loader (HSDL) for smaller or corrective loads
Worker REST services for incremental updates after go-live
Matched on national identifier, name and date of birth to avoid duplicate people.
No gaps and no overlaps across assignment rows.
Job, position, grade, department and location all present before the assignment.
Not merely at the current date.
Assignments and salary cannot start before the work relationship.
Vary by legal employer country and are enforced per country.
What has to exist before this object can load.
What actually fails on this object, and why.
Counts alone rarely prove this object migrated correctly.
Headcount at cutover: active workers in source vs loaded, by legal employer
Total worker records including terminated, which is normally far higher than active headcount
Assignment count against the expected worker-to-assignment ratio, allowing for concurrent jobs
Manager coverage: every worker who should have a supervisor has one
Effective-date span per worker compared to the agreed history depth
Key field comparison on a sample: hire date, job, department, FTE, salary
Detailed employment history for long-terminated workers is a common archive candidate. Retention obligations often run seven years or more, but the new HCM only needs the population it will administer. Migrating active and recently terminated workers and archiving the rest keeps the tenant clean and licensing honest.
Extraction, mapping, transformation, validation preparation and target load generation.
Explore DataMove →Preserves source, prepared and target states for reconciliation, lineage and audit evidence.
Explore DataVault →Migration progress, data quality, exceptions and readiness across cycles.
Explore DataLens →Source-specific guidance for moving this object.
Published case studies whose scope included workers.
Tell us your source application, target system, object scope, volume and migration timeline. We can discuss the recommended migration approach and relevant Syntra ETL project experience.