Examples of Loading Seniority Hours using Oracle HCM HDL

 

✅ Oracle HCM HDL: Load Seniority Hours (Create / Update / Delete) – Worker.dat Examples

For hourly paid workers, many organizations calculate seniority in hours instead of days. To support accurate seniority calculations in Oracle Fusion HCM, you can load seniority hours using HCM Data Loader (HDL).

In this post, you’ll learn how to create, update, and delete Seniority Hours using HDL with both:

• Source Keys (SourceSystemOwner + SourceSystemId)

• User Keys (AssignmentNumber + FromDate)

---

⭐ What are Seniority Hours in Oracle HCM?

Seniority Hours represent the number of hours worked that contribute to a worker’s length of service calculation.

This is mainly used for:

• Hourly paid workers

• Union or bargaining unit employees

• Time & Labor based seniority

• Payroll-driven seniority hours

---

📌 Sources of Seniority Hours Data

You can obtain seniority hours from:

• Oracle Time and Labor (OTL)

• Oracle Global Payroll

• A third-party time system

• External payroll system

---

✅ Important Prerequisites (Must Read)

Before loading seniority hours:

1) Assignment must exist

The assignment must already exist in Oracle HCM.

2) Assignment must be active

The assignment must be active as of the FromDate of the seniority hours.

3) Worker must be hourly paid

The worker must be paid hourly for the entire period you are loading hours.

---

🔍 How to Verify Loaded Seniority Hours

After loading, you can verify data from:

Option 1: UI Page

✅ Manage Seniority Dates page (worker level)

Option 2: Database Query

For multiple workers:
✅ Query table: PER_SENIORITY_HOURS

---

🧾 HDL Object Used

Seniority Hours are loaded using the HDL component:

✅ SeniorityHour (Worker.dat)

---

📂 File Name

📌 File Name:
Worker.dat

---

🔥 Examples of Loading Seniority Hours (HDL)

---

1) Create Seniority Hours Using Source Keys

METADATA|SeniorityHour|AssignmentId(SourceSystemId)|ToDate|FromDate|Hours
|SourceSystemOwner|SourceSystemId
MERGE|SeniorityHour|1031101972|2001/01/01|2000/01/01|500|VISION|UT00214

📌 Notes:

• SourceSystemOwner + SourceSystemId uniquely identify the record

• This is best for integrations from external systems

---

2) Create Seniority Hours Using User Keys

The user keys for SeniorityHour are:

✅ AssignmentNumber + FromDate

METADATA|SeniorityHour|AssignmentNumber|ToDate|FromDate|Hours
MERGE|SeniorityHour|E00214|2001/01/01|2000/01/01|500

---

✏️ Updating Seniority Hours

---

3) Update Seniority Hours Using Source Keys

METADATA|SeniorityHour|AssignmentId(SourceSystemId)|ToDate|FromDate|Hours
|SourceSystemOwner|SourceSystemId
MERGE|SeniorityHour|1031101972|2001/01/01|2000/01/01|600|VISION|UT00214

📌 The update happens because the same SourceSystemOwner + SourceSystemId exists.

---

4) Update Seniority Hours Using User Keys

METADATA|SeniorityHour|AssignmentNumber|ToDate|FromDate|Hours
MERGE|SeniorityHour|E00214|2001/01/01|2000/01/01|600

📌 Oracle identifies the record using:

• AssignmentNumber

• FromDate

---

🗑️ Deleting Seniority Hours

---

5) Delete Seniority Hours Using Source Keys

METADATA|SeniorityHour|AssignmentId(SourceSystemId)|SourceSystemOwner|SourceSystemId
DELETE|SeniorityHour|1031101972|VISION|UT00214

---

6) Delete Seniority Hours Using User Keys

METADATA|SeniorityHour|AssignmentNumber|ToDate|FromDate|Hours
DELETE|SeniorityHour|E00214|2001/01/01|2000/01/01|500

---

✏️ Updating Seniority Hours

✅ Example 1: Load Seniority Hours for Multiple Periods (Same Assignment)

Use this when you want to load hours month-wise / week-wise.

METADATA|SeniorityHour|AssignmentNumber|FromDate|ToDate|Hours
MERGE|SeniorityHour|E00214|2024/01/01|2024/01/31|168
MERGE|SeniorityHour|E00214|2024/02/01|2024/02/29|160
MERGE|SeniorityHour|E00214|2024/03/01|2024/03/31|176