Symptom
A picklist field in the Requisition is mapped to a custom-long EC field in Recruit to Hire Data Mapping; Value appears correctly in the Suite Integration Test Tool, however value is not visible during Onboarding.
Environment
SAP SuccessFactors Onboarding
Cause
The target field jobInfo.custom-long is a numeric long type, but it is being treated as a picklist in configuration and supplied with a picklist external code (string). Picklist external codes are strings and are incompatible with a numeric long field, causing the value to fail and display as blank.
Resolution
- Avoid using a custom-long field when mapping a picklist from RCM, to avoid data mismatch.
- Create a new custom-string, not custom-long, field in Manage Business Configuration.
- Map the field in Recruit to Hire Data Mapping.
- Pass valid value from RCM to ONB.
See Also
SAP Help Portal | Help with Mapping Fields from Recruiting to Onboarding
Keywords
jobInfo.custom-long10, custom-long, picklist external code, data type mismatch, recruiting to onboarding mapping, rcm to onb, onboarding data review, employee central job info, field not populating, picklist mapping, onboarding field type , KBA , LOD-SF-OBX-RCM , Initiate onboarding from RCM , Problem
SAP Knowledge Base Article - Public