SAP Knowledge Base Article - Public

3719735 - Time Zone Semantics of Scheduling Fields in API_PRODUCTION_ORDER_2_SRV

Symptom

When retrieving scheduling data via API_PRODUCTION_ORDER_2_SRV, the date and time values may raise questions regarding their time zone reference.

The scheduling time displayed in SAP Fiori applications and the values exposed by the API represent the same maintained scheduling data.

Environment

SAP S/4HANA Cloud Public Edition

Cause

The scheduling date and time values exposed by API_PRODUCTION_ORDER_2_SRV are provided according to the plant time zone.

The API:

  • Does not perform automatic conversion of scheduling data to UTC.
  • Does not normalize scheduling values to another time zone before exposure.
  • Returns the stored scheduling values as maintained in the system.

The values displayed in SAP applications and the values exposed by the API are aligned and both reflect the plant time zone.

This behavior is consistent with the intended system design.

Resolution

This behavior is correct by design.

Scheduling values are stored and exposed according to the plant time zone configuration. No automatic time zone transformation is applied during OData exposure.

If a different time zone representation is required, the conversion must be handled explicitly outside the scope of the API.

See Also

Keywords

time zone, UTC, CET, SAP API, integration suite, MES system, time shift, timestamp conversion, daylight saving time, manufacturing processes, production order, incorrect time handling, local time zone, middleware , KBA , PP-SFC-ES-2CL , Enterprise Services in Shop Floor Control (Public Cloud) , Problem

Product

SAP S/4HANA Cloud Public Edition all versions