Local Transfer vs Global Transfer in Oracle Fusion HCM HDL – Technical Differences, Use Cases, and Best Practices

 

Local Transfer vs Global Transfer (HDL)

Description

Understand the difference between Local and Global Transfers in Oracle Fusion HCM HDL. Learn object-level changes, effective dating rules, HDL sequencing, and common errors with a clear technical comparison.

---

Introduction

Employee transfers are common in enterprise organizations, but in Oracle Fusion HCM, not all transfers are the same. From an HDL (HCM Data Loader) perspective, Local Transfers and Global Transfers behave very differently and impact different Core HR objects.

Misunderstanding this difference often leads to:

• Assignment failures

• WorkRelationship errors

• Incorrect legal employer data

This blog provides a complete technical comparison of Local vs Global Transfers using HDL, including object structure, effective dating rules, HDL sequencing, and real project guidance.

---

High-Level Difference

Local Vs Global Transfer Comparison Flow 

---

Local Transfer – Technical Overview

What Is a Local Transfer?

A Local Transfer occurs when an employee moves within the same Legal Employer, such as:

• Department change

• Job or position change

• Location or manager change

The WorkRelationship remains unchanged.

---

Local Transfer – Data Model Impact

Worker
 └─ WorkRelationship (Same LE)
     └─ WorkTerms (Same)
         └─ Assignment (Updated)

---

Local Transfer – HDL Approach

• Use MERGE on Assignment

• No need to create new WorkRelationship or WorkTerms

• Effective date reflects the transfer date

Objects Used

• Worker (optional)

• Assignment (MERGE)

---

Common Local Transfer Errors

• Incorrect effective start date

• Using CREATE instead of MERGE

• Overwriting historical assignment data

---

Global Transfer – Technical Overview

What Is a Global Transfer?

A Global Transfer occurs when an employee moves from one Legal Employer to another, often across countries.

This requires creation of a new WorkRelationship.

---

Global Transfer – Data Model Impact

Worker
 ├─ WorkRelationship (Old LE) → End-dated
 └─ WorkRelationship (New LE)
     └─ WorkTerms
         └─ Assignment

---

Global Transfer – HDL Approach

• End-date old WorkRelationship

• Create new WorkRelationship

• Create new WorkTerms

• Create new Assignment

Objects Used

• Worker (MERGE – optional)

• WorkRelationship (MERGE + CREATE)

• WorkTerms (CREATE)

• Assignment (CREATE)

---

Effective Dating Comparison

Rule	Local Transfer	Global Transfer
WorkRelationship	No change	End-date old, create new
WorkTerms	No change	Start with new WR
Assignment Start Date	Transfer date	Same as new WR
Historical Data	Preserved	Preserved

---

HDL Sequencing Comparison

Local Transfer

1. Assignment.dat (MERGE)

Global Transfer

1. WorkRelationship.dat (End-date old)

2. WorkRelationship.dat (Create new)

3. WorkTerms.dat (Create)

4. Assignment.dat (Create)

---

How to Decide: Local vs Global Transfer

Ask these questions:

1. Is the Legal Employer changing?

2. Is the payroll or country changing?

3. Is a new WorkRelationship required?

If the answer to #1 is YES, it is a Global Transfer.

---

Common Mistakes to Avoid

❌ Treating Global Transfer as Local Transfer
❌ Reusing Assignment across Legal Employers
❌ Missing WorkTerms during Global Transfer
❌ Incorrect effective dating across objects

---

Best Practices

• Always confirm Legal Employer change first

• Use incremental HDL loads

• Keep separate files for each object

• Test transfer scenarios in lower environments

• Validate results in Person Management UI

---

Conclusion

Understanding the technical difference between Local and Global Transfers in HDL is essential for accurate data management in Oracle Fusion HCM. While Local Transfers are assignment-level changes, Global Transfers require precise handling of WorkRelationship, WorkTerms, and Assignment objects.

Mastering this distinction is a key skill for senior Fusion HCM Technical Consultants.

---