Oracle Fusion HCM Global Transfer Using HDL – Complete Template, Examples & Errors

🧩 Introduction (SEO + User Intent)

Learn how to perform Global Transfer in Oracle Fusion HCM using HDL with complete WorkRelationship, WorkTerms, and Assignment templates. Includes sample .dat files, common errors, troubleshooting, and best practices.

Global Transfer in Oracle Fusion HCM is used when an employee moves from one legal employer to another within the organization.
This process can be automated using HDL (HCM Data Loader) by updating WorkRelationship, WorkTerms, and Assignment objects.

In this blog, you will learn:

• What is Global Transfer in Oracle Fusion HCM

• Prerequisites for Global Transfer using HDL

• Complete HDL template with examples

• Explanation of each HDL object

• Common errors and troubleshooting

• Best practices for Global Transfer

---

✅ Prerequisite for Global Transfer using HDL

Before performing Global Transfer, ensure the following:

1. Worker data must already exist in the system. Worker Sample Load

2. PersonNumber must be valid.

3. Legal Employer must exist in the target country.

4. Business Unit, Job, Grade, Location, Department must be configured.

5. Worker.dat file should be loaded earlier.

👉 Worker.dat is mandatory before performing Global Transfer.

You can see step by step video to do global transfer of worker using this Link

---

🧠 What Objects Are Required for Global Transfer?

For Global Transfer, you must load:

Object	Purpose
WorkRelationship	Creates new legal employer relationship
WorkTerms	Updates employment terms
Assignment	Updates assignment details

✅ For Global Transfer, all three objects are required.

---

📄 HDL Template for Global Transfer of Worker

1️⃣ WorkRelationship (Global Transfer Flag)

METADATA|WorkRelationship|PersonNumber|LegalEmployerName|DateStart|ActualTerminationDate|PrimaryFlag|WorkerNumber|WorkerType|RehireRecommendationFlag|OnMilitaryServiceFlag|ActionCode|ReasonCode|DateOfDeath|GlobalTransferFlag

MERGE|WorkRelationship|XXTEST2|US3 Legal Entity|2021/01/05||Y|XXTEST2|E|Y|N|GLB_TRANSFER|||Y

🔍 Explanation

• ActionCode = GLB_TRANSFER → Indicates global transfer

• GlobalTransferFlag = Y → Mandatory for global transfer

• LegalEmployerName → New legal employer

2️⃣ WorkTerms (New Employment Terms)

METADATA|WorkTerms|ActionCode|PersonNumber|LegalEmployerName|DateStart|WorkerType|AssignmentNumber|EffectiveStartDate|EffectiveEndDate|EffectiveLatestChange|EffectiveSequence|AssignmentType|PersonTypeCode|AssignmentStatusTypeCode|BusinessUnitShortCode|GradeCode|JobCode|LocationCode|DepartmentName|PrimaryWorkTermsFlag|SystemPersonType|ReasonCode

MERGE|WorkTerms|GLB_TRANSFER|XXTEST2|US3 Legal Entity|2021/01/05|E|XXTEST_WRKTERM2-1|2021/01/05|4712/12/31|Y|1|ET|Employee|ACTIVE_PROCESS|US1 Business Unit|XXTEST_GRADE1|XXTEST_CFO|XXTEST_LOC5|XXTEST Department1|Y|EMP|REORG

🔍 Explanation

• EffectiveLatestChange = Y → Must be Y for latest record

• EffectiveEndDate = 4712/12/31 → Future date

• AssignmentNumber → New WorkTerms assignment number

3️⃣ Assignment (New Assignment Record)

METADATA|Assignment|ActionCode|PersonNumber|LegalEmployerName|DateStart|WorkerType|AssignmentNumber|WorkTermsNumber|EffectiveStartDate|EffectiveEndDate|EffectiveLatestChange|EffectiveSequence|AssignmentType|PersonTypeCode|AssignmentStatusTypeCode|BusinessUnitShortCode|GradeCode|JobCode|LocationCode|DepartmentName|ManagerFlag|LabourUnionMemberFlag|ReasonCode

MERGE|Assignment|GLB_TRANSFER|XXTEST2|US3 Legal Entity|2021/01/05|E|XXTEST_ASSIGN2-1|XXTEST_WRKTERM2-1|2021/01/05|4712/12/31|Y|1|E|Employee|ACTIVE_PROCESS|US1 Business Unit|XXTEST_GRADE1|XXTEST_CFO|XXTEST_LOC5|XXTEST Department1|Y|N|REORG

🔍 Explanation

• WorkTermsNumber → Must match WorkTerms AssignmentNumber

• ManagerFlag → Y/N

• ReasonCode → Business reason for transfer

⚠️ Common Errors & Troubleshooting

Common Issues in HCM Global Transfers

💡 Best Practices for Global Transfer Using HDL

• Always load WorkRelationship first

• Ensure effective dates do not overlap

• Use unique AssignmentNumber for new legal employer

• Validate reference data before loading

• Test in lower environment before PROD

🔗 Recommended Internal Links 

Add internal links to:

• HDL Worker.dat Template

• HDL Assignment Change Template

• HDL Salary Data Load

• Common HDL Errors in Oracle Fusion

• Sample eText BIP Template

• Dependent Enrollment using HDL

• Assignment Supervisor Update using HDL

❓ FAQ – Global Transfer in Oracle Fusion HCM

Q1. What is Global Transfer in Oracle Fusion HCM?

Global Transfer is the movement of an employee from one legal employer to another within the organization.

Q2. Is Worker.dat required for Global Transfer?

Yes, Worker.dat must be loaded before performing Global Transfer.

Q3. Can Global Transfer be done without WorkTerms?

No, WorkTerms and Assignment are mandatory.

Q4. Why does HDL complete but Global Transfer not appear?

Usually due to EffectiveLatestChange not set to Y or date issues.

Q5. Difference between Global Transfer and Local Transfer?

Global Transfer changes legal employer, while Local Transfer changes assignment within the same legal employer.