3382858 - Hour Field Is Showing UTC Time, Not UTC -6:00 (or Another Time Zone)

Extension fields are showing UTC time instead of UTC -6:00 (or other time zone), for example.

• SAP Cloud for Customer
• SAP Business ByDesign
  
  

1. Go to the work center affected;
2. Check the hour field;
Result: Is appearing in the UTC time zone, not the desire time zone.

There is a logical reason why separate date and time fields are handled differently than a combined datetime field.

Separate Date and Time fields can be used for different purposes in different documents.

For example, there could be just a Date field without time, which denotes the start date of something.

There could also be scenarios where just a Time without Date is required in a document, in order to specify at what time something happens.

Not in every scenario, a Date field occurs tightly coupled with a Time field. But it is logically impossible to convert a single time without date into any other time zone, also it is logically impossible to convert a single date without any time into any other time zone.

Only complete datetime timestamps can be converted, because only then it is uniquely defined if the corresponding timestamp currently observes daylight saving or not in the requested time zone.

DateTime fields are stored with time zone UTC in the backend and are converted to the time zone of the login user, when displayed on UI.

This is not the case for Date fields or Time fields. They remain in UTC.

This is the current standard system behavior.

2409024 - How to Use the Local Time Zone of Your Company in an Extension Field
2425640 - Difference between Workflow Rule Time and Execution Time
2455759 - "Payment Approved Date" filed is updated based upon UTC time zone if triggerred by a workflow rule.

DateTime; UTC; time zone , KBA , AP-RC-UIF-FLX , Page Layout & Key User Configuration , Problem