3804132 - Absence Reallocation task completes with errors – EMPLOYEE_TIME_HAS_BOOKINGS_ON_CLOSED_ACCOUNT

The Automated Reallocation of Time Account Balances process fails to reallocate valid absence records for an employee, even though all configuration prerequisites are correctly set (Posting Order = "Oldest First by Bookable Period", Absence Reallocation Enabled = Yes, Enable Recalculation = Yes).

Typical scenario:
- An absence is cancelled, freeing up balance on an older Time Account.
- Days from another absence that had "overflowed" into a newer Time Account should be automatically reallocated back to the older account once balance becomes available (e.g., after a new triggering Leave Booking is created).
- The reallocation does not occur; the newer account balance remains unchanged.

The following error may be visible in system/application logs, associated with the internal batch correction process:
- EMPLOYEE_TIME_HAS_BOOKINGS_ON_CLOSED_ACCOUNT
- PROCESSING_OTHER_TIMES_FAILED

No new Absence Reallocation task is created after the trigger event, or the task completes with status "Completed with errors.

SAP SuccessFactors Employee Central - Time off

1. Create an absence that fully depletes the balance of an older Time Account.
2. Create a second absence that overflows into the next Time Account, since the older account is depleted.
3. Cancel the first absence, releasing balance back to the older account.
4. Create a new absence to trigger reallocation processing.
5. Check both accounts: the overflowed days do not migrate back to the older account, even though balance is now available.

This is expected, by design behavior not a defect.

The reallocation process uses an "all-or-nothing" logic per employee. This exists because dependencies can exist between absences with respect to balance (reallocation/recalculation may reveal insufficient balance), and the system needs to avoid a scenario where only some records are saved "by chance" while others are skipped.

Absence Reallocation only picks up EmployeeTime records where editable ≠ false. In the affected scenario, some EmployeeTime records tied to a closed Time Account were still marked editable = true, instead of being set to editable = false.

Normally, EmployeeTime.editable should stay in sync with the related Time Account's closed status: when a Time Account is closed (typically via the Period-End Process – PEP), its associated EmployeeTime records are automatically set to editable = false, so they are excluded from future recalculation/reallocation.

When this sync is broken, reallocation tries to include the stale editable=true records, attempts to deallocate them from their now-closed account, and raises EMPLOYEE_TIME_HAS_BOOKINGS_ON_CLOSED_ACCOUNT. Due to the per-employee "all-or-nothing" processing, this single error blocks reallocation for the valid, unrelated records of the same employee (e.g., current-year accounts), and the task completes with errors.

Common reasons the editable/closed-account sync gets broken:
- A booking was posted or re-posted to the account after it was already closed (a manual/retro correction).
- Records were imported or migrated with editable left at its default value, not explicitly set to false, even though the account was already closed.
- The Time Account was closed manually or outside the standard Period-End Process, so the automatic update to set EmployeeTimes to non-editable never ran.

Set the affected EmployeeTime records to editable = false so they are excluded from reallocation. This can be done via:

    •    Manage Data (per individual record), or
    •    MDF import (for several records)

on the EmployeeTime object. Apply this only to the stale records tied to closed accounts.

After that, re-run the reallocation  the valid records will process successfully.

EMPLOYEE_TIME_HAS_BOOKINGS_ON_CLOSED_ACCOUNT, PROCESSING_OTHER_TIMES_FAILED, Absence Reallocation, EmployeeTime editable, Time Account closed, all-or-nothing reallocation, MDF CORRECT, Completed with errors, Period-End Process PEP , KBA , LOD-SF-EC-TIM-ABS , Absence error's - Calculations, Deductions, TT&ET , Problem