Showing posts with label Worker Salary. Show all posts
Showing posts with label Worker Salary. Show all posts

Sunday, 30 June 2024

HDL Template for Salary Data In Fusion HCM


How to Load Worker Salary in Oracle Fusion HCM Using HDL (Salary.dat)

Learn how to create or update worker salary in Oracle Fusion HCM using HDL Salary.dat. Step-by-step guide with sample template, required fields, salary basis, action codes, approval flag, and common error fixes.

Oracle Fusion HCM allows you to load or update worker salary using HCM Data Loader (HDL).
This is useful when you need to migrate salary data during:

  • New implementation (initial data load)

  • Bulk salary updates

  • Salary corrections

  • Salary changes during hiring

In this blog, you will learn:

✅ Salary HDL file name and structure
✅ Required attributes
✅ Salary basis and approval flag
✅ Sample Salary.dat template
✅ Common errors and troubleshooting

You can see step by step video to load Salary data using this Click Here


📌 HDL File Used

To load salary data, use:

✅ Salary.dat


✅ Prerequisites (Very Important)

Before loading salary using HDL, make sure:

1) Worker & Assignment already exist

Salary is always tied to an assignment.

So these must exist first:

  • Worker record

  • AssignmentNumber


2) Salary Basis must exist

SalaryBasisName should already be configured.

Example:

  • US1 Annual Salary

  • Monthly Salary

  • Hourly Rate

Navigation:
My Client Groups → Salary → Salary Basis


3) Worker must have valid payroll / employment info

Salary often fails if assignment is missing:

  • legislation code

  • grade

  • payroll details (in some setups)


✅ Salary.dat Template (Sample)

Use the below sample:

METADATA|Salary|AssignmentNumber|DateFrom|DateTo|SalaryAmount|SalaryBasisName|ActionCode|SalaryApproved

MERGE|Salary|ORACLE_ASG12|1991/01/01||10000|US1 Annual Salary|HIRE|Y



✅ Field Explanation (Salary HDL)

1) AssignmentNumber

This is the unique assignment number of the worker.

Example:

ORACLE_ASG12

2) DateFrom / DateTo

  • DateFrom = salary effective start date

  • DateTo = keep blank unless you want to end-date salary

Example:

1991/01/01

3) SalaryAmount

Salary amount to load.

Example:

10000

4) SalaryBasisName

This must match exactly with configured Salary Basis.

Example:

US1 Annual Salary

5) ActionCode

Defines why salary is being loaded.

Common values:

  • HIRE

  • SALARY_CHANGE

  • PROMOTION

  • TRANSFER

Example:

HIRE

6) SalaryApproved

Salary approval flag.

Values:

  • Y = approved

  • N = not approved

Example:

Y

✅ Step-by-Step: Load Salary Using HDL

Step 1: Create Salary.dat file

Create a .dat file and add metadata + merge line.


Step 2: Create .zip file

Create a zip file:

Example:

Salary.zip

Inside zip:

Salary.dat

Step 3: Upload in HDL

Navigate to:

My Client Groups → Data Exchange → HCM Data Loader

Steps:

  1. Import and Load Data

  2. Upload Salary.zip

  3. Submit


Step 4: Monitor HDL Status

Check:

  • Import Status

  • Load Status

  • Completed Successfully / Error


Step 5: Validate Salary in UI

Navigate to:

My Client Groups → Person Management → Search Worker → Salary

Confirm:

  • Salary Amount

  • Salary Basis

  • Effective date


⭐ Example: Load Salary for Multiple Workers

METADATA|Salary|AssignmentNumber|DateFrom|DateTo|SalaryAmount|SalaryBasisName|ActionCode|SalaryApproved MERGE|Salary|ORACLE_ASG12|1991/01/01||10000|US1 Annual Salary|HIRE|Y MERGE|Salary|ORACLE_ASG13|1991/01/01||12000|US1 Annual Salary|HIRE|Y MERGE|Salary|ORACLE_ASG14|1991/01/01||15000|US1 Annual Salary|HIRE|Y

🔥 Common HDL Errors & Fixes

❌ 1) Salary basis not found

Error:
SalaryBasisName is invalid

✅ Fix:

  • Verify Salary Basis exists

  • Match exact name (case-sensitive)


❌ 2) Assignment number not found

Error:
AssignmentNumber doesn’t exist

✅ Fix:

  • Confirm assignment is created successfully

  • Load worker/assignment first


❌ 3) Salary overlaps existing salary

Error:
Overlapping salary records

✅ Fix:

  • End-date previous salary using DateTo

  • Or use correct DateFrom


❌ 4) Salary not approved

Error:
Salary not visible in UI

✅ Fix:

  • Set SalaryApproved = Y

  • Ensure approvals not required in workflow


🔗 Internal Links 



⭐ FAQs 

Q1. Which file is used to load salary using HDL?

Salary is loaded using Salary.dat in Oracle Fusion HCM.

Q2. What is required before loading salary using HDL?

Worker and Assignment must exist, and Salary Basis must be configured.

Q3. Can we update salary using MERGE?

Yes, MERGE can create or update salary records depending on the effective date.

Q4. What is SalaryApproved in Salary.dat?

SalaryApproved is a flag that indicates whether the salary record is approved (Y) or not approved (N).

Q5. What is the most common reason salary HDL fails?

The most common reasons are invalid SalaryBasisName and incorrect AssignmentNumber.

Wednesday, 18 January 2023

HDL Template for Salary of Worker


How to Load Worker Salary in Oracle Fusion HCM Using HDL (Salary.dat)

Learn how to create or update worker salary in Oracle Fusion HCM using HDL Salary.dat. Step-by-step guide with sample template, required fields, salary basis, action codes, approval flag, and common error fixes.

Oracle Fusion HCM allows you to load or update worker salary using HCM Data Loader (HDL).
This is useful when you need to migrate salary data during:

  • New implementation (initial data load)

  • Bulk salary updates

  • Salary corrections

  • Salary changes during hiring

In this blog, you will learn:

✅ Salary HDL file name and structure
✅ Required attributes
✅ Salary basis and approval flag
✅ Sample Salary.dat template
✅ Common errors and troubleshooting

You can see step by step video to load Salary data using this Click Here


📌 HDL File Used

To load salary data, use:

Salary.dat


✅ Prerequisites (Very Important)

Before loading salary using HDL, make sure:

1) Worker & Assignment already exist

Salary is always tied to an assignment.

So these must exist first:

  • Worker record

  • AssignmentNumber


2) Salary Basis must exist

SalaryBasisName should already be configured.

Example:

  • US1 Annual Salary

  • Monthly Salary

  • Hourly Rate

Navigation:
My Client Groups → Salary → Salary Basis


3) Worker must have valid payroll / employment info

Salary often fails if assignment is missing:

  • legislation code

  • grade

  • payroll details (in some setups)


✅ Salary.dat Template (Sample)

Use the below sample:

METADATA|Salary|AssignmentNumber|DateFrom|DateTo|SalaryAmount|SalaryBasisName|ActionCode|SalaryApproved

MERGE|Salary|ORACLE_ASG12|1991/01/01||10000|US1 Annual Salary|HIRE|Y



✅ Field Explanation (Salary HDL)

1) AssignmentNumber

This is the unique assignment number of the worker.

Example:

ORACLE_ASG12

2) DateFrom / DateTo

  • DateFrom = salary effective start date

  • DateTo = keep blank unless you want to end-date salary

Example:

1991/01/01

3) SalaryAmount

Salary amount to load.

Example:

10000

4) SalaryBasisName

This must match exactly with configured Salary Basis.

Example:

US1 Annual Salary

5) ActionCode

Defines why salary is being loaded.

Common values:

  • HIRE

  • SALARY_CHANGE

  • PROMOTION

  • TRANSFER

Example:

HIRE

6) SalaryApproved

Salary approval flag.

Values:

  • Y = approved

  • N = not approved

Example:

Y

✅ Step-by-Step: Load Salary Using HDL

Step 1: Create Salary.dat file

Create a .dat file and add metadata + merge line.


Step 2: Create .zip file

Create a zip file:

Example:

Salary.zip

Inside zip:

Salary.dat

Step 3: Upload in HDL

Navigate to:

My Client Groups → Data Exchange → HCM Data Loader

Steps:

  1. Import and Load Data

  2. Upload Salary.zip

  3. Submit


Step 4: Monitor HDL Status

Check:

  • Import Status

  • Load Status

  • Completed Successfully / Error


Step 5: Validate Salary in UI

Navigate to:

My Client Groups → Person Management → Search Worker → Salary

Confirm:

  • Salary Amount

  • Salary Basis

  • Effective date


⭐ Example: Load Salary for Multiple Workers

METADATA|Salary|AssignmentNumber|DateFrom|DateTo|SalaryAmount|SalaryBasisName|ActionCode|SalaryApproved MERGE|Salary|ORACLE_ASG12|1991/01/01||10000|US1 Annual Salary|HIRE|Y MERGE|Salary|ORACLE_ASG13|1991/01/01||12000|US1 Annual Salary|HIRE|Y MERGE|Salary|ORACLE_ASG14|1991/01/01||15000|US1 Annual Salary|HIRE|Y

🔥 Common HDL Errors & Fixes

❌ 1) Salary basis not found

Error:
SalaryBasisName is invalid

✅ Fix:

  • Verify Salary Basis exists

  • Match exact name (case-sensitive)


❌ 2) Assignment number not found

Error:
AssignmentNumber doesn’t exist

✅ Fix:

  • Confirm assignment is created successfully

  • Load worker/assignment first


❌ 3) Salary overlaps existing salary

Error:
Overlapping salary records

✅ Fix:

  • End-date previous salary using DateTo

  • Or use correct DateFrom


❌ 4) Salary not approved

Error:
Salary not visible in UI

✅ Fix:

  • Set SalaryApproved = Y

  • Ensure approvals not required in workflow


🔗 Internal Links 



⭐ FAQs 

Q1. Which file is used to load salary using HDL?

Salary is loaded using Salary.dat in Oracle Fusion HCM.

Q2. What is required before loading salary using HDL?

Worker and Assignment must exist, and Salary Basis must be configured.

Q3. Can we update salary using MERGE?

Yes, MERGE can create or update salary records depending on the effective date.

Q4. What is SalaryApproved in Salary.dat?

SalaryApproved is a flag that indicates whether the salary record is approved (Y) or not approved (N).

Q5. What is the most common reason salary HDL fails?

The most common reasons are invalid SalaryBasisName and incorrect AssignmentNumber.

Oracle HCM HDL: Load Seniority Date Adjustments

  ✅ Oracle HCM HDL: Load / Update Seniority Date Adjustments (V3) – Examples + Worker.dat Templates Seniority Date in Oracle HCM is the dat...