SAP Knowledge Base Article - Public

3666952 - Behavior of the Time Recording Calendar‑Based Time Sheet Auto‑Submission Event

Symptom

This KBA provides additional explanation to help understand the behavior of the Time Recording Calendar‑Based Time Sheet Auto‑Submission event.

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

Environment

SAP SuccessFactors Time Tracking

Cause

Here is a summary of what is actually happening in the system:

1. `TLMTriggerTask`performs several actions related to Time Off and subsequently initiates TLMTriggerRecalculation job.
2. Once the recalculation job is triggered, `TLMTriggerTask` completes its process and does not execute any additional steps.  
3. The jobs mentioned in the SAP Help documentation are not directly executed by `TLMTriggerTask`. Instead, each job in the sequence triggers the next job upon completion.  
4. The Time Sheet Submit job does not initiate another Recording Calendar job. Instead, it triggers an event, and that event is processed further within the system. 
5. The customer will not see these triggers or job connections directly in the system.

Some time gaps may appear between the scheduled jobs, especially when system resources are heavily utilized by the overall data center workload.
For example, the TLMTriggerRecalculation job may be scheduled to start more than one hour after the TLMTriggerTask job has executed.


This behavior is expected when the TLMTriggerTasks job runs during periods of high system load, as described in KBA 2927303 - Change In Run Time Of Jobs Scheduled By TLMTriggerTask Job.

As a result, all jobs and events, including the calendar‑based time sheet auto‑submission, may occur several hours after the TLMTriggerTasks job executes.
This is normal and correct behavior based on the system’s resource and load balancing mechanisms.

Note: This is why, by standard, only one daily TLMTriggerTasks job should be scheduled, ideally at midnight when the system is least busy.
Scheduling multiple TLMTriggerTasks jobs is never recommended due to the risks detailed in KBA 2705723 - Can Multiple Trigger Tasks Jobs Be Created or Scheduled at Custom Times?

Resolution

If there is very special customer requirement to have TLMTriggerTasks job executed at a different time than 12AM of the Tenant Preferred Time Zone, and you experienced "delay" as explained above, you may consider below workaround to prepone the execution time of the jobs scheduled by TLMTriggerTasks job, including calendar-based time sheet auto-submission.
Note: This is only a workaround for the emergency situation. Please DO NOT use it as a daily routine. 

Triggering the TLMTriggerRecalculation job immediately will also prepone the whole job series, including calendar-based time sheet auto-submission event, and this is possible by below steps from the Provisioning. 

  1. Access "Manage Scheduled jobs". 
  2. Choose Job Type: Trigger Recalculation. 
  3. If you have not scheduled other recalculation job manually, the latest one should be scheduled by the daily TLMTriggerTask job. 
  4. Click Run It Now. 
  5. The TLMTriggerRecalculation job should execute immediately.
  6. The subsequent jobs in the sequence each trigger the next job upon completion:   
    • Time Sheet Import job
    • Time Sheet Generate job
    • Time Sheet Submit job
    • Calendar Run events

Note: The calendar-based time sheet auto-submission event cannot be viewed from the Provisioning or the Execution Manager Dashboard. Please check the approval status of the concerned Employee Time Sheet directly. 

See Also

Keywords

TLMTriggerTasks Job, trigger task job, trigger recalculation job, submit time sheet job, time recording calendar, time sheet auto submission, auto submit, tms, Employee Time Sheet, submit job, delay, time gap, scheduled run time , KBA , LOD-SF-TTR-TMS , Time Sheet , How To

Product

SAP SuccessFactors Time Tracking all versions

Attachments

Pasted image.png
Pasted image.png