2955460 - Integration Center showing effective dated information one day earlier

When you schedule a run for employees whose effective date field is on e.g. 12/14/2020 00:00:00, the employees are being shown at the run of 12/13/2020.

• SuccessFactors Integration Center
• SuccessFactors OData API

1. Build an Integration Center query based with users based on effective dated fields (e.g. termination date of employees).
2. You schedule the Integration Center job to run at 8PM UTC-4
3. Employees terminated on the next days are already being shown at the file

Integration Center displays the date time values in UTC timezone for all outbound integrations.

Let us consider an example where the server timezone is UTC-4 and the datetime value of the Start Date field is 2020-01-20 23:59:59 UTC-4. Integration Center displays the datetime as 2020-01-21T03:59:59Z, which is the value of the Start Date field in the UTC timezone.

In order to fetch the values for your current timezone, always consider the UTC-00 when building your query at Integration Center. e.g. if you have an  UTC-4 timezone, consider running/scheduling the job prior to 20:00:00.

2554717 - EC entities time based filters in Integration Center

2742107 - Integration Center: Frequently asked questions

Integration Center Handbook

Integration center picking effective dated records before UTC Timezone , KBA , LOD-SF-INT-INC , Integration Center , LOD-SF-INT , Integrations , LOD-SF-INT-ODATA , OData API Framework , How To