Logistics and warehouse on S/4HANA

Shipment exception and on-time recovery on SAP S/4HANA

Finds deliveries that will miss the customer's requested date, shows the cause, offers expedite, split or a new date, and records the customer's confirmation on the order.

SCREENSDATA HANDLERSS/4HANA · READ IN PLACES01 Deliveries at riskS02 Delivery detailS03 Recovery optionsS04 Customer messageS05 Carrier portalS06 Boarddh_deliveryDeliveryLIKP · LIPSdh_sales_order_lineSales order lineVBAK · VBAP · VBEPdh_stock_positionStock positionMARD · MCHB · MATDOC_EXTRACTdh_production_orderProduction orderAFKO · AFPO · AFVCdh_customer_masterCustomer masterKNA1 · KNB1 · KNVVWRITE BACK TO S/4HANADelivery → BAPI_OUTB_DELIVERY_CHANGE · BAPI_OUTB_DELIVERY_CONFIRM_DECSales order line → BAPI_SALESORDER_CHANGE · BAPI_SALESORDER_CREATEFROMDAT2rows stay in S/4HANA · access rules applied at read time · each write acknowledged and logged
The screens of the app, the data handler behind each, and the S/4HANA object it reads in place. Writes below the line go through released interfaces with an acknowledgement.
5
objects read in place from S/4HANA
catalogue
6
screens on those rows
catalogue
5 days
to production-grade
estimate
2
objects written back
catalogue
0
rows copied to build it
product
What the app reads

The S/4HANA objects behind each handler

Tables are read in place through the SAP connector, using released read interfaces; changed rows arrive through change capture where the basis team allows it. The rows stay in SAP.

ObjectRead fromFields the app usesFreshness
DeliveryLIKP · LIPSLIKP.ROUTE (route) · LIKP.WADAT (planned gi) · LIKP.WADAT_IST (actual gi) · LIKP.VBELN (number)live; change capture where enabled
Sales order lineVBAK · VBAP · VBEPVBEP.EDATU (requested date) · VBAK.VBELN (number) · VBAP.POSNR (line) · VBAK.KUNNR (customer)live; change capture where enabled
Stock positionMARD · MCHB · MATDOC_EXTRACTMARD.MATNR (material) · MARD.WERKS (plant) · MARD.LGORT (sloc) · MARD.LABST (on hand)live; change capture where enabled
Production orderAFKO · AFPO · AFVCAFKO.AUFNR (number) · AFPO.MATNR (material) · AFPO.PSMNG (qty) · AFKO.GSTRP (start)live; change capture where enabled
Customer masterKNA1 · KNB1 · KNVVKNA1.KUNNR (id) · KNA1.NAME1 (name) · KNA1.LAND1 (country) · KNVV.VKORG (sales org)live; change capture where enabled
The trigger

The start criterion in S/4HANA's own fields

In plain words: An open delivery whose planned goods issue date has passed with actual goods issue empty, or whose planned goods issue plus the transit days of the route falls after the requested date on the order line.

The criterion runs in S/4HANA through the data handler, so only the matching rows return. The editor shows the rows it selects, and their count, as it is written.

# start criterion in S/4HANA fields
LIKP.WADAT_IST = '' and (LIKP.WADAT < today or LIKP.WADAT + route_days(LIKP.ROUTE) > VBEP.EDATU)

# the same criterion in canonical fields
{delivery.actual_gi} = '' and ({delivery.planned_gi} < today or {delivery.planned_gi} + route_days({delivery.route}) > {so.requested_date})
What the app writes back

Through released interfaces

Writes go through released BAPIs and IDocs. Each call returns a document number or an error message, and the app records both beside the decision.

ObjectWhat changesInterface
Deliveryplanned goods issue, route or carrier changed; delivery split into a partial delivery through the delivery change interfaceBAPI_OUTB_DELIVERY_CHANGE · BAPI_OUTB_DELIVERY_CONFIRM_DEC
Sales order lineconfirmed date and the customer's confirmation written as a note on the order lineBAPI_SALESORDER_CHANGE · BAPI_SALESORDER_CREATEFROMDAT2
Acknowledged and logged

Each write stores the identifier S/4HANA returns beside the decision, the person and the time, so the log answers who changed what, and the reconciliation shows it arrived.

Access and prerequisites

What is in place before the first build

SAP roles are mapped to Lima access policies once. A buyer who sees purchasing organisation 1000 in SAP sees the same rows in the app.

  • An SAP user for the connector with read authorisation on the objects the app uses
  • The BAPIs the app writes with, enabled for that user
  • Network path to the application server (PrivateLink or VPN)
  • Change capture switched on for the objects that should refresh within minutes
Register the handlers5 objects from the catalog; each shows its rows at once.
Also on SAP ECC

The same app on SAP ECC

On SAP ECC the same objects live in the classic tables named beside each row; MATDOC becomes MKPF and MSEG, ACDOCA becomes BKPF and BSEG. The BAPIs are the same.

ObjectOn S/4HANAOn SAP ECC
DeliveryLIKP · LIPSsame tables
Sales order lineVBAK · VBAP · VBEPsame tables
Stock positionMARD · MCHB · MATDOC_EXTRACTMARD · MCHB · MBEW
Production orderAFKO · AFPO · AFVCsame tables
Customer masterKNA1 · KNB1 · KNVVsame tables
Nearby

This app on other systems, and other apps on S/4HANA

Shipment exception and on-time recovery on

Other apps on S/4HANA

Terms on this page

On time in fullA delivery that arrives on the customer's requested date with the full quantity; the board counts the share of deliveries that meet both.
Goods issueThe posting that records goods leaving the warehouse; the planned goods issue date is when it should happen.
Read in placeThe rows stay in S/4HANA; the handler sends the filter and the columns and S/4HANA returns the matching rows.
Questions

Does this app copy data out of S/4HANA?

The screens read through handlers that leave the rows in S/4HANA. History the app needs at scale is landed in the lake by the Backbone, which is the exception by design.

What does S/4HANA need to allow?

The prerequisites above: an integration identity with read rights on the objects listed and write rights on the interfaces named, connectivity, and the scopes agreed with the process owner.

Can I run it on SAP ECC as well?

Yes. The screens, criteria and roles stay; the handlers are re-bound to the other system's objects, listed above.

See this app on your data

Bring the process and the systems it touches. In the first session we register the data handlers, draw the levels or the lanes and run the first screen on your live rows.