SAP Knowledge Base Article - Public

2752345 - Integration Center: Using datetime range in Advanced Filters


You are using 'Advanced Filters' within the 'Filter and Sort' page of Integration Center

1. You have defined a datetime range filter:

(e.g. lastModifiedDateTime 'less than' or 'less than or equal to' AND  lastModifiedDateTime 'greater than' or 'greater than or equal to'):


2. You observe that records with a last modified value outside of the range you have defined are being selected:


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


  • SuccessFactors BizX
  • Integration Center

Reproducing the Issue

To reproduce the issue, please perform the following steps:

  1. Create an integration in Integration Center 
  2. Choose an effective-dated entity as your starting entity (e.g. EmpJob, EmpCompensation)
  3. Define a datetime range filter in the 'Advanced Filters' section of the 'Filter and Sort' page (as shown in the Symptom Section)


The cause of the incorrect datetimes being selected is due to the effective-dated starting entity:

  • Effective-dated entities are delimited by datetimes (e.g. Start Date & End Date)
  • Each Segment of the effective-dated record will have an associated Last Modified datetime value
  • If any of the Last Modified datetimes present in any effective-dated segment(s) of the record satisfies either of the above conditions in the datetime range
    • ---->  The record will be selected


  • As it is an effective-dated entity, Integration Center, will by default, return the latest / most recent effective-dated segment of the record
  • And subsequently displaying an incorrect datetime 


  • The same is true for deleted effective-dated segments of a record:
    • i.e. If a segment is deleted but the datetime is still present in the record in the database, a past-dated record can be shown


  • The same behavior will be present for any datetime values in effective-dated entities (e.g. Start Date, End Date, Last Modified On, Last Modified Date Time)
    • This behavior extends from the OData API


We can use a datetime range filter ONLY in non effective-dated entities (e.g. User):


We can see that only datetimes within the specified range are selected by the job:


For effective-dated entities, we must use the provided time-based filters provided on the 'Filter and Sort' section of Integration Center:



Integration Center, Filters, Range, Datetime, Last Modified, Start Date, End Date, Effective Dated, Time-Based Filters, Filter and Sort , KBA , LOD-SF-INT-INC , Integration Center , LOD-SF-INT , Integrations , LOD-SF-INT-ODATA , OData API Framework , Problem


SAP SuccessFactors HCM suite all versions