Not Able to End Date Person Contact Relationship Using HDL in Oracle Fusion HCM

Not Able to End Date Person Contact Relationship Using HDL in Oracle Fusion HCM

Overview

While working with HCM Data Loader (HDL) in Oracle Fusion HCM, you may encounter a scenario where you try to end date a Person Contact Relationship using HDL—but the load fails or does not behave as expected.

This blog explains why end dating a Person Contact Relationship is not possible using HDL, and what the supported workaround is.

---

Problem Description

You are attempting to end date an existing Person Contact Relationship (such as Emergency Contact, Spouse, or Dependent) using HDL.

Despite providing correct effective dates in the HDL file, the relationship does not get end dated, or the load results in an error.

---

Why This Happens

Oracle Fusion HCM does not support end dating Person Contact Relationships through HDL.

This is a product limitation, not a data issue or configuration problem. The HDL framework currently allows you to:

• Create Person Contact Relationships

• Delete Person Contact Relationships

But it does not allow updating or end dating existing contact relationships.

---

Resolution / Supported Approach

✅ Delete the Person Contact Relationship Using HDL

Since end dating is not supported, the only available option is to delete the Person Contact Relationship using HDL.

When the contact relationship is no longer required:

• Identify the relationship record

• Use a DELETE operation in the HDL file

• Load the file using standard HDL steps

This approach fully removes the relationship from the system.

---

Important Notes

• HDL cannot update or end date Person Contact Relationships

• This limitation applies across all environments (DEV, TEST, PROD)

• Functional UI may still allow updates depending on the relationship type

• Always validate business impact before deleting relationships

---

Best Practices

• Confirm with functional teams before deleting contact relationships

• Maintain backup of original HDL files

• Test DELETE operations in lower environments

• Document deleted relationships for audit purposes

---

Alternative Options

If end dating is required for reporting or compliance:

• Consider managing the relationship manually through the Fusion UI (if supported)

• Evaluate custom reporting logic to handle deleted relationships

• Log the change history externally if required

---

Conclusion

If you are not able to end date a Person Contact Relationship using HDL, it is due to an Oracle-supported limitation. The only supported workaround is to delete the relationship using HDL.

Understanding such limitations helps avoid unnecessary troubleshooting and ensures your data loads remain compliant with Oracle Fusion HCM standards.

💬 Have you faced similar HDL limitations or different contact-related errors? Share your experience in the comments.

You Can’t Delete a Person Contact Relationship Because the Person Is a Benefit Dependent or Beneficiary

Overview

While managing Person Contact Relationships in Oracle Fusion HCM, you may encounter an error when trying to delete or end date a contact using HDL or the UI.

This issue typically occurs when the contact is linked to Benefits as a dependent or beneficiary. In this blog, we’ll explain the error, why it happens, and the exact steps to resolve it.

---

Error Message

You may see one of the following error messages:

You cannot delete the contact because the person is designated as a benefit dependent or beneficiary, or an attempt was made to process the benefit designation

OR

Error removing a duplicate beneficiary/contact

---

Why This Error Occurs

Oracle Fusion HCM restricts the deletion or end dating of a Person Contact Relationship when the person is:

• Added as a benefit dependent

• Designated as a beneficiary in one or more benefit plans

• Actively covered under a benefits plan

• Associated with a processed or backed-out life event

This validation ensures data integrity for benefits processing and payroll calculations.

---

Resolution Steps

Follow the steps below in sequence to resolve the issue.

---

✅ Step 1: Check if the Contact Is Added as a Beneficiary

• Navigate to the employee’s Benefits section

• Verify whether the dependent/contact is added as a beneficiary

• If yes, remove the beneficiary designation

---

✅ Step 2: Check if the Dependent Is Elected in Any Benefit Plan

• Review all benefit plans where the contact may be elected as:

  • Primary beneficiary

  • Secondary beneficiary

• If the dependent is elected in any plan, remove the election

---

✅ Step 3: Check If the Dependent Is Covered in Any Plan

If the dependent is actively covered:

1. Identify the life event associated with the coverage

2. Void or back out the life event

3. Run the ESS job:

Purge Backed-Out or Voided Life Event Data

This step is mandatory to fully remove benefit-related dependencies.

---

Final Step: Delete or End Date the Person Contact Relationship

Once all benefit dependencies are cleared:

• You can now delete or end date the Person Contact Relationship

• This can be done using:

  • HDL

  • Fusion UI

The system will no longer block the action.

---

Important Notes

• Benefits dependencies always take precedence over contact maintenance

• HDL and UI both follow the same benefit validation rules

• Always confirm with functional/benefits teams before removing dependent data

• Perform these steps in lower environments first

---

Best Practices

• Review benefit dependencies before deleting contacts

• Maintain audit records when removing beneficiaries

• Purge voided life events to avoid residual data issues

• Use consistent effective dates during benefit cleanup

---

Conclusion

If you’re unable to delete or end date a Person Contact Relationship in Oracle Fusion HCM, the most common reason is that the person is linked as a benefit dependent or beneficiary.

By removing beneficiary elections, clearing dependent coverage, and purging backed-out life events, you can successfully delete or end date the contact using HDL or the UI.

💬 Have you faced similar benefit-related HDL issues? Share them in the comments.

 

HDL Template for Benefit Participant Enrollment (Oracle Fusion HCM)

Introduction

Oracle Fusion HCM allows Benefit enrollments to be loaded in bulk using HCM Data Loader (HDL). This is especially useful during New Hire loads, Open Enrollment, Life Events, or mass corrections.

In this blog, we will walk through a complete end-to-end process to load Benefit Participant Enrollment using the ParticipantEnrollment.dat file, along with a related CompensationObject section.

---

When to Use ParticipantEnrollment.dat

You should use ParticipantEnrollment.dat when you need to:

• Enroll an employee into a Benefits Program

• Assign Plans, Options, and Coverage

• Process enrollments triggered by Life Events (New Hire, Marriage, etc.)

• Perform initial benefit enrollment for new hires

---

Prerequisites

Before loading the file, ensure the following:

1. Employee already exists in the system (Person record created)

2. Date of Birth (DOB) is populated for the employee - Required for age-based eligibility, dependent validation, and certain benefit plans.

3. Payroll is assigned to the employee - Payroll effective date aligns with hire/enrollment date

4. Salary is assigned - Salary record is active as of the benefit enrollment date (Required for benefit plans that calculate rates, premiums, or coverage based on salary)

5. Benefits Program, Plan, and Options are already configured

6. Life Event (e.g., New Hire) exists and is active

7. Dates align with the employee’s hire date and benefit eligibility

8. HDL access is available

---

File Name

ParticipantEnrollment.dat

---

HDL File Structure Overview

This file consists of two main sections:

1. ParticipantEnrollment – Defines the employee and life event

2. CompensationObject – Assigns benefit program, plan, option, and coverage

Both sections are mandatory for successful enrollment.

---

Section 1: ParticipantEnrollment

Purpose

This section identifies who is being enrolled and why (Life Event).

Metadata Definition

METADATA|ParticipantEnrollment|PersonNumber|ParticipantLastName|
ParticipantFirstName|BenefitRelationship|LifeEvent|
LifeEventOccuredDate|EffectiveDate

Sample Data

MERGE|ParticipantEnrollment|7628|XXTEST|Adam|DFLT|New Hire|
2026/01/12|2026/01/12

🔹 Tip: LifeEventOccuredDate and EffectiveDate should normally match the hire date for New Hire enrollments.

---

Section 2: CompensationObject

Purpose

This section assigns the Benefit Program, Plan, Option, and Coverage.

Metadata Definition

METADATA|CompensationObject|Program|OriginalEnrollmentDate|
PersonNumber|LineNumber|Plan|Option|Coverage|Rate

Sample Data

MERGE|CompensationObject|Choice Program (Core)|2026/01/12|7628|1|
Medical PPO|Participant Only|1000|

Field Explanation

🔹 Tip: Program, Plan, and Option values must exactly match the configuration in Fusion.

---

Complete Sample ParticipantEnrollment.dat File

METADATA|ParticipantEnrollment|PersonNumber|ParticipantLastName|
ParticipantFirstName|BenefitRelationship|LifeEvent|
LifeEventOccuredDate|EffectiveDate
MERGE|ParticipantEnrollment|7628|XXTEST|Adam|DFLT|New Hire|
2026/01/12|2026/01/12

METADATA|CompensationObject|Program|OriginalEnrollmentDate|PersonNumber
|LineNumber|Plan|Option|Coverage|Rate
MERGE|CompensationObject|Choice Program (Core)|2026/01/12|7628|1|
Medical PPO|Participant Plus One|1000|

---

HDL Load Steps

1. Navigate to Data Exchange → HCM Data Loader

2. Upload ParticipantEnrollment.dat

3. Submit the Load

4. Monitor the process:

   • Load File

   • Import and Load

   • Completion status should be Succeeded

---

Validation After Load

After successful load:

1. Navigate to Benefit Administration 

2. Search for the employee

3. Verify:

   • Program enrollment

   • Plan and option selection

   • Coverage details

   • Effective dates

---

Common Errors & Troubleshooting

                       Common Errors Participant Load

---

Key Takeaways

• ParticipantEnrollment.dat is essential for benefit enrollments via HDL

• Both ParticipantEnrollment and CompensationObject sections are required

• Dates, names, and configurations must match Fusion setup exactly

• Always validate enrollment post-load

---

Conclusion

HDL provides a powerful and efficient way to manage bulk Benefit enrollments in Oracle Fusion HCM. With a correctly structured ParticipantEnrollment.dat file, you can seamlessly enroll employees into benefit programs triggered by life events such as New Hire.

This end-to-end template can be reused and extended for other plans and options as needed.

If you want, I can also help with:

• Open Enrollment HDL

• Multiple plans in one file

• Retro or correction enrollments

• Error-handling scenarios

How to sort data in rtf template

 How to sort data in rtf template

Sort the data in Data model is the recommended approach.

But if you want to sort the data in rtf template then you have to use below xml tag code.

<?sort:fieldname?><?fieldname?>  

this will sort the data in ascending order be default as it is not mentioned.

if user want to sort the data in descending order then use below code

<?sort:fieldname;'descending'?><?fieldname?>  

Prenotification Status of Personal Payment Method in Oracle HCM

 

Prenotification Status of Personal Payment Method in Oracle HCM

Prenote Status is not stored directly in table, you can find the corresponding details in pay_bank_account_prenotes table.

Prenote status you have to use below logic.

CASE
WHEN pay_bank_account_prenotes.PRENOTE_DATE=TO_DATE('31/12/4712','DD/MM/YYYY') THEN 'ORA_R'
WHEN pay_bank_account_prenotes.PRENOTE_DATE=TO_DATE('01/01/0001','DD/MM/YYYY') THEN 'ORA_SK'
WHEN NVL((pay_bank_account_prenotes.PRENOTE_DATE),TO_DATE('31/12/4712','DD/MM/YYYY'))=TO_DATE('31/12/4712','DD/MM/YYYY') THEN 'ORA_N_S'
WHEN TRUNC(pay_bank_account_prenotes.PRENOTE_DATE+NVL(OrganizationPaymentMethodDEO.VALIDATION_DAYS,0)) <= TRUNC(SYSDATE) THEN 'ORA_C'
ELSE 'ORA_S'
END AS PRENOTE_STATUS

Step-by-Step Guide to Customize Oracle Seeded Job Offer Letter Template

Step-by-Step Guide to Customize Oracle Seeded Job Offer Letter Template

Introduction 

Customizing a Job Offer Letter Template in Oracle Recruiting is an essential task for HR and Talent Management teams to ensure candidate communications are personalized, branded, and compliant. Oracle provides seeded job offer templates, but they often require customization to meet organizational needs.

In this blog, we’ll walk you through the complete process to customize Oracle seeded Job Offer Letter templates, from downloading the template to uploading and activating it in the Recruiting Content Library.

Click here for step by step video to create job offer letter template customization

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 

• Load Worker Data using HDL (Worker.dat)

• Load Personal Payment Method using HDL

• HDL Common Errors and Solutions

• HCM Extract Changes Only Mode

• Oracle Fusion HCM Technical Interview Questions

• Oracle eText Template BIP Report 

• Oracle Benefit Participant Load using HDL

---

⭐ 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.