Error during Worker HDL load
Error Message1 : You Must a Primary Value
Solution: Add PrimaryWorkTermsFlag attribute in Workterm Metadata.
Error Message2 : Person can have only 1 active Primary WorkRelationship
Solution: Update the termination date tagged with previously terminated Workrelationship.
Error Message3 : SourceSystemOwner is unknown
Solution: Update the HRC_SOURCE_SYSTEM_OWNER lookup by removing FUSION from the custom lookup code, then update the same value in the Worker (or relevant) HDL file.
Zip the updated file and load it via My Client Groups → Data Exchange → Import and Load File, and refresh to confirm successful completion.Error Message4 : JBO-FND:::FND_FLEX_SEG_VAL_NOT_IN_LIST: xxx is not in the list
Solution: Resolve the issue by either updating the Site Code value for the affected Position record and removing the end date, or by extending the end date of the Site Code.
After making the correction, reload the Worker HDL file to apply the changes.Error Message5 : You must enter a valid value for the GradeId field.
Solution: Provide the correct GradeId/GradeCode for the new Position in the DAT file, or alternatively pass #NULL (with
In both scenarios, run the ESS job – Synchronize Person Assignment from Position to sync grade, job, and other position-related fields.PER_ENFORCE_VALID_GRADE = Y) or set PER_ENFORCE_VALID_GRADE = N to avoid passing grade values.Error Message6 : The values xxxx aren't valid for the attribute LegislationCode.
Solution: Update the existing Legal Entity with a unique Registration Number via Setup & Maintenance → Legal Structures → Manage Legal Reporting Unit Registrations, then save the changes.
After the update, reload the Worker HDL file to complete the process.Error Message7 : METADATA line for the {BO_NAME} business object is invalid, When attempting to load a Worker HDL file to add Person Extra Information
Solution: Refresh the Worker HDL object, download the latest template, and update the Worker HDL file with the required PEI EFF, EFF_CATEGORY_CODE, and FLEX attributes by following the Oracle documentation for loading extensible flexfields.
Save, zip, and reload the file via My Client Groups → Data Exchange → Import and Load Data to confirm the error is resolved.Error Message8 : You cannot update this record because the SourceSystemId <SOURCE_SYSTEM_ID_1> and the SourceSystemOwner ABC are invalid when attempting Assignment Supervisor.
Solution: The user can either remove Source System ID/Owner and use surrogate or user keys for Assignment Supervisor, or align the Source System ID/Owner with Fusion-supported keys, ensuring parent/child objects do not mix different key types.
Alternatively, identify and update source key mappings via HRC_INTEGRATION_KEY_MAP using SourceKeys.dat, after which the original AssignmentSupervisor data can be successfully loaded—this approach is best suited for existing Fusion integrations.Error Message9 : You must provide only one parent record Worker and it must start on the earliest effective start date and not have an end date.
Solution: Pass the same date for both StartDate and EffectiveStartDate, ensuring it matches the first effective start date from PER_ALL_PEOPLE_F for the person.
If only creating a new work relationship or assignment, remove the METADATA Worker and MERGE Worker records from the data file.Error Message10 : No Assignment record from 2018-10-27
Solution: Assignment data is missing in Worker.dat from the effective date 2018-10-27.
