SAP Knowledge Base Article - Public

3284465 - Candidate Profile Mapping Behavior after Deconversion - Recruiting Management

Symptom

  • What happens to the data in a custom field mapped from Employee Profile to Candidate Profile after Deconversion?
  • Internal Candidate Profile custom field configured in sm-mapping becomes blank after Candidate is Deconverted to External Profile

Environment

SAP SuccessFactors Recruiting Management

Reproducing the Issue

  1. Map a custom field from Employee Profile to Internal Candidate Profile
  2. Data will sync to the candidate profile
  3. Inactive the user/terminate in EC
  4. Process the Internal to External Candidate Deconversion in Provisioning
  5. Data has disappeared in the candidate profile

Resolution

As confirmed by Product Management, this is an expected behavior. The sm-mapping works for internal candidate profile since it is linked to the employee profile. Once the internal candidate profile is de-converted to an external profile, the link to the employee profile (which is the source of data) is gone.

See Also

2233525 - How is the system working with sm-mapping? - Recruiting Management - SAP for Me

Keywords

sm-mapping; employee to candidate deconversion; , KBA , LOD-SF-RCM-CAN , General Candidate Issues (not Offers, not Profiles) , How To

Product

SAP SuccessFactors Recruiting 2205