Takes a deviation reported on the floor through containment, root cause, corrective action and an effectiveness check, with the notification, blocked stock and batch status kept in the ERP.
Today a deviation is a paper tag on a pallet and a line in the shift log, and the quality notification is typed in the next morning. The root cause lives in a slide and the effectiveness check depends on someone remembering to look.
An operator or inspector reports the deviation from a mobile screen with the scanned order or batch, a defect code from the catalogue, the quantity and a photo, and the app creates the quality notification in the ERP within seconds. The shift lead contains it: the affected quantity moves to blocked stock, the batch is set to restricted and the production order is held while the cause is open. The quality engineer records the cause chain with evidence, proposes corrective actions with owners and dates, and the quality manager approves them. The app then watches the next inspection lots for the material and defect, and closes the notification when they come back clean.
| Lane | Does |
|---|---|
| Operator or inspector | reports the deviation from the mobile screen |
| Shift lead | contains it: blocks stock, restricts the batch, holds the order |
| Quality engineer | finds the root cause and proposes corrective actions |
| Process owner | implements the actions by their dates |
| Quality manager | approves the actions and closes the notification after the effectiveness check |
Every screen renders for desktop and mobile; portal screens are the same screens delivered to an outside login.
| Screen | What is on it |
|---|---|
| S01 Report deviation | mobile screen: order or batch scan, defect code from the catalogue, quantity affected, photo, description; submit |
| S02 Containment | affected batch and stock by location, quantity to block, sort or rework choice, order hold; block button; works on a tablet |
| S03 Investigation | cause chain (the 5 whys), cause category, evidence uploads, similar notifications in the last 12 months for the same material and defect; propose-action button |
| S04 Corrective action | actions with owner, due date and cost; verification method and date; approve button for the quality manager |
| S05 Effectiveness check | results of the next 3 inspection lots, or 30 days of production, for the material and defect; close or reopen |
| S06 Board | open notifications by age and priority, blocked stock value, repeat defects per material, actions past due |
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 |
|---|---|---|
| Quality notification | quality notifications with defect code, priority and tasks | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Inspection lot | inspection lots and their results for the effectiveness check | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Batch | status of the affected batch | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Stock position | quantity in blocked stock and its value | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Production order | the order in progress when the deviation occurred | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Object | What changes |
|---|---|
| Quality notification | notification created from the mobile screen with defect code, tasks and status; set to complete at closure |
| Stock position | affected quantity moved to blocked stock and back with a goods movement |
| Batch | batch status set to restricted during containment and released after the decision |
Start: An operator or inspector submits a deviation on the mobile screen S01; a quality notification of the internal defect type created directly in the ERP opens a case as well.
| Step | Moves when |
|---|---|
| Deviation reported | notification created in the ERP within seconds; shift lead notified; priority set from the defect code and quantity |
| Contained | affected quantity moved to blocked stock and the batch restricted within 4 hours; production order held while the cause is open |
| Root cause found | quality engineer records the cause chain and evidence within 5 working days; a repeat defect raises the priority |
| Actions approved | quality manager approves actions with owners and dates; a batch already delivered informs sales as well |
| Effectiveness checked | 3 inspection lots with an accepted decision, or 30 clean days, close the notification; a repeat reopens it |
| Component | Trigger → action → outcome |
|---|---|
| btn_report | on tap → create the quality notification through the ERP interface with the scanned order, defect code, quantity and photo → notify the shift lead, start the 4-hour containment clock |
| btn_block | on tap → post the transfer to blocked stock for the affected quantity and set the batch status to restricted → record the material document on the notification |
| btn_propose_action | on click → add the actions as tasks on the notification with owner and due date → route them to the quality manager for approval |
| btn_close | on click → check the last 3 inspection lot decisions for the material and defect → set the notification to complete, release the batch when the decision allows, refresh S06 |
| Step | Time limit and escalation |
|---|---|
| Containment | 4 working hours, then the production manager is alerted |
| Root cause | 5 working days, or 2 for a high priority, then the quality manager is copied |
| Corrective action | the due date per action; 3 days past due escalates to the process owner's manager |
Names, places and figures are illustrative; the pattern is the catalogue's.
At 06:40 Marek, an inspector on line 3 in Wrocław, scanned a production order and reported 220 housings with a burr at the parting line, photo attached. The shift lead moved the batch to blocked stock from her tablet at 07:05 and held the order; the quality engineer traced the cause to a worn mould insert by Tuesday afternoon and proposed a replacement with a check every 20,000 shots. The quality manager approved on Wednesday at 09:15, the next 3 inspection lots were accepted, and the notification closed on 14 May with the material documents beside it. The board showed 2 repeat defects that month, down from 7.
The objects with their real names, the criteria in that system's fields, the write interface and what to set up first.
Quality notification read from QMEL · QMFE · QMMA; also on SAP ECC.
Open the S/4HANA page →Quality notification read from Quality Management REST: qualityIssues · qualityActions; also on Oracle E-Business Suite.
Open the Oracle Fusion page →Quality notification read from CONFORMED.QUALITY_NOTIFICATION; lakehouse.
Open the Snowflake page →Quality notification read from silver.quality_notification; 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.
