App catalogue Manufacturing and quality

Production schedule change

Lets a planner move firmed production orders on a live schedule, shows the effect on components and customer dates, collects the signatures and writes the new dates to the ERP.

HIERARCHY · PRODUCTION SCHEDULE CHANGEPlanningL1: production plannerscreen · usersL2: planning managerscreen · usersProductionL1: production leadscreen · usersL2: plant managerscreen · usersSalesL1: order deskscreen · usersL2: sales managerscreen · usersMaterialsL1: material plannerscreen · usersa person created at a level is assigned their parent-level and child-level users at the same timeTrigger and flow criteriaA planner or production lead starts a change on S01 for a work center and a window; a breakdown recorded on th…
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
7
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 a schedule change is agreed at the morning meeting and typed into the ERP order by order in the afternoon, and sales hears about a moved customer date from the customer. The component check happens when the picker finds the shelf empty.

A planner or production lead starts a change for a work center and a window of days, and the app shows the firmed production and planned orders in that window on a schedule you drag. Each move shows, within seconds, the components covered or short after the move from live stock, the customer orders fed by the moved order and their confirmed dates, and the work center's load from the routing's setup and run times. The production lead confirms crew and tooling, the order desk informs the customers whose dates move, and the planning manager or plant manager signs by value. The app writes the new production order and planned order dates and the customer confirmations to the ERP.

Who takes part

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

FunctionLevelDoes
PlanningLevel 1: production plannerproposes the new sequence and dates
PlanningLevel 2: planning managersigns a change that touches a customer date
ProductionLevel 1: production leadconfirms crew, tooling and setup for the new sequence
ProductionLevel 2: plant managerdecides moves above 250,000 of order value or beyond 5 days
SalesLevel 1: order deskinforms customers and updates confirmed dates
SalesLevel 2: sales managersigns a moved date on a key account order
MaterialsLevel 1: material plannerconfirms components for orders pulled forward
Screens

7 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 Change requestwork center, window of days, reason (breakdown, rush order, shortage, maintenance), orders affected picked from the live schedule; submit
S02 Schedulechart of firmed production and planned orders on the work center for 3 weeks; drag an order to a new slot; component cover and customer date effect shown per move
S03 Effectsmoved orders with old and new dates, customer orders affected with confirmed dates, components short after the move, work center load by day
S04 Production checkcrew, tooling and setup for the new sequence; confirm or comment
S05 Sales updatecustomer orders with new dates; inform-customer button; confirmed date field
S06 Approvalsummary of effects and values; approve or return; write-back button
S07 Boardchanges per week by reason, customer dates moved, orders started on time after a change
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
Production orderfirmed production orders with dates, quantities and confirmationsS/4HANA · Oracle Fusion · Snowflake · Databricks
Planned orderfirmed planned orders in the windowS/4HANA · Oracle Fusion · Snowflake · Databricks
Sales order linecustomer orders fed by the moved orders and their confirmed datesS/4HANA · Oracle Fusion · Snowflake · Databricks
Stock positioncomponent availability for orders pulled forwardS/4HANA · Oracle Fusion · Snowflake · Databricks
Routingsetup and run times per operation and work centerS/4HANA · Oracle Fusion · Snowflake · Databricks

Written back

ObjectWhat changes
Production orderstart and finish dates changed through the production order interface
Planned orderfirmed planned orders rescheduled
Sales order lineconfirmed dates updated on the affected customer orders
The flow

From the trigger to the last write

THE FLOW · PRODUCTION SCHEDULE CHANGE1Change startedorders in the windowread live with statusand confirmations;case opened for theplanner2Sequenceproposedplanner moves orderson S02; componentcover and customerdate effects shownfor each move3Productionconfirmedproduction leadconfirms crew andtooling within 4working hours4Sales informedcustomer orders witha moved date go tothe order desk; a keyaccount needs thesales manager'ssignature5Approvedplanning managersigns; the plantmanager signs movesabove 250,000 orbeyond 5 days6Written backproduction andplanned order dateschanged and customerconfirmations updatedin the ERP; caseclosed
Each step and the criterion that moves it.

Start: A planner or production lead starts a change on S01 for a work center and a window; a breakdown recorded on the floor screen starts one as well.

StepMoves when
Change startedorders in the window read live with status and confirmations; case opened for the planner
Sequence proposedplanner moves orders on S02; component cover and customer date effects shown for each move
Production confirmedproduction lead confirms crew and tooling within 4 working hours
Sales informedcustomer orders with a moved date go to the order desk; a key account needs the sales manager's signature
Approvedplanning manager signs; the plant manager signs moves above 250,000 or beyond 5 days
Written backproduction and planned order dates changed and customer confirmations updated in the ERP; case closed
Actions, clocks and measures

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

ComponentTrigger → action → outcome
cht_scheduleon drop → recompute component cover and the customer orders fed by the moved order → show the effects on S03, flag a key account
btn_check_loadon click → sum setup and run times from the routing against the work center's hours per day → mark overloaded days on S03
btn_inform_customeron click → send the new date to the customer contact and record it → fill the confirmed date field on S05
btn_write_backon click → call the ERP interfaces for production order, planned order and sales order dates → store each acknowledgement, close the case, refresh S07

Clocks

StepTime limit and escalation
Production check4 working hours, then the plant manager is copied
Sales update1 working day, then the sales manager is reminded
Approval1 working day, then the change goes to the plant manager

Measures

changes written back within a daycustomer dates moved per weekorders started on time after a changework center load after the movechanges by reason
A day with the app

Illustrative

Names, places and figures are illustrative; the pattern is the catalogue's.

At 05:50 the night shift in Gothenburg recorded a spindle failure on machining centre 4, and the app opened a change for the 14 firmed orders on it that week. Erik, the planner, moved 9 of them to centre 6 by 07:30; the effects screen showed every component covered and 2 customer orders moving by 2 days, one of them for a key account. The production lead confirmed tooling at 08:10, the sales manager signed the key account move at 09:00 after the order desk had spoken to the customer, and the planning manager approved at 09:20. The production order dates and the customer confirmations reached the ERP within seconds, and the board showed the plant manager 3 changes that week, all written back the same day.

illustrative scenario · Production schedule change
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

Firmed orderA production or planned order the planning run leaves in place; a person changes its dates and quantity.
Work centerThe machine or line where an operation runs; the routing states its setup and run time.
Confirmed dateThe delivery date promised to the customer on the sales order line.
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.