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.
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.
| Function | Level | Does |
|---|---|---|
| Planning | Level 1: production planner | proposes the new sequence and dates |
| Planning | Level 2: planning manager | signs a change that touches a customer date |
| Production | Level 1: production lead | confirms crew, tooling and setup for the new sequence |
| Production | Level 2: plant manager | decides moves above 250,000 of order value or beyond 5 days |
| Sales | Level 1: order desk | informs customers and updates confirmed dates |
| Sales | Level 2: sales manager | signs a moved date on a key account order |
| Materials | Level 1: material planner | confirms components for orders pulled forward |
Every screen renders for desktop and mobile; portal screens are the same screens delivered to an outside login.
| Screen | What is on it |
|---|---|
| S01 Change request | work center, window of days, reason (breakdown, rush order, shortage, maintenance), orders affected picked from the live schedule; submit |
| S02 Schedule | chart 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 Effects | moved orders with old and new dates, customer orders affected with confirmed dates, components short after the move, work center load by day |
| S04 Production check | crew, tooling and setup for the new sequence; confirm or comment |
| S05 Sales update | customer orders with new dates; inform-customer button; confirmed date field |
| S06 Approval | summary of effects and values; approve or return; write-back button |
| S07 Board | changes per week by reason, customer dates moved, orders started on time after a change |
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 |
|---|---|---|
| Production order | firmed production orders with dates, quantities and confirmations | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Planned order | firmed planned orders in the window | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Sales order line | customer orders fed by the moved orders and their confirmed dates | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Stock position | component availability for orders pulled forward | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Routing | setup and run times per operation and work center | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Object | What changes |
|---|---|
| Production order | start and finish dates changed through the production order interface |
| Planned order | firmed planned orders rescheduled |
| Sales order line | confirmed dates updated on the affected customer orders |
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.
| Step | Moves when |
|---|---|
| Change started | orders in the window read live with status and confirmations; case opened for the planner |
| Sequence proposed | planner moves orders on S02; component cover and customer date effects shown for each move |
| Production confirmed | production lead confirms crew and tooling within 4 working hours |
| Sales informed | customer orders with a moved date go to the order desk; a key account needs the sales manager's signature |
| Approved | planning manager signs; the plant manager signs moves above 250,000 or beyond 5 days |
| Written back | production and planned order dates changed and customer confirmations updated in the ERP; case closed |
| Component | Trigger → action → outcome |
|---|---|
| cht_schedule | on drop → recompute component cover and the customer orders fed by the moved order → show the effects on S03, flag a key account |
| btn_check_load | on click → sum setup and run times from the routing against the work center's hours per day → mark overloaded days on S03 |
| btn_inform_customer | on click → send the new date to the customer contact and record it → fill the confirmed date field on S05 |
| btn_write_back | on click → call the ERP interfaces for production order, planned order and sales order dates → store each acknowledgement, close the case, refresh S07 |
| Step | Time limit and escalation |
|---|---|
| Production check | 4 working hours, then the plant manager is copied |
| Sales update | 1 working day, then the sales manager is reminded |
| Approval | 1 working day, then the change goes to the plant manager |
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.
The objects with their real names, the criteria in that system's fields, the write interface and what to set up first.
Production order read from AFKO · AFPO · AFVC; also on SAP ECC.
Open the S/4HANA page →Production order read from Manufacturing REST: workOrders; also on Oracle E-Business Suite.
Open the Oracle Fusion page →Production order read from CONFORMED.PRODUCTION_ORDER; lakehouse.
Open the Snowflake page →Production order read from silver.production_order; 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.