Customers and onboarding team more often than not would like to cancel onboarding of records seen in the onboarding dashboard.
If you receive an error ” [Onboarding] Cancel OnboardingError : [COE0018]The cancellation request fornew hire xxx has failed. Please contact youradministrator (Onboarding/Offboarding) “, it means there is a missing configuration in the instance.
Assuming other required configurations such as NoShow in the picklist and No Show related event reasons are configured correctly, in this blog we will review what config need to be made to resolve the error.
Configuration:
Goto Manage Data >> Country/Region
Search for the country where the onboardee will (would have) join.
Check if the event reasons, No Show (NO_SHOW) and NO_SHOW_EVENT_REPORT are assigned to the particular country.
If the event reasons are not configured, you are required to configure the event reasons to all countries where you have an onboarding process.
Country/Region – Event Reasons configuration
Note: If the country/region table do not have a functionality to configure event reasons, then you are required configure this wrapper. You do this in the configuration step: Configure Object Definition >> Country/Region, and configure the associations.
After the event reasons are configured, goto OData API Metadata Refresh And Export, and do a cache refresh.
Configuring the event reasons for the specific country will remove one of the potential errors that we see while cancelling onboarding.
If still run into issues, there can be other configuration related topics (either missing or use them for EC only).
One of the places to check will be in employmentInfo. You can access employmentInfo from Admin Center >> Manage Business Configuration.
Check if the end-date (more often with customer label Termination Date) if a mandatory field. If it is, this can be one of the reasons, why you are not able cancel an onboarding record.
The suggested workaround is, to make the end-date as non-mandatory. If you are not able to do so in BCUI, download the XML in provisioning. Make the change, re-import again.
Do an odata metadata cache refresh, and try to cancel the onboarding record. It should go through.
Conclusion:
In this blog post, we looked at couple of scenario’s which can cause an error when you try to cancel an onboarding record, and the configurations you can look at, to mitigate (resolve) these errors.
If there are additional scenarios’ that you have encountered, do leave them in the comments section.
