- When using the Recruit-To-Hire Mapping Tool, recruiting field from the selected template is not showing.
- Some of the RCM fields are not visible in Recruit-To-Hire Mapping.
"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."
- SAP SuccessFactors Recruiting Management
- SAP SuccessFactors Onboarding 2.0
NOTE: After adding the fields, run an OData API Metadata Refresh - 2171588 - OData API Metadata Refresh and Export in SuccessFactors Cloud
The logic when mapping EC field to RCM using Recruit-To-Hire is that they should have the same data type. We cannot map a string field with number or date or picklist. To identify the EC data type, you can go to Manage Business Configuration and check the target EC field.
If you are using custom field, it's important to mark as custom="true" in the XML template. If the field is not marked as custom="true" and is a custom field, it will not be displayed in the drop down to map the values in Recruit-To-Hire Mapping Tool. Also, do not configure a standard field ID as custom.
If the field is configured on the template with proper data type but still does not show in Recruit-To-Hire, check if the specific field ID data type is consistent to all templates. The system will be confused what data type to display if the same field ID is configured differently per template.
For custom offer approval field that is derived from job requisition or application, it will only show in Job Offer template dropdown if the field is marked as reportable. Making the field as reportable will make it editable in Offer. For standard field ID or non-reportable custom field in Offer, you can map it directly in their source template (Job Requisition or Job Application) since these field will only appear as read only in Offer approval.
RCM, OBD, EC, obd 2.0, manage, pending, hires, recruits, field, unavailable, visible, selectable. , KBA , LOD-SF-RCM , Recruiting Management , LOD-SF-EC , Employee Central , LOD-SF-OBD , Onboarding , LOD-SF-OBX , Onboarding 2.0 , Problem