3362299 - UTC Migration impact on Performance Management (PM) & 360-MTR - SAP SuccessFactors

What is the impact of UTC Migration on SuccessFactors  Performance Management (PM) & 360-MTR forms?

Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.

SAP SuccessFactors Performance Management

• 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.
• After migration:
  • The original server time zone will be used to set the Tenant Preferred Time Zone(TPT) (For more information on TPT, refer KBA: 3319478 - Perferred Tenant Time Zone )
  • For customers already running on a server in UTC the Tenant Preferred Time Zone(TPT) will be set to UTC.

The confirmed schedule can be found in KBA 3101935

Below are list all the known areas that will have some change due to UTC Migration. In case of any deviations to the same, please contact support.

General

• After the migration, all datetime type values will be displayed as before without behavior changes (Tenant prefered timezone will be applied to keep the timezone as same as before). ​

• Added some new logical columns in SAC and Ad-hoc reports, which need customers to take actions to adopt them, the guidance will be centrally described in Reporting section.

• Session information validation job name will be displayed with timezone information, the example screenshot is followed: 

• Mass session creation job name will be displayed with timezone information, the example screenshot is followed

• Export All Sessions job name will be displayed with timezone information, the example screenshot is followed:

360-MultiRater:

• Calculate 360 benchmark to trigger s2 job, the returned job complete time will be displayed with timezone information, the example screenshot is followed:

Performance Management:

Note: There is no change in the formReviewStartDate fetched in the Odata API.These time types are floatDate, so they are not affected by UTC migration.

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

UTC, timestamp, SF, SuccessFactors,Universal,Coordinated,Performance management , KBA , LOD-SF-PM , Performance Management , LOD-SF-CAL , Calibration Module , LOD-SF-MTR , 360 Multi Rater , How To