HDL vs HSDL in Oracle HCM Cloud

 

✅ HSDL vs HDL in Oracle HCM Cloud – What’s the Difference? (Complete Guide)

If you work on Oracle HCM Cloud, you’ve definitely heard about HDL and HSDL. Many people get confused because both tools are used for loading and updating HCM data — but they are designed for different purposes.

In this blog, you will understand:

• What is HDL and where it is used

• What is HSDL and why it is business-friendly

• Key differences between HSDL vs HDL

• Which tool is best for conversions, integrations, and ongoing maintenance

• Best practices and recommendations

---

📌 What is HDL (HCM Data Loader)?

HDL (HCM Data Loader) is Oracle’s powerful bulk data loading tool used mainly for:

✅ Initial data migration
✅ Large volume transactions
✅ Complex object hierarchy loads
✅ Background processing

Key Features of HDL

• File-based loader using .dat files

• Requires object-level technical understanding

• Supports full object structures like:

  • Work Relationships

  • Work Terms

  • Assignments

  • Person Details

  • Payroll, Absence, Benefits (depends on object)

• Best suited for implementation and mass updates

💡 Ideal for:
Conversions, integrations, and large-scale changes.

---

📌 What is HSDL (HCM Spreadsheet Data Loader)?

HSDL (HCM Spreadsheet Data Loader) is a spreadsheet-based tool built on top of HDL. It is designed for business-friendly data entry.

Key Features of HSDL

• Uses Excel templates

• Validates data before submission

• User-friendly interface

• Faster for small to medium data loads

• No need to manually write .dat files

• Suitable for functional users

• Limited compared to full HDL capability

💡 Ideal for:
Quick updates, ongoing maintenance, and functional team usage.

---

🔥 HDL vs HSDL – Key Differences (Comparison Table)

Feature	HDL	HSDL
Format	.dat files	Excel templates
Skill Required	Technical + object knowledge	Functional / business friendly
Best For	Conversions + integrations	Quick operational updates
Data Volume	High volume supported	Small to medium volume
Complex Hierarchy	Fully supported	Limited
Validations	Mostly during load	Pre-validation in Excel
Processing	Background	Submission through spreadsheet
Error Handling	HDL logs + stage tables	Spreadsheet validation + errors
Usage	Implementation team	Business users + HR operations

---

✅ When to Use HDL?

Use HDL when you need:

• Initial employee conversion

• Mass updates (10K+ records)

• Complex object loads (Worker + Assignment + Manager + Payroll objects)

• Integrations (scheduled automated file loads)

• Data migration for go-live

📌 Example HDL Use Cases:

• Worker conversion using Worker.dat

• Loading seniority hours

• Loading absence entries in bulk

• Loading organization, jobs, grades, locations

• Payroll-related objects

---

✅ When to Use HSDL?

Use HSDL when you need:

• Quick business updates

• Ongoing maintenance

• Smaller loads

• User-friendly templates

• HR team managed loads

📌 Example HSDL Use Cases:

• Updating phone numbers

• Updating addresses

• Updating manager (small volume)

• Updating cost center assignment

• Updating personal details

---

⭐ My Recommendation (Best Practice)

✅ Use HDL for:

• Implementations

• Integrations

• Mass loads

• Conversions

• Complex hierarchy loads

✅ Use HSDL for:

• Quick business-driven updates

• Day-to-day operational loads

• HR/functional team maintenance

📌 Both tools are essential in Oracle HCM Cloud.
Choosing the right one improves productivity and reduces errors.

✅ Flow Chart : 

HDL vs HSDL

---

🧠 Real Project Tip (Very Important)

During conversions, teams often load Worker data in multiple batches.

In that scenario:

• HDL is always the best option

• You can control performance by disabling auto-trigger processes

• You can run post conversion ESS jobs once at the end

(Example: Refresh Manager Hierarchy, Update Person Search Keywords)

---

🔗 Internal Links 

• Oracle HDL Worker Data Load (Complete Guide) → (worker HDL link)

• HDL Seniority Date Adjustments Examples → (seniority date post link)

• HDL Seniority Hours Template + Examples → (seniority hours post link)

• HDL Absence Entry Template → (Absence entry post link)

• Post Conversion ESS Jobs After HDL (Best Practices) → (ESS jobs post link)

---

❓ FAQ – HSDL vs HDL in Oracle HCM Cloud

Q1. Is HSDL different from HDL?

HSDL is built on top of HDL. It uses Excel templates and converts the data into HDL format internally.

Q2. Which is better for conversion – HDL or HSDL?

HDL is better for conversions because it supports large volume and complex object hierarchy loads.

Q3. Can HSDL load Worker object like HDL?

HSDL supports many worker-related templates, but HDL gives full control and supports complex dependencies.

Q4. Do we need technical knowledge for HSDL?

Not much. HSDL is designed for functional users and HR operations.

Q5. Why is HDL preferred for integrations?

Because HDL can be automated using file-based loads, scheduled processes, and it supports large datasets.

Q6. Which tool gives better error reporting?

HDL provides detailed logs, stage tables, and error records. HSDL provides template validation and simplified errors.

Q7. Can we use both HDL and HSDL in the same project?

Yes. Most Oracle HCM implementations use HDL for conversion and HSDL for business maintenance.

---

💬 Feedback & Comments

Did you use HDL or HSDL in your project?

Share in the comment section:

• Which object you loaded (Worker, Absence, Payroll, etc.)

• Any error you faced

• Whether you used HDL, HSDL, or both

I reply to all comments with solutions and sample templates. 🙌

Oracle HCM Payroll: YTD Balance Query

 

✅ Oracle HCM Payroll: YTD Balance Query (SQL) – Complete Guide

If you are working on Oracle HCM Cloud Payroll, one of the most common requirements is to extract YTD (Year-To-Date) balances for employees.

This is needed for:

• Payroll reconciliation

• Payslip validation

• Tax reporting

• Audit requirements

• Integration with third-party payroll/finance systems

In this blog, you will learn how to fetch Payroll YTD balances using SQL from Oracle Fusion HCM tables, with practical examples.

---

📌 What is YTD Balance in Payroll?

YTD (Year-To-Date) is the total accumulated balance for an employee from the beginning of the payroll year up to the current payroll period.

Example:

• Jan payroll run: YTD = Jan amount

• Feb payroll run: YTD = Jan + Feb

• Mar payroll run: YTD = Jan + Feb + Mar

Oracle Payroll stores balances at different dimensions like:

• Relationship

• Assignment

• Person

• Tax unit

• Payroll statutory unit

---

🔥 Important Oracle Payroll Tables for Balance Queries

Oracle Fusion payroll balances are stored and derived using these major objects:

Package 

• PAY_BALANCE_VIEW_PKG.GET_BALANCE_DIMENSIONS

Core Balance Tables (Commonly Used)

• PAY_PAYROLL_ACTIONS

• PAY_PAYROLL_REL_ACTIONS

• PAY_PAYROLL_ASSIGNMENTS

• PAY_BALANCE_TYPES_VL

• PAY_DIMENSION_USAGES_VL

Person/Assignment Tables

• PER_ALL_PEOPLE_F

• PER_ALL_ASSIGNMENTS_M

• PER_PERIODS_OF_SERVICE

---

✅ Best Practice Approach for YTD Balance Query

There are 2 ways to extract balances:

Method 1 : Query from Balance Package

This is the cleanest method.

Method 2 (Recommended): Using HCM Extract

This is the fasted Method.

---

✅ 1) YTD Balance Query (Most Common)

This query returns YTD balances for a person for a given balance name.

⚠️ Note: Table names and columns may vary slightly by release and security model, but the logic remains the same.

select   BAL.BALANCE_VALUE,
ppra.PAYROLL_ACTION_ID,
ppa.effective_date,
bal.balance_dimension_id  ,
bal.BALANCE_TYPE_ID  
from 
PAY_PAYROLL_ACTIONS ppa
,PAY_PAYROLL_REL_ACTIONS ppra
,PAY_PAYROLL_ASSIGNMENTS pasg
,PAY_BALANCE_TYPES_VL B
,PAY_DIMENSION_USAGES_VL D
,TABLE (pay_balance_view_pkg.get_balance_dimensions(B.BALANCE_TYPE_ID
   , ppra.PAYROLL_REL_ACTION_ID
		, NULL
 , NULL)) BAL
where 1=1
AND Ppa.PAYROLL_ACTION_ID = ppra.PAYROLL_ACTION_ID
AND BAL.BALANCE_VALUE <> 0
and  ppa1.effective_date =:effective_date
and ppra.PAYROLL_RELATIONSHIP_ID = pasg.PAYROLL_RELATIONSHIP_ID 
			 AND EXISTS (SELECT 1 FROM PAY_RUN_RESULTS PRR
			  WHERE PRR.PAYROLL_REL_ACTION_ID = ppra.PAYROLL_REL_ACTION_ID)
 AND Ppa.ACTION_TYPE IN ('Q','R')
and ppa.effective_date =:P_Effective_date
AND d.balance_dimension_id = bal.balance_dimension_id
AND b.balance_name = 'Gross'
AND d.database_item_suffix = '_REL_NOCB_YTD'
and d.LEGISLATION_CODE ='US'
and :Assignment_id = pasg.HR_ASSIGNMENT_ID	

Example Inputs

• Balance Name = Gross Pay

• Dimension = Relationship Year to Date

Note:- Recommendation method to extract the balance using HCM Extract only due to performance issues in BIP Report.

---

🧠 How to Find Correct Balance Name and Dimension?

Balance Name

Navigate:
My Client Groups → Payroll → Balance Definitions

Dimension Name

Navigate:
Balance Definitions → Balance Dimensions

Common dimensions:

• Relationship Year to Date

• Assignment Year to Date

• PSU Year to Date

• Tax Unit Year to Date

---

⚠️ Common Issues in YTD Balance SQL

1) Balance value is coming as NULL

Possible reasons:

• balance not fed by any element

• payroll not run

• wrong dimension selected

• wrong effective date filters

2) Duplicate rows

Reason:

• multiple effective rows in *_F tables
  Solution:

• use correct effective date filters

3) Wrong totals

Reason:

• using Assignment YTD instead of Relationship YTD

• multiple payroll relationships

---

🔗 Internal Links 

• HDL Worker Data Load Guide → (Worker HDL post link)

• HDL Absence Entry Template → (Absence HDL post link)

• HDL Seniority Hours Template → (Seniority Hours post link)

• HDL Template for Benefit Enrollment  → (HDL post link)

• eText BIP Report → (HDL post link)

---

✅ FAQ (Frequently Asked Questions)

Q1. Which table stores payroll balances in Oracle Fusion?

Payroll balances are stored in PAY_BALANCES and related balance definition tables like PAY_BALANCE_TYPES_F and PAY_BALANCE_DIMENSIONS_F.

Q2. What is the best dimension for YTD in payroll?

For most use cases, the best dimension is Relationship Year to Date.

Q3. Why do I see multiple YTD rows for one employee?

This happens when the employee has multiple payroll relationships or multiple effective dated rows. Use Payroll Relationship ID for accuracy.

Q4. Can I calculate YTD from run results instead of balance tables?

Yes. You can sum PAY_RUN_RESULT_VALUES by period, but it is slower and mainly used for audit and breakdown.

Q5. What is the difference between PTD and YTD?

PTD is Period-To-Date (only current payroll period), while YTD is Year-To-Date (sum from payroll year start).

Q6. How do I find the correct balance name?

Go to Balance Definitions in the Payroll module and copy the exact balance name.

Q7. Can YTD balances be extracted for terminated employees?

Yes, but ensure your effective date filters include termination date or use a parameterized date instead of SYSDATE.

Oracle HCM Post Conversion ESS Jobs After HDL

 

✅ Post Conversion Best Practices in Oracle HCM Cloud  – ESS Jobs After HDL

When you complete a data conversion or perform incremental updates using HDL (HCM Data Loader) in Oracle HCM Cloud, the work is not finished yet. HDL Post Conversion Processes.

A successful HDL load updates core tables, but several dependent tables and search indexes still need to be refreshed for:

• Correct reporting

• Accurate person search results

• Manager hierarchy visibility

• Role provisioning and LDAP synchronization

• Seniority date creation

This article covers the most important post conversion ESS processes, when to run them, and the best scheduling strategy.

---

📌 Why Post Conversion ESS Processes Are Required?

After bulk HDL loads, Oracle HCM Cloud may not automatically:

• Update manager hierarchy tables

• Rebuild person keyword search indexes

• Synchronize person data to consuming applications

• Push role/user requests to LDAP

• Generate default seniority date records

Running the right ESS processes at the right time avoids:

❌ Missing managers in hierarchy
❌ People not appearing in search
❌ Incorrect reporting
❌ Delayed user provisioning
❌ Seniority records not created

---

✅ Post Conversion ESS Processes (Complete List)

#	Program	Description
1	Synchronize Person Records	Publishes events to consuming applications (example: TCA model) for changes in person/assignment details.
2	Refresh Manager Hierarchy	Refreshes denormalized hierarchy table PER_MANAGER_HRCHY_DN for performance.
3	Update Person Search Keywords	Populates keywords into PER_KEYWORDS table for fast search.
4	Optimize Person Search Keywords Index	Optimizes/rebuilds the PER_KEYWORDS index.
5	Autoprovision Roles for All Users	Evaluates all users against role provisioning rules (heavy + LDAP intensive).
6	Send Pending LDAP Requests	Sends user and role requests to LDAP.
7	Send Personal Data for Multiple Users to LDAP	Syncs name/email/manager fields from HCM to LDAP after bulk updates.
8	Synchronize Person Assignments from Position	Required if using Position Management and PositionOverrideFlag = Y.
9	Calculate Seniority Dates	Generates default V3 seniority records based on configured rules.

---

⚡ Auto-Triggered Processes After Worker HDL Load

By default, Oracle triggers these after Worker.dat finishes:

✅ Refresh Manager Hierarchy
✅ Update Person Search Keywords

How to disable auto-trigger?

You can disable one or both using a SET instruction in Worker.dat.

This is helpful when:

• You are running multiple worker batches

• You want to run these processes only once at the end

---

📅 When to Run Post Conversion ESS Programs?

This is a debated topic, but below is a practical schedule that works for most conversions.

Program	One-time Conversion	Incremental Updates	Notes
Synchronize Person Records	✅ Yes	✅ Yes	Run after bulk loads, best after hours.
Refresh Manager Hierarchy	✅ Yes (Auto-trigger)	✅ Yes (Auto-trigger)	Run manually if auto-trigger disabled.
Update Person Search Keywords	✅ Yes (Auto-trigger)	✅ Yes (Auto-trigger)	Run manually if auto-trigger disabled.
Optimize Person Search Keywords Index	✅ Yes	✅ Yes	Best daily during low system usage.
Autoprovision Roles for All Users	❌ No	❌ No	Run only when provisioning rules change.
Send Pending LDAP Requests	✅ Yes	✅ Yes	Best daily schedule for future dated requests too.
Personal Data for Multiple Users to LDAP	✅ Yes	Depends	Required only after bulk name/email/manager updates.
Synchronize Person Assignments from Position	Depends	Depends	Required for full HR + position management.
Calculate Seniority Dates	✅ Yes	✅ Yes	Required after worker loads if using seniority.

---

🔍 Deep Dive: How to Run Each ESS Process

---

1) Synchronize Person Records

This job is resource intensive because it publishes events to SOA.

Recommended Run Time

✅ After hours
✅ After bulk HDL worker loads

Parameters

1. From Date

2. To Date

3. After Batch Load (Yes/No/Blank)

How to run (Daily)

• From Date = System Date

• To Date = System Date

• After Batch Load = No

How to run (Specific Period)

Example:

• From Date = 12-Aug-2019

• To Date = 18-Aug-2019

⚠️ Important Note

• Maximum date range should be 7 days

• First run can accept more than 7 days

• Subsequent runs with >7 days may end in Warning and publish no events

---

2) Refresh Manager Hierarchy

Oracle stores manager hierarchy in a denormalized table:

📌 PER_MANAGER_HRCHY_DN

HDL updates do not always refresh this automatically unless auto-trigger is enabled.

Parameter

• Updated Within the Last N Days

  • Use 1 day for daily schedule

  • Leave blank for initial full refresh

---

3) Update Person Search Keywords

This process populates the keyword table:

📌 PER_KEYWORDS

Parameters

1. Batch Id

2. Name

3. After Batch Load (Yes/No/Blank)

Best Ways to Run

✅ For a specific HDL batch

• Enter Batch Id only

• Leave other parameters blank

✅ For one person

• Enter Name only

• Leave others blank

✅ Delta/Incremental mode

• After Batch Load = Yes

• Works only when delta size < 20K

⚠️ For delta > 20K
Run with no parameters (All People)

---

4) Optimize Person Search Keywords Index

This improves performance of keyword search.

Recommended Scheduling

✅ Daily during maintenance window
✅ Run after “Update Person Search Keywords”

Parameters

1. Maximum Optimization Time (default 180 minutes)

2. Optimization Level

   • Full Optimization (default)

   • Rebuild Index

---

5) Autoprovision Roles for All Users

This job evaluates ALL users against auto role provisioning rules.

⚠️ It is heavy and can generate many LDAP requests.

Best Practice

❌ Do not schedule daily
✅ Run manually only when provisioning rules change

Parameter

• Process Generated Role Requests (Yes/No)

✅ Recommended: No (defer processing)

---

6) Send Pending LDAP Requests

This job sends pending user/role requests to LDAP.

Best Practice

✅ Run after bulk HDL worker loads
✅ Schedule daily for ongoing requests + future dated processing

Parameters

1. User Type (All/Party/Person)

2. Batch Size

   • Use A (auto calculate)

---

7) Send Personal Data for Multiple Users to LDAP

This job ensures LDAP personal data matches HCM:

• First Name

• Last Name

• Email

• Manager

When required?

✅ After bulk updates via HDL or Spreadsheet loaders
✅ Recommended once after conversion

---

8) Synchronize Person Assignments from Position

Required if:

• You are using Position Management

• You load assignments with PositionOverrideFlag = Y

• You want manager or attributes synchronized from position

Parameters

1. Past Period in Days (default 30)

2. Run at Enterprise Level (Yes/No)

3. Legal Employer

---

9) Calculate Seniority Dates

📌 Important:
You cannot create V3 seniority records using HDL.
HDL supports only updates.

So after loading Worker.dat, you must run:

✅ Calculate Seniority Dates

Parameters

1. Person Number (optional list)

2. Past Period in Days (default 1)

3. Include Terminated Work Relationships

4. Legal Employer

5. Union

6. Selected Seniority Date Rules

---

⚙️ Performance Tip: Chunk Size for Calculate Seniority Dates

The Past Period in Days controls how many workers are picked.

• Large period = more workers = slower run

• Small period = fewer workers = faster run

Improve performance using multi-threading

Oracle supports multi-threading via profile option:

📌 PER_EMP_SD_MAX_PROCESS_REC

Steps

1. Navigate to Manage Profile Options

2. Create profile option:

• Profile Option Code: PER_EMP_SD_MAX_PROCESS_REC

• Display Name: PER_EMP_SD_MAX_PROCESS_REC

• Application: Global Human Resources

• Module: Employment

• Start Date: 01/01/1951

3. Enable it and allow update at Site level

4. Navigate to Manage Administrator Profile Values

5. Set site value (example: 2000 / 10000)

This value becomes the chunk size and controls number of threads.

---

✅ Recommended Post Conversion Run Sequence (Best Practice)

For a one-time conversion, this sequence is practical:

1. Refresh Manager Hierarchy

2. Update Person Search Keywords

3. Optimize Person Search Keywords Index

4. Calculate Seniority Dates

5. Send Pending LDAP Requests

6. Send Personal Data for Multiple Users to LDAP

7. Synchronize Person Records

---

🔗 Internal Links

• HDL Worker Data Load Guide → (URL)

• HDL Seniority Date Adjustments → (URL)

• HDL Seniority Hours Template → (URL)

• HDL Absence Entry Template → (URL)

• eText Template Report in Oracle Fusion  → (URL)

• Third Party Load in Oracle Fusion → (URL)

---

❓ Frequently Asked Questions (FAQ)

Q1. Are Refresh Manager Hierarchy and Update Person Search Keywords mandatory?

Yes. These processes ensure manager visibility and person search performance after HDL loads.

Q2. Can I disable auto-triggered processes after Worker.dat?

Yes. Use SET instructions in Worker.dat to prevent automatic execution.

Q3. Should I schedule “Autoprovision Roles for All Users” daily?

No. Run it only when auto role provisioning rules change.

Q4. Why are people not visible in search after HDL?

Usually because PER_KEYWORDS is not updated or the index needs optimization.

Q5. Why are managers missing after HDL?

Because PER_MANAGER_HRCHY_DN is not refreshed. Run Refresh Manager Hierarchy.

Q6. Why are seniority dates missing after conversion?

Because V3 seniority records are not created by HDL. Run Calculate Seniority Dates.

Q7. Which job sends new user accounts to LDAP?

Send Pending LDAP Requests.

Q8. When should I run Synchronize Person Records?

After bulk person loads, preferably after hours, using correct date range.

---

💬 Feedback & Comments

Have you faced issues after HDL conversion like:

• missing managers

• people not appearing in search

• delayed user provisioning

• seniority dates not created

Drop your questions in the comment section 👇

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