3798215 - LOA total days uses expected return date instead of actual return date until next change (time off)

• LOA calculation dates are incorrect, using the expected return date instead of the actual return date.
• The calculated total LOA days initially show an inflated value instead of the correct value
• The issue occurs when creating a leave of absence and then recording the return to work; the total LOA days correct only after a subsequent modification.

• SAP SuccessFactors Employee Central
• Time Off

1. Create a leave of absence starting on 07/12/2026 and set an expected return date.
2. Enter an actual return to work on 07/19/2026 and check the total LOA days calculated by a job information onSave rule (for example, rule “EC_CalTotalLOADays”).
3. Observe that the total LOA days initially reflect a value based on the expected return date rather than the actual return date.
4. Perform any subsequent change (for example, add a new job info record or edit a field) and save; the total LOA days then update to the correct value.

Known onSave cross‑portlet timing limitation: the job information onSave rule runs before the return‑to‑work record is committed, so rule functions read data that still reflects the expected return date/end boundary; the correct value appears only after a later save when all records are committed.

Immediate workaround: Perform a minimal change on the relevant job information record (for example, update a non-impacting custom field) and save to update the LOA days with the correct value.

Business rule execution timing for onSave

loa days, leave of absence, expected return date, actual return date, return to work, onSave rule timing, cross portlet, job information rule, rule recalculation, time off calculation, integration center, custom mdf, employee time, recalculation after save, rule function , KBA , LOD-SF-EC-TIM , Time Off , Product Enhancement