2507544 - Employee Central - Troubleshooting Recruiting and Onboarding to Employee Central Integrations

• This KB article was created to assist with troubleshooting field mapping, propagation and other configuration related issues in regards to Onboarding and Recruiting to Employee Central.
• Most of the issues covered in this article occur when adding a new employee via Manage Pending Hires.

• SAP SuccessFactors HXM Suite
• SAP SuccessFactors Employee Central
• SAP SuccessFactors Onboarding
• SAP SuccessFactors Recruiting

Index

• Implementation Guides
• Field Mapping Configuration
• Common Issues
• Propagation from RCM/ONB

Implementation Guides

Most data issues when adding a new employee from RCM and/or ONB are due to either field mapping or propagation (via propagation xml or Business Rules). The field mapping issues can be resolved by confirming the configuration is correct as per the implementation guides:

• Onboarding Implemenation Guide
• Recruiting Management Implementation Guide
• Using Onboarding with Recruiting Management and Employee Central

Field Mapping Configuration

The following table includes common field mapping issues and error messages that occur during the new hire process:

Common Issues

 The following table includes common issues/errors found when attempting to hire/rehire an employee from Manage Pending Hires:



Propagation from RCM/ONB

Another major consideration when troubleshooting newhire/rehire issues is data propagating from RCM/ONB to EC. The data coming from RCM/ONB to EC can be overwritten by a number of different sources on the EC side. Please review the information below to understand the causes of the data (coming from RCM/ONB) to be overwritten when adding a employee in 'Add New Employee' or 'Manage Pending Hires' tools:

Important note: System will first load the mapping data when candidate is opened in manage pending hires hence this can have impact on country specific fields/mapping as system will read first the country passed and then will store the country specific mappings that are valid for that country, in this case, if the country is changed during the manage pending hires system will not load the mapping again for these fields.

New hire employee
Employee does not have any previously maintained data in the system. New Hire data (if mapped correctly) coming from RCM/ONB can be overwritten by the following (in order):

1. onInit Business Rules
2. onChange Business Rules

_{If the field is overwritten, check any of the three sources above to verify if the data is being propagated as expected}

Rehire employee
Employee is a Rehire and was previously Terminated. The Rehire data will have the source information coming from the database as the records already exist in the system. This data can then be overwritten by the following (in order):

1.) RCM/ONB data will overwrite the database information if the field mapping is setup correctly
2.) onInit Business Rules
3.) onChange Business Rules

Note: The value below the field is always the value coming from ONB/RCM as shown below

Internal Hire
The user is a current employee being hired for another position through RCM and possibly ONB. This behavior is similiar to that of Rehired employees as the source information will be coming from the database because the records already exist. The data can then be overwritten in the following (in order):

1.) RCM/ONB data will overwrite the database information if the field mapping is setup correctly
2.) onChange Business Rules

** onInit Rules are not triggered during the Internal Hire process

Note: For internal hires, the first value stored below the field is always the previously stored database value and the second value is coming from RCM or ONB. When using the v12 UI, the second value will appear to the right of the field. For PP3, the second value appears below the first value, example below:

The behavior regarding old values displayed for internal hires is documented in KBA 2514357

Final comments on propagation: If a field is showing unexpected/incorrect or missing data, it could be caused by any of the following: onInit Business Rules and/or onChange Business Rules. Always check these sources to validate if they are causing the data for the field to be overwritten.

OnInit rules and onChange rules can cause data to be overwritten on page load, for example, when navigating from the Personal Information section to Job Information, first the system will trigger any onInit rules that are setup/configured and then process onChange rules for RCM/ONB fields on page load. Please note, onChange rules typically are only triggered when a change is made to the field the onChange rule is set on, however if data is coming from RCM/ONB, for example when mapping Position data, then the onChange rule will trigger on page load.

Note: If there is specific mapping only defined in RCM transformation template to EC and onboaring process in involved then this mapping will not work. Only direct mapping will work to EC.

sf, success factors, EC, ONB, OBD, on boarding, RCM, newhire, rehire, internalhire, manage pending hires, mph, invalid data, pre-day1, manage pending recruits, FAQ , KBA , LOD-SF-EC-INT , Manage Pending Hires (Integration RCM/ ONB/ OBX + UI) , LOD-SF-EC , Employee Central , LOD-SF-RCM-INT , Integration Center & Intelligent Services , LOD-SF-OBD-INT , Integrations with Onboarding , How To