App catalogue Manufacturing and quality

Engineering change request

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.

SCREENSDATA HANDLERSSOURCE OBJECTS, READ IN PLACES01 Change requestscreenS02 ImpactscreenS03 Function reviewscreenS04 Review boardscreenS05 Executionscreendh_ecnEngineering changedh_bomBill of materialsdh_stockStock positiondh_poPurchase order linedh_prod_orderProduction orderS/4HANAAENR · AEOIS/4HANAMAST · STKO · STPOS/4HANAMARD · MCHB · MATDOC_EXTRACTS/4HANAEKKO · EKPO · EKET · EKBES/4HANAAFKO · AFPO · AFVCrows stay in the source · access rules apply at read time · writes go through the source's released interface and are confirmed
The screens, the data handlers behind them and the objects each handler reads in place on S/4HANA. Other systems have their own page.
6 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 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.

Who takes part

Process app: lanes and boxes first, then screens per box, then roles, then the criteria on each arrow

LaneDoes
Requesting engineerdescribes the change and proposes the effectivity
Planningassesses stock and demand for the old component and proposes run-out
Procurementhandles open purchase orders and informs the supplier
Qualitysets validation needs such as a first-article check
Review boarddecides effectivity and approves; chaired by the engineering manager
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 Change requestaffected part or assembly, type of change (replace component, quantity, drawing), reason, proposed valid-from, urgency; attachments; submit
S02 Impactwhere-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 reviewplanning's run-out proposal, procurement's order actions, quality's validation need; agree or comment per function
S04 Review boardthe request, the impact and the 3 reviews; effectivity options: immediate, run-out, fixed date; approve, return, reject; note
S05 Executionchange number, BOM lines changed with valid-from, affected orders with action and status; confirm buttons
S06 Trackerrequests by stage, age and urgency; this week's board agenda; changes effective this month
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
Engineering changechange numbers with status, valid-from and assigned objectsS/4HANA · Oracle Fusion · Snowflake · Databricks
Bill of materialsthe structures that use the affected componentS/4HANA · Oracle Fusion · Snowflake · Databricks
Stock positionon hand and value of the old component by plantS/4HANA · Oracle Fusion · Snowflake · Databricks
Purchase order lineopen purchase order lines for the old componentS/4HANA · Oracle Fusion · Snowflake · Databricks
Production orderproduction orders in progress on the old structureS/4HANA · Oracle Fusion · Snowflake · Databricks
Material masterthe old and new parts with type and statusS/4HANA · Oracle Fusion · Snowflake · Databricks

Written back

ObjectWhat changes
Engineering changechange number created with the approved valid-from and status; affected objects assigned
Bill of materialscomponent replaced under the change number with the valid-from
Purchase order lineopen order lines for the old component reduced or closed as procurement decides
The flow

From the trigger to the last write

THE FLOW · ENGINEERING CHANGE REQUEST1Request submittedimpact read live from theBOM, stock and orders; caseopened with an impact valueand a run-out date2Functions reviewedplanning, procurement andquality each record theirview within 5 working days,or 1 for an urgent request3Board decidedweekly board approves withan effectivity; an impactvalue above 100,000 needsthe plant manager as well4Change createdchange number created inthe ERP with thevalid-from; BOM componentswapped under it5Orders adjustedopen purchase ordersreduced or moved andproduction orders on theold structure flagged; caseclosed when every action isconfirmed
Each step and the criterion that moves it.

Start: An engineer submits a change request on S01 naming the affected part and the reason.

StepMoves when
Request submittedimpact read live from the BOM, stock and orders; case opened with an impact value and a run-out date
Functions reviewedplanning, procurement and quality each record their view within 5 working days, or 1 for an urgent request
Board decidedweekly board approves with an effectivity; an impact value above 100,000 needs the plant manager as well
Change createdchange number created in the ERP with the valid-from; BOM component swapped under it
Orders adjustedopen purchase orders reduced or moved and production orders on the old structure flagged; case closed when every action is confirmed
Actions, clocks and measures

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

ComponentTrigger → action → outcome
btn_submiton 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_effectivityon change → recompute the stock to use up or scrap and the orders to change → show the value of each option on S04
btn_approveon 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_actionon click → record the order change with its document number → close the item, close the case when the last item is done

Clocks

StepTime limit and escalation
Function review5 working days, or 1 for an urgent request, then the function's lead is reminded
Board decisionthe next weekly board; a request waiting more than 10 working days escalates to the engineering director
Execution10 working days after approval, then the item owner's lead is copied

Measures

days from request to change numberimpact value per changechanges effective on the planned datestock scrapped through changesexecution items past due
A day with the app

Illustrative

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.

illustrative scenario · Engineering change request
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

EffectivityThe date or condition from which a change applies in production.
Where-usedThe list of every assembly whose bill of materials contains a given component.
Run-outUsing up the remaining stock of the old component before the change applies.
Questions

How long does it take to have this running?

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.

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.