Symptom
The time data is imported with the correct date; however, the generated time sheet entry shows a start date one day earlier than the imported date. "Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."
Environment
- SAP SuccessFactors HCM Suite
- SAP SuccessFactors Time Tracking
Reproducing the Issue
- The imported time data successfully processed with correct start date. (In the example below, the imported start date is January 3rd.)
- Navigate to the corresponding employee time sheet, where the start date displayed in the time sheet is one day earlier than the imported start date. (The start date is displayed as January 2nd.)
Cause
After the import process, the work schedule changes from a cross-midnight shift to a non-cross-midnight shift. The system does not automatically recalculate the logical dates for past timesheets when this change occurs.
Resolution
Manually reprocess the affected external time data:
- Navigate to Manage Data and search for the affected external time data.
- Change the status to "New".
- Save and refresh the page to ensure the external time data is marked as processed.
Keywords
successfactors, time management, time sheet, time tracking, CICO, time event, start date, physical start date, logical date, mismatch, employee time sheet entry, time sheet recalculation, logical date recalculation, import, external time data, new, processed, work schedule, cross-midnight, non-cross-midnight, time sheet entry discrepancy, time recording mismatch , KBA , LOD-SF-TTR-TMS , Time Sheet , LOD-SF-TTR-CIO , Clock In/ Clock Out , LOD-SF-TTR , Time Tracking , Problem
Product
Attachments
| 2.png |
SAP Knowledge Base Article - Public