HDL for Global Transfers in Oracle Fusion HCM – Complete Technical Walkthrough

 

HDL for Global Transfers: Technical Walkthrough

Description

Learn how to perform Global Transfers using Oracle Fusion HCM HDL with the WorkRelationship data model. This technical walkthrough explains required objects, effective dating, HDL structure, common errors, and best practices.

---

Introduction

A Global Transfer in Oracle Fusion HCM occurs when an employee moves from one legal employer to another while retaining the same person record. From an HDL perspective, global transfers are one of the most complex Core HR transactions due to effective dating, object relationships, and sequencing rules.

With the current HCM data model, Global Transfers are handled using WorkRelationship , WorkTerms and Assignment

This blog provides a step-by-step technical walkthrough of handling Global Transfers using HCM Data Loader (HDL) based on the correct object structure.

---

Global Transfer – Correct Data Model Structure

Visual Diagram – Before vs After Global Transfer

BEFORE Global Transfer

Worker (PersonNumber: E1001)
 └─ WorkRelationship (India Legal Employer)
     └─ WorkTerms
         └─ Assignment (Primary)

AFTER Global Transfer

Worker (PersonNumber: E1001)
 ├─ WorkRelationship (India Legal Employer) → End-dated
 │   └─ WorkTerms
 │       └─ Assignment (End-dated)
 │
 └─ WorkRelationship (US Legal Employer)
     └─ WorkTerms
         └─ Assignment (Primary)

This visual clearly shows that during a Global Transfer:

• The Person record remains unchanged

• A new WorkRelationship is created for the new Legal Employer

• WorkTerms and Assignment are never reused across Legal Employers

Worker (same PersonNumber)
 ├─ WorkRelationship (Old Legal Employer) → End-dated
 └─ WorkRelationship (New Legal Employer)
     └─ WorkTerms
         └─ Assignment

---

Key HDL Objects Involved

To process a Global Transfer using HDL, the following objects are required:

1. Worker

2. WorkRelationship (End-date old)

3. WorkRelationship (Create new)

4. WorkTerms (Create new)

5. Assignment (Create new)

⚠️ WorkTerms and Assignments cannot be reused across Legal Employers.

---

Important Pre-Requisites

Before loading HDL:

• New Legal Employer must exist

• Business Unit must be correctly mapped

• Job, Position, Grade, Location must be valid for the new LE

• SourceSystemOwner must remain consistent

---

Effective Dating Rules for Global Transfers

Follow these critical rules:

• New WorkRelationship start date = Global transfer date

• Old WorkRelationship end date = Day before new WorkRelationship start date

• WorkTerms start date = New WorkRelationship start date

• Assignment start date = WorkTerms start date

Violating these rules will cause HDL failures.

---

HDL Load Sequencing (Mandatory)

Load HDL files in this exact order:

1. Worker.dat (MERGE – optional updates)

2. WorkRelationship.dat (End-date old WR)

3. WorkRelationship.dat (Create new WR)

4. WorkTerms.dat (Create new WT)

5. Assignment.dat (Create new Assignment)

---

Common HDL Errors and Fixes

❌ Assignment Exists Under Old Legal Employer

Error:

Assignment already exists

Fix:

• Do not reuse old AssignmentNumber

• Create a new Assignment under the new WorkRelationship

---

❌ Effective Date Validation Error

Error:

Effective start date must be on or after WorkRelationship start date

Fix:

• Align WorkRelationship, WorkTerms, and Assignment start dates

---

❌ Missing WorkRelationship

Error:

No WorkRelationship exists

Fix:

• Ensure new WorkRelationship load completed successfully

---

Post-Load Validation Checklist

After HDL load:

• Verify old WorkRelationship is end-dated

• Confirm new Legal Employer on WorkRelationship

• Validate WorkTerms and Assignment details

• Check Person Management UI

---

Best Practices for Global Transfers via HDL

• Always test in lower environments

• Use incremental loads only

• Keep separate HDL files per object

• Maintain clear SourceSystemId strategy

• Capture ESS Request IDs

---

Real Project Scenario

Scenario: Employee transferred from India LE to US LE

Approach:

• End-date India WorkRelationship on 31-Mar

• Create US WorkRelationship on 01-Apr

• Create WorkTerms and Assignment under US LE

Result: Clean Global Transfer without data corruption.

---

Conclusion

Global Transfers using HDL require precise control over WorkRelationship, WorkTerms, and Assignment objects, along with strict effective dating and sequencing. When executed correctly, HDL provides a reliable and auditable way to manage cross–legal employer movements.

This knowledge is a key differentiator for senior Fusion HCM Technical Consultants.