2978874 - [ONB2.0]Error while Cancelling Onboarding Process

Below Error appearing while trying to Cancel ONB process from Dashboard.

[COE0018]The cancellation request for new recruit [User ID] has failed. Please contact your administrator.

Successfactors Onboarding 2.0

• Login to Instance
• Click on Dashboard
• Open the Candidate and Click View All task
• Click on Action and Try to Cancel and you get error

• Invalid Configuration for No Show Event Reason or Missing Standard Field

After B2005 release, it is Mandatory to configure No Show Event reason in order to Cancel the Onboarding for Candidate Activity.

Make sure below steps is followed. 

1) Configuring No-Show Event
2) Configuring the Employee Status
3) Configuring the Event Reason

Below is the Document Link on No Show Event Configuration.

https://help.sap.com/viewer/c94ed5fcb5fe4e0281f396556743812c/2005/en-US/51dfc0af23e043c094ad7d56f93c1345.html?q=Triggering%20No-Show%20for%20a%20New%20Hire

4) Report No Show Edit Permission from RBP under Employee data
5) For Cancel ONB EmpEmploymentTermination and okToRehire is mandatory to be present in Odata API Data Dictionary. If this is not present in Odata ApI Data Dictionary, needs to be enabled from Emp Info entity from manage Business configuration. Enable the Field from Emp Info entity.
6) Refresh Odata API and check again to Cancel ONB again
7) Check in Splunk whether you can find similar error as below (note: fields may vary according to the implementation):

Failed to upsert data for entity :EmpEmploymentTerminationresult : custom-string16 is a required field and cannot be blank.,
custom-string17 is a required field and cannot be blank.,
custom-string18 is a required field and cannot be blank.,
custom-string19 is a required field and cannot be blank.
Failed record info: {EmpEmploymentTermination/okToRehire=true, EmpEmploymentTermination/eventReason=ReportedNoShow,

If so, this is a known issue.

In case of any custom field marked as mandatory in EmpInfo then EmpEmploymentTermination used in No Show also is expecting to pass this mandatory field as part of API invocation when we trigger No Show as part of Onboarding cancellation. However there might be cases that if the onboarding is getting cancelled in early stages then these custom fields may not have been populated in that the API throws error.

Product Support please see Internal Memo for more information.

Cancel Onboarding, ONB 2.0 , KBA , LOD-SF-OBX-DG , Generation of Documents using PFS , Problem