3782670 - Retrieving Employee Time latest record in Integration Center or OData API

Employee Time is not an effective-dated entity/object in the same way as entities such as Job Information:    

• Effective-dated behavior (e.g. Job Information): 
  The current record typically has an End Date of 9999-12-31. This allows Integration Center and the OData API to easily distinguish between historical, current, and future records.
  
  
• Non effective-dated behavior (e.g. Biological information):
  Although Employee Time contains Start Date and End Date fields, the End Date always contains the actual end of the absence period (not 9999-12-31).
  Because of this design, an employee can have multiple absence records for different periods, all valid at the same time from a data perspective.

In addition, there is no other field that can be used to uniquely identify the "latest" absence record to be used as filter, something like "Is_Last_Record=true".

SAP SuccessFactors HCM Suite

Within Integration Center:

Records can only be sorted using available fields, such as Start Date, to control the order in which records are returned. However, sorting alone does not provide a reliable way to identify a single "latest" absence record in all scenarios.

Another option is to use the Modified Since filter to retrieve recently changed Employee Time records. However, this approach is based on modification activity rather than the absence period itself. As a result, if an older absence record is updated, it will also be included in the results.

Within SAP Cloud Integration (CPI):

If your requirement is to consistently identify and retain only the latest absence record, a more advanced integration tool may be required. 

For example, SAP Cloud Integration (CPI) allows you to extract all absence records then apply custom logic to isolate the record with the greatest End Date (latest record).

KBA , LOD-SF-INT-INC-ODATA , ODATA API In Integration Center , LOD-SF-INT-EC , Employee Central SFAPI & OData Entities , Problem