Symptom
You observe inconsistencies in the behavior of the DateTime Default Value: <TODAY> within Integration Center:
For example:
- When comparing this <TODAY> value to a startDate, you observe that in some cases the match is not achieved despite the two values being equal.
- However in other cases you may observe that a match is achieved when the two values being equal.
You may observe similar behaviour on <FIRSTOFMONTH> and / or <FIRSTOFYEAR> DateTime Default Values
Image/data in this KBA is from SAP internal system, sample data, or demo systems. Any resemblance to real data is purely coincidental.
Environment
- SAP SuccessFactors HXM Suite
- Integration Center
Cause
The calculation of the <TODAY> should always be the start of the day [00:00:00], but currently the underlying Java Calendar function is based on time of the day,
where between 00:00 and 12:00, the value is 00:00:00, and between 12:00 and 00:00:00, the value is 12:00:00.
This is because of usage of Calender.HOUR which uses the 12 hour format.
Resolution
Our Engineering team have began a deeper analysis of these inconsistencies & are carrying out further investigations to determine what option / alternatives are available
Currently this is planned to be fixed in 2H 2024 (internal reference: INT-18065).
Workaround:
- In terms of workaround we have observed that the correct / desired result is achieved if running the job before 12:00PM local time
Update: The fix to address these inconsistencies has been delivered in 2H Release
Keywords
KI2405, INT-18065, Integration Center, calculation, comparison, calculated, field, TODAY, FIRSTOFMONTH, FIRSTOFYEAR, equal, calendar, , KBA , LOD-SF-INT-INC-FWK , Integration Center UI Framework , LOD-SF-INT-INC , Integration Center , Problem