Showing posts with label HDL. Show all posts
Showing posts with label HDL. Show all posts

Thursday, 19 January 2023

HDL Template to Absence Entry of Worker

HDL Template to Absence Entry of Worker

Please find the below sample template :

File Name - PersonAbsenceEntry.dat


Note :- Please verify Absence plan must be enrolled first to load absence entry. 


METADATA|PersonAbsenceEntry|Employer|PersonNumber|AbsenceType|AbsenceReason|AbsenceStatus|ApprovalStatus|StartDatetime|EndDatetime|StartDate|StartTime|EndDate|EndTime|SourceSystemOwner|SourceSystemId

MERGE|PersonAbsenceEntry|US3 Legal Entity|XXTEST2|Sick||SUBMITTED|APPROVED||2021/07/12 08:00:00|2021/07/12|08:00|2021/07/12|16:30|XXTEST|XXTEST2_SICK1


METADATA|PersonAbsenceEntryDetail|AbsenceDate|Employer|PersonNumber|AbsenceType|AssignmentNumber|AbsenceStartDate|AbsenceStartTime|RowSeq|StartTime|EndTime|SourceSystemOwner|SourceSystemId

MERGE|PersonAbsenceEntryDetail|2021/07/12|US3 Legal Entity|XXTEST2|Sick|XXTEST_ASSIGN2-1|2021/07/12|08:00|1|06:00|16:30|XXTEST|XXTEST2_SICK1

Note - For any doubts or additional information, please reach out in the comment section.

HDL Template to Accrual Plan Enrollment of Worker

HDL Template to Accrual Plan Enrollment of Worker

Please find the below sample template :

File Name - PersonAccrualPlanEnrollment.dat


METADATA|PersonAccrualPlanEnrollment|PersonNumber|WorkTermAsgNum|PlanName|EnrtStDt|SourceSystemId|SourceSystemOwner

MERGE|PersonAccrualPlanEnrollment|XXTEST22|XXTEST_WRKTERM22|Sick|2021/01/01|XXTEST_SICK1|XXTEST

Wednesday, 18 January 2023

HDL Template for Salary of Worker

 Salary Of Worker using HDL.

For this use Salary.dat


Please find the below sample template :


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

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


Wednesday, 28 December 2022

HDL Template for Global Temporary Transfer of Worker

For this use Worker.dat


Please find the below sample template :

METADATA|WorkRelationship|PersonNumber|LegalEmployerName|DateStart|ActualTerminationDate|PrimaryFlag|WorkerNumber|WorkerType|RehireRecommendationFlag|OnMilitaryServiceFlag|ActionCode|ReasonCode|DateOfDeath

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



METADATA|WorkTerms|ActionCode|PersonNumber|LegalEmployerName|DateStart|WorkerType|AssignmentNumber|EffectiveStartDate|EffectiveEndDate|EffectiveLatestChange|EffectiveSequence|AssignmentType|PersonTypeCode|AssignmentStatusTypeCode|BusinessUnitShortCode|PrimaryWorkTermsFlag|SystemPersonType|ReasonCode

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|


METADATA|Assignment|ActionCode|PersonNumber|LegalEmployerName|DateStart|WorkerType|AssignmentNumber|WorkTermsNumber|EffectiveStartDate|EffectiveEndDate|EffectiveLatestChange|EffectiveSequence|AssignmentType|PersonTypeCode|AssignmentStatusTypeCode|BusinessUnitShortCode|GradeCode|JobCode|LocationCode|DepartmentName|ManagerFlag|LabourUnionMemberFlag|ReasonCode

MERGE|Assignment|GLB_TEMP_ASG|XXTEST9|US1 Legal Entity|2018/01/01|E|XXTEST_ASSIGN9|XXTEST_WRKTERM9|2019/01/01|4712/12/31|Y|1|E|Employee|SUSPEND_PROCESS|US1 Business Unit|XXTEST_GRADE1|XXTEST_CFO|XXTEST_LOC12|XXTEST Department1|Y|N|

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|

 

Friday, 20 August 2021

HDL Template for Candidate

 For this use Candidate.dat file.

You can see step by step video to load Candidate data using this Link


Please find the below sample template :

METADATA|Candidate|CandidateNumber|CandPrefLanguageCode|StartDate|ConfirmedFlag|CountryOfBirth|DateOfBirth|RegionOfBirth|Source|SourceMedium|TownOfBirth|VisibleToCandidateFlag

MERGE|Candidate|CT123|US|2019/03/20|Y||1980/08/05||direct Source|||Y


METADATA|CandidateAddress|CandidateNumber|EffectiveStartDate|AddressLine1|AddressType|AddressLine2|Country|PostalCode|Region2|Region1|TownOrCity|EffectiveEndDate

MERGE|CandidateAddress|CT123|2019/03/20|1257 Test1|HOME|Test|US|12576|NC|Wayne|Pikeville|


METADATA|CandidatePhone|CandidateNumber|DateFrom|PhoneType|PhoneNumber|CountryCodeNumber|AreaCode|DateTo|Extension|LegislationCode|SpeedDialNumber|Validity|GUID

MERGE|CandidatePhone|CT123|2019/03/20|H1|9605804|1|262|4712/12/31||US|||


METADATA|CandidateName|EffectiveStartDate|EffectiveEndDate|CandidateNumber|NameType|LegislationCode|FirstName|LastName

MERGE|CandidateName|2019/03/20||CT123|GLOBAL|US|Amar|Test


METADATA|CandidateProfile|CandidateNumber|ContentType|ContentItem|SectionContext|DateFrom|ItemDate7|ItemNumber9|ItemText2401|CountryGeographyCode|CountryCountryCode|ProfileItemId

MERGE|CandidateProfile|CT123|DEGREE|BA - Bachelor of Arts|PERSON_DEGREE|2019/03/20|2019/03/20|||US|US|122



Monday, 28 June 2021

HDL Template for Documents Of Record

 For this use DocumentsOfRecord.dat file.

You can see step by step video to load Documents Of Record using this Link

Please find the below sample template :


METADATA|DocumentsOfRecord|SourceSystemOwner|SourceSystemId|DocumentsOfRecordId|PersonNumber|DocumentTypeId|DocumentType|Country|DocumentCode|DocumentName|DocumentNumber|DateFrom|DateTo|IssuingAuthority|IssuedDate|IssuingCountry|IssuingLocation|Comments|Publish|PublishDate|Status|VerifiedBy|VerifiedDate

MERGE|DocumentsOfRecord|XXTEST|XXTEST_DOCREC01||XXTEST2||Passport||XXTEST_DOCREC01|Passport|XXTEST2123|||||US|||||||


METADATA|DocumentAttachment|SourceSystemOwner|SourceSystemId|PersonNumber|DocumentType|Country|DocumentCode|DataTypeCode|Title|URLorTextorFileName|File

MERGE|DocumentAttachment|XXTEST|XXTEST_DOCREC01|XXTEST2|Passport||XXTEST_DOCREC01|passport.png|passport.png|FILE|passport.png



Friday, 23 April 2021

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

 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

 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 :


METADATA|PersonalPaymentMethod|SourceSystemOwner|SourceSystemId|LegislativeDataGroupName|AssignmentNumber|PersonalPaymentMethodCode|EffectiveStartDate|PaymentAmountType|Amount|Percentage|ProcessingOrder|OrganizationPaymentMethodCode|BankName|BankBranchNumber|BankCountryCode|BankAccountNumber|BankAccountType


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

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 :


METADATA|ExternalBankAccount|SourceSystemOwner|SourceSystemId|AccountNumber|BankBranchName|BankName|CountryCode|CurrencyCode|AccountType

MERGE|ExternalBankAccount|XXTEST|XXTEST_BANKACCT2|123456|AMC123|American Bank|US|USD|Checking


METADATA|ExternalBankAccountOwner|SourceSystemOwner|SourceSystemId|PersonNumber|AccountNumber|BankBranchNumber|BankNumber|CountryCode|CurrencyCode|BankBranchName|BankName|ExternalBankAccountId(SourceSystemId)

MERGE|ExternalBankAccountOwner|XXTEST|XXTEST_ACCTOWNER2|XXTEST2|123456|123|Test123|US|USD|AMC123|American Bank|XXTEST_BANKACCT2

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 :

METADATA|Bank|BankName|CountryCode|BankNumber|SourceSystemOwner|SourceSystemId

MERGE|Bank|American Bank|US|Test123|XXTEST|XXTEST_BANKTest123


Bank Branch: 


METADATA|BankBranch|BankName|BankBranchNumber|BankBranchName|CountryCode|EftSwiftCode|SourceSystemOwner|SourceSystemId

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:

  1. Worker assignment exists (AssignmentNumber)

  2. Payroll definitions are configured in Oracle HCM

  3. Legislative data groups are correctly set

  4. Unique Source System identifiers are used


🔹 Objects Required

ObjectPurpose
AssignedPayrollAssigns payroll definitions to a worker’s assignment and links to legislative data groups

🔹 Sample AssignedPayroll.dat Template

File Name - AssignedPayroll.dat

METADATA|AssignedPayroll|EffectiveStartDate|AssignmentNumber|PayrollDefinitionCode|LegislativeDataGroupName|StartDate

MERGE|AssignedPayroll|2021/04/09|XXTEST_ASSIGN1|Weekly|US Legislative Data Group|2021/04/09


🔹 Field Explanation (Infographic Ready)

Assigned Payroll Key fields
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

Thursday, 8 April 2021

Oracle Fusion HCM: Element Entry HDL – Complete Template & Examples (ElementEntry.dat)


🔹 Introduction: What is Element Entry HDL?

Learn how to load element entry details for workers in Oracle Fusion HCM using ElementEntry.dat and ElementEntryValue.dat files. Complete HDL templates, step-by-step guide, common errors, troubleshooting, and FAQ included.

In Oracle Fusion HCM, element entries allow you to define payroll elements such as allowances, deductions, or benefits for employees.

Using ElementEntry and ElementEntryValue via HCM Data Loader (HDL) enables you to:

  • Load bulk element entries for multiple workers

  • Maintain consistency in payroll calculations

  • Avoid manual data entry errors

  • Manage repetitive or complex payroll elements efficiently

You can see step by step video to element entry details of worker using this ElementEntry.dat


🔹 Prerequisites

Before loading Element Entry HDL, ensure:

  1. Worker/assignment exists (AssignmentNumber must be valid)

  2. Element names are configured in Oracle HCM

  3. Legislative data groups are correctly set

  4. Source system identifiers are unique for each entry


🔹 Objects Required

ObjectPurpose
ElementEntryDefines the payroll element entry for an assignment
ElementEntryValueDefines specific values for each element entry (amount, periodicity, flags)

🔹 Sample HDL Templates

ElementEntry

METADATA|ElementEntry|EffectiveEndDate|EffectiveStartDate|ElementName|LegislativeDataGroupName|MultipleEntryCount|EntryType|AssignmentNumber|SourceSystemOwner|SourceSystemId|ReplaceLastEffectiveEndDate

MERGE|ElementEntry|4712/12/31|2021/04/06|Housing Allowance Expat|US Legislative Data Group||E|XXTEST_ASSIGN1|XXTEST|XXTEST_ENTRY2|

ElementEntryValue.dat

METADATA|ElementEntryValue|EffectiveEndDate|EffectiveStartDate|InputValueName|ScreenEntryValue|AssignmentNumber|ElementName|LegislativeDataGroupName|ElementEntryId(SourceSystemId)|SourceSystemOwner|SourceSystemId|ReplaceLastEffectiveEndDate

MERGE|ElementEntryValue|4712/12/31|2021/04/06|Periodicity|PRD|XXTEST_ASSIGN1|Housing Allowance Expat|US Legislative Data Group|XXTEST_ENTRY2|XXTEST|XXTEST_ENTRYVALUE4|

MERGE|ElementEntryValue|4712/12/31|2021/04/06|Amount|100|XXTEST_ASSIGN1|Housing Allowance Expat|US Legislative Data Group|XXTEST_ENTRY2|XXTEST|XXTEST_ENTRYVALUE5|

MERGE|ElementEntryValue|4712/12/31|2021/04/06|Process Separately|Y|XXTEST_ASSIGN1|Housing Allowance Expat|US Legislative Data Group|XXTEST_ENTRY2|XXTEST|XXTEST_ENTRYVALUE6|


🔹 Field Explanation (Infographic Ready)

Element Entry Key Fields




🔹 Step-by-Step Process to Load Element Entries Using HDL

  1. Prepare ElementEntry.dat and ElementEntryValue.dat

  2. Validate AssignmentNumber and element reference data

  3. Zip the files into a single HDL package

  4. Go to Tools → HCM Data Loader → Upload

  5. Submit the load process and monitor status

  6. Verify element entries in the employee’s assignment


🔹 Common Errors & Resolutions

Common Errors in Element Entry Load




🔹 FAQ – Oracle Fusion HCM Element Entry HDL

1️⃣ What is ElementEntry HDL in Oracle HCM?

It allows bulk loading of payroll element entries such as allowances, deductions, and benefits.

2️⃣ Which files are required for element entry load?

ElementEntry and ElementEntryValue metadata are mandatory.

3️⃣ How to load multiple elements for one assignment?

Include multiple ElementEntry records with unique SourceSystemId. Use ElementEntryValue for specific amounts/flags.

4️⃣ Can I overwrite previous entries using HDL?

Yes, set ReplaceLastEffectiveEndDate = Y to overwrite older entries.

5️⃣ Why am I seeing “element not created” error?

  • Invalid AssignmentNumber

  • Element not configured in Oracle HCM

  • Dates not valid

  • Duplicate SourceSystemId

Person Contact HDL in Oracle Fusion HCM – Complete Guide with Contact.dat Template


🔹 Introduction: Why Load Person Contact Using HDL?

In Oracle Fusion HCM, person contact details include email addresses, phone numbers, emergency contacts, dependents, and beneficiaries.
Loading these contacts using HDL allows bulk updates and avoids manual entry.

This is essential for:

  • Employee onboarding

  • Emergency contact management

  • Payroll and benefits integration

  • Accurate HR reporting

You can see step by step video to load person contact details using this Link


🔹 Prerequisites

Before loading Contact.dat, ensure:

  1. Worker/person exists in Oracle HCM (PersonNumber must be valid)

  2. Source system codes are configured correctly

  3. Legislation codes are set (e.g., US, GLOBAL)

  4. Contact types and relationships are defined in reference data


🔹 Objects Required for Person Contact HDL

ObjectPurpose
ContactLoads person contact records (start date, end date)
ContactNameLoads names for the contact (first, middle, last, title)
ContactRelationshipDefines relationships (emergency, dependent, beneficiary, bondholder)

🔹 Sample HDL Templates (Contact.dat hdl template)

  • Contact Metadata - Covers Start Date,End Date of Contact

METADATA|Contact|SourceSystemOwner|SourceSystemId|EffectiveStartDate|EffectiveEndDate|PersonNumber|StartDate

MERGE|Contact|XXTEST|XXTEST_PERCNT2|2019/09/01|4712/12/31|XXTEST_CNT1|2019/09/01

  • ContactName Metadata - Covers Name of the Person contact

METADATA|ContactName|SourceSystemOwner|SourceSystemId|PersonId(SourceSystemId)|EffectiveStartDate|EffectiveEndDate|LegislationCode|NameType|FirstName|MiddleNames|LastName|Title

MERGE|ContactName|XXTEST|XXTEST_CNTNM2|XXTEST_PERCNT2|2019/09/01|4712/12/31|US|GLOBAL|ADAM||TEST|MR.

  • ContactRelationship Metadata - Covers Relation of Person Contact with Worker

METADATA|ContactRelationship|SourceSystemOwner|SourceSystemId|EffectiveStartDate|EffectiveEndDate|PersonId(SourceSystemId)|RelatedPersonId(SourceSystemId)|ContactType|BeneficiaryFlag|DependentFlag|EmergencyContactFlag|BondholderFlag

MERGE|ContactRelationship|XXTEST|XXTEST_CREL_CNT2|2019/09/01|4712/12/31|XXTEST_PERCNT2|XXTEST_PER1|Emergency|||Y|


🔹 Field Explanation (Infographic Ready)

FieldDescription
SourceSystemOwnerSource system that owns the record
SourceSystemIdUnique ID from source system
PersonNumberOracle Fusion employee number
EffectiveStartDateStart date of contact record
EffectiveEndDateEnd date of contact record
LegislationCodeCountry/region (e.g., US, GLOBAL)
NameTypeType of contact name (GLOBAL, LOCAL)
ContactTypeEmergency, Dependent, Beneficiary, Bondholder
EmergencyContactFlagY = Yes, this is emergency contact
DependentFlagY = Yes, this is dependent
BeneficiaryFlagY = Yes, this is beneficiary
BondholderFlagY = Yes, this is bondholder

🔹 Step-by-Step Process to Load Person Contact Using HDL

  1. Prepare Contact , ContactName , and ContactRelationship metadata

  2. Validate PersonNumber and reference data

  3. Zip files in a single HDL upload package

  4. Go to Tools → HCM Data Loader → Upload

  5. Submit process and monitor load status

  6. Verify contact records


🔹 Common Errors & Resolutions

IssueResolution
Contact not createdVerify PersonNumber exists
No change after loadCheck EffectiveStartDate and EffectiveEndDate
Invalid ContactTypeValidate reference data setup
Missing NameEnsure ContactName loaded correctly
Emergency/Dependent flag not updatedVerify flags (Y/N)

🔹 Best Practices

  • Always test in test environment first

  • Validate PersonNumber before upload

  • Use unique SourceSystemId for each contact

  • Keep EffectiveStartDate/EndDate consistent

  • Use separate files for Contact, ContactName, ContactRelationship


🔹 Internal Linking (SEO Boost)

Link this post to:

HDL Template for Person Profile Photo

 For this use  Worker.dat

You can see step by step video to upload the profile photo of worker using this Link

Please find the below sample template :

Save the Blob images in BlobFiles folder and make zip of both .dat and BlobFiles folder 

METADATA|PersonImage|SourceSystemOwner|SourceSystemId|PersonNumber|Image|ImageName|PrimaryFlag

MERGE|PersonImage|XXTEST|XXTEST_PER_IMAGE1|XXTEST2|images.jpeg|XXTEST2|Y

Oracle Fusion HCM Global Transfer Using HDL – Complete Template, Examples & Errors


🧩 Introduction (SEO + User Intent)

Learn how to perform Global Transfer in Oracle Fusion HCM using HDL with complete WorkRelationship, WorkTerms, and Assignment templates. Includes sample .dat files, common errors, troubleshooting, and best practices.

Global Transfer in Oracle Fusion HCM is used when an employee moves from one legal employer to another within the organization.
This process can be automated using HDL (HCM Data Loader) by updating WorkRelationship, WorkTerms, and Assignment objects.

In this blog, you will learn:

  • What is Global Transfer in Oracle Fusion HCM

  • Prerequisites for Global Transfer using HDL

  • Complete HDL template with examples

  • Explanation of each HDL object

  • Common errors and troubleshooting

  • Best practices for Global Transfer


✅ Prerequisite for Global Transfer using HDL

Before performing Global Transfer, ensure the following:

  1. Worker data must already exist in the system. Worker Sample Load

  2. PersonNumber must be valid.

  3. Legal Employer must exist in the target country.

  4. Business Unit, Job, Grade, Location, Department must be configured.

  5. Worker.dat file should be loaded earlier.

👉 Worker.dat is mandatory before performing Global Transfer.


You can see step by step video to do global transfer of worker using this Link



🧠 What Objects Are Required for Global Transfer?

For Global Transfer, you must load:

ObjectPurpose
WorkRelationshipCreates new legal employer relationship
WorkTermsUpdates employment terms
AssignmentUpdates assignment details

✅ For Global Transfer, all three objects are required.


📄 HDL Template for Global Transfer of Worker

1️⃣ WorkRelationship (Global Transfer Flag)

METADATA|WorkRelationship|PersonNumber|LegalEmployerName|DateStart|ActualTerminationDate|PrimaryFlag|WorkerNumber|WorkerType|RehireRecommendationFlag|OnMilitaryServiceFlag|ActionCode|ReasonCode|DateOfDeath|GlobalTransferFlag

MERGE|WorkRelationship|XXTEST2|US3 Legal Entity|2021/01/05||Y|XXTEST2|E|Y|N|GLB_TRANSFER|||Y


🔍 Explanation

  • ActionCode = GLB_TRANSFER → Indicates global transfer

  • GlobalTransferFlag = Y → Mandatory for global transfer

  • LegalEmployerName → New legal employer

HDL Template for Dependent Enrollment in Oracle Fusion HCM (DependentEnrollment.dat)

  HDL Template for Dependent Enrollment in Oracle Fusion HCM (DependentEnrollment.dat) (Using DependentEnrollment.dat) Introduction In O...