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.
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.
| Object | Read from | Fields the app uses | Freshness |
|---|---|---|---|
| Delivery | LIKP · LIPS | LIKP.ROUTE (route) · LIKP.WADAT (planned gi) · LIKP.WADAT_IST (actual gi) · LIKP.VBELN (number) | live; change capture where enabled |
| Sales order line | VBAK · VBAP · VBEP | VBEP.EDATU (requested date) · VBAK.VBELN (number) · VBAP.POSNR (line) · VBAK.KUNNR (customer) | live; change capture where enabled |
| Stock position | MARD · MCHB · MATDOC_EXTRACT | MARD.MATNR (material) · MARD.WERKS (plant) · MARD.LGORT (sloc) · MARD.LABST (on hand) | live; change capture where enabled |
| Production order | AFKO · AFPO · AFVC | AFKO.AUFNR (number) · AFPO.MATNR (material) · AFPO.PSMNG (qty) · AFKO.GSTRP (start) | live; change capture where enabled |
| Customer master | KNA1 · KNB1 · KNVV | KNA1.KUNNR (id) · KNA1.NAME1 (name) · KNA1.LAND1 (country) · KNVV.VKORG (sales org) | live; change capture where enabled |
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})
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.
| Object | What changes | Interface |
|---|---|---|
| Delivery | planned goods issue, route or carrier changed; delivery split into a partial delivery through the delivery change interface | BAPI_OUTB_DELIVERY_CHANGE · BAPI_OUTB_DELIVERY_CONFIRM_DEC |
| Sales order line | confirmed date and the customer's confirmation written as a note on the order line | BAPI_SALESORDER_CHANGE · BAPI_SALESORDER_CREATEFROMDAT2 |
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.
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.
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.
| Object | On S/4HANA | On SAP ECC |
|---|---|---|
| Delivery | LIKP · LIPS | same tables |
| Sales order line | VBAK · VBAP · VBEP | same tables |
| Stock position | MARD · MCHB · MATDOC_EXTRACT | MARD · MCHB · MBEW |
| Production order | AFKO · AFPO · AFVC | same tables |
| Customer master | KNA1 · KNB1 · KNVV | same tables |
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.
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.
Yes. The screens, criteria and roles stay; the handlers are re-bound to the other system's objects, listed above.
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.