App catalogue Logistics and warehouse

Shipment exception and on-time recovery

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 HANDLERSSOURCE OBJECTS, READ IN PLACES01 Deliveries at riskscreenS02 Delivery detailscreenS03 Recovery optionsscreenS04 Customer messagescreenS05 Carrier portalscreendh_deliveryDeliverydh_soSales order linedh_stockStock positiondh_prod_orderProduction orderdh_customerCustomer masterS/4HANALIKP · LIPSS/4HANAVBAK · VBAP · VBEPS/4HANAMARD · MCHB · MATDOC_EXTRACTS/4HANAAFKO · AFPO · AFVCS/4HANAKNA1 · KNB1 · KNVVrows stay in the source · access rules apply at read time · writes go through the source's released interface and are confirmed
The screens, the data handlers behind them and the objects each handler reads in place on S/4HANA. Other systems have their own page.
5 days
of configuration to a production-grade version
estimate
6
screens, desktop and mobile
catalogue
5
data handlers, read in place
catalogue
4
systems with a page for this app
catalogue
3
clocks with escalation
catalogue
What it does

Today, and with the app

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.

Who takes part

Data-driven app: starts from the records a criterion selects; each record launches its own flow

LaneDoes
Shipping coordinatorreviews the delivery at risk, sees the cause, chooses the option
Customer serviceinforms the customer, records the confirmation or the escalation
Carrierconfirms an express pickup on the portal screen with the time and the cost
Logistics leadapproves express cost above the band and sourcing from another plant
Screens

6 screens, composed from the handlers

Every screen renders for desktop and mobile; portal screens are the same screens delivered to an outside login.

ScreenWhat is on it
S01 Deliveries at riskgrid 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 detailorder 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 optionsexpedite 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 messagemessage with the new date from a template, customer contact, confirmation received or escalation; note written to the order line
S05 Carrier portalportal screen for the carrier: express pickup request with time, pallets and cost; confirm or propose another time
S06 Boarddeliveries on time in full by week, exceptions by cause, express cost per month, customer confirmations pending
Data handlers

5 objects, read where they live

The first object is the main one; each system page shows the real table or resource behind every handler.

ObjectWhy the app reads itSee it on
Deliveryopen deliveries: planned and actual goods issue, route, carrier, quantityS/4HANA · Oracle Fusion · Snowflake · Databricks
Sales order linethe order lines behind the delivery: requested date, confirmed quantity, customer, valueS/4HANA · Oracle Fusion · Snowflake · Databricks
Stock positionavailable quantity at the shipping plant and at alternate plantsS/4HANA · Oracle Fusion · Snowflake · Databricks
Production orderproduction orders feeding the delivery: finish date and confirmed quantityS/4HANA · Oracle Fusion · Snowflake · Databricks
Customer masterthe account: contact, priority class, termsS/4HANA · Oracle Fusion · Snowflake · Databricks

Written back

ObjectWhat changes
Deliveryplanned goods issue, route or carrier changed; delivery split into a partial delivery through the delivery change interface
Sales order lineconfirmed date and the customer's confirmation written as a note on the order line
The flow

From the trigger to the last write

THE FLOW · SHIPMENT EXCEPTION AND ON-TIME RECOVERY1Risk detectedcase opened for theshipping coordinator of theplant; ranked by days atrisk and order value2Cause identifiedpick status, stock,production finish andcarrier status read; causeset on the case3Option chosencoordinator picks anoption; express cost above2,000, or sourcing fromanother plant, goes to thelogistics lead4Customer informedcustomer service sends thenew date; the customerconfirms or escalateswithin 1 working day5Delivery updateddelivery changed in theERP; note on the orderline; case closed whenactual goods issue isposted
Each step and the criterion that moves it.

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})

StepMoves when
Risk detectedcase opened for the shipping coordinator of the plant; ranked by days at risk and order value
Cause identifiedpick status, stock, production finish and carrier status read; cause set on the case
Option chosencoordinator picks an option; express cost above 2,000, or sourcing from another plant, goes to the logistics lead
Customer informedcustomer service sends the new date; the customer confirms or escalates within 1 working day
Delivery updateddelivery changed in the ERP; note on the order line; case closed when actual goods issue is posted
Actions, clocks and measures

What the components do, what the clocks enforce, what the board shows

ComponentTrigger → action → outcome
grd_riskon 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_optionon change → compute the new arrival date and the cost for the chosen option → require the logistics lead's approval above 2,000
btn_spliton click → call the delivery change interface to split the delivery by available quantity → create the partial delivery, refresh S02
btn_informon 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

Clocks

StepTime limit and escalation
Option decision4 working hours from detection, then the logistics lead is reminded
Customer confirmation1 working day, then the customer service lead is copied
Express approval2 working hours, then the case is flagged on the board

Measures

deliveries on time in full by weekexceptions recovered before the requested dateexpress cost per monthcustomer confirmations within 1 dayexceptions by cause
A day with the app

Illustrative

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.

illustrative scenario · Shipment exception and on-time recovery
On your systems

One page per system

The objects with their real names, the criteria in that system's fields, the write interface and what to set up first.

Other systems connect through the same handlers; see how SmartApps connect.

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.
RouteThe shipping path from the plant to the customer and the transit days it takes.
Questions

How long does it take to have this running?

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.

Which system does it run on?

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.

Who takes part from outside the company?

Roles on portal screens see only the rows the access policy allows, and their steps are logged like everyone else's.

What does the audit record hold?

Every step, value, decision, notification and write-back acknowledgement of every instance, with the version of the app, append-only.

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.