Symptom
SM-mapping is a configuration in the Candidate Profile template which allows synchronization of data between the Candidate Profile and the Employee Profile when you update one of them. This requires first of all a correct configuration. When creating sm-mapping entries, the Implementation Partner should make sure that the mapped fields have the same field type e.g. text to text and picklist to picklist. Also, both fields have to be defined with the same picklist ID when sm-mapping picklist fields. The field ID itself does not need to match between templates in order to map successfully, unless it concerns a background element.
Typical sm-mapping related issues:
- Candidate Profile and Employee Profile are not synchronized
- The candidate search doesn't work for sm-mapped fields
- When hiring a candidate through Manage Pending Hires an error message appears (at the last step of EC-RCM integration)
- sm-mapped data is not reportable from Recruiting V2 domain
- A recruiter cannot edit a sm-mapped field in an internal Candidate Profile
Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.
Read more...
Environment
SAP SuccessFactors Recruiting Management
Product
Keywords
Error while updating updateCandBackgroundWithSuccession for candidate, sm-mapping, candidate profile, candidate profile template, background element, employee profile sync, cpt, succession data model to candidate profile template. , KBA , LOD-SF-RCM-ADM , Admin Center, RBP, Permissions and Settings , How To
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.