Manufacturing and quality on S/4HANA

Supplier quality incident (8D) on SAP S/4HANA

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 HANDLERSS/4HANA · READ IN PLACES01 IncidentsS02 Incident detailS03 8D reportS04 VerificationS05 CommercialS06 Boarddh_quality_notificationQuality notificationQMEL · QMFE · QMMAdh_supplier_masterSupplier masterLFA1 · LFB1 · LFM1 (business partner inS/4)dh_inspection_lotInspection lotQALS · QAMR · QAVEdh_goods_receiptGoods receiptMATDOC (material documents)dh_stock_positionStock positionMARD · MCHB · MATDOC_EXTRACTdh_purchase_order_linePurchase order lineEKKO · EKPO · EKET · EKBEWRITE BACK TO S/4HANAQuality notification → BAPI_QUALNOT_CREATE · BAPI_QUALNOT_ADD_DATA · BAPI_QUALNOT_MODIFY_DATAStock position → BAPI_GOODSMVT_CREATE (transfer, scrap, block)Purchase order line → BAPI_PO_CHANGE · BAPI_PO_CREATE1rows stay in S/4HANA · access rules applied at read time · each write acknowledged and logged
The screens of the app, the data handler behind each, and the S/4HANA object it reads in place. Writes below the line go through released interfaces with an acknowledgement.
6
objects read in place from S/4HANA
catalogue
6
screens on those rows
catalogue
6 days
to production-grade
estimate
3
objects written back
catalogue
0
rows copied to build it
product
What the app reads

The S/4HANA objects behind each handler

Tables are read in place through the SAP connector, using released read interfaces; changed rows arrive through change capture where the basis team allows it. The rows stay in SAP.

ObjectRead fromFields the app usesFreshness
Quality notificationQMEL · QMFE · QMMAQMEL.QMART (type) · QMEL.LIFNUM (vendor) · QMEL.QMNUM (number) · QMEL.MATNR (material)live; change capture where enabled
Supplier masterLFA1 · LFB1 · LFM1 (business partner in S/4)LFA1.LIFNR (id) · LFA1.NAME1 (name) · LFA1.LAND1 (country) · LFA1.SPERR (block)live; change capture where enabled
Inspection lotQALS · QAMR · QAVEQALS.PRUEFLOS (lot) · QALS.MATNR (material) · QALS.HERKUNFT (origin) · QAMR.MBEWERTG (result)live; change capture where enabled
Goods receiptMATDOC (material documents)MATDOC.MBLNR (document) · MATDOC.EBELN (po) · MATDOC.MATNR (material) · MATDOC.MENGE (qty)live; change capture where enabled
Stock positionMARD · MCHB · MATDOC_EXTRACTMARD.MATNR (material) · MARD.WERKS (plant) · MARD.LGORT (sloc) · MARD.LABST (on hand)live; change capture where enabled
Purchase order lineEKKO · EKPO · EKET · EKBEEKKO.EBELN (number) · EKPO.EBELP (line) · EKKO.LIFNR (vendor) · EKPO.MATNR (material)live; change capture where enabled
The trigger

The start criterion in S/4HANA's own fields

In plain words: A quality notification of the supplier type created in the ERP, from a rejected inspection lot at goods receipt or from the floor.

The criterion runs in S/4HANA through the data handler, so only the matching rows return. The editor shows the rows it selects, and their count, as it is written.

# start criterion in S/4HANA fields
QMEL.QMART = supplier and QMEL.LIFNUM is present

# the same criterion in canonical fields
{qn.type} = supplier and {qn.vendor} is present
What the app writes back

Through released interfaces

Writes go through released BAPIs and IDocs. Each call returns a document number or an error message, and the app records both beside the decision.

ObjectWhat changesInterface
Quality notification8D disciplines recorded as tasks with status and dates; notification set to complete at D8BAPI_QUALNOT_CREATE · BAPI_QUALNOT_ADD_DATA · BAPI_QUALNOT_MODIFY_DATA
Stock positionaffected quantity moved to blocked stock and returned to the supplier with a return deliveryBAPI_GOODSMVT_CREATE (transfer, scrap, block)
Purchase order linereplacement quantity added to the order lineBAPI_PO_CHANGE · BAPI_PO_CREATE1
Acknowledged and logged

Each write stores the identifier S/4HANA returns beside the decision, the person and the time, so the log answers who changed what, and the reconciliation shows it arrived.

Access and prerequisites

What is in place before the first build

SAP roles are mapped to Lima access policies once. A buyer who sees purchasing organisation 1000 in SAP sees the same rows in the app.

  • An SAP user for the connector with read authorisation on the objects the app uses
  • The BAPIs the app writes with, enabled for that user
  • Network path to the application server (PrivateLink or VPN)
  • Change capture switched on for the objects that should refresh within minutes
Register the handlers6 objects from the catalog; each shows its rows at once.
Also on SAP ECC

The same app on SAP ECC

On SAP ECC the same objects live in the classic tables named beside each row; MATDOC becomes MKPF and MSEG, ACDOCA becomes BKPF and BSEG. The BAPIs are the same.

ObjectOn S/4HANAOn SAP ECC
Quality notificationQMEL · QMFE · QMMAsame tables
Supplier masterLFA1 · LFB1 · LFM1 (business partner in S/4)LFA1/LFB1/LFM1 vendor master, XK01 via BAPI
Inspection lotQALS · QAMR · QAVEsame tables
Goods receiptMATDOC (material documents)MKPF and MSEG
Stock positionMARD · MCHB · MATDOC_EXTRACTMARD · MCHB · MBEW
Purchase order lineEKKO · EKPO · EKET · EKBEsame tables
Nearby

This app on other systems, and other apps on S/4HANA

Supplier quality incident (8D) on

Other apps on S/4HANA

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.
Read in placeThe rows stay in S/4HANA; the handler sends the filter and the columns and S/4HANA returns the matching rows.
Questions

Does this app copy data out of S/4HANA?

The screens read through handlers that leave the rows in S/4HANA. History the app needs at scale is landed in the lake by the Backbone, which is the exception by design.

What does S/4HANA need to allow?

The prerequisites above: an integration identity with read rights on the objects listed and write rights on the interfaces named, connectivity, and the scopes agreed with the process owner.

Can I run it on SAP ECC as well?

Yes. The screens, criteria and roles stay; the handlers are re-bound to the other system's objects, listed above.

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.