SAP Knowledge Base Article - Public

3810634 - Delivery Date Reduced by One Day When Creating Inbound Deliveries via API_INBOUND_DELIVERY_SRV (SAP S/4HANA Cloud Public Edition)

Symptom

When creating an inbound delivery using API_INBOUND_DELIVERY_SRV, the DeliveryDate sent in the request differs from the Delivery Date displayed in the inbound delivery.

Example:

  • Request DeliveryDate: 2026-09-20
  • Delivery Date displayed in SAP S/4HANA Cloud: 2026-09-19
  • Delivery Time displayed: 17:00
  • Receiving location time zone: PST

The integration may use SAP Integration Suite to transform the source date into yyyy-mm-dd format. The target payload contains the expected DeliveryDate, but the resulting inbound delivery shows the previous calendar day.

Environment

SAP S/4HANA Cloud Public Edition

Reproducing the Issue

  1. Create an inbound delivery using API_INBOUND_DELIVERY_SRV in SAP S/4HANA Cloud Public Edition.
  2. In the request payload, provide a DeliveryDate without explicitly providing DeliveryTime. For example:
    • DeliveryDate: 2026-09-20
  3. Use a receiving plant/location with a local time zone behind UTC, for example PST.
  4. Execute the API request and open the created inbound delivery in the corresponding app.
  5. Compare the Delivery Date sent in the API request with the Delivery Date displayed in the inbound delivery. The displayed date may be one day earlier, for example:
    • API request: 20.09.2026
    • Displayed Delivery Date: 19.09.2026
    • Displayed Delivery Time: 17:00 PST

The API response may still show DeliveryDate as 2026-09-20T00:00:00.000 while the application displays the corresponding local date and time.

Cause

The behavior can occur due to UTC/local time conversion.

Date and time field pairs used by API_INBOUND_DELIVERY_SRV are handled in UTC, while the inbound delivery application displays the corresponding local time.

When DeliveryDate is provided without an explicit DeliveryTime, the resulting date/time can correspond to midnight UTC. Depending on the time zone of the receiving location, conversion to local time may result in the previous calendar day.

For example:

20.09.2026 00:00 UTC -> 19.09.2026 17:00 PST.

The receiving location time zone can be reflected in LIKP-TZONRC and is derived from the relevant location configuration.

Resolution

When a specific local delivery date/time is required, provide the appropriate DeliveryDate and DeliveryTime values in UTC, taking the receiving location time zone into account.

The UTC value should be determined based on the receiving location time zone and the relevant delivery date.

Review KBA 3350306, "Incorrect Delivery Date from Standard API: API_OUTBOUND_DELIVERY_SRV/API_INBOUND_DELIVERY_SRV".

See Also

KBA 3350306 - "Incorrect Delivery Date from Standard API: API_OUTBOUND_DELIVERY_SRV/API_INBOUND_DELIVERY_SRV".

Keywords

API_INBOUND_DELIVERY_SRV, inbound delivery, delivery date offset, date reduced by one day, UTC conversion, time zone, DeliveryDate, DeliveryTime, receiving location time zone, integration mapping, date shift, S/4HANA Cloud, delivery management API, timezone conversion, LIKP-LFDAT , KBA , LE-SHP-DL-2CL , Delivery Processing (Public Cloud) , How To

Product

SAP S/4HANA Cloud Public Edition all versions