3616157 - Recalculation cannot correct the logical date according to the new planned working time.

It is noticed recalculation will not reassign the time recording to the new logical date after planned working time has been changed via change of Work Schedule or Temporary Time Information. 

Let me explain with a sample CICO employee who records time punches too. 

The employee was originally assigned with a cross-midnight planned working time of 22:00 - 05:00(+1).
If the employee clocks in and out at 01:38 and 02:38 on Jun 3, the generated time recording is correctly assigned to logical date of Jun 2, because the period falls within Jun 2's planned working time.

Then the planned working time is changed to a non-cross-midnight one of 08:00 - 17:00, either via Work Schedule change or Temporary Time Information assignment. 
With this new planned working time, the 01:38 - 02:38 on Jun 3 should belong to Jun 3 because there is no longer planned cross-midnight. 
However, even after triggering recalculation, the generated time recording still belongs to Jun 2, while we expect it to be moved to Jun 3 based on the new planned working time.

Similar situation may also happen with imported external time data, and even manually recorded entries.

SAP SuccessFactors Time Tracking

CICO, time event, punch, clock, times, in, out, external, data, import, logic, logical, date, +1, next, tti, temporary, information, info, workschedule, work, schedule, planned, working, plan, original, overwrite, override, recalculation, recalculate, event, management, sheet, trigger, next , KBA , LOD-SF-TTR , Time Tracking , LOD-SF-TTR-CIO , Clock In/ Clock Out , LOD-SF-TTR-TMS , Time Sheet , Product Enhancement