Takes a change request from the engineer's form through a live impact on BOM, stock and open orders to the review board, and creates the change number in the ERP.
Today the impact of a change is a set of numbers each function looks up for the board meeting, and the stock figure is a week old by the time the board sees it. The change number is created afterwards from the meeting minutes.
An engineer submits the change with the affected part, the type of change and a proposed date. Within seconds the app reads the where-used list from the bill of materials (BOM), the stock of the old component at every plant with its value, the open purchase orders and the production orders in progress, and computes a run-out date and an impact value. Planning, procurement and quality each record their view, and the weekly review board approves an effectivity: immediate, run-out or a fixed date. The app creates the change number in the ERP, swaps the BOM component under it with the valid-from, and tracks the order changes until each one is confirmed.
| Lane | Does |
|---|---|
| Requesting engineer | describes the change and proposes the effectivity |
| Planning | assesses stock and demand for the old component and proposes run-out |
| Procurement | handles open purchase orders and informs the supplier |
| Quality | sets validation needs such as a first-article check |
| Review board | decides effectivity and approves; chaired by the engineering manager |
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 | affected part or assembly, type of change (replace component, quantity, drawing), reason, proposed valid-from, urgency; attachments; submit |
| S02 Impact | where-used list from the BOM, stock of the old component by plant with value, open purchase orders with quantities and dates, production orders in progress; run-out date and impact value computed |
| S03 Function review | planning's run-out proposal, procurement's order actions, quality's validation need; agree or comment per function |
| S04 Review board | the request, the impact and the 3 reviews; effectivity options: immediate, run-out, fixed date; approve, return, reject; note |
| S05 Execution | change number, BOM lines changed with valid-from, affected orders with action and status; confirm buttons |
| S06 Tracker | requests by stage, age and urgency; this week's board agenda; changes effective this month |
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 |
|---|---|---|
| Engineering change | change numbers with status, valid-from and assigned objects | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Bill of materials | the structures that use the affected component | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Stock position | on hand and value of the old component by plant | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Purchase order line | open purchase order lines for the old component | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Production order | production orders in progress on the old structure | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Material master | the old and new parts with type and status | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Object | What changes |
|---|---|
| Engineering change | change number created with the approved valid-from and status; affected objects assigned |
| Bill of materials | component replaced under the change number with the valid-from |
| Purchase order line | open order lines for the old component reduced or closed as procurement decides |
Start: An engineer submits a change request on S01 naming the affected part and the reason.
| Step | Moves when |
|---|---|
| Request submitted | impact read live from the BOM, stock and orders; case opened with an impact value and a run-out date |
| Functions reviewed | planning, procurement and quality each record their view within 5 working days, or 1 for an urgent request |
| Board decided | weekly board approves with an effectivity; an impact value above 100,000 needs the plant manager as well |
| Change created | change number created in the ERP with the valid-from; BOM component swapped under it |
| Orders adjusted | open purchase orders reduced or moved and production orders on the old structure flagged; case closed when every action is confirmed |
| Component | Trigger → action → outcome |
|---|---|
| btn_submit | on click → read the where-used list and the stock, purchase orders and production orders for the old component → compute the run-out date and impact value, open the reviews |
| dd_effectivity | on change → recompute the stock to use up or scrap and the orders to change → show the value of each option on S04 |
| btn_approve | on click → create the change number through the ERP change interface with the chosen valid-from → replace the BOM component under that number, open the execution items |
| btn_confirm_action | on click → record the order change with its document number → close the item, close the case when the last item is done |
| Step | Time limit and escalation |
|---|---|
| Function review | 5 working days, or 1 for an urgent request, then the function's lead is reminded |
| Board decision | the next weekly board; a request waiting more than 10 working days escalates to the engineering director |
| Execution | 10 working days after approval, then the item owner's lead is copied |
Names, places and figures are illustrative; the pattern is the catalogue's.
Jonas, a design engineer in Stuttgart, submitted a request at 14:20 to replace a relay on 3 assemblies with a pin-compatible part. Within a minute the impact screen showed 6,400 pieces of the old relay across 2 plants worth 41,000, 2 open purchase orders and 11 production orders in progress, and a run-out date 9 weeks out. Planning proposed run-out effectivity the next morning, procurement closed 1 order and kept the other, and quality asked for a first-article check on the first 50 assemblies. The board approved on Thursday at 15:00; the change number and the new BOM lines existed in the ERP by 15:03, and the tracker showed 4 execution items with owners.
The objects with their real names, the criteria in that system's fields, the write interface and what to set up first.
Engineering change read from AENR · AEOI; also on SAP ECC.
Open the S/4HANA page →Engineering change read from Product Hub REST: productChangeOrdersV2; also on Oracle E-Business Suite.
Open the Oracle Fusion page →Engineering change read from CONFORMED.ENGINEERING_CHANGE; lakehouse.
Open the Snowflake page →Engineering change read from silver.engineering_change; 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 6 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.