3048929 - Multiple National IDs Are Mapped And Candidate Initiated From Recruiting Is Resulting In An Error- Onboarding

• Error is occurring for candidates initiated from Recruiting with no National ID, as for some countries, it is required in Onboarding
• Is it possible to map multiple National ID from Recruiting and pass only few?
• An error occurred while saving the HRIS data for the user NEW HIRE due to the following reason: {"responsePayload":[{"userSysId":"123456","hrisSaveStatus":[{"elementType":null,"key":null,"statusCode":"ERROR","errorInfo":"Business key - card-type - has invalid value: for entity nationalIdCard 1 for userSysId 123456"}]}]}."

Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental

SAP SuccessFactors Onboarding

1. Initiate a candidate from recruiting with or without a national ID

Cause 1: As per current behavior, in case that we are not going to use an specific variant - We must ensure that there's no data being sent from Recruiting.

For scenarios where we are partially sending data from Recruiting (like just the primary field), the rest of the fields for national ID will become as required.

Cause 2: record-id field is mapped and enabled in Manage Business Configuration

Resolution 1:

• It will be necessary to Run script to enable "isSkipOnMissingMandatoryInputEntityEnabled". Once we enable this sysconfig value, the nationalId from Recruiting will be skipped if nationalId value is passed as "NULL" or empty string
• Please, raise a ticket with Support Team referring this KBA. Component: LOD-SF-OBX-RCM.

Note: If there are any existing rules in Manage business configuration under National id portlet, making changes to other entities based on national id condition, those might not work i.e will get skipped with this relaxation.

Sample rule that will get skipped:

Resolution 2:

• Ensure that isSkipOnMissingMandatoryInputEntityEnabled script was executed already. If issue persist, it could be due to that the record-id is enabled in the Manage Business Configuration and is mapped
• It is observed that field 'record-id' is the new field added in 2411 by EC team.
• Please note if this behavior is NOT intentionally added or NOT used, please disable this in Manage business Configuration under entity > nationalIdCard
• If it is needed, in that case 'record-id' is the new business key with this new change and needs to be mapped with valid value from Recruiting.

Post changes, you may restart the BP error for candidates initiated from RCM, or it will be necessary to cancel the process trigger of affected candidates and test with a new candidate initiated from RCM 

obx, Onboarding, national id error, Business key - card-type - has invalid value: for entity nationalIdCard, View user validation errors , KBA , LOD-SF-OBX-RCM , Initiate onboarding from RCM , Problem