Symptom
- Inconsistent behavior when separation records are created or updated: two records with separation event reason appear with different effective dates.
- Separation event reason is incorrectly applied to earlier Job Information records (for example, hire or other data change records) below a later release/cutover stack.
- No validation error is shown; the system displays two separation records.
- When the user opens All Actions → Employment Details, selects an Event Reason, and clicks Cancel (without saving), a prior Job Information record is updated to a separation event reason. The same behaviour is happening when the modification Saved, or only initiated without Save or Cancel action.
- When updating the separation effective date in Job Information history and then interacting with Employment Details, the prior record may be overwritten with separation.
- No specific error messages or error codes are displayed.
Environment
SAP SuccessFactors Employee Central
Reproducing the Issue
- Initiate a separation with an effective date (via UI or direct API/integration).
- Update the separation effective date in Job Information history and save.
- Navigate to All Actions → Employment Details.
- Open the Event Reason dropdown (select the same or a different separation reason) or modify a value in Employment Details.
- Click Cancel on the Employment Details page (do not save) / Save the change / Perform the change without clicking on Save or Cancel
- Return to Job Information and observe that a prior record (below a later release/cutover stack) has been updated with a separation event reason, resulting in two separation records with different effective dates.
Resolution
Engineering has confirmed the fix. A Patch (2605p7) will be deployed in June 2nd in Preview and June 4th in Production environments.
As a temporary corrective action, restore the affected Job Information records via Full Purge import:
- Prepare a Job Information Full Purge file that resets the incorrect event reason/effective-dated record back to the intended values.
- Import in Full Purge mode to correct the stack as per referenced guidance.
See Also
Keywords
PTCH-50235, ECT-273004, KI1H2026, INC27190289, CS20260012465239, separation, termination, employment details, job information, event reason, duplicate separation, effective date, cancel without save, ui behavior, api direct, sfapi, unintended separation, job info stack, last day worked, release regression , KBA , LOD-SF-EC-TER , Termination Details , Bug Filed
SAP Knowledge Base Article - Public