Symptom
Clock In Clock Out is used, and it is noticed that for cross-midnight clock time events that cross the date when day-light savings time starts or ends, the duration of the paired time events does not consider the change of day-light savings. There is 1 hour difference.
For example,
The employee clocks in before start date of day-light savings at 10:00PM, and clocks out after start date of day-light savings at 02:00AM, the generated duration should be 3 hours. But 4 hours is generated.
The employee clocks in before end date of day-light savings at 10:00PM, and clocks out after end date of day-light savings at 02:00AM, the generated duration should be 5 hours. But 4 hours is generated.
Environment
SAP SuccessFactors Time Tracking
Cause
This is a known limitation, and due to the complexity of this situation, the support on day-light savings with Clock In Clock Out will still take time to come. But it is in our roadmap.
Resolution
Before day-light savings is fully supported, please consider the following workaround to adjust the 1 hour difference for cross-midnight clock times overlapping with the start or end of day-light savings time change.
- Export the External Time Data generated from the paired cross-midnight clock time events that covers the change date of day-light savings.
- Adjust the start or end time of the External Time Data to add or deduct the 1 hour.
- Import the External Time Data back to the system.
Or you can also manually change the start or end time on this particular External Time Data to adjust the 1 hour from Manage Data.
See Also
Keywords
daylight, day-light, summer, winter, time, savings, offset, clock, in, out, external, data, externaltimedata, ETD, CICO, punch, manage, Sunday, October, March, change, shift, switch, tms, ttr, ui , KBA , LOD-SF-TTR-CIO , Clock In/ Clock Out , LOD-SF-TTR , Time Tracking , LOD-SF-TTR-TMS , Time Sheet , Problem