Symptom
- A rehire was processed under new employment, creating a duplicate employee profile.
- There is a request to merge the new (duplicate) employee record into the original record while preserving all Onboarding 2.0 data and completed tasks.
- Clarification is requested on whether Onboarding 2.0 data would be retained after a merge.
- No error messages are provided.
Environment
SAP SuccessFactors Onboarding
Reproducing the Issue
- Perform a rehire using new employment, which creates a new employee profile and user id (duplicate).
- Attempt to merge the duplicate profile into the original profile while preserving Onboarding 2.0 data and completed tasks.
Cause
A duplicate profile was created because the rehire was performed with new employment instead of rehire with old employment. Onboarding 2.0 data is tied to the user id and employment record under which it was initiated and cannot be merged into a different profile.
Resolution
- Note that there is no native “merge” function for Onboarding 2.0 data; data remains bound to the initiating user id/employment record.
- Identify the incorrect/duplicate onboardee profile that must be removed.
- Use DRTM Master Data Purge to remove the duplicate onboardee profile; a separate DRTM Onboarding Purge is not required afterward.
- Prepare and upload a list of inactive users (by user id or assignment id) that includes the duplicate profile to be purged.
- If immediate removal is required, select “Ignore data retention time configuration for this purge request.”
- Execute the purge and verify that the duplicate profile is removed to prevent downstream issues.
See Also
Keywords
onboarding 2.0, duplicate profile, duplicate user, rehire with new employment, rehire with old employment, merge employee records, no merge function, drtm master data purge, purge onboardee, user id, assignment id, data retention time, employee central, rehire correction, downstream issues , KBA , LOD-SF-OBX-RHM , Rehire Mechanism , Problem
SAP Knowledge Base Article - Public