3619088 - Troubleshooting Guide: Data not flowing between Recruiting and Onboarding - RCM/OBX

This guide is designed to assist users in troubleshooting common issues encountered during the onboarding and recruiting processes within SuccessFactors. It outlines systematic steps for verifying and resolving field mapping and data transfer discrepancies between the Recruiting (RCM) and Onboarding (OBX) modules.

Purpose and Scope

The primary aim of this guide is to streamline the onboarding and recruiting processes by providing clear instructions for checking data mappings, configurations, and integrations to avoid invalid handovers between modules.

Key Features

• Onboarding Verification: Detailed steps to examine field mappings, integration test pages, and business configurations that could obstruct data transfer from recruiting to onboarding.

• Recruiting Verification: Instructions for validating field presence and configuration accuracy within the Recruiting system, including handling custom fields, picklist modifications, and naming conventions.

By following the procedures outlined in this guide, users can efficiently diagnose and rectify issues, ensuring a smoother transition, improved system performance, and enhanced data integrity. This guide serves as an essential resource for maintaining effective onboarding and recruiting workflows.

These symptoms indicate potential issues with the data integration pipeline between ONB and RCM, which may require technical troubleshooting to identify and resolve underlying causes. Users experiencing these issues are advised to follow the troubleshooting guide of this for detailed steps on addressing and rectifying the data flow problems.

• SAP SuccessFactors Recruiting Management
• SAP SuccessFactors Onboarding 2.0

Onboarding Verification:

When a field is not transferred from Recruiting to Onboarding, begin by reviewing its mapping in the Recruit-to-hire data mapping fields. It is advisable to map all mandatory fields and their related associations, as some fields are interconnected. For instance, failing to map an email field means no email information will be sent from the Recruiting side.

Once the mapping is verified, proceed to examine the Suite Integration Test Page to observe the data transferred from RCM to ONB for the specific candidate. Follow these steps:

1. Go to Provisioning and choose Suite Integration Test Page.
2. Run an Ad hoc report to find out the candidateId, applicationId, and JobReqId for the applicant, or get the applicant information from Recruiting.
3. Enter the candidateId, applicationId, and JobReqId details of the applicant in the Request Parameters:
    

For example:

           {

               "candidateId" : "216",

               "appId" : "270",

               "reqId" : "154",

               "onboardingId" : ""

            }

• Click on Get Data from RCM Or ONB and will get Json Response.
• Verify if data is flowing getting passed from RCM or not.

Use the guide link for more details: Checking the Values Passed from Recruiting to Onboarding | SAP Help Portal

When the information is successfully passed, issues may arise on the Onboarding side that prevent field acceptance. Typically, this points to a misconfiguration within the Manage Business Configuration settings. Possible issues include masking of the field or mismatches in data types between Onboarding and Recruiting. Also, ensure no business rules are assigned to the field that could delete the transferred information.

For the data to be transmitted correctly between the modules, the data type of the fields needs to be the same.

For example, if in Onboarding I am mapping the field Nationality as String, it is necessary to have the same data type in Recruiting's field. As well as in EC.

It is not possible to have a field in Onboarding mapped as String in one module and in the other be mapped as Picklist.

These are the essential steps to verify during the Onboarding. If this is properly maintained, the other verifications tend to be reviewed on the recruiting side.

Note: If the information above it's properly maintained, the recommendation it's to raise a case to Recruiting Module.

Recruiting Verification:

If a field is mapped in the recruit-to-hire data mapping tool but appears null on the Recruiting side, the configuration must be validated within the Recruiting system.

1. Field Mapping Verification: The initial step is to verify whether the information is maintained in the location where it is mapped. For instance, if the mapping in the recruit-to-hire tool directs to a field within the application template, open the application of the respective candidate and confirm that the information is accurately maintained.

2. Custom Field Configuration: If the information is maintained, determine if it is associated with a custom field. All custom fields in Recruiting Management (RCM) need to be made reportable to function correctly, ensuring values flow accurately. After making the field reportable, synchronize the data and attempt to initiate onboarding once more.

3. Handling Modified Picklists: If a picklist is modified within the template in RCM, the system retains the option ID of the previously selected value due to design behavior. Consequently, when a picklist is altered and the value needs to be transferred to Onboarding or Employee Central, select a valid option from the source, which should facilitate a successful value flow.

4. Field Naming Consistency: Ensure that the field configured in the recruit-to-hire tool matches the field associated in the data model and recruiting templates. For example, if in recruit-to-hire the field is designated as "marital_status," but in the data model and recruiting templates it is defined as "marital-status," the system may fail to establish a connection between the fields. Certain fields must be defined uniformly, as specified in the recruit-to-hire data mapping tool, to ensure proper functionality.

These guidelines will help streamline the recruiting process, enhance system efficiency, and mitigate errors in field mapping and data transfer.

Note: If the information above it's properly maintained, the recommendation it's to raise a case to Onboarding Module.

@Support Engineer: Please refer "Internal Memo" section for additional information and clarification on this topic.

• Integration of Recruiting with Onboarding
• Checking the Values Passed from Recruiting to Onboarding

Internal Support KBAs for additional troubleshooting:

• INTERNAL ONLY - Country Field Mapping Behavior | Manage Pending Hires - Recruiting Management
• [INTERNAL] Field Mapping Enhancement for Manage Pending Hires - Recruiting Management

data not flowing, custom fields, rcm pipeline, onboarding 2.0, review new hire data, marital-status, area-code, phone-type, isPrimary, misconfiguration, data model template, application template, integration center, intelligent services, troubleshooting, guide, recruiting , KBA , LOD-SF-RCM-ONB , Onboarding integration , LOD-SF-OBX-RCM , Initiate onboarding from RCM , How To