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.
Read more...
Environment
SAP SuccessFactors Time Tracking
Product
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, day, light, saving , KBA , LOD-SF-TTR-CIO , Clock In/ Clock Out , LOD-SF-TTR , Time Tracking , LOD-SF-TTR-TMS , Time Sheet , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview