Oracle Fusion HCM Tutorials – HDL Templates & SQL: πŸ§‘‍πŸ’Ό Oracle HCM: Load Contingent Worker Using HDL (Complete Guide with Example)

Saturday, 21 March 2026

πŸ§‘‍πŸ’Ό Oracle HCM: Load Contingent Worker Using HDL (Complete Guide with Example)

 

Oracle Worker.dat HDL Template with Example | Oracle Fusion HCM Guide

πŸ“Œ Overview

In Oracle HCM Cloud, contingent workers (contractors, freelancers, temporary staff) are managed as non-payroll resources. These workers are:

  • Identified with “C” (Contingent Worker type)
  • Not processed through payroll
  • Can submit expenses
  • Can be converted into employees

Using HCM Data Loader (HDL), you can efficiently load contingent worker data in bulk.


🎯 When to Use Contingent Worker HDL Load?

Use HDL when:

  • Migrating contractor data from legacy systems
  • Hiring bulk contingent workforce
  • Integrating third-party vendor workers
  • Managing project-based workforce

🎯 Employee Vs Contingent Worker Comparison

Employee Vs Contingent Worer



πŸ”Ή Prerequisites 

Before you start:

  1. Work structure must be loaded

    Click here for a sample Work Structure

  2. You must have a Source Key defined. In earlier blogs, we created “XXTEST” as our source key.

  3. Download the object templates from your instance:

Navigator → My Client Group → Data Exchange → View Business Objects

🎯 When to Use Contingent Worker HDL Load?🧩 Key HDL Components for Contingent Worker

To successfully load a contingent worker, you must include:

ComponentPurpose
WorkerCore person record
PersonNameWorker name details
PersonEmailEmail information
PersonNationalIdentifierID (SSN, PAN, etc.)
PersonLegislativeDataGender, marital status
WorkRelationshipEmployment relationship
WorkTermsTerms of work
AssignmentJob assignment

πŸ“„ Sample HDL File For Contingent Worker

Below is a ready-to-use HDL template for loading a contingent worker:

METADATA|Worker|SourceSystemOwner|SourceSystemId|EffectiveStartDate
|EffectiveEndDate|PersonNumber|ActionCode|StartDate|DateOfBirth MERGE|Worker|XXTEST|XXTEST_PER2|2018/01/01|4712/12/31|XXTEST2|HIRE
|2018/01/01|1975/01/01

METADATA|PersonName|SourceSystemOwner|SourceSystemId|PersonId(SourceSystemId)
|EffectiveStartDate|EffectiveEndDate|LegislationCode|NameType|FirstName
|MiddleNames|LastName|Title
MERGE|PersonName|XXTEST|XXTEST_PERNAME2|XXTEST_PER2|2018/01/01
|4712/12/31|US|GLOBAL|AdamCWK||Baro|MR.

METADATA|PersonNationalIdentifier|SourceSystemOwner|SourceSystemId
|PersonId(SourceSystemId)|LegislationCode|IssueDate|ExpirationDate
|NationalIdentifierType|NationalIdentifierNumber|PrimaryFlag MERGE|PersonNationalIdentifier|XXTEST|XXTEST_NID2|XXTEST_PER2|US
|||SSN|456-24-4167|Y

METADATA|PersonEmail|SourceSystemOwner|SourceSystemId|
PersonId(SourceSystemId)|DateFrom|DateTo|EmailType|EmailAddress
|PrimaryFlag MERGE|PersonEmail|XXTEST|XXTEST_EMAIL2|XXTEST_PER2|2018/01/01|
4712/12/31|W1|AdamCWK.baro@ha.com|Y
METADATA|PersonLegislativeData|SourceSystemOwner|SourceSystemId
|EffectiveStartDate|EffectiveEndDate|PersonId(SourceSystemId)|
LegislationCode|MaritalStatus|MaritalStatusDate|Sex MERGE|PersonLegislativeData|XXTEST|XXTEST_LEG2|2018/01/01|4712/12/31
|XXTEST_PER2|US|M|1998/05/12|M

METADATA|WorkRelationship|SourceSystemOwner|SourceSystemId
|PersonId(SourceSystemId)|LegalEmployerName|DateStart|
EnterpriseSeniorityDate|LegalEmployerSeniorityDate|ActualTerminationDate
|Comments|LastWorkingDate|NotifiedTerminationDate|PrimaryFlag|
ProjectedTerminationDate|RehireAuthorizerPersonId|RehireAuthorizor
|RehireReason|WorkerNumber|WorkerType|OnMilitaryServiceFlag|
RehireRecommendationFlag MERGE|WorkRelationship|XXTEST|XXTEST_PDSERVICE2|XXTEST_PER2|
US1 Legal Entity|2018/01/01|||||||Y|||||XXTEST2|C|N|Y
METADATA|WorkTerms|ActionCode|SourceSystemOwner|SourceSystemId
|EffectiveStartDate|EffectiveEndDate|EffectiveSequence|
EffectiveLatestChange|AssignmentName|AssignmentNumber|
AssignmentStatusTypeCode|AssignmentType|BusinessUnitShortCode|
PositionOverrideFlag|PrimaryWorkTermsFlag|PeriodOfServiceId(SourceSystemId)
|PersonId(SourceSystemId)|LegalEmployerName|SystemPersonType|
ProposedUserPersonType
MERGE|WorkTerms|HIRE|XXTEST|XXTEST_WRKTERM2|2018/01/01|4712/12/31
|1|Y||XXTEST_WRKTERM2|ACTIVE_PROCESS|CT|US1 Business Unit|Y|Y|
XXTEST_PDSERVICE2|XXTEST_PER2|US1 Legal Entity||Contingent Worker

METADATA|Assignment|ActionCode|SourceSystemOwner|SourceSystemId
|EffectiveStartDate|EffectiveEndDate|EffectiveSequence|
EffectiveLatestChange|AssignmentName|AssignmentNumber|
AssignmentStatusTypeCode|AssignmentType|BusinessUnitShortCode|
PositionOverrideFlag|PrimaryAssignmentFlag|PrimaryFlag|
SystemPersonType|LegalEmployerName|JobId(SourceSystemId)|
LocationCode|OrganizationId(SourceSystemId)|PositionId(SourceSystemId)
|GradeId(SourceSystemId)|PeriodOfServiceId(SourceSystemId)|
PersonId(SourceSystemId)|PersonTypeCode|ManagerFlag|
LabourUnionMemberFlag|WorkTermsAssignmentId(SourceSystemId)|
AssignmentCategory|Frequency|HourlySalariedCode|NormalHours|NoticePeriod
|ProbationPeriod|ProbationUnit|ReasonCode|WorkerType
MERGE|Assignment|HIRE|XXTEST|XXTEST_ASSIGN2|2018/01/01|
4712/12/31|1|Y|E-XXTEST2|XXTEST_ASSIGN2|ACTIVE_PROCESS|C|
US1 Business Unit|Y|Y|Y|CWK|US1 Legal Entity|XXTEST_JOB1|ComUSHQ|
XXTEST_DEPT1||XXTEST_GRADE01|XXTEST_PDSERVICE1|XXTEST_PER2||Y|N
|XXTEST_WRKTERM2|FR|W|S|40|0|||NEWHIRE|C



πŸ”Ή Steps to Load Worker.dat in Oracle Fusion

  1. Save all HDL objects as Worker.dat

  2. Create a zip file containing Worker.dat and all other HDL files

  3. Navigate to:

Navigator → My Client Group → Data Exchange → Import and LoadImport

  1. Upload the zip file

  2. Refresh page to verify load status

  3. Once successfully loaded, confirm work structure is updated correctly

πŸŽ₯ Step-by-step video guide is available here


⚠️ Important Considerations

  • WorkerType must be “C” (Contingent Worker)
  • AssignmentType must be “C” or “CT”
  • No payroll setup required
  • Ensure Legal Employer & Business Unit exist
  • Use unique SourceSystemId

πŸ”— Internal Links 

πŸ‘‰ Payroll Related Blogs:

πŸ‘‰ HDL Guides:


❓ FAQ Section 

1. What is a contingent worker in Oracle HCM?

A contingent worker is a non-payroll worker such as a contractor or freelancer managed in Oracle HCM.


2. What is WorkerType “C” in HDL?

WorkerType “C” represents a Contingent Worker.


3. Can contingent workers be converted to employees?

Yes, Oracle HCM provides conversion flows to convert contingent workers into employees.


4. Do contingent workers run through payroll?

No, contingent workers are non-payroll resources.


5. What is AssignmentType for contingent workers?

AssignmentType is usually C (Contingent) or CT (Contingent Terms).


6. Is WorkTerms mandatory for contingent workers?

Yes, WorkTerms define the structure of assignment and must be included.


7. Can we load contingent workers using HSDL?

Yes, but HDL is preferred for bulk and complex loads.


8. What happens if WorkerType is incorrect?

The load will fail or create incorrect worker classification.


πŸ’¬ Feedback Section

Was this article helpful?

πŸ‘ Yes – Clear HDL example
πŸ‘Ž No – Need more scenarios

πŸ’‘ Comment below if you want:

  • Contingent Worker → Employee Conversion HDL
  • Supplier / Agency Worker Integration
  • Time & Labor setup for contingent workers

No comments:

Post a Comment

🧾 Element Eligibility Costing in Oracle HCM Using HDL (Complete Guide with Example)

Element Eligibility Costing in Oracle HCM | HDL Step-by-Step Guide πŸ“Œ Overview Element Eligibility Costing in Oracle HCM Cloud allows org...