SAP Knowledge Base Article - Public

3842164 - Consecutive LOA handling: return-to-work and job information behavior in Time Off — SAP SuccessFactors Employee Central

Symptom

To record consecutive leave of absence (LOA) in SAP SuccessFactors Time Off where no actual return to work occurs between them — for example, maternity protection leave immediately followed by parental leave. The following questions arise:

  • What is the recommended approach: setting the actual return date of the first LOA to the start date of the consecutive LOA, or leaving it empty?
  • When the actual return date is set, two job information records appear on the same date — a Return to Work record (status: Active) and a Leave of Absence record (status: Dormant). Is this expected?
  • Are there functional drawbacks to leaving the actual return date empty?
  • The Leave of Absence Return Date field on the LOA start job information record for the second LOA shows the return date of the previous LOA, not the current one. Is this intended?

Environment

SAP SuccessFactors Employee Central - Time Off

Reproducing the Issue

  1. Create LOA A with start and expected/actual return dates.
  2. Create LOA B that starts on the same date as LOA A’s actual return date (no active day in between).
  3. Set LOA A’s actual return date to LOA B’s start date.
  4. Observe that two job information records are created on the same date: Return to Work (Active), then Leave of Absence (Dormant).
  5. Alternatively, leave LOA A’s actual return date empty and observe that no Return to Work record is created between the two LOAs.

Cause

  • By-design job information record creation sequence: when an actual return date is maintained for a previous LOA and a consecutive LOA exists, the system creates a Return to Work record on the same date before the subsequent LOA record.
  • Position Management with Right to Return requires an actual return date (or ending a global assignment) before adding a new LOA to ensure correct rights to return and position assignments.
  • The LOA data model separates start and return job information references; the LOA start record can reflect the previously maintained return date until the current LOA’s Return to Work record is created.

Resolution

1. Recommended Approach — Set the Actual Return Date

Setting the actual return date of the first LOA to the start date of the consecutive LOA is the supported and recommended approach. The Right to Return documentation states:

"When adding multiple leaves of absence (Time Off) or global assignments, you must add an actual return date to the leave of absence or end the global assignment before adding a new one. This ensures that the rights to return, including position assignments, are created correctly."

This is a hard requirement when Position Management with Right to Return is active. Without Right to Return, it remains the recommended approach per the standard data model.

Required sequence — known system validation:

The system raises a validation error if you attempt to set the actual return date while the consecutive LOA already exists with the same start date. This is documented behavior. The Validations for Leave of Absence (LOA) article describes the required sequence:

  1. Delete the consecutive LOA.
  2. Set the actual return date on the first LOA.
  3. Re-create the consecutive LOA.

Example: Maternity leave starts 27 July, expected return 03 November. Parental leave starts 03 November. To record the maternity leave's actual return date as 03 November: delete the parental leave, set 03 November as the actual return date on the maternity leave, then re-create the parental leave.


2. Two Same-Date Job Information Records — Expected Behavior

When the actual return date of the first LOA equals the start date of the consecutive LOA, two job information records are created on the same date:

  • Return to Work (Active) — generated by the actual return date entry
  • Leave of Absence (Dormant) — generated by the consecutive LOA

This is documented standard system behavior. The Validations for Leave of Absence (LOA) article explicitly states:

"The system creates a new record in the job information with 'return' from leave, although the user is still on LOA (due to consecutive LOAs)."

These records are not an error. The Return to Work record formally closes the first LOA; the Leave of Absence record opens the second. The employee's effective status on that date is Dormant (Leave of Absence) because the LOA record succeeds the Return to Work record in the job information chain.

Note on downstream impact: The impact of same-date Return to Work and LOA records on payroll replication, accrual rules, or reporting depends on the customer's specific system configuration. These areas should be validated in context before go-live.


3. Leaving the Actual Return Date Empty — Implications

If Position Management with Right to Return is active: Leaving the actual return date empty before creating a new LOA is not supported. The Right to Return documentation cited above is explicit on this requirement.

If Right to Return is not in use: Leaving the actual return date empty is technically possible. The Limitations and Restrictions of Importing Leave Requests article confirms that when the actual return date is blank, only the LOA start job information record is created — no Return to Work record.

The practical consequences:

  • The first LOA has no formal closure in the job information history.
  • No same-date Return to Work record is created, which avoids the transient Active status.
  • Depending on accrual rule configuration, the absence of a Return to Work record may affect accrual calculations or reporting that evaluates employee status transitions.

Leaving the actual return date empty is therefore not the recommended approach and should only be considered after validating the impact on all relevant downstream processes.


4. Leave of Absence Return Date on the LOA Start Record — Design Behavior

The Employee Time article describes the LOA data model:

  • Leave of Absence Job Info ID (Start): References the job information history entry on the LOA start date.
  • Leave of Absence Job Info ID (Return To Work): References the job information history entry effective on the absence end date + 1.

The return date of an LOA is stored on its Return to Work job information record — not on the LOA start record. When consecutive LOAs share the same date, the LOA start record for the second LOA inherits the most recently populated return date value in the job information chain at that point, which is the actual return date of the first LOA.

The second LOA's own return date (expected or actual) will appear on the Return to Work record that is created when that LOA is eventually ended. There is no supported configuration to display the current LOA's return date directly on its own LOA start job information record. This is by design: the data model separates LOA start data and return date data across two distinct job information records.

Practical guidance: To view the return date of the current LOA, navigate to the Return to Work job information record associated with that LOA, or refer to the Employee Time record where the Expected Return Date and Actual Return Date fields are stored directly on the leave request object.

See Also

Keywords

consecutive loa, back-to-back leave, return to work, job information, same-day records, leave of absence, time off, actual return date, right to return, position management, dormant status, payroll replication, accruals, reporting, expected behavior , KBA , LOD-SF-EC-TIM-ABS , Absence error's - Calculations, Deductions, TT&ET , How To

Product

SAP SuccessFactors Employee Central all versions