Symptom
When you are trying to update the field loaActualReturnDate of the Employee Time entity/portlet to any future date using SuccessFactors OData API or Employee central imports, you are receiving the following warning/error message:
Actual return date must be one day later than end date. with the index 0
Environment
-
SuccessFactors HCM suite
- OData API
- SuccessFactors Employee Central
- Time off
Reproducing the Issue
Run your OData upsert or import the data using EC imports
Cause
When you update one Leave of absence (LOA), you need to pass the field End Date and also Actual Return Date (loaActualReturnDate) together in the payload.
Resolution
While doing this activity in the SucccessFactors user interface, the system will fill out the field "End Date" with day -1 considering the value that you are passing in the field "Actual Return Date".
To avoid the issue described in this KBA, please always pass both fields together ("Actual Return Date" and "End Date" with day -1) in the payload while upserting the entity EmployeeTime.
Keywords
SuccessFactors OData API, End Date, Expected Return Date, loaActualReturnDate, Employee time, Employeetime, LOA, Actual return date must be one day later than end date. with the index 0, EC imports, Employee Central Time off, error / warning message , KBA , LOD-SF-INT-ODATA , OData API Framework , LOD-SF-EC , Employee Central , LOD-SF-INT , Integrations , LOD-SF-EC-TIM , Time Off , How To