We would like to share our experiences of using National ID mapping Integration in between Recruitment Management and Onboarding 2.0. It provides solution to complex client requirements to integrated candidate national ID information only for selected countries in between RCM and ONB 2.0. Here, we are presenting you how to integrate national ID information from RCM to Onboarding 2.0 for only selected countries. This will help you address similar requirements in your projects.
In general, National ID information will capture by New Hire in personal data collection step during Onboarding 2.0 process. But in our current project, the client has running operations in 80+ countries, only USA external candidate should capture National ID information in RCM and rest of the country’s external candidates will capture during Personal Data Collection step in Onboarding process.
Scenario 1: The customer wants to capture new hire national ID information for USA only in Recruitment management and it should be integrated with Onboarding 2.0
Scenario 2: Rest of the countries national ID will capture during Onboarding process (Rest of the countries, new hires will capture national ID during Onboarding process)
As per the current SuccessFactors system design, if we do national ID mapping in the recruit to hire data field mapping in Onboarding, the system will have limitations because the national ID mapping will apply to all countries after initiating onboarding from Recruitment and the result is as follows:
Scenario 1 (For example USA):
Please find below the KBA for more information.
https://me.sap.com/notes/3048929
Scenario 2 (Global Countries) :
Expected Output / Outcome
Scenario 1: As soon as initiated Onboarding from RCM, the onboarding process initiated successfully for USA and can see new hire record in Onboarding dashboard. The responsible group user (who will do review new hire data step) can see SSN information in review new hire data step.
Scenario 2: As soon as initiated Onboarding from RCM, the onboarding process initiated successfully for Global countries and can see new hire record in Onboarding dashboard.
Benefits
The main benefits are as follows:
Conclusion
As per the current SuccessFactors system design, if we do national ID mapping in the recruit to hire data field mapping in Onboarding, the system will have limitations because the national ID mapping will apply to all countries. This document will help to the customers who need the National ID information for specific countries during the recruitment process. The detailed configuration steps of this document will helpful to trigger Onboarding process for only specific countries from Recruitment where The onboarding process will only be successful for the country where we capture the national ID in Recruitment and simultaneously the onboarding process will get success for the remaining countries that did not capture national ID information during recruitment.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 42 | |
| 12 | |
| 11 | |
| 7 | |
| 6 | |
| 5 | |
| 4 | |
| 4 | |
| 3 | |
| 3 |