Turns a quality notification against a supplier into an 8D case the supplier works on a portal screen, with blocked stock, return delivery and closure recorded in the ERP.
Today the 8D report is a document template emailed to the supplier, and its progress is a column in the supplier quality engineer's spreadsheet. The rejected lot waits on a pallet while the return delivery and the debit note follow weeks later.
The app reads every quality notification of the supplier type, most of them raised from a rejected inspection lot at goods receipt, and opens a case for the supplier quality engineer with the lot result, the receipt, the batch and the photos. The engineer starts the 8D, and the supplier works each discipline on the portal screen, from the team and problem description through containment, root cause, corrective actions, validation and prevention. The engineer verifies each discipline and the buyer handles the return delivery, the replacement line and the cost recovery. The quality manager closes the notification, and a supplier with 3 incidents in 12 months goes under review.
| Lane | Does |
|---|---|
| Incoming inspector | records the finding with the lot, photos and quantity from a handheld |
| Supplier quality engineer | owns the notification and verifies each discipline |
| Supplier | works the 8 disciplines on the portal screen |
| Buyer | posts the return delivery, adds the replacement line and recovers the cost |
| Quality manager | closes the notification and decides on a purchasing block |
Every screen renders for desktop and mobile; portal screens are the same screens delivered to an outside login.
| Screen | What is on it |
|---|---|
| S01 Incidents | grid of open supplier notifications with supplier, material, defect, quantity, priority, discipline reached, days open; open button |
| S02 Incident detail | inspection lot result, goods receipt and batch, blocked quantity, photos, order line; start-8D button; sort, rework or return choice |
| S03 8D report | portal screen with a tab per discipline D1 to D8 and the fields each needs; supplier team members; save and submit per discipline |
| S04 Verification | supplier quality engineer accepts or returns each discipline with a note; evidence checklist |
| S05 Commercial | return delivery, replacement order line, sorting cost and debit note amount; buyer's confirm buttons |
| S06 Board | incidents by supplier and defect, average days to D3 and D8, cost recovered, repeat incidents |
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 | supplier-type quality notifications with defect, priority and tasks | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Supplier master | supplier contacts and purchasing block | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Inspection lot | the inspection lot at goods receipt with result and usage decision | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Goods receipt | the receipt and batch the lot came from | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Stock position | the blocked quantity and its location | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Purchase order line | the order line for the return and the replacement | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Object | What changes |
|---|---|
| Quality notification | 8D disciplines recorded as tasks with status and dates; notification set to complete at D8 |
| Stock position | affected quantity moved to blocked stock and returned to the supplier with a return delivery |
| Purchase order line | replacement quantity added to the order line |
Start: A quality notification of the supplier type created in the ERP, from a rejected inspection lot at goods receipt or from the floor.
# start criterion, in canonical fields; each system page shows it in that system's fields
{qn.type} = supplier and {qn.vendor} is present| Step | Moves when |
|---|---|
| Incident opened | supplier-type notification with the rejected lot read from the ERP; case opened; priority set from quantity and line-stop risk |
| Containment | D1 to D3: supplier confirms sorting or replacement within 24 hours; affected stock blocked and the return delivery posted |
| Root cause | D4: supplier submits the cause and evidence within 10 working days; the engineer verifies or returns it |
| Corrective actions | D5 and D6: actions with dates implemented and validated on the next 3 receipts inspected |
| Prevention | D7: standards, control plan and failure mode analysis updates uploaded and verified |
| Closed | D8: quality manager closes the notification; cost recovery debited; a third incident in 12 months puts the supplier under review |
| Component | Trigger → action → outcome |
|---|---|
| btn_start_8d | on click → create the portal 8D with the notification facts and photos → invite the supplier contact, start the 24-hour D3 clock |
| btn_block_and_return | on tap → post the transfer to blocked stock and the return delivery against the order line through the ERP goods movement interface → record the material documents on the notification |
| btn_verify | on click → accept or return the discipline with the note → open the next discipline on the portal, start its clock |
| btn_close | on click → set the notification to complete and record the cost recovered → refresh S06, flag the supplier when incidents in 12 months reach 3 |
| Step | Time limit and escalation |
|---|---|
| D3 containment | 24 hours, then the supplier's account manager and the buyer are alerted |
| D4 root cause | 10 working days, then the supplier's quality manager is copied and the open 8D shows on the scorecard |
| D8 closure | 60 days from open, then the quality manager decides on a purchasing block or an extension |
Names, places and figures are illustrative; the pattern is the catalogue's.
At 10:20 an inspector in Brno rejected a lot of 5,000 machined brackets for an out-of-tolerance bore, and the notification opened a case for Petra, the supplier quality engineer. She started the 8D at 10:40; the supplier confirmed containment on the portal at 15:30 with a sorted replacement lot for the next morning, and the buyer posted the return delivery from S05 before he left. The root cause, a worn fixture shim, came in on day 6, the next 3 receipts were accepted, and Petra closed D8 on day 34 with 8,200 recovered by debit note. The board showed the quality manager 11 open 8Ds and 1 supplier with a third incident.
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.
Roles on portal screens see only the rows the access policy allows, and their steps are logged like everyone else's.
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.