Symptom
The Background Element entry title displays the Picklist Option ID instead of the Picklist Label on the Internal Candidate Profile when the Picklist field is configured as the first field in the Background Element.
Environment
SAP SuccessFactors Recruiting Management
Reproducing the Issue
- Go to Careers > My Candidate Profile.
- In Employment History, ensure a picklist field (for example, a yes/no field) is configured as the first/primary field of the background element.
- Add or edit an entry and save.
- Observe the entry title shows the picklist option ID instead of the label; expanding the entry shows the correct label in the details.
- The same behavior can be seen when viewing an internal candidate in Recruiting > Candidates and in the job application candidate profile snapshot. External candidate profiles and reporting show the correct label.
Cause
The Picklist field configured as the first field in the Background Element has an invalid field mapping. As a result, the system is unable to resolve the Picklist label and falls back to displaying the raw Option ID.
Resolution
- A permanent code fix has been developed and will be available after the 2H2026 major release.
- As a temporary workaround, move the picklist field out of the primary/title position in the background element by placing a meaningful non-picklist field at the top.
See Also
- KBA 3514023 - Option ID appearing instead of Picklist Value
- KBA 2918216 - Using the same picklist field on both the Candidate Profile and Application
- KBA 2233525 - How is the system working with sm-mapping? - Recruiting Management
- KBA 3091327 - SM-Mapping in Candidate Profile - Recruiting Management
- SAP Help Portal - Check SM-Mapping | Help Portal
Keywords
candidate profile, employment history, picklist, option id, label not displaying, current employer, yesno picklist, background element, internal candidate, primary field, title field, sm-mapping, succession data model, CPT, SDM, UI display issue , KBA , LOD-SF-RCM-CAN , General Candidate Issues (not Offers, not Profiles) , Problem
SAP Knowledge Base Article - Public