Symptom
When updating fields such as phone number via the Integration Center, the changes appear as successfully completed in execution logs and candidate history; however, they are not reflected in the Candidate Profile UI.
Environment
SAP SuccessFactors Recruiting Management
Reproducing the Issue
- Start the Integration Center job that updates candidate data using the Candidate or CandidateLight entities.
- Verify on a candidate profile (internal candidate) that the target field (for example, primary phone) is blank before the run.
- Run the Integration Center job and confirm the job execution/history and candidate audit show the field as updated.
- Refresh and review the candidate profile UI; the field remains blank and does not reflect the update.
- Perform the same update via OData API; the field appears correctly on the candidate profile UI.
Cause
This behavior is related to how the Integration Center processes updates for internal candidates in instances where SM-Mapping is being used.
In these scenarios, the information displayed in the Candidate Profile UI is sourced from the Employee data. While the Integration Center job completes successfully and records the update, the corresponding Employee data is not updated at the same time. As a result, the changes are not reflected in the Candidate Profile UI.
Resolution
This issue will be corrected in the 2H 2026 Release. Release dates can be found on SAP SuccessFactors Product Release & Road Map Information.
As a workaround, you can perform candidate updates using OData API.
See Also
Keywords
integration center, candidatelight, candidate profile, internal candidate, primary phone, phone number, ui not updated, not reflected in ui, odata api, batch update, sm-mapped instance, csv import, RCM-159411 , KBA , LOD-SF-RCM-INT , Integration Center & Intelligent Services , Problem
SAP Knowledge Base Article - Public