Symptom
- Two Hired events are seen in a Candidate's application history.
- One entry is shown on the day the Candidate was moved to the Hired Status on the Job Requisition.
- A second entry shows the Candidate moved to the Hired Status on the first day of their subsequent employment.
Environment
- SAP SuccessFactors Recruiting Management
- SAP SuccessFactors Onboarding 1.0
Reproducing the Issue
- Hire a candidate using Recruiting Management.
- The Candidate is Onboarded using ONB 1.0.
Cause
Prior to the 1H 2505 release, 2 entries logged in audit trail (RCM_APP_STATUS_AUD table), HIRED status change:
- First time, when the operator is moving the candidate from HIRABLE to HIRED status manually through status pipeline.
- Additionally, on the subsequent start day for this Candidate, when the "OnStartDateStatusChange" job picks the candidate who is getting hired - a second entry is recorded. This job is triggered from ONB1.0 side.
Resolution
As part of the 1H 2025 release, the database will storing only one entry (not to show the same second HIRED entry in audit trail for this use case when for RCM-ONB1.0 hiring flow), when the hiring flow is getting invoked twice.
This fix will be available as part of the 1H 2025 Release and will be part of the notable fixes and "What's new Viewer (WNV)" in 1H 2025 documents.
See Also
Keywords
SAP SuccessFactors, Recruiting Management, Pipeline, Status, Hired, Technical User, Candidate, Employee , KBA , LOD-SF-RCM-APP , Applicants and Job Applications , Problem