Oracle HDL Multiple Assignment Load for Worker
Organizations often require employees to perform multiple jobs simultaneously. Oracle Fusion HCM supports Multiple Assignments, allowing a worker to hold more than one active assignment within the same legal employer or across different business functions.
Using HCM Data Loader (HDL), organizations can efficiently load primary and secondary assignments during implementation, mergers, acquisitions, or workforce restructuring projects.
🔹 What is Multiple Assignment?
A Multiple Assignment worker has:
- One Person Record
- One Work Relationship
- Multiple Work Terms
- Multiple Assignments
Example:
| Employee | Assignment |
|---|---|
| Adam Baro | HR Analyst (Primary) |
| Adam Baro | Project Coordinator (Secondary) |
The employee receives separate assignment records while maintaining a single worker profile.
🔹 Business Scenario
Vision Corporation hires Adam Baro as a full-time employee.
Primary Assignment
- HR Analyst
- Effective Date: 01-Jan-2018
- Primary Assignment = Yes
Secondary Assignment
- Project Coordinator
- Effective Date: 01-May-2021
- Primary Assignment = No
Both assignments exist under the same work relationship.
🔹 HDL Components Used
The HDL file contains the following business objects:
| HDL Component | Purpose |
|---|---|
| Worker | Creates person record |
| PersonName | Worker name details |
| PersonNationalIdentifier | SSN/National ID |
| WorkRelationship | Employment relationship |
| WorkTerms | Terms of employment |
| Assignment | Worker assignments |
🔹 Multiple Assignment HDL Structure
🔹 HDL Sample
Worker
METADATA|Worker|SourceSystemOwner|SourceSystemId|EffectiveStartDate|EffectiveEndDate
|PersonNumber|ActionCode|StartDate|DateOfBirth MERGE|Worker|XXTEST|XXTEST_PER1|2018/01/01|4712/12/31|XXTEST1|HIRE|2018/01/01
|1975/01/01Person Name
METADATA|PersonName|SourceSystemOwner|SourceSystemId|PersonId(SourceSystemId)
|EffectiveStartDate|EffectiveEndDate|LegislationCode|NameType|FirstName
|MiddleNames|LastName|Title MERGE|PersonName|XXTEST|XXTEST_PERNAME1|XXTEST_PER1|2018/01/01|4712/12/31|US
|GLOBAL|Adam||Baro|MR.
National Identifier
METADATA|PersonNationalIdentifier|SourceSystemOwner|SourceSystemId
|PersonId(SourceSystemId)|LegislationCode|IssueDate|ExpirationDate
|NationalIdentifierType|NationalIdentifierNumber|PrimaryFlag MERGE|PersonNationalIdentifier|XXTEST|XXTEST_NID1|XXTEST_PER1|US||
|SSN|456-23-4167|Y
Work Relationship
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_PDSERVICE1|XXTEST_PER1|US1 Legal Entity
|2018/01/01|||||||Y|||||XXTEST1|E|N|Y
Primary WorkTerms
METADATA|WorkTerms|ActionCode|SourceSystemOwner|SourceSystemId|EffectiveStartDate
|EffectiveEndDate|EffectiveSequence|EffectiveLatestChange|AssignmentName
|AssignmentNumber|AssignmentStatusTypeCode|AssignmentType|BusinessUnitShortCode
|PositionOverrideFlag|PrimaryWorkTermsFlag|PeriodOfServiceId(SourceSystemId)
|PersonId(SourceSystemId)|LegalEmployerName|SystemPersonType MERGE|WorkTerms|HIRE|XXTEST|XXTEST_WRKTERM1|2018/01/01|4712/12/31|1|Y|
|XXTEST_WRKTERM1|ACTIVE_PROCESS|ET|US1 Business Unit|Y|Y|XXTEST_PDSERVICE1
|XXTEST_PER1|US1 Legal Entity|EMP
Secondary WorkTerms
MERGE|WorkTerms|HIRE|XXTEST|XXTEST_WRKTERM2|2021/05/01|4712/12/31|2|Y|
|XXTEST_WRKTERM2|ACTIVE_PROCESS|ET|US1 Business Unit|Y|N|XXTEST_PDSERVICE1
|XXTEST_PER1|US1 Legal Entity|EMP
Primary Assignment
METADATA|Assignment|ActionCode|SourceSystemOwner|SourceSystemId|EffectiveStartDate
|EffectiveEndDate|EffectiveSequence|EffectiveLatestChange|AssignmentName
|AssignmentNumber|AssignmentStatusTypeCode|AssignmentType|BusinessUnitShortCode
|PositionOverrideFlag|PrimaryAssignmentFlag|PrimaryFlag|SystemPersonType
|LegalEmployerName|JobId(SourceSystemId)|LocationId(SourceSystemId)
|OrganizationId(SourceSystemId)|PositionId(SourceSystemId)|GradeId(SourceSystemId)
|PeriodOfServiceId(SourceSystemId)|PersonId(SourceSystemId)|PersonTypeCode
|ManagerFlag|LabourUnionMemberFlag|WorkTermsAssignmentId(SourceSystemId)
|AssignmentCategory|Frequency|HourlySalariedCode|NormalHours|NoticePeriod
|ProbationPeriod|ProbationUnit|ReasonCode MERGE|Assignment|HIRE|XXTEST|XXTEST_ASSIGN1|2018/01/01|4712/12/31|1|Y
|E-XXTEST1|XXTEST_ASSIGN1|ACTIVE_PROCESS|E|US1 Business Unit|Y|Y|Y|EMP
|US1 Legal Entity|XXTEST_JOB1|XXTEST_LOC65XXTEST_DEPT1||XXTEST_GRADE01
|XXTEST_PDSERVICE1|XXTEST_PER1|Employee|Y|N|XXTEST_WRKTERM1|FR|W|S|40|0|||NEWHIRE
Secondary Assignment
MERGE|Assignment|HIRE|XXTEST|XXTEST_ASSIGN2|2021/05/01|4712/12/31|2|Y
|E-XXTEST2|XXTEST_ASSIGN2|ACTIVE_PROCESS|E|US1 Business Unit|Y|N|N|EMP
|US1 Legal Entity|XXTEST_JOB1|XXTEST_LOC65XXTEST_DEPT1||XXTEST_GRADE01
|XXTEST_PDSERVICE1|XXTEST_PER1|Employee|Y|N|XXTEST_WRKTERM2|FR|W|S|40|0|
||NEWHIRE
🔹 Understanding Primary Flags
Only one assignment can be primary.
🔹 Common Use Cases
Multiple Job Roles
Employee works as:
- HR Analyst
- Payroll Specialist
Project-Based Assignment
Employee receives temporary assignment on project.
Academic Institutions
Faculty member also serves as:
- Professor
- Department Coordinator
🔹 HDL Load Process
Worker HDL Process
🔹 Validation Checklist
Before Loading
✔ Worker does not already exist
✔ Legal Employer exists
✔ Business Unit exists
✔ Department exists
✔ Job exists
✔ Grade exists
✔ Location exists
✔ Source Keys are unique
✔ Work Terms references are correct
After Loading
✔ Worker created successfully
✔ Work Relationship created
✔ Primary Work Terms created
✔ Secondary Work Terms created
✔ Primary Assignment visible
✔ Secondary Assignment visible
✔ Assignment flags validated
🔹 Common HDL Errors
Q1 - Assignment Not Created
Cause: Incorrect WorkTermsAssignmentId
Resolution: Verify Work Terms source key.
Q2 - Multiple Primary Assignments
Cause: PrimaryAssignmentFlag = Y on multiple assignments
Resolution:Only one assignment should be primary.
Q3 - Invalid Department
Cause: Department Source Key Missing
Resolution: Load department before assignment.
Q4 - Invalid Job
Cause: Job not available
Resolution: Load workforce structures first.
🔹 Best Practices
Load Workforce Structures First
- Jobs
- Grades
- Locations
- Departments
Maintain Effective Dating
Ensure assignment dates follow business requirements.
Validate Primary Assignment Logic
Only one primary assignment should exist.
🔹 Frequently Asked Questions (FAQ)
What is a multiple assignment worker in Oracle Fusion HCM?
A multiple assignment worker is an employee who holds more than one active assignment under the same work relationship.
Can a worker have multiple work terms?
Yes. Oracle Fusion supports multiple work terms associated with a single work relationship.
Can both assignments be primary?
No. Only one assignment can have PrimaryAssignmentFlag = Y.
Can secondary assignments have different departments?
Yes. Secondary assignments can belong to different departments, jobs, grades, or locations.
Can HDL load multiple assignments in one file?
Yes. Multiple Work Terms and Assignment records can be loaded in a single HDL file.
What assignment type is used for employees?
Employee assignments typically use:
AssignmentType = E
Can payroll be attached to multiple assignments?
Yes, depending on payroll and enterprise configuration.
