Can I change a non-primary work relationship to primary in Oracle Fusion?

Yes, by using HDL and setting PrimaryFlag=Y along with DateForPrimaryFlagChange in the Worker.dat file.

What happens to the existing primary work relationship?

Oracle Fusion automatically updates the previous primary work relationship to non-primary once you change another to primary.

Which HDL attributes are required to change primary work relationship?

The key attributes are PrimaryFlag (set to Y) and DateForPrimaryFlagChange. You must also include LegalEmployerName, DateStart, PersonNumber, WorkerNumber, and WorkerType.

Can I update multiple work relationships at the same time?

Yes, but ensure only one work relationship is marked primary for a given effective date. Others must have PrimaryFlag=N or omitted.

What are common errors when changing primary work relationships?

Common errors include 'Person can have only 1 active Primary Work Relationship', effective date mismatch, invalid PersonNumber/WorkerNumber, or missing LegalEmployerName.

What is AssignedPayroll HDL in Oracle HCM?

AssignedPayroll HDL assigns a payroll definition to a worker’s assignment for accurate payroll processing.

Which file is required for Assigned Payroll load?

AssignedPayroll.dat is mandatory.

Can I assign multiple payroll definitions to one assignment?

No, each assignment can have one active payroll definition at a time.

How to correct 'Payroll not created' error?

Verify AssignmentNumber exists, validate PayrollDefinitionCode, and check LegislativeDataGroupName.

How to overwrite an existing assigned payroll?

Update the EffectiveStartDate with MERGE. Ensure dates do not overlap previous assignments.

Showing posts with label HCM Data Loader. Show all posts

Wednesday, 7 January 2026

The values {attributes} are not valid for the attribute BankAccountId

Error While Loading PersonalPaymentMethod Using HCM Data Loader

Introduction

Oracle Fusion HCM HCM Data Loader (HDL) is commonly used to load payroll-related data such as Personal Payment Methods. However, while loading PersonalPaymentMethod.dat, you may encounter validation errors related to bank account resolution.

One of the most common errors is:

HRC-1035539 – The values {attributes} are not valid for the attribute BankAccountId

This blog explains why this error occurs, the root causes, and multiple solutions to fix it using real project scenarios.

Cause Analysis

Cause 1: Missing BankAccountType

Consider a scenario where two bank accounts exist for the same person:

Bank Account 1 → No BankAccountType
Bank Account 2 → Has BankAccountType

In this case:

If you refer to Bank Account 1, HDL can resolve it without BankAccountType
If you refer to Bank Account 2, BankAccountType becomes mandatory

❗ If the existing ExternalBankAccount has a value for BankAccountType, it must be provided in PersonalPaymentMethod.dat.

Cause 2: Invalid Bank Account Attribute Combination

The system is unable to identify a valid BankAccountId because the values provided for:

BankName
BankCountryCode
BankAccountNumber
BankAccountType
BankBranchName
BankBranchNumber

do not match any existing External Bank Account in Oracle Fusion.

Solution 1: Provide BankAccountType When Required

If the External Bank Account already has a BankAccountType, then it must be passed in PersonalPaymentMethod.dat.

Best Practice

✔ Always provide BankAccountType when multiple bank accounts exist
✔ Ensure the value exactly matches what exists in Fusion

This ensures unique resolution of ExternalBankAccount.

Solution 2: Validate Bank Account Details in Fusion

Ensure that the following attributes in PersonalPaymentMethod.dat match an existing bank account:

Bank Name
Bank Country Code
Bank Account Number
Bank Account Type
Bank Branch Name
Bank Branch Number

If any of these values are incorrect, Fusion will fail to resolve the BankAccountId.

Query to Validate Bank Account Data

Use the below SQL query to verify whether the bank account exists and matches the provided details:


SELECT
    ppr.payroll_relationship_id payrollrelationshipid,
    ppr.person_id personid,
    h.party_id partyid,
    eba.bank_account_id bankaccountid,
    eba.bank_account_num bankaccountnumber,
    eba.bank_id bankid,
    eba.bank_name bankname,
    eba.bank_number banknumber,
    eba.branch_number branchnumber,
    eba.branch_id branchid,
    eba.bank_branch_name branchname,
    eba.eft_swift_code eftswiftcode,
    eba.bank_home_country homecountry,
    eba.bank_account_type bankaccounttype
FROM
    pay_bank_accounts eba,
    iby_account_owners ebao,
    hz_parties h,
    pay_pay_relationships_dn ppr,
    per_persons p,
    hz_orig_sys_references hosp
WHERE
    eba.bank_account_id = ebao.ext_bank_account_id
    AND ebao.account_owner_party_id = h.party_id
    AND hosp.owner_table_id = h.party_id
    AND hosp.orig_system_reference = TO_CHAR(ppr.person_id)
    AND hosp.owner_table_name = 'HZ_PARTIES'
    AND hosp.orig_system = 'FUSION_HCM'
    AND ppr.person_id = p.person_id
    AND h.status = 'A'
    AND eba.bank_account_num = <enter bank account num>
    AND eba.bank_name = <enter Bank Name>
    AND eba.bank_branch_name = <bank branch name>;

🔎 Replace data with values from your PersonalPaymentMethod.dat file.

Final Root Causes Summary

Cause 1

BankAccountType not provided even though it exists in the system

Cause 2

No matching BankAccountId exists for the provided bank details

Conclusion

The error occurs when Oracle Fusion HCM cannot uniquely identify the External Bank Account for a Personal Payment Method. By ensuring accurate bank details and providing BankAccountType when required, this issue can be resolved effectively.

This approach is widely used in payroll implementations and data migration projects.

Common Errors During Worker HDL Load in Oracle Fusion HCM (With Solutions)

Loading worker data using HDL (HCM Data Loader) in Oracle Fusion HCM is powerful—but even small configuration or data issues can cause errors that block the load process.

In this blog, we’ll cover 10 common Worker HDL load errors, explain why they occur, and provide clear, step-by-step solutions to resolve them quickly.

1️⃣ Error: You Must a Primary Value

🔍 Cause

The system requires a primary work term for the worker, but it is missing.

✅ Solution

Add the PrimaryWorkTermsFlag attribute in the WorkTerms metadata and set it to Y.

Tip:
Each worker must have exactly one primary work term.

2️⃣ Error: Person can have only 1 active Primary WorkRelationship

🔍 Cause

The worker already has an active primary work relationship, and a new one is being created.

✅ Solution

Update the termination date of the previously terminated work relationship to ensure only one active primary work relationship exists.

3️⃣ Error: SourceSystemOwner is unknown

🔍 Cause

The SourceSystemOwner value in the HDL file does not match the lookup configuration.

✅ Solution

Navigate to Setup & Maintenance
Search for Manage Common Lookups
Open lookup type HRC_SOURCE_SYSTEM_OWNER
Remove FUSION from the custom lookup code
Update the same value in the Worker.dat (or relevant HDL file)
Zip and reload the file via
My Client Groups → Data Exchange → Import and Load Data
Refresh and verify successful completion

4️⃣ Error:

JBO-FND:::FND_FLEX_SEG_VAL_NOT_IN_LIST: xxx is not in the list

🔍 Cause

The Site Code linked to the Position is invalid or expired.

✅ Solution

Remove the end date for the Site Code
OR
Extend the end date for the Site Code

After correction, reload the Worker HDL file.

5️⃣ Error: You must enter a valid value for the GradeId field

🔍 Cause

An invalid or missing grade is passed for a position-based assignment.

✅ Solution (Choose one):

Provide the correct GradeId or GradeCode
Pass #NULL (with PER_ENFORCE_VALID_GRADE = Y)
Set PER_ENFORCE_VALID_GRADE = N to skip grade validation

📌 After loading, run the ESS job:
Synchronize Person Assignment from Position

This syncs grade, job, and other position attributes.

6️⃣ Error: The values xxxx aren't valid for the attribute LegislationCode

🔍 Cause

The Legal Entity registration setup is incomplete or duplicated.

✅ Solution

Go to Setup & Maintenance
Navigate to Legal Structures
Open Manage Legal Reporting Unit Registrations
Assign a unique Registration Number
Save and reload the Worker HDL file

7️⃣ Error:

METADATA line for the {BO_NAME} business object is invalid
(While loading Person Extra Information)

🔍 Cause

Outdated Worker HDL template or missing EFF attributes.

✅ Solution

Refresh the Worker HDL object
Download the latest Worker template
Update the file with:
- PEI EFF
- EFF_CATEGORY_CODE
- FLEX attributes
Follow Oracle documentation for Extensible Flexfields
Zip and reload via Import and Load Data

8️⃣ Error:

You cannot update this record because the SourceSystemId and SourceSystemOwner are invalid
(Assignment Supervisor)

🔍 Cause

Mismatch between source keys and Fusion surrogate keys.

✅ Solution (Best Options):

Remove SourceSystemId/Owner and use Fusion surrogate or user keys
Ensure parent and child objects use the same key type
For integrations:
- Update mappings using HRC_INTEGRATION_KEY_MAP
- Load mappings via SourceKeys.dat
- Reload AssignmentSupervisor data

9️⃣ Error:

You must provide only one parent record Worker and it must start on the earliest effective start date

🔍 Cause

Incorrect Worker effective dates or duplicate Worker records.

✅ Solution

Ensure StartDate = EffectiveStartDate
Match the earliest date from PER_ALL_PEOPLE_F
If creating only a new assignment or work relationship:
- Remove METADATA Worker
- Remove MERGE Worker records

🔟 Error: No Assignment record from 2018-10-27

🔍 Cause

Assignment data is missing from the Worker HDL file for the specified effective date.

✅ Solution

Add the Assignment record in Worker.dat starting from 2018-10-27, then reload the file.

✅ Best Practices for Worker HDL Loads

Always use the latest HDL templates
Validate effective dates carefully
Avoid mixing Fusion surrogate keys and source keys
Run required ESS jobs after position-based updates
Test loads in DEV or TEST before PROD

🔚 Conclusion

Worker HDL errors in Oracle Fusion HCM are common—but most are caused by data inconsistencies, configuration gaps, or outdated templates. Understanding these errors and applying the correct solution can save hours of troubleshooting and ensure smooth data loads.

💬 Have questions or faced a different error?
Drop them in the comments—I’ll help you troubleshoot.

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

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:

Identify the life event associated with the coverage
Void or back out the life event
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.

Thursday, 19 January 2023

HDL Template to Accrual Plan Enrollment of Worker

Please find the below sample template :

File Name - PersonAccrualPlanEnrollment.dat

HDL Template to Disability of Worker

HDL Template to Person Disability

Please find the below sample template :

File Name- PersonDisability.dat

MERGE|PersonDisability|XXTEST|XXTEST_DIS21|2021/07/07|4712/12/31|US|100000609337422|XXTEST21|ORA_PER_YES_US|NA|1|A

Wednesday, 18 January 2023

HDL Template to Change Hire Date of Worker

For this use Worker.dat

Please find the below sample template :

SET PURGE_FUTURE_CHANGES N

HDL Template for Salary of Worker

Salary Of Worker using HDL.

For this use Salary.dat

Please find the below sample template :

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

HDL Template for Worker Extra Information of Worker (EIT)

HDL Template for Worker Extra Information of Worker (EIT).

For this use Worker.dat

Please find the below sample template :

Sample file for Worker EIT.

MERGE|WorkerExtraInfo|PS5|2010/11/02||HRX_IN_MISCELLANEOUS|HRX_IN_MISCELLANEOUS|PER_EIT|HRX_IN_MISCELLANEOUS|PER_EIT|Test123|Backward|||||||

Wednesday, 28 December 2022

HDL Template for Global Temporary Transfer of Worker

For this use Worker.dat

Please find the below sample template :

MERGE|WorkRelationship|XXTEST9|US1 Legal Entity|2018/01/01||Y|XXTEST9|E|Y|N|GLB_TEMP_ASG||

MERGE|WorkRelationship|XXTEST9|UK Legal Entity|2019/01/01||N|XXTEST9|E|Y|N|GLB_TEMP_ASG||

MERGE|WorkTerms|GLB_TEMP_ASG|XXTEST9|US1 Legal Entity|2018/01/01|E|XXTEST_WRKTERM9|2019/01/01|4712/12/31|Y|1|ET|Employee|SUSPEND_PROCESS|US1 Business Unit|Y|EMP|

MERGE|WorkTerms|GLB_TEMP_ASG|XXTEST9|UK Legal Entity|2019/01/01|E|XXTEST_WRKTERM9-2|2019/01/01|4712/12/31|Y|1|ET|Employee|ACTIVE_PROCESS|UK Business Unit|Y|EMP|

MERGE|Assignment|GLB_TEMP_ASG|XXTEST9|UK Legal Entity|2019/01/01|E|XXTEST_ASSIGN9-2|XXTEST_WRKTERM9-2|2019/01/01|4712/12/31|Y|1|E|Employee|ACTIVE_PROCESS|UK Business Unit|XXTEST_GRADE1|ADM|XXTEST_LOC12|XXTEST Department1|Y|N|

Monday, 28 February 2022

How to Change Non-Primary Work Relationship to Primary Using Worker.dat (Oracle Fusion HDL)

Introduction

In Oracle Fusion HCM, an employee can have only one Primary Work Relationship at any given time.

During data corrections or integrations, you may encounter a requirement to change an existing non-primary work relationship to primary.

Oracle Fusion allows this update using HCM Data Loader (HDL) by passing specific attributes in the Worker.dat file.

This blog explains:

When this scenario occurs
Required HDL attributes
Sample Worker.dat template
What happens after upload

Sample Templates for eText BI Publisher Reports (Delimiter & Fixed Position)

Introduction to eText BI Publisher Reports

Oracle BI Publisher (BIP) provides eText report templates to generate text-based output files such as .txt, .dat, or interface files required for integrations with external systems.

Unlike PDF or Excel outputs, eText reports are mainly used when:

Data must follow a specific layout
Files are consumed by external payroll, banking, or legacy systems
Strict formatting rules (delimiter or fixed length) are required

In this blog, we’ll cover:

What eText BI Publisher reports are
how to create eText report in BI Publisher
Differences between Delimiter-Based and Fixed Position-Based eText
BI Publisher eText report example
how to create fixed position eText report
common errors in BI Publisher eText report

Difference Between Delimiter & Fixed Position eText

Delimiter VS Fixed Position eText

You can see step by step video to develop eText BIP Report using this Link

🔹 Sample 1: Delimiter-Based eText Template

This template generates output with values separated by a delimiter (for example, |).

You can see step by step video to develop eText BIP Report using this Link

<TEMPLATE TYPE>	DELIMITER_BASED
<OUTPUT CHARACTER SET>	iso-8859-1
<CASE CONVERSION>	UPPER
<NEW RECORD CHARACTER>	Carriage Return

<LEVEL>	DATA_DS
<MAXIMUMLENGTH>	<FORMAT>	<DATA>	<COMMENTS>
<NEW RECORD>	TableHeader
20	Alpha	'Person Id'
1	Alpha	'\|'
20	Alpha	'Title'
1	Alpha	'\|'
20	Alpha	'First Name'
1	Alpha	'\|'
20	Alpha	'Last Name'

<LEVEL>	G_1
<MAXIMUMLENGTH>	<FORMAT>	<DATA>	<COMMENTS>
<NEW RECORD>	CLRDAta
20	Alpha	PERSON_ID
1	Alpha	'\|'
20	Alpha	TITLE
1	Alpha	'\|'
20	Alpha	FIRST_NAME
1		'\|'
20	Alpha	LAST_NAME
<END LEVEL>	G_1

<END LEVEL>

DATA_DS

This format is useful when the target system expects delimiter-separated text files.

HDL Template for Personal Payment Method Details

Prerequisite:

1. Bank and Bank Branches data should be loaded. Click here to find the sample bank details.

2. External bank Account should be loaded. Click here to find the sample file.

For this use PersonalPaymentMethod.dat file.

You can see step by step video to load Personal Payment Method Details using this Link

Please find the below sample template :

MERGE|PersonalPaymentMethod|XXTEST|XXTEST_PAYMETHOD2|US Legislative Data Group|XXTEST_ASSIGN2|XXTEST_PAYMETHOD2|2021/04/19|P||100|1|Direct Deposit|American Bank|000000123|US|3456|Checking

Tuesday, 20 April 2021

HDL Template for External Bank Account Details

Prerequisite:

1. Bank and Bank Branches data should be loaded. Click here to find the sample bank details.

For this use ExternalBankAccount.dat file.

You can see step by step video to load External Bank Account Details using this Link

Please find the below sample template :

HDL Template for Bank and Bank Branch Details

For this use Bank.dat and BankBranch.dat file.

You can see step by step video to load Bank and Bank Branch Details using this Link

Please find the below sample template :

Bank :

Bank Branch:

MERGE|BankBranch|American Bank|123|AMC123|US||XXTEST|XXTEST_BANKBRANCHAM123

Tuesday, 13 April 2021

Oracle Fusion HCM: Assigned Payroll HDL – Complete Template & Example (AssignedPayroll.dat)

🔹 Introduction: What is Assigned Payroll HDL?

In Oracle Fusion HCM, assigned payroll determines the payroll schedule and payroll definition for an employee’s assignment.

Using AssignedPayroll.dat via HCM Data Loader (HDL) allows you to:

Assign payroll definitions like Weekly, Monthly, or Biweekly
Link legislative data groups for country-specific payroll rules
Ensure accurate payroll processing
Avoid manual assignment errors

You can see step by step video to load Assigned Payroll details of worker using this Link

🔹 Prerequisites

Before loading Assigned Payroll HDL, ensure:

Worker assignment exists (AssignmentNumber)
Payroll definitions are configured in Oracle HCM
Legislative data groups are correctly set
Unique Source System identifiers are used

🔹 Objects Required

Object	Purpose
AssignedPayroll	Assigns payroll definitions to a worker’s assignment and links to legislative data groups

🔹 Sample AssignedPayroll.dat Template

File Name - AssignedPayroll.dat

🔹 Field Explanation (Infographic Ready)

Assigned Payroll Keyfields

🔹 Step-by-Step Process to Load Assigned Payroll Using HDL

Step 1️⃣ Prepare AssignedPayroll.dat

Use correct AssignmentNumber
Validate PayrollDefinitionCode

Step 2️⃣ Upload File in Oracle HCM

Navigation:
Tools → HCM Data Loader → Import and Load Data

Step 3️⃣ Monitor HDL Process

Check status:
✔ Completed
❌ Error

Step 4️⃣ Validate in Oracle HCM UI

Person Management → Payroll Relationship

🔹 Common Errors & Resolutions

Common Issues in Assigned Payroll Load

Wednesday, 7 January 2026

Error While Loading PersonalPaymentMethod Using HCM Data Loader

Introduction

Cause Analysis

Cause 1: Missing BankAccountType

Cause 2: Invalid Bank Account Attribute Combination

Solution 1: Provide BankAccountType When Required

Best Practice

Solution 2: Validate Bank Account Details in Fusion

Query to Validate Bank Account Data

Final Root Causes Summary

Cause 1

Cause 2

Conclusion

Thursday, 1 January 2026

Common Errors During Worker HDL Load in Oracle Fusion HCM (With Solutions)

1️⃣ Error: You Must a Primary Value

🔍 Cause

✅ Solution

2️⃣ Error: Person can have only 1 active Primary WorkRelationship

🔍 Cause

✅ Solution

3️⃣ Error: SourceSystemOwner is unknown

🔍 Cause

✅ Solution

4️⃣ Error:

🔍 Cause

✅ Solution

5️⃣ Error: You must enter a valid value for the GradeId field

🔍 Cause

✅ Solution (Choose one):

6️⃣ Error: The values xxxx aren't valid for the attribute LegislationCode

🔍 Cause

✅ Solution

7️⃣ Error:

🔍 Cause

✅ Solution

8️⃣ Error:

🔍 Cause

✅ Solution (Best Options):

9️⃣ Error:

🔍 Cause

✅ Solution

🔟 Error: No Assignment record from 2018-10-27

🔍 Cause

✅ Solution

✅ Best Practices for Worker HDL Loads

🔚 Conclusion

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

Overview

Error Message

Why This Error Occurs

Resolution Steps

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

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

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

Final Step: Delete or End Date the Person Contact Relationship

Important Notes

Best Practices

Conclusion

Thursday, 19 January 2023

HDL Template to Accrual Plan Enrollment of Worker

HDL Template to Person Disability

Wednesday, 18 January 2023

HDL Template to Change Hire Date of Worker

Wednesday, 28 December 2022

Monday, 28 February 2022

How to Change Non-Primary Work Relationship to Primary Using Worker.dat (Oracle Fusion HDL)

Introduction

Friday, 23 April 2021

Sample Templates for eText BI Publisher Reports (Delimiter & Fixed Position)

Introduction to eText BI Publisher Reports

Difference Between Delimiter & Fixed Position eText

🔹 Sample 1: Delimiter-Based eText Template

HDL Template for Personal Payment Method Details

Tuesday, 20 April 2021

HDL Template for External Bank Account Details

Tuesday, 13 April 2021

🔹 Introduction: What is Assigned Payroll HDL?

🔹 Prerequisites