App catalogue Supply chain and planning

Critical component shortage room

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.

HIERARCHY · CRITICAL COMPONENT SHORTAGE ROOMPlanningL1: material plannerscreen · usersL2: planning managerscreen · usersSourcingL1: buyerscreen · usersL2: category leadscreen · usersSalesL1: order deskscreen · usersL2: sales directorscreen · usersPlantL1: production schedulerscreen · usersa person created at a level is assigned their parent-level and child-level users at the same timeTrigger and flow criteriaEach working day at 07:00 the app projects stock for every component on the critical list; a component whose p…
The hierarchy: functions, levels, and the criterion that starts the flow. Each level carries a screen and its people.
7 days
of configuration to a production-grade version
estimate
6
screens, desktop and mobile
catalogue
6
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 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.

Who takes part

Collaborative app: levels first, then screens per level, then people, then the flow and trigger criteria

FunctionLevelDoes
PlanningLevel 1: material plannerprojects the shortfall and proposes the allocation
PlanningLevel 2: planning managerchairs the room and decides allocations up to 500,000 of order value
SourcingLevel 1: buyerrecords pull-ins, alternates and broker offers
SourcingLevel 2: category leadapproves premium buys above 25,000
SalesLevel 1: order deskranks customer orders by commitment and margin
SalesLevel 2: sales directorsigns a customer date move and allocations above 500,000
PlantLevel 1: production schedulerresequences production orders to the allocation
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 Agendatoday'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 roomchart 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 Allocationgrid 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 actionspull-in request per order line, premium buy with price and quantity, alternate part with engineering approval; approve buttons
S05 Decision logeach allocation with who, when and value; customer date moves awaiting the sales director; write-back status per document
S06 Boardshort components by day, customer value protected, premium spend per month, decisions open
Data handlers

6 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
Material masterthe critical component list with lead timesS/4HANA · Oracle Fusion · Snowflake · Databricks
Stock positionon hand by plant and storage locationS/4HANA · Oracle Fusion · Snowflake · Databricks
Purchase order lineopen supply with confirmed dates and received quantitiesS/4HANA · Oracle Fusion · Snowflake · Databricks
Production orderproduction orders that consume the componentS/4HANA · Oracle Fusion · Snowflake · Databricks
Sales order linecustomer orders and their confirmed quantitiesS/4HANA · Oracle Fusion · Snowflake · Databricks
Bill of materialsthe link from component to the finished goods on orderS/4HANA · Oracle Fusion · Snowflake · Databricks

Written back

ObjectWhat changes
Production orderstart and finish dates changed to the allocation
Purchase order linepull-in date and quantity changed on the schedule line; premium buy added as a new line
Sales order lineconfirmed quantity and date updated on the customer order
The flow

From the trigger to the last write

THE FLOW · CRITICAL COMPONENT SHORTAGE ROOM1Shortfall projectedcomponent on the agenda at07:00 with its first shortweek and the customerorders affected2Options gatheredbuyer records pull-ins,alternates and brokeroffers by 09:00; schedulermarks which productionorders can move3Room decidesat 09:30 the planningmanager allocates theavailable quantity; acustomer date move needsthe sales director'ssignature4Sourcing approvedpremium buy above 25,000signed by the category leadwithin the hour5Written backproduction order dates,purchase order lines andcustomer confirmationschanged in the ERP;decision logged with eachdocument number
Each step and the criterion that moves it.

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

StepMoves when
Shortfall projectedcomponent on the agenda at 07:00 with its first short week and the customer orders affected
Options gatheredbuyer records pull-ins, alternates and broker offers by 09:00; scheduler marks which production orders can move
Room decidesat 09:30 the planning manager allocates the available quantity; a customer date move needs the sales director's signature
Sourcing approvedpremium buy above 25,000 signed by the category lead within the hour
Written backproduction order dates, purchase order lines and customer confirmations changed in the ERP; decision logged with each document number
Actions, clocks and measures

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

ComponentTrigger → action → outcome
grd_allocationon edit → recompute the short quantity per customer order from the allocated quantities → highlight orders whose confirmed date moves
btn_pull_inon click → send the pull-in request for the chosen order lines to the supplier's portal screen → start the 4-hour reply clock
btn_decideon 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_backon click → call the ERP interfaces for production order dates, purchase order lines and sales order confirmations → store each acknowledgement, refresh S01

Clocks

StepTime limit and escalation
Supplier pull-in reply4 working hours, then the buyer calls and the category lead is copied
Sales director signature4 working hours, then the planning manager confirms the move as proposed and the director is informed
Room decisionsame day; a component left undecided sits at the top of the next day's agenda

Measures

short components per daycustomer value protectedpremium spend per monthdecisions written back the same daydays from first shortfall to recovery
A day with the app

Illustrative

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.

illustrative scenario · Critical component shortage room
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

Projected stockOn hand plus receipts due minus demand, computed week by week.
AllocationThe decision of which orders receive a scarce quantity and how much each gets.
Pull-inA request to a supplier to deliver an existing order line earlier than its confirmed date.
Questions

How long does it take to have this running?

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.

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?

Every role in this app is inside the company; an outside role can be added as a lane with a portal screen.

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.