SAP Knowledge Base Article - Public

3101935 - SAP SuccessFactors is moving to Coordinated Universal Time (UTC) - Table Report/Canvas/Tiles/Report Story

Symptom

SAP SuccessFactors is standardizing the use of time across all our systems (applications, databases, and servers) across all our data centers in our continuous effort to align with the cloud industry's best practices for improved data integrity, security and scalability. SAP SuccessFactors is moving its platform to Coordinated Universal Time (UTC).

SAP SuccessFactors offers global services and currently supports multiple time zones. We must have a consistent, reliable time zone across all geographies to ensure that applications behave the same regardless of physical location. UTC is a natural choice given our global customer base, and UTC is not subject to Daylight Saving Time.

The impact that will be seen is that a new version of some date fields (columns) for Table, Tile, Canvas, and Story reports are available, suffixed with either (Timestamp) or (Date).

To identify these fields, there will be a suffix in the new fields that indicates that the fields are resilient to time zone changes. The fields suffixed with (Timestamp) display a transaction date as per the tenant preferred time zone (or as per the logged-in user's time zone), whereas the fields suffixed with (Date) are independent of time zone and always display the same values. To know more about tenant preferred time zone, refer to the Tenant Preferred Time Zone Available in the Admin Center topic. To see the list of new fields, refer to the articles in the resolution section.

"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 HXM Suite

Resolution

The platform time will be changed to UTC, first on your non-Production environment, followed by the Production environment. All customers will receive a 60 days notice prior to the change happening on each DC.

The confirmed dates are currently scheduled as per the table below: 

Data Center

Region

Environment

Date and Time

DC30 (Shanghai)

APJ

Preview

Friday, 4th Aug 2023, 3pm UTC – 10pm UTC

DC30 (Shanghai)

APJ

Production

Friday, 15th Sep 2023, 3pm UTC – 10pm UTC

DC70 (Virginia)

AMER

Preview

Friday 10th May, 4 am – 11 am UTC

DC70 (Virginia)

AMER

Production

Saturday 22nd June, 4 am – 11 am UTC

DC68 (Virginia)

AMER

Preview

Monday 29th July, 4am UTC – 11am UTC

DC68 (Virginia)

AMER

Production

Saturday 21st Sep, 4am UTC – 11am UTC

DC57 (Amsterdam)

EMEA

Preview

Monday, 22nd July 2pm UTC - 9pm UTC

DC57 (Amsterdam)

EMEA

Production

Friday, 30th Aug 10pm UTC - Saturday 31st Aug 5am UTC

DC33 (Frankfurt)

EMEA

Preview

Not applicable 

DC33 (Frankfurt)

EMEA

Production

Friday 6th Sep 10pm UTC - Saturday 7th Sep 5am UTC

DC66 (Sydney)

APJ

Preview

Monday 12th Aug 10am UTC - 5pm UTC

DC66 (Sydney)

APJ

Production

Friday 13th Sep 3pm UTC - 10pm UTC

DC40 (Virginia)

AMER

Preview

Not applicable

DC40 (Virginia)

AMER

Production

TBD

Planning for this change, with the 2H 2021 release we have introduced the Tenant Preferred Time Zone field to mitigate the impact of the UTC migration.

Changes in the different reporting models (i.e.meta data changes) are done to meet the expected behavior of time zone changes and ensure UTC resilience. Typically these model changes are made available to customers as new columns which are copies of existing columns and containing the metadata change.

We highly recommend that you replace the older date columns in your Table, Tile, Canvas, and Story reports with their newer version, which are time zone resilient. Additionally, you must use only the newer version of the date fields in all your future reports as informed on the past.

See below how the fields will appear for selection:

Example on how the fields will appear on Report Table:

Example on how the field will appear on Report Story:


Please see below example of change on the extract of data on table reports:

Local Server time/TPT: CHN (UTC +8 hours)
User Preferred Timezone CHN (UTC +8 hours)

Old Column
Application Date

New Column:
Application Date (Timestamp)

Before MigrationApplication Date 22.06.2020Application Date 22.06.2020 07:02:38
After Migration (-8 hours)Application Date 21.06.2020
(change in reporting)
Application Date 22.06.2020 07:02:38
(no change in reporting)

Please see below example of change on the extract of data on Story reports:

Local Server time/TPT: CHN (UTC +8 hours)

Client Timezone CHN (UTC +8 hours)

Old Column

Application Date

New Column

Application Date (Timestamp)

Before MigrationApplication Date 22.06.2020Application Date 22.06.2020 07:02:38
After Migration (-8 hours)Application Date 21.06.2020
(change in reporting)
Application Date 22.06.2020 07:02:38
(no change in reporting)

The date fields that will change are mentioned on the KBAs below which will be available up to the release date:

KBA 3106280 for fields on Story
KBA 3106255 for fields on Table/Canvas/Tile and Dashboards

See Also

List of Fields on Stories: 3106280 - List of fields that will face UTC changes for Story reports - People Analytics
List of Fields on Legacy tools: 3106255 - List of fields that will face UTC changes for table reports/canvas on live data/tile and dashboards
Impact for WFA: 3353113 - What is the impact on WFA after moving to Coordinated Universal Time (UTC)? - WFA on Hana and SQL

Customer Community Blog - SAP SuccessFactors is moving to Coordinated Universal Time (UTC)
Customer Community Blog - New Data Fields in Reporting supporting Tenant Preferred Time Zone in 2H 2021 Release - Difference on Tenant Preferred Time zone and Localized

FAQ KBA for Integrations module - 3140223

Keywords

(Timestamp), (Date), field, change, timezone , KBA , LOD-SF-ANA , Analytics & Reporting (Ad Hoc, YouCalc, ORD) , Product Enhancement

Product

SAP SuccessFactors HCM suite all versions