HDL Error Worker.dat: "A Payroll Relationship With This Number Already Exists. Enter A Unique Number (PAY-1635393)"
(Doc ID 2391447.1)
Last updated on AUGUST 31, 2023
Applies to:
Oracle Fusion Global Human Resources Cloud Service - Version 11.13.17.11.0 and laterInformation in this document applies to any platform.
Symptoms
When attempting to load Worker.zip with HDL,
the following error occurs.
ERROR
-----------------------
A payroll relationship with this number already exists. Enter a unique number. ( PAY-1635393 )
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Load Worker.zip that contains Worker.dat with the below METADATA lines, where Source Keys are used
METADATA|Assignment|SourceSystemOwner|SourceSystemId|WorkTermsAssignmentId(SourceSystemId)|ActionCode|EffectiveStartDate|EffectiveEndDate|EffectiveSequence|EffectiveLatestChange|AssignmentStatusTypeCode|PersonTypeCode|BusinessUnitShortCode|PrimaryAssignmentFlag|DepartmentName|JobCode
METADATA|PersonLegislativeData|PersonLegislativeId|EffectiveStartDate|EffectiveEndDate|PersonId|PersonNumber|LegislationCode|HighestEducationLevel|MaritalStatus|MaritalStatusDate|Sex|GUID|SourceSystemOwner|SourceSystemId
METADATA|PersonName|PersonNameId|EffectiveStartDate|EffectiveEndDate|PersonId|PersonNumber|LegislationCode|NameType|FirstName|MiddleNames|LastName|Honors|KnownAs|PreNameAdjunct|MilitaryRank|PreviousLastName|Suffix|Title
METADATA|Worker|PersonId|EffectiveStartDate|EffectiveEndDate|PersonNumber|BloodType|CorrespondenceLanguage|StartDate|DateOfBirth|DateOfDeath|CountryOfBirth|RegionOfBirth|TownOfBirth|ApplicantNumber|CategoryCode|ActionCode|ReasonCode|GUID|SourceSystemOwner|SourceSystemId
METADATA|WorkRelationship|LegalEmployerName|PersonId|PersonNumber|DateStart|WorkerType|LegalEmployerSeniorityDate|ActualTerminationDate|LegalEntityId|Comments|EnterpriseSeniorityDate|PrimaryFlag|ProjectedTerminationDate|TerminateWorkRelationshipFlag|GUID|SourceSystemOwner|SourceSystemId
METADATA|WorkTerms|ActionCode|AssignmentId|AssignmentName|AssignmentNumber|EffectiveEndDate|EffectiveLatestChange|EffectiveSequence|EffectiveStartDate|PeriodOfServiceId(SourceSystemId)|PrimaryWorkTermsFlag|SourceSystemOwner|SourceSystemId
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |