Person Contact HDL in Oracle Fusion HCM – Complete Guide with Contact.dat Template

🔹 Introduction: Why Load Person Contact Using HDL?

In Oracle Fusion HCM, person contact details include email addresses, phone numbers, emergency contacts, dependents, and beneficiaries.
Loading these contacts using HDL allows bulk updates and avoids manual entry.

This is essential for:

• Employee onboarding

• Emergency contact management

• Payroll and benefits integration

• Accurate HR reporting

You can see step by step video to load person contact details using this Link

---

🔹 Prerequisites

Before loading Contact.dat, ensure:

1. Worker/person exists in Oracle HCM (PersonNumber must be valid)

2. Source system codes are configured correctly

3. Legislation codes are set (e.g., US, GLOBAL)

4. Contact types and relationships are defined in reference data

---

🔹 Objects Required for Person Contact HDL

Object	Purpose
Contact	Loads person contact records (start date, end date)
ContactName	Loads names for the contact (first, middle, last, title)
ContactRelationship	Defines relationships (emergency, dependent, beneficiary, bondholder)

---

🔹 Sample HDL Templates (Contact.dat hdl template)

• Contact Metadata - Covers Start Date,End Date of Contact

METADATA|Contact|SourceSystemOwner|SourceSystemId|EffectiveStartDate|EffectiveEndDate|PersonNumber|StartDate

MERGE|Contact|XXTEST|XXTEST_PERCNT2|2019/09/01|4712/12/31|XXTEST_CNT1|2019/09/01

• ContactName Metadata - Covers Name of the Person contact

METADATA|ContactName|SourceSystemOwner|SourceSystemId|PersonId(SourceSystemId)|EffectiveStartDate|EffectiveEndDate|LegislationCode|NameType|FirstName|MiddleNames|LastName|Title

MERGE|ContactName|XXTEST|XXTEST_CNTNM2|XXTEST_PERCNT2|2019/09/01|4712/12/31|US|GLOBAL|ADAM||TEST|MR.

• ContactRelationship Metadata - Covers Relation of Person Contact with Worker

METADATA|ContactRelationship|SourceSystemOwner|SourceSystemId|EffectiveStartDate|EffectiveEndDate|PersonId(SourceSystemId)|RelatedPersonId(SourceSystemId)|ContactType|BeneficiaryFlag|DependentFlag|EmergencyContactFlag|BondholderFlag

MERGE|ContactRelationship|XXTEST|XXTEST_CREL_CNT2|2019/09/01|4712/12/31|XXTEST_PERCNT2|XXTEST_PER1|Emergency|||Y|

---

🔹 Field Explanation (Infographic Ready)

Field	Description
SourceSystemOwner	Source system that owns the record
SourceSystemId	Unique ID from source system
PersonNumber	Oracle Fusion employee number
EffectiveStartDate	Start date of contact record
EffectiveEndDate	End date of contact record
LegislationCode	Country/region (e.g., US, GLOBAL)
NameType	Type of contact name (GLOBAL, LOCAL)
ContactType	Emergency, Dependent, Beneficiary, Bondholder
EmergencyContactFlag	Y = Yes, this is emergency contact
DependentFlag	Y = Yes, this is dependent
BeneficiaryFlag	Y = Yes, this is beneficiary
BondholderFlag	Y = Yes, this is bondholder

---

🔹 Step-by-Step Process to Load Person Contact Using HDL

1. Prepare Contact , ContactName , and ContactRelationship metadata

2. Validate PersonNumber and reference data

3. Zip files in a single HDL upload package

4. Go to Tools → HCM Data Loader → Upload

5. Submit process and monitor load status

6. Verify contact records

---

🔹 Common Errors & Resolutions

Issue	Resolution
Contact not created	Verify PersonNumber exists
No change after load	Check EffectiveStartDate and EffectiveEndDate
Invalid ContactType	Validate reference data setup
Missing Name	Ensure ContactName loaded correctly
Emergency/Dependent flag not updated	Verify flags (Y/N)

---

🔹 Best Practices

• Always test in test environment first

• Validate PersonNumber before upload

• Use unique SourceSystemId for each contact

• Keep EffectiveStartDate/EndDate consistent

• Use separate files for Contact, ContactName, ContactRelationship

---

🔹 Internal Linking (SEO Boost)

Link this post to:

• Worker.dat HDL Template

• Assignment Change HDL

• Global Transfer HDL

• Termination HDL

• HDL Common Errors

HDL Template for Person Profile Photo

 For this use  Worker.dat

You can see step by step video to upload the profile photo of worker using this Link

Please find the below sample template :

Save the Blob images in BlobFiles folder and make zip of both .dat and BlobFiles folder 

METADATA|PersonImage|SourceSystemOwner|SourceSystemId|PersonNumber|Image|ImageName|PrimaryFlag

MERGE|PersonImage|XXTEST|XXTEST_PER_IMAGE1|XXTEST2|images.jpeg|XXTEST2|Y

🔥 Oracle HDL Terminate Template (WorkRelationship) with Example & Errors

✅What We Will Cover in This Blog Section (Oracle HDL Blog)

Learn how to terminate a worker in Oracle Fusion HCM using HDL with complete WorkRelationship template, prerequisites, sample .dat file, common errors, and troubleshooting guide.

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

HDL Template for Assignment Changes of Worker in Oracle Fusion HCM (Worker.dat)

HDL Template for Assignment Changes of Worker in Oracle Fusion HCM (With Examples)

Introduction

Assignment changes are one of the most common HR transactions in Oracle Fusion HCM, such as changes in grade, job, department, or location.
Using HCM Data Loader (HDL), these changes can be handled efficiently with WorkTerms and Assignment Objects.

You can see step by step video to make any changes in assignment of worker using this Link

This blog explains:

• Prerequisites

• Complete HDL templates

• Effective dating best practices

• Common mistakes and tips

---

Prerequisites

Before performing assignment changes using HDL, ensure the following:

1. Worker record must already exist

   • Worker should be loaded using Worker.dat

   • 👉 Internal Link: HDL Template to Load Worker 

2. Valid reference data

   • Grade

   • Job

   • Location

   • Department

   • Business Unit

🎥 You can also follow a step-by-step video guide for assignment changes using HDL:
👉 Internal Link: Assignment Change HDL Video Tutorial

---

HDL Template – Assignment Changes Using WorkTerms Object

Metadata

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

Sample Data

MERGE|WorkTerms|ASG_CHANGE|XXTEST2|US1 Legal Entity|2018/01/01|E|
XXTEST_WRKTERM2|2018/01/01|2021/01/02|Y|1|ET|Employee|ACTIVE_PROCESS|
US1 Business Unit|XXTEST_GRADE1|XXTEST_CFO|XXTEST_LOC5|
XXTEST Department1|Y|EMP|PER_REORGANIZATION

MERGE|WorkTerms|ASG_CHANGE|XXTEST2|US1 Legal Entity|2018/01/01|E|
XXTEST_WRKTERM2|2021/01/03|4712/12/31|Y|1|ET|Employee|ACTIVE_PROCESS|
US1 Business Unit|XXTEST_GRADE2|XXTEST_PM|XXTEST_LOC6|XXTEST Department2
|Y|EMP|PER_REORGANIZATION

📌 Key Notes

• Always split records using effective dates

• Use 4712/12/31 for open-ended records

• ASG_CHANGE is mandatory for assignment updates

---

HDL Template – Assignment Changes Using Assignment Object

Metadata

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

Sample Data

MERGE|Assignment|ASG_CHANGE|XXTEST2|US1 Legal Entity|2018/01/01|E|
XXTEST_ASSIGN2|XXTEST_WRKTERM2|2021/01/03|4712/12/31|Y|1|E|Employee|
ACTIVE_PROCESS|US1 Business Unit|XXTEST_GRADE2|XXTEST_PM|XXTEST_LOC6|
XXTEST Department2|Y|N|PER_REORGANIZATION

MERGE|Assignment|ASG_CHANGE|XXTEST2|US1 Legal Entity|2018/01/01|E|
XXTEST_ASSIGN2|XXTEST_WRKTERM2|2018/01/01|2021/01/02|Y|1|E|Employee|
ACTIVE_PROCESS|US1 Business Unit|XXTEST_GRADE1|XXTEST_CFO|XXTEST_LOC5|
XXTEST Department1|Y|N|PER_REORGANIZATION

---

Effective Dating Best Practices

✔ Always maintain continuous date ranges
✔ Never overlap effective dates
✔ Ensure WorkTerms and Assignment dates match
✔ Sequence older record first, then new change

---

Common Errors & Troubleshooting

Assignment Change HDL Common Issue

---

Related HDL Blogs (Internal Links)

• HDL Template for Worker.dat

• Termination of Worker Using HDL

• Reverse Termination of Worker

• Global Transfer of Worker Using HDL

---

Conclusion

Assignment changes using HDL in Oracle Fusion HCM require both WorkTerms and Assignment Objects, correct effective dating, and valid reference data. When done correctly, HDL becomes the fastest and safest way to manage mass assignment updates.

If you found this helpful, bookmark the page and share it with your HCM team 🚀

HDL Template to Reverse Termination of Worker in Oracle Fusion HCM

HDL Template for Reverse Termination of Worker in Oracle Fusion HCM

Introduction

In Oracle Fusion HCM, there are scenarios where an employee is terminated by mistake or needs to be rehired with original service details intact. Instead of creating a new work relationship, Oracle provides a way to reverse the termination using HCM Data Loader (HDL).

This blog explains how to reverse a worker termination using HDL, prerequisites, sample Worker.dat template, and common mistakes to avoid.

You can see step by step video to reverse termination of worker using this Link

---

What Is Reverse Termination in Oracle Fusion?

Reverse termination restores a previously terminated worker by:

• Re-activating the same work relationship

• Preserving seniority, assignments, and service history

• Avoiding creation of a new employee record

This is commonly used when:

• Termination was loaded incorrectly

• Incorrect termination date was applied

• HR wants to undo a termination action

---

Prerequisites

Before reversing a termination using HDL, ensure:

1. Worker data already exists
   (Refer to sample Worker.dat for loading worker)

2. Worker is already terminated
   (Termination must be completed successfully via UI or HDL)

3. Correct SourceSystemOwner and SourceSystemId are known for:

   • WorkRelationship

   • Person

---

Object Used for Reverse Termination

To reverse termination, you must use the WorkRelationship object in Worker.dat.

---

HDL Template for Reverse Termination of Worker

Sample HDL Template

METADATA|WorkRelationship|SourceSystemOwner|SourceSystemId|
PersonId(SourceSystemId)|PersonNumber|DateStart|WorkerType|
LegalEmployerName|ReverseTerminationFlag


MERGE|WorkRelationship|XXTEST|XXTEST_PDSERVICE2|XXTEST_PER2|
XXTEST2|2018/01/01|E|US1 Legal Entity|Y

---

Steps to Reverse Termination Using HDL

1. Prepare Worker.dat with WorkRelationship object

2. Set ReverseTerminationFlag = Y

3. Zip the file

4. Navigate to:

   My Client Groups → Data Exchange → Import and Load Data
   

5. Upload and submit the HDL zip

6. Monitor process status

7. Validate worker record in UI

---

Post Load Validation Checklist

After successful load, verify:

• Worker status is Active

• Assignment is restored

• Termination dates are cleared

• No new work relationship created

---

Common Errors & Troubleshooting

Reverse Termination Common Issues

---

When NOT to Use Reverse Termination

Do not use reverse termination if:

• Employee must be rehired as a new hire

• Legal employer has changed

• Service history must restart

In these cases, perform a new hire action instead.

---

Best Practices

✅ Always confirm termination exists before reversal
✅ Use original WorkRelationship SourceSystemId or User Keys
✅ Validate in lower environments first
✅ Avoid mixing reverse termination with assignment updates

---

Related Articles

• Load Worker Data Using HCM Loader

• HDL Template to Terminate Worker

• Change Non Primary WRL to Primary Work Relationship Using HDL

• Common Worker.dat HDL Errors and Fixes

---

Conclusion

Reverse termination using HDL is a powerful feature when handled correctly. By setting the ReverseTerminationFlag to Y on the WorkRelationship object, you can quickly restore an employee without data loss.

If you frequently work with Oracle Fusion HCM HDL, mastering reverse termination can save hours of manual correction.

Oracle Assignment Supervisor HDL Template with Example | Worker.dat Guide

Overview

In Oracle Fusion HCM, assignment supervisor details (such as Line Manager) can be loaded or updated using HCM Data Loader (HDL). To load an assignment supervisor, Oracle uses the Worker.dat file with the AssignmentSupervisor business object.

You can see step by step video to load assignment supervisor using this Link

This blog explains:

• Prerequisites for loading Assignment Supervisor

• HDL template and sample data

• Key attributes and explanations

• Common errors and troubleshooting

---

Prerequisites

Before loading assignment supervisor data, ensure the following:

1. Worker data must already be loaded

   • Employee, Manager, and their assignments should exist in Fusion.

   • Assignment SourceSystemId must be available.

   • Load Worker data using Worker.dat

2. Assignment and Manager details

   • Both employee and manager must have valid assignments.

   • Manager person and assignment must exist on or before the supervisor effective date.

📌 Note: Assignment Supervisor data is loaded using the Worker.dat file, not a separate HDL file.

---

HDL File Used

Worker.dat

---

Assignment Supervisor HDL Template

METADATA Section

METADATA|AssignmentSupervisor|AssignmentId(SourceSystemId)|SourceSystemOwner
|SourceSystemId|EffectiveStartDate|EffectiveEndDate|
ManagerAssignmentId(SourceSystemId)|ManagerId(SourceSystemId)|
ManagerType|PersonId(SourceSystemId)|PrimaryFlag

Sample MERGE Data

MERGE|AssignmentSupervisor|XXTEST_ASSIGN2|XXTEST|XXTEST_MANAGER1
|2018/01/01|4712/12/31|XXTEST_ASSIGN1|XXTEST_PER1|LINE_MANAGER|
XXTEST_PER2|Y

---

Common Use Cases

• Load Line Manager during employee migration

• Update reporting manager

• Correct supervisor details

• Bulk manager changes using HDL

---

Common Errors & Troubleshooting

Assignment Supervisor Issue

---

Best Practices

• Always validate Assignment and Manager SourceSystemIds

• Use 4712/12/31 as EffectiveEndDate for active supervisors

• Avoid overlapping primary supervisors

• Test with a single record before bulk load

---

Frequently Asked Questions (FAQ)

❓ Which HDL file is used to load Assignment Supervisor?

Assignment Supervisor data is loaded using the Worker.dat file.

❓ Can I update an existing manager using HDL?

Yes, use the same SourceSystemId with updated manager details.

❓ Can I load multiple supervisors?

Yes, but only one primary supervisor is allowed per assignment.

❓ What ManagerType should I use for reporting manager?

Use LINE_MANAGER for standard reporting hierarchy.

❓ Can I end-date a supervisor using HDL?

Yes, update the EffectiveEndDate with the required date.