Symptom
- Candidates are moved to the "Hired on Other Req" status.
- No actions were taken by the user, and the candidates were not hired on another requisition.
Environment
SAP SuccessFactors Recruiting Management
Reproducing the Issue
- Move a candidate to Hired status in a first Requisition
- Keep the first Requisition open
- The same candidate applies to a new Requisition and will be in a Default status
- Now close the first requisition
- The candidate is moved to "Hired on Other Req" status in the new Requisition.
Cause
When a requisition under which a candidate was hired remains open for an extended period (e.g., a year) and is later closed while the candidate is in an in-progress status for another requisition, the candidate will be moved to "Hired on Other Requisition" status for the current requisition.
Resolution
- Identify the requisition under which the candidates were hired.
- Verify the closure date of the requisition.
- Understand that the Provisioning job named moveCandidatesToHiredOnOtherReqStatus is triggered when a requisition is closed, automatically or manually.
- Confirm that this job reviews all active applications of the candidate and moves them to the "Hired on Other Requisition" status accordingly.
- If necessary, review the system configuration and job settings to prevent unintended status changes in the future.
See Also
Keywords
sap successfactors recruiting, hired on other requisition status, candidate management, provisioning job, moveCandidatesToHiredOnOtherReqStatus, requisition closure, candidate status change, recruitment management, candidate issue, status update, system configuration, operational challenges, troubleshooting. , KBA , LOD-SF-RCM-CAN , General Candidate Issues (not Offers, not Profiles) , Problem
SAP Knowledge Base Article - Public