Oracle Worker.dat HDL Template with Example | Oracle Fusion HCM Guide

Introduction

Oracle Worker.dat HDL template is used to load employee, assignment, and work relationship data into Oracle Fusion HCM using HCM Data Loader (HDL). This tutorial explains Worker.dat HDL file structure, examples, loading steps, and common errors..

You will also find:

• Sample HDL templates

• Required components per object

• Loading steps and verification

• Related articles for Oracle Fusion troubleshooting

Oracle Cloud - Creation of Simple OTBI Report

Development of Simple OTBI Report

In this blog we are going to learn how to develop/create your first OTBI report.

You can see Step by Step Creation of OTBI Report in this video

We will develop the report for below details:

• Person Number
• Date of Birth
• First Name
• Last Name
• Grade Name
• Job Name
• Department

To achieve this requirement follow the below steps.

Step 1 - 

Open the Oracle Fusion Application.

Step 2 - Navigation

Follow the below navigation,

Navigator -> Tools -> Report & Analytics -> Click on Browse Catalog

Step 3 - Creation of Simple Report 

Click on New and then Analysis

It will pop up list of predefined Subject Areas in Oracle Fusion.

Select the appropriate Subject Area to develop the OTBI report.

As per our requirement we are going to select "Worker Management - Worker Assignment Real Time"

Subject Area.

It will open the report development page.

It contains 3 sections:

1) Subject Area - 

It hold all the selected Subject Area Details.

2) Selected Columns - 

In this section we can add columns required for report.

3) Filters - 

Using this section we can add filter to restrict the data in report.

Step 4 - Adding Column in Report

As per our requirement add the columns.

Person Number, DOB, First name, Last Name are related to Worker.

Expand the Selected Subject Area then Search for Worker Folder to add above columns.

Expand Worker Folder add above mentioned columns like Person Number, DOB etc.

Then add Job,Grade and Department Name columns from respective folders.

To run the report click on Results.

It will give you the output.

Step 5 - Change the Column Heading

Click Column Setting -> Column Properties -> Column Format (tab)

Enable the Custom Heading check box.

Enter the required Column Heading.

Run the report again to check if column heading are changed or not.

Step 5 - Add Filter on OTBI Report.

Suppose we need to apply filter on Person Number then click Column Setting  of Person Number, select Filter.

It will popup filter details window.

In this you can mention how you need to apply the filter based on your requirement.

Run the report to check if filter is working fine.

Step 6 - Save the OTBI Report.

Save the report in My Folder.

You can find your report in My Folder.

You can see Step by Step Creation of OTBI Report in this video

Oracle Cloud - Load Work Structure Components - HDL

Load Work Structure Using HCM Data Loader in Oracle Fusion HCM

Oracle Fusion HCM provides HCM Data Loader (HDL) as a powerful and efficient tool to load and maintain large volumes of HCM data. One of the most common technical requirements during implementation or data migration is loading Work Structure components.

In this blog, we will walk through how to load Work Structure using HCM Data Loader in Oracle Fusion HCM, with complete HDL file examples and step-by-step instructions.

In an earlier blog, we explained how to define Source Keys and created a custom Source System Owner – XXTEST. The same source system will be reused while loading Work Structure objects.

📽️ A step-by-step video walkthrough is also available using the provided link.

---

What Are Work Structures in Oracle Fusion HCM?

Work Structures define the organizational framework of an enterprise and are prerequisites for loading Worker and Assignment data.

Using HCM Data Loader, the following Work Structure components can be loaded:

• Grade

• Job

• Location

• Organization

• Position

Each component is loaded using its respective HDL object and must follow a proper dependency sequence.

---

Download Work Structure Object Templates

Before creating HDL files, download the required object templates from your Fusion instance.

Navigation:

Navigator → My Client Group → Data Exchange → View Business Objects

This page displays all business objects supported by HCM Data Loader. Download the templates related to Work Structure Objects.

Note: In this blog, only the required attributes are used from the template to simplify the data load.

---

Load Grade Using HCM Data Loader

Grades define employee levels within an organization.

HDL File – Grade

METADATA|Grade|SourceSystemOwner|SourceSystemId|EffectiveStartDate
|EffectiveEndDate|SetCode|GradeCode|GradeName|ActiveStatus

MERGE|Grade|XXTEST|XXTEST_GRADE01|1951/01/01|4712/12/31|COMMON
|XXTEST_GRADE01|XXTEST Grade01|A

🔑 Source Keys Used

• SourceSystemOwner: XXTEST

• SourceSystemId: XXTEST_GRADE01

📁 Save the file as Grade.dat

---

Load Job Using HCM Data Loader

Jobs represent roles such as Manager, Analyst, or Director.

HDL File – Job

METADATA|Job|SourceSystemOwner|SourceSystemId|EffectiveStartDate
|EffectiveEndDate|SetCode|JobCode|Name|ActiveStatus|RegularTemporary

MERGE|Job|XXTEST|XXTEST_JOB1|1951/01/01|4712/12/31|COMMON|XXTEST_CFO
|XXTEST: Chief Financial Officer|A|R

📁 Save the file as Job.dat

---

Load Location Using HCM Data Loader

Locations define physical or logical work locations.

HDL File – Location

METADATA|Location|SourceSystemOwner|SourceSystemId|EffectiveStartDate
|EffectiveEndDate|SetCode|LocationCode|LocationName|Description
|ActiveStatus|AddressLine1|AddressLine2|TownOrCity|Region1|Region2
|PostalCode|Country

MERGE|Location|XXTEST|XXTEST_LOC5|1951/01/01|4712/12/31|COMMON
|XXTEST_LOC5|XXTEST Location5|XXTEST Location6|A|250 Some st1||Pasadena
|Los Angeles|CA|91101|US

📁 Save the file as Location.dat

---

Load Organization Using HCM Data Loader

Organization loading requires two HDL objects.

1️⃣ Organization

METADATA|Organization|SourceSystemOwner|SourceSystemId|EffectiveStartDate
|EffectiveEndDate|Name

MERGE|Organization|XXTEST|XXTEST_DEPT1|1951/01/01|4712/12/31
|XXTEST Department1

---

2️⃣ Org Unit Classification

METADATA|OrgUnitClassification|SourceSystemOwner|SourceSystemId
|EffectiveStartDate|EffectiveEndDate|OrganizationId(SourceSystemId)
|ClassificationCode|SetCode|Status

MERGE|OrgUnitClassification|XXTEST|XXTEST_DEPT_CLASS1|1951/01/01
|4712/12/31|XXTEST_DEPT1|DEPARTMENT|COMMON|A

📁 Save both records in a single file as Organization.dat

---

Load Position Using HCM Data Loader

Positions define individual instances of jobs within departments.

HDL File – Position

METADATA|Position|SourceSystemOwner|SourceSystemId|EffectiveStartDate
|EffectiveEndDate|PositionCode|Name|BusinessUnitName|ActiveStatus
|JobId(SourceSystemId)|DepartmentId(SourceSystemId)|HiringStatus
|PositionType|FTE|HeadCount|FullPartTime|WorkingHours|Frequency

MERGE|Position|XXTEST|XXTEST_POSITION1|1951/01/01|4712/12/31|
XXTEST_POS1|XXTEST Position1|US1 Business Unit|A|XXTEST_JOB1|
XXTEST_DEPT1|APPROVED|NONE|1|1|FULL_TIME|40|W

📁 Save the file as Position.dat

---

Create ZIP File for HDL Load

Create a ZIP file containing all HDL .dat files:

• Grade.dat

• Job.dat

• Location.dat

• Organization.dat

• Position.dat

Example:

WorkStructure_HDL_Load.zip

---

Load HDL Files into Oracle Fusion HCM

Navigation:

Navigator → My Client Group → Data Exchange → Import and Load → Import

Steps:

1. Upload the ZIP file

2. Submit the Import and Load process

3. Refresh to monitor the load status

Once the process completes successfully, the Work Structure data is loaded.

---

Verify Work Structure Data

After successful load, verify the data from respective pages:

• Manage Grades

• Manage Jobs

• Manage Locations

• Manage Organizations

• Manage Positions

---

Conclusion

Using HCM Data Loader, Work Structure components in Oracle Fusion HCM can be efficiently loaded by defining correct Source Keys, using the required attributes, and following the proper load sequence.

This approach is commonly used during:

• Data migration

• Initial implementation

• Test-to-production refresh

---

What’s Next?

➡️ In the next blog, we will cover how to load Worker Data in Oracle Fusion HCM using HCM Data Loader, including Worker, Assignment, and Element Entry objects.

Define Source System Owner in Oracle Fusion HCM (HDL Source Keys Explained)

Introduction

When loading data into Oracle Fusion HCM using HDL (HCM Data Loader), Source Keys play a critical role in uniquely identifying records across multiple data loads.
Without properly defining the Source System Owner, HDL loads will fail or behave inconsistently.

In this blog, you’ll learn:

• What Source System Owner is

• How it works with Source System ID

• Step-by-step process to define Source System Owner in Oracle Fusion

• Why it is mandatory for HDL loads

You can see step by step video using this link.

---

What Are Source Keys in Oracle Fusion HCM?

Source Keys are unique identifiers used by Oracle Fusion to track records loaded via HDL.

Source Keys consist of two components:

1. SourceSystemOwner

2. SourceSystemId

📌 These keys help Oracle Fusion:

• Identify records uniquely

• Support incremental loads

• Prevent duplicate data

• Enable updates using the same source reference

---

What Is Source System Owner?

Source System Owner represents the external or internal system from which the data originates.

Examples:

• Legacy HR System

• Payroll System

• Custom Data Migration Source

• Interface Program

Before using Source Keys in HDL files, the Source System Owner must be defined in Fusion.

---

Prerequisite

• Access to Setup & Maintenance

• Appropriate implementation privileges

---

Navigation to Define Source System Owner

Follow the steps below:

1. Navigator

2. Go to Setup & Maintenance

3. Open Task Panel tab

4. Click Search

5. Search for Manage Common Lookups

6. Open Manage Common Lookups

---

Search for Source System Owner Lookup

1. In the Meaning field, enter:

   Source System Owner
   

2. Click Search

3. In the results, you will see the Source System Owner lookup definition along with existing lookup values

---

Add a New Source System Owner

In the Lookup Code Values section, click Add (+) and enter the following details:

Field	Value
Lookup Code	XXTEST
Display Sequence	1
Enabled	✔ Checked
Start Date	01/01/1951
End Date	12/31/4712
Meaning	XXTEST
Description	XXTEST

📌 Dates ensure the lookup remains valid indefinitely.

---

Save the Lookup

Click Save and Close.

✅ Your Source System Owner is now successfully defined.

---

How This Is Used in HDL

Once the Source System Owner is defined:

• You can reference it in HDL files

• Combine it with SourceSystemId to form Source Keys

• Use Source Keys to create or update records

Example:

SourceSystemOwner = XXTEST
SourceSystemId    = EMP001

This combination uniquely identifies the record in Oracle Fusion.

---

Common Issues & Tips

• ❌ HDL fails if Source System Owner is not defined

• ❌ Typo in SourceSystemOwner causes load errors

• ✔ Always use consistent Source Keys across loads

• ✔ Avoid changing Source System Owner once data is loaded

---

Conclusion

Defining Source System Owner is a mandatory and foundational step when working with HDL in Oracle Fusion HCM.
It ensures data integrity, smooth incremental loads, and reliable record identification.

Once configured, you can confidently use Source Keys across all HDL objects.

---

What’s Next?

👉 In the next blog, we will cover:

How to Load Work Structure in Oracle HCM Fusion using HDL

Stay tuned 🚀