Many customers have reported issues while initiating onboarding for candidates, the candidates do not appear in dashboard. The candidate's Onboarding Workflow fails due to error.
SAP SuccessFactors Onboarding
Reproducing the Issue
- Initiate onboarding for candidates from RCM
- Candidates do not appear in Onboarding Dashboard
- Check the process object of the candidate, Process Variant is not assigned
- In BPE:Monitor Processes the Onboarding Workflow for the candidate fails due to an error
There could be different reasons for the Onboarding Workflow to fail. In this KBA we will be discussing error due to failure in saving compensation data for the candidate. A support ticket can be created to get the exact error logs. Before that you can follow the steps mentioned in the resolution to perform the initial check on the data passed for the candidate from RCM.
Check the Suite Integration Test Page to get data passed from RCM to ONB for the particular candidate. You can follow https://launchpad.support.sap.com/#/notes/2917185 on detailed steps to get the same.
Check for PayComponent Recurring and PayComponent Non Recurring data passed from RCM. You will see one or more pay component variants have null values passed for different fields mapped.
Case 1: PayComponent variant is applicable for the job requisition or for the candidate
Please be informed that if a pay component variant is applicable for the particular job requisition then you should not pass null value for "pay-component" field. In this case a valid value needs to be passed for this field and for the particular pay component variant null values should not be passed from RCM for any of the mandatory mapped fields.
Note: Irrespective of the fact whether paycompvalue(amount) field is mandatory or non-mandatory in "Business Configuration" or "Recruit to Hire Data Mapping", value for it needs to be passed while sending data for "PayComponent" variant. As "amount" field is mandatory from database side, it throws exception in case null value is passed for amount.
Case 2: PayComponent variant is not applicable for the job requisition or for the candidate
If a pay component variant is not applicable for the particular job requisition then you can pass null value(invalid value) for "pay-component" field. In this case if invalid value for field "pay-component" is passed, that variant of Pay-Component will be skipped even before it validates for amount value. As a result, if "pay-component" field with invalid value is passed and amount is null it won't land into any error.
Onboarding Initiation from RCM, Compensation data not saved, pay component, Onboarding2Workflow error , KBA , LOD-SF-OBX-RCM , Integration RCM , Known Error