Runs the daily shortage meeting on live projected stock: planning, sourcing, sales and the plant allocate scarce components to orders and write the decisions to the ERP.
Today the shortage meeting starts with a planner reading a stock extract aloud, and the allocation is agreed on a whiteboard. Sales learns which customer order moved when the customer calls, and the purchase order change goes in the next day.
Each working day at 07:00 the app projects stock week by week for every component on the critical list: on hand, plus open order receipts on their confirmed dates, minus the demand from production orders and customer orders linked through the bill of materials (BOM). A component whose projected stock falls below 0 within 4 weeks goes on the day's agenda with the customer orders it affects and their value. The buyer records pull-ins, alternates and broker offers before the 09:30 room, the room allocates the available quantity to ranked customer orders, and each level signs what it owns. Production order dates, purchase order lines and customer confirmed quantities are written to the ERP before the room ends.
| Function | Level | Does |
|---|---|---|
| Planning | Level 1: material planner | projects the shortfall and proposes the allocation |
| Planning | Level 2: planning manager | chairs the room and decides allocations up to 500,000 of order value |
| Sourcing | Level 1: buyer | records pull-ins, alternates and broker offers |
| Sourcing | Level 2: category lead | approves premium buys above 25,000 |
| Sales | Level 1: order desk | ranks customer orders by commitment and margin |
| Sales | Level 2: sales director | signs a customer date move and allocations above 500,000 |
| Plant | Level 1: production scheduler | resequences production orders to the allocation |
Every screen renders for desktop and mobile; portal screens are the same screens delivered to an outside login.
| Screen | What is on it |
|---|---|
| S01 Agenda | today's short components with projected stock by week for 8 weeks, days to the first shortfall, customer value at risk; sort by value; open button |
| S02 Component room | chart of projected stock by week; open order lines with confirmed dates; production orders that need the part; customer orders they feed through the BOM; alternates on file |
| S03 Allocation | grid of customer orders ranked with confirmed date, value, margin and strategic flag; allocated quantity per order; the remainder shown as short; propose button |
| S04 Sourcing actions | pull-in request per order line, premium buy with price and quantity, alternate part with engineering approval; approve buttons |
| S05 Decision log | each allocation with who, when and value; customer date moves awaiting the sales director; write-back status per document |
| S06 Board | short components by day, customer value protected, premium spend per month, decisions open |
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 |
|---|---|---|
| Material master | the critical component list with lead times | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Stock position | on hand by plant and storage location | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Purchase order line | open supply with confirmed dates and received quantities | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Production order | production orders that consume the component | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Sales order line | customer orders and their confirmed quantities | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Bill of materials | the link from component to the finished goods on order | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Object | What changes |
|---|---|
| Production order | start and finish dates changed to the allocation |
| Purchase order line | pull-in date and quantity changed on the schedule line; premium buy added as a new line |
| Sales order line | confirmed quantity and date updated on the customer order |
Start: Each working day at 07:00 the app projects stock for every component on the critical list; a component whose projected stock falls below 0 within 4 weeks is on that day's agenda.
# start criterion, in canonical fields; each system page shows it in that system's fields
{stock.on_hand} + ({po.qty} - {po.received_qty} due within 28 days) < demand from {prod_order.qty} and {so.qty} within 28 days| Step | Moves when |
|---|---|
| Shortfall projected | component on the agenda at 07:00 with its first short week and the customer orders affected |
| Options gathered | buyer records pull-ins, alternates and broker offers by 09:00; scheduler marks which production orders can move |
| Room decides | at 09:30 the planning manager allocates the available quantity; a customer date move needs the sales director's signature |
| Sourcing approved | premium buy above 25,000 signed by the category lead within the hour |
| Written back | production order dates, purchase order lines and customer confirmations changed in the ERP; decision logged with each document number |
| Component | Trigger → action → outcome |
|---|---|
| grd_allocation | on edit → recompute the short quantity per customer order from the allocated quantities → highlight orders whose confirmed date moves |
| btn_pull_in | on click → send the pull-in request for the chosen order lines to the supplier's portal screen → start the 4-hour reply clock |
| btn_decide | on click → record the allocation with the values on screen → route date moves to the sales director and premium buys to the category lead |
| btn_write_back | on click → call the ERP interfaces for production order dates, purchase order lines and sales order confirmations → store each acknowledgement, refresh S01 |
| Step | Time limit and escalation |
|---|---|
| Supplier pull-in reply | 4 working hours, then the buyer calls and the category lead is copied |
| Sales director signature | 4 working hours, then the planning manager confirms the move as proposed and the director is informed |
| Room decision | same day; a component left undecided sits at the top of the next day's agenda |
Names, places and figures are illustrative; the pattern is the catalogue's.
At 07:00 the agenda for the Austin plant listed 6 short components, the largest a power controller with 1.4 million of customer orders in week 3. Kenji, the buyer, had a pull-in of 4,000 pieces confirmed by the supplier at 08:50 and a broker offer for 2,000 more at a 30 percent premium. At 09:30 the room allocated the confirmed pieces to 3 strategic customers, the category lead signed the broker buy at 10:05, and the sales director signed a 1-week move for 2 smaller orders at 11:00. The production orders, the purchase order and the customer confirmations were updated in the ERP before lunch, and the board showed 1.1 million protected.
The objects with their real names, the criteria in that system's fields, the write interface and what to set up first.
Material master read from MARA · MARC · MAKT; also on SAP ECC.
Open the S/4HANA page →Material master read from Product Hub REST: itemsV2; also on Oracle E-Business Suite.
Open the Oracle Fusion page →Material master read from CONFORMED.MATERIAL; lakehouse.
Open the Snowflake page →Material master read from silver.material; 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 7 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.
Every role in this app is inside the company; an outside role can be added as a lane with a portal screen.
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.