3679706 - How to avoid Time Zone conversion in Story reports

Story reports will, by default, convert timestamped date records to the time zone of the machine running the report. I.e.:

• A Start Date is stored in the database as December 10th 2:00 AM UTC+1. If you run a Story report while located in UTC-3, the record will come up as December 9th 10:00 PM.

This KBAs provides an approach to avoid this time zone conversion in Story reports.

SAP SuccessFactors HCM Suite

Create a calculated column like the following replacing the highlighted sections by the column/field you wish to apply this workaround to:

• TODATE(CONCAT(CONCAT(CONCAT(TOTEXT(DAY([TIMEMANAGEMENT#EmployeeTime#startDate] )) ,'/' ) ,CONCAT(TOTEXT(MONTH([TIMEMANAGEMENT#EmployeeTime#startDate] )) ,'/' ) ) ,TOTEXT(YEAR([TIMEMANAGEMENT#EmployeeTime#startDate] )) ),'dd/mm/yyyy' )

This will make so the initial field is deconstructed, rebuilt using DAY, MONTH and YEAR functions, which are not affected by localization, and converted back to a date field using the TODATE function.

It is important to highlight this approach will make so only the date itself is returned, which means the previous timestamp will not be included in the calculation output.

3584115 - Adjusting browser time zone to align Story Reports outputs with UI outputs

Story, wrong date, time zone, conversion, timestamp, timezone, people stories, time management, timesheet, report. , KBA , LOD-SF-ANA-SAC-QDS , Query Designer - Filter, Calculated Column, Params , How To