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.
Today the shipping coordinator learns about a late delivery when the carrier's pickup passes, and customer service learns about it when the customer calls. The recovery is agreed by phone and the new date lives in an email.
The app watches every open delivery against its planned goods issue date, the transit days of its route and the requested date on the sales order line. A delivery whose goods issue has passed, or whose arrival falls after the requested date, opens a case with the cause read from the ERP: pick open, stock short at the plant, production finishing late or carrier pickup missed. The shipping coordinator chooses an option with its cost and new arrival date, customer service sends the customer the new date and records the answer on the order line, and the app changes the delivery in the ERP.
| Lane | Does |
|---|---|
| Shipping coordinator | reviews the delivery at risk, sees the cause, chooses the option |
| Customer service | informs the customer, records the confirmation or the escalation |
| Carrier | confirms an express pickup on the portal screen with the time and the cost |
| Logistics lead | approves express cost above the band and sourcing from another plant |
Every screen renders for desktop and mobile; portal screens are the same screens delivered to an outside login.
| Screen | What is on it |
|---|---|
| S01 Deliveries at risk | grid of deliveries with customer, requested date, planned goods issue, expected arrival, days at risk, value and cause; filter by plant, customer and carrier; open button |
| S02 Delivery detail | order lines, picked and packed quantities, stock at the plant and at alternate plants, production order finish, route and transit days, carrier status; cause flags |
| S03 Recovery options | expedite with express carrier and cost, split into a partial delivery, source from another plant, new date; new arrival date and cost per option; choose and approve |
| S04 Customer message | message with the new date from a template, customer contact, confirmation received or escalation; note written to the order line |
| S05 Carrier portal | portal screen for the carrier: express pickup request with time, pallets and cost; confirm or propose another time |
| S06 Board | deliveries on time in full by week, exceptions by cause, express cost per month, customer confirmations pending |
The first object is the main one; each system page shows the real table or resource behind every handler.
| Object | Why the app reads it | See it on |
|---|---|---|
| Delivery | open deliveries: planned and actual goods issue, route, carrier, quantity | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Sales order line | the order lines behind the delivery: requested date, confirmed quantity, customer, value | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Stock position | available quantity at the shipping plant and at alternate plants | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Production order | production orders feeding the delivery: finish date and confirmed quantity | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Customer master | the account: contact, priority class, terms | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Object | What changes |
|---|---|
| Delivery | planned goods issue, route or carrier changed; delivery split into a partial delivery through the delivery change interface |
| Sales order line | confirmed date and the customer's confirmation written as a note on the order line |
Start: 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.
# start criterion, in canonical fields; each system page shows it in that system's fields
{delivery.actual_gi} = '' and ({delivery.planned_gi} < today or {delivery.planned_gi} + route_days({delivery.route}) > {so.requested_date})| Step | Moves when |
|---|---|
| Risk detected | case opened for the shipping coordinator of the plant; ranked by days at risk and order value |
| Cause identified | pick status, stock, production finish and carrier status read; cause set on the case |
| Option chosen | coordinator picks an option; express cost above 2,000, or sourcing from another plant, goes to the logistics lead |
| Customer informed | customer service sends the new date; the customer confirms or escalates within 1 working day |
| Delivery updated | delivery changed in the ERP; note on the order line; case closed when actual goods issue is posted |
| Component | Trigger → action → outcome |
|---|---|
| grd_risk | on load → read open deliveries against planned goods issue, route transit days and the requested date → rank by days at risk and order value, show the cause |
| dd_option | on change → compute the new arrival date and the cost for the chosen option → require the logistics lead's approval above 2,000 |
| btn_split | on click → call the delivery change interface to split the delivery by available quantity → create the partial delivery, refresh S02 |
| btn_inform | on click → send the customer message with the new date → store the customer's answer on the order line, close the case when actual goods issue is posted |
| Step | Time limit and escalation |
|---|---|
| Option decision | 4 working hours from detection, then the logistics lead is reminded |
| Customer confirmation | 1 working day, then the customer service lead is copied |
| Express approval | 2 working hours, then the case is flagged on the board |
Names, places and figures are illustrative; the pattern is the catalogue's.
At 07:50 the app listed 17 deliveries at risk for the Antwerp plant, 4 of them for a retailer with a Friday delivery slot. Sofie, the shipping coordinator, saw that 2 waited on a pick and 2 on stock arriving on Thursday; she split the 2 short deliveries and booked an express pickup for the rest at 08:30, which the carrier confirmed on the portal at 08:45. Customer service sent the new dates by 09:15 and the retailer confirmed at 10:02. The board showed the logistics lead the express cost of 1,400 against an order value of 86,000, and 96 percent on time in full for the week.
The objects with their real names, the criteria in that system's fields, the write interface and what to set up first.
Delivery read from LIKP · LIPS; also on SAP ECC.
Open the S/4HANA page →Delivery read from Shipping REST: shipmentLines · shipments; also on Oracle E-Business Suite.
Open the Oracle Fusion page →Delivery read from CONFORMED.DELIVERY; lakehouse.
Open the Snowflake page →Delivery read from silver.delivery; lakehouse.
Open the Databricks page →Other systems connect through the same handlers; see how SmartApps connect.
About 30 minutes to a first running screen on your live rows, and 5 working days to the production-grade version described here, most of it spent agreeing screens and criteria with the process owner.
Any of SAP S/4HANA, Oracle Fusion Cloud, Snowflake, Databricks, with the objects read in place; the pages above show the objects and the write path for each. Two systems at once is one handler per object per system.
Roles on portal screens see only the rows the access policy allows, and their steps are logged like everyone else's.
Every step, value, decision, notification and write-back acknowledgement of every instance, with the version of the app, append-only.
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.