3753330 - Time off monthly automatic accrual shows delay between createdOn and lastRunDate

Accrual is configured to run automatically on a monthly basis.

In Manage Data > Time Account Change Calendar, there is an observable time gap (for example, ~3 hours) between the "CreatedOn" and "LastRunDate" timestamps.

A request exists to run the monthly accrual at a specific local time (for example, 08:00) instead of the observed execution time (for example, 11:05).

Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.  

SAP SuccessFactors Employee Central

1. Configure a Time Account Type for monthly accruals with Automatic Accrual Creation.
2. Open Manage Data > Time Account Change Calendar for the relevant month.
3. Review the calendar entry and compare the "CreatedOn" and "LastRunDate" values; note that execution time does not align to a fixed hour.

• The TLMTriggerTasks job creates automatic Time Account Change Calendar entries at midnight based on the tenant preferred time zone; this run time cannot be customized.
• After creation, subsequent system jobs run sequentially and load is balanced across the data center; execution of calendar entries is distributed over an approximate 6-hour window.
• As designed, calendar entries are not executed immediately upon creation, resulting in a normal gap between "CreatedOn" and "LastRunDate".

Nothing can be impacted. It is normal that the change calendar is not executed immediately once it is created. 

• KBA2705723 - Can Multiple Trigger Tasks Jobs Be Created or Scheduled at Custom Times?
• Handbook: Using Admin Center >> Updating Tenant Preferred Time Zone

time account change calendar, createdon, lastrundate, delay, monthly accrual, automatic accrual creation, tlmtriggertasks, tenant preferred time zone, fixed execution time, midnight run, time off, employee central, scheduling, execution window, accrual timing , KBA , LOD-SF-EC-TIM , Time Off , How To