Human Capital Management Blog Posts by Members
Explore blogs from customers or SAP partners to gain best practices and fresh insights to succeed.
cancel
Showing results for 
Search instead for 
Did you mean: 
1,555

Introduction

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.

Trends/Problem Statement / Overview

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)

Challenges

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:

  • The onboarding process will only be successful for the country where we capture the national ID in Recruitment.
  • The onboarding process will fail for the remaining countries that did not capture national ID information during recruitment and candidates will appear in Onboarding BPE error tile.

Solution

Scenario 1 (For example USA):

  • We need to create specific job application template for USA and there we need to define the field for SSN. So, external candidate will capture SSN during the recruitment process.
  • Configured Business Rule as shown in below

RajendraPrasadAllam_0-1741591051234.png

 

  • Placed business rule in Manage Rules in Recruitment as shown in below

RajendraPrasadAllam_1-1741591051237.png

RajendraPrasadAllam_2-1741591051239.png

 

  • National ID mapping in recruit to hire data field mapping.

RajendraPrasadAllam_3-1741591051245.png

  • Create an SAP incident in SAP launchpad and request SAP to run the script

Please find below the KBA for more information.

https://me.sap.com/notes/3048929

RajendraPrasadAllam_4-1741591051250.png

 

RajendraPrasadAllam_5-1741591051256.png

Scenario 2 (Global Countries) :

  • We need to create specific application template for global countries without national ID field. So, external candidate will capture national ID information during the Onboarding process.

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:

  • It provides solutions 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.
  • The rehire process for candidates who have national ID details captured during the recruitment process will be determined by the system and they will be placed in the first rehire check by matching their exact profile.
  • The onboarding process will get success for the remaining countries that did not capture national ID information during recruitment.

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.

SAP SuccessFactors Onboarding 

1 Comment