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.

HDL Template for Assignment Supervisor

HDL Template for Assignment Supervisor in Oracle Fusion HCM

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.