App catalogue Manufacturing and quality

Supplier quality incident (8D)

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.

SCREENSDATA HANDLERSSOURCE OBJECTS, READ IN PLACES01 IncidentsscreenS02 Incident detailscreenS03 8D reportscreenS04 VerificationscreenS05 Commercialscreendh_qnQuality notificationdh_vendorSupplier masterdh_lotInspection lotdh_grGoods receiptdh_stockStock positionS/4HANAQMEL · QMFE · QMMAS/4HANALFA1 · LFB1 · LFM1S/4HANAQALS · QAMR · QAVES/4HANAMATDOCS/4HANAMARD · MCHB · MATDOC_EXTRACTrows 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 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.

Who takes part

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

LaneDoes
Incoming inspectorrecords the finding with the lot, photos and quantity from a handheld
Supplier quality engineerowns the notification and verifies each discipline
Supplierworks the 8 disciplines on the portal screen
Buyerposts the return delivery, adds the replacement line and recovers the cost
Quality managercloses the notification and decides on a purchasing block
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 Incidentsgrid of open supplier notifications with supplier, material, defect, quantity, priority, discipline reached, days open; open button
S02 Incident detailinspection lot result, goods receipt and batch, blocked quantity, photos, order line; start-8D button; sort, rework or return choice
S03 8D reportportal screen with a tab per discipline D1 to D8 and the fields each needs; supplier team members; save and submit per discipline
S04 Verificationsupplier quality engineer accepts or returns each discipline with a note; evidence checklist
S05 Commercialreturn delivery, replacement order line, sorting cost and debit note amount; buyer's confirm buttons
S06 Boardincidents by supplier and defect, average days to D3 and D8, cost recovered, repeat incidents
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
Quality notificationsupplier-type quality notifications with defect, priority and tasksS/4HANA · Oracle Fusion · Snowflake · Databricks
Supplier mastersupplier contacts and purchasing blockS/4HANA · Oracle Fusion · Snowflake · Databricks
Inspection lotthe inspection lot at goods receipt with result and usage decisionS/4HANA · Oracle Fusion · Snowflake · Databricks
Goods receiptthe receipt and batch the lot came fromS/4HANA · Oracle Fusion · Snowflake · Databricks
Stock positionthe blocked quantity and its locationS/4HANA · Oracle Fusion · Snowflake · Databricks
Purchase order linethe order line for the return and the replacementS/4HANA · Oracle Fusion · Snowflake · Databricks

Written back

ObjectWhat changes
Quality notification8D disciplines recorded as tasks with status and dates; notification set to complete at D8
Stock positionaffected quantity moved to blocked stock and returned to the supplier with a return delivery
Purchase order linereplacement quantity added to the order line
The flow

From the trigger to the last write

THE FLOW · SUPPLIER QUALITY INCIDENT (8D)1Incident openedsupplier-typenotification with therejected lot readfrom the ERP; caseopened; priority setfrom quantity andline-stop risk2ContainmentD1 to D3: supplierconfirms sorting orreplacement within 24hours; affected stockblocked and thereturn deliveryposted3Root causeD4: supplier submitsthe cause andevidence within 10working days; theengineer verifies orreturns it4CorrectiveactionsD5 and D6: actionswith datesimplemented andvalidated on the next3 receipts inspected5PreventionD7: standards,control plan andfailure mode analysisupdates uploaded andverified6ClosedD8: quality managercloses thenotification; costrecovery debited; athird incident in 12months puts thesupplier under review
Each step and the criterion that moves it.

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

StepMoves when
Incident openedsupplier-type notification with the rejected lot read from the ERP; case opened; priority set from quantity and line-stop risk
ContainmentD1 to D3: supplier confirms sorting or replacement within 24 hours; affected stock blocked and the return delivery posted
Root causeD4: supplier submits the cause and evidence within 10 working days; the engineer verifies or returns it
Corrective actionsD5 and D6: actions with dates implemented and validated on the next 3 receipts inspected
PreventionD7: standards, control plan and failure mode analysis updates uploaded and verified
ClosedD8: quality manager closes the notification; cost recovery debited; a third incident in 12 months puts the supplier under review
Actions, clocks and measures

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

ComponentTrigger → action → outcome
btn_start_8don click → create the portal 8D with the notification facts and photos → invite the supplier contact, start the 24-hour D3 clock
btn_block_and_returnon 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_verifyon click → accept or return the discipline with the note → open the next discipline on the portal, start its clock
btn_closeon click → set the notification to complete and record the cost recovered → refresh S06, flag the supplier when incidents in 12 months reach 3

Clocks

StepTime limit and escalation
D3 containment24 hours, then the supplier's account manager and the buyer are alerted
D4 root cause10 working days, then the supplier's quality manager is copied and the open 8D shows on the scorecard
D8 closure60 days from open, then the quality manager decides on a purchasing block or an extension

Measures

days to containmentdays to closureopen 8Ds by suppliercost recoveredrepeat incidents per supplier
A day with the app

Illustrative

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.

illustrative scenario · Supplier quality incident (8D)
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

8DA problem-solving method in 8 steps: team, problem, containment, root cause, corrective action, validation, prevention and closure.
Inspection lotThe ERP record for a set of goods inspected at receipt, holding the results and the usage decision.
Return deliveryThe goods movement that sends rejected goods back to the supplier against the purchase order.
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?

Roles on portal screens see only the rows the access policy allows, and their steps are logged like everyone else's.

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.