Symptom
When Concurrent Employment is enabled for Contingent Workers, the system performs a rehire on a new employment record. However, the Original Start Date of the new employment is incorrectly retained from the previous employment, instead of being reset to the Work Order Start Date.
Environment
- SAP SuccessFactors Employee Central
Reproducing the Issue
- In SuccessFactors, create a Contingent Worker with:
- Worker ID: XXXX
- Start Date: 1st January 2025
- Terminate the worker with an effective date of 15th February 2025.
- Rehire the same worker with an effective start date of 1st April 2025.
- A popup may appear prompting to select the previous employee. Select Yes.
- Set the new Work Assignment to be active until 30th April 2025.
- Observe that the newly created work assignment reflects the start date as 1st January 2025 instead of 1st April 2025.
Cause
This is a Known Issue. When concurrent employment is enabled, the system does not reset the Original Start Date to the Work Order Start Date during rehire.
Resolution
The fix for this issue is planned to be deployed on 2H 2025 release.
For release timelines, please review SAP SuccessFactors Product Release & Road Map Information.
Keywords
Contingent Worker, Contingent Worker originalStartDate, Concurrent Employment, Rehire Issue, Original Start Date, Work Order Start Date, Employment Lifecycle, SuccessFactors, Employee Central, Start Date Mismatch, Work Assignment, 2H2505 Release, Rehire on New Employment, Employment Record Error, EC Contingent Workforce, Data Inconsistency, Rehire Workflow, Termination and Rehire, Start Date Override, originalStartDate, MDI Contingent Worker Replication, MDI Replication, Incorrect originalStartDate, ECT-255762 , KBA , LOD-SF-EC-CWF , Contingent Workforce , Known Error