Symptom
- When Importing Global Information for Dependents, an Error message appears "This record was not saved because there were errors in other records for <Dependent ID>".
- When other fields that are marked as Non-Mandatory (Ex . Last Name (Official / at Birth), Highest Degree, First Name (Official), Salutation, Native Preferred Language, Nationality) are also supplied to the Import file, the Error no Longer appears.
- You have personalinfo_dependents model with fields set as non-mandatory but they are set as mandatory in parent personalInfo.
Environment
SAP SuccessFactors Employee Central - Dependents Management
Reproducing the Issue
- Import Employee Data -> Entity: Global Information/Personal Information.
- Fill all the details for dependents.
- An Error message "XXXX is a required field and cannot be blank" occurs which is preventing the Import.
Cause
- The error happens because of error message "PERSONAL_INFO : Last Name (Official / at Birth), Highest Degree, First Name (Official), Salutation, Native Preferred Language, Nationality is a required field and cannot be blank: ECT_service_layer_REQUIRED_FIELD_EMPTY".
- These fields are configured as mandatory fields in the BCUI PersonalInfo. It is available on PersonalInfo portlet when it is invisible on Dependent.PersonalInfo section.
- There is a known gap. In the Import, personalInfo metadata is shared by both employee personal and dependent personal, despite existing child model personalinfo_dependents or personalinfo_employee with different requirements.
- That means, Import behavior will always check the BCUI configuration of parent personalInfo. If the fields are mandatory for personalinfo and not for the person types, they will be mandatory for import. Child model personalinfo_dependents will be respected just for UI changes.
Resolution
To unblock for import, you can set these fields as mandatory = "No" for personalInfo and try the import again.
If you do not wish to maintain these fields (Last Name (Official / at Birth), Highest Degree, First Name (Official), Salutation, Native Preferred Language, Nationality) values for dependent personal before Importing Dependent.GlobalInfo, they can make the BCUI configuration as below:
1. For PersonalInfo: Set Last Name (Official / at Birth), Highest Degree, First Name (Official), Salutation, Native Preferred Language, Nationality fields as mandatory="No".
2. For personalInfo_employee: Add same fields as personalInfo, set Last Name (Official / at Birth), Highest Degree, First Name (Official), Salutation, Native Preferred Language, Nationality fields as mandatory="Yes".
With above configurations:
- UI behavior:
- For the GlobalInfo or PersonalInfo portlet, these fields are mandatory.
- For the dependent's GlobalInfo or PersonalInfo portlet, these fields are not mandatory.
- Import behavior:
- For dependent's GlobalInfo or PersonalInfo, it will not throw mandatory error for these five fields., and Employee's Personal Info can also be imported without data on these fields.
Keywords
SF, EC, Success factors, Employee Central, ECT_service_layer_REQUIRED_FIELD_EMPTY, import, importing, personalinfo, dependents, person type, Import, PersonalInfo, parent, is a required field and cannot be blank, Globalinfo, Global Information, Personal Information , KBA , LOD-SF-EC-DPD , Dependents Management , Known Error