Symptom
Wrong Person UUID is assigned to the Onbordees when during Pre-Onboarding verification (1st Rehire check) they were accepted as New Hire, and during Onboarding Rehire Verification (2nd Rehire check) accepted as Rehire with New Employment.
Environment
SAP SuccessFactors Onboarding 2311
Reproducing the Issue
- An Employee is terminated in EC
- Candidate initiated from Recruiting
- Candidate lands into Pre-Onboarding verification (1st Rehire check)
- Admin continues "as New Hire"
- Onbordee completes Personal Data Collection step
- Candidate lands into Onboarding Rehire Verification (2nd Rehire check)
- Admin continues with Rehire as New Employment
- At this point, candidate gets the wrong Person UUID. The Person UUID is taken from the new Person UUID created after Step 3, instead than from the previous Person UUID which was assigned to the Rehire.
Cause
Known issue.
Resolution
- Engineering have already made a fix in the upcoming release b2405, and it is currently Under Validation.
Next release dates: Product Release & Road Map Information
First Half 2024 | Preview: April 19-21 | Production: May 17-19 - As a Workaround: Please use the Pre-Onboarding verification (1st Rehire check).
Keywords
Person UUID, 2nd Rehire Check, Rehire as New Employment, RONE , KBA , LOD-SF-OBX-RHM , Rehire Mechanism , Known Error
Product
SAP SuccessFactors Onboarding 2311