SAP Knowledge Base Article - Public

3364562 - The maximum number of time events for a user in a request should not be greater than 200

Symptom

This KBA helps to understand the reasoning behind the error faced during the Time events import using the REST API "Time Events".

 {"status":"BAD_REQUEST","message":"The maximum number of time events for a user in a request should not be greater than 200.","errors":["Request Validation Error"]} 

Environment

SAP SuccessFactors Time Tracking - Clock In Clock Out

Reproducing the Issue

  1. You are doing batch import of Time data from an external system via the REST API "Time Events".
  2. For a single employee you have sent more than 200 time events in a single batch. 

Cause

The number of time events that can be sent for a single user is limited to 200.

Resolution

  • Use case 1
    Specifically, you are exporting time data for 1 employee who has more than 200 time events into a single file/single batch request.
    SAP Recommendation:
    Batch the data into 200 records in single file/single batch 
  • Use case 2
    Mass exporting the time events for re-conciliation or data migration use case
    SAP Recommendation:
    Sort the employee time export data on the "timestamp" field to avoid this issue. You can keep the batch size to 1000 when you have already sorted the time data for employees.  

See Also

3216279 - REST API for Sending Time Events from Terminal to Clock In Clock Out

REST API for Sending Time Events from Terminal to Clock In Clock Out

Keywords

Clock in Clock out, CICO, terminal, terminal integration, rest api, Time Tracking, punch, events, limit, batch, BAD_REQUEST, 200, 1000 , KBA , LOD-SF-TTR-CIO , Clock In/ Clock Out , Problem

Product

SAP SuccessFactors HCM suite all versions ; SAP SuccessFactors Time Tracking all versions