Symptom
When import data onto a custom MDF object there is an error in the job response stating that fields/associations are required despite them being populated in the import file.
Example error:
- XXXXX is a required field/association in Object XXXXX.
- XXXXX is a required field/association in Object XXXXX.
- XXXXX is a required field/association in Object XXXXX.
Environment
SAP SuccessFactors HCM
Reproducing the Issue
- Log into affected system.
- Download template of the object you will be importing the data onto.
- Fill out import template files, add attachments in a separate folder and compress all files and attachments to a zip file.
- Validate zip file.
- Import the file after successful validation.
- Notice that the import fails.
- Go to the Job Manager.
- Download the Job Response.
- See the errors mentioned present.
Cause
External code has a value of AutoNumber but there is no value for this maintained in the import file causing it to fail.
Resolution
Input a value such as #1, #2, #3 and so forth for the external code and import the file again.
For example if there are two records with different effective date in these object then use the external code as #1 for both the records.
However, if those entries are totally two different record than put #1 and #2 instead
See Also
Keywords
Custom MDF, MDF, Import and Export, MDF Import, failing, LOD-SF-MDF-IMP, autonumber, required field, required association, attachments, object , KBA , LOD-SF-MDF-IMP , Import and Export Issues , Problem