Takes a produced batch from complete inspection results through QA review to a usage decision, sets the batch status in the ERP and produces the certificate of analysis.
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.
| Object | Read from | Fields the app uses | Freshness |
|---|---|---|---|
| Batch | MCH1 · MCHA · MCHB | MCH1.CHARG (batch) · MCH1.MATNR (material) · MCH1.VFDAT (expiry) · MCH1.HSDAT (produced) | live; change capture where enabled |
| Inspection lot | QALS · QAMR · QAVE | QAMR.MBEWERTG (result) · QAVE.VCODE (decision) · QALS.HERKUNFT (origin) · QALS.PRUEFLOS (lot) | live; change capture where enabled |
| Production order | AFKO · AFPO · AFVC | AFKO.AUFNR (number) · AFPO.MATNR (material) · AFPO.PSMNG (qty) · AFKO.GSTRP (start) | live; change capture where enabled |
| Quality notification | QMEL · QMFE · QMMA | QMEL.QMNUM (number) · QMEL.QMART (type) · QMEL.MATNR (material) · QMEL.LIFNUM (vendor) | live; change capture where enabled |
| Stock position | MARD · MCHB · MATDOC_EXTRACT | MARD.MATNR (material) · MARD.WERKS (plant) · MARD.LGORT (sloc) · MARD.LABST (on hand) | live; change capture where enabled |
In plain words: An inspection lot from production (origin 04) whose results are recorded for every characteristic and whose usage decision is still open.
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 QALS.HERKUNFT = '04' and QAMR.MBEWERTG = 'recorded' and QAVE.VCODE = '' # the same criterion in canonical fields {lot.origin} = '04' and {lot.result} = 'recorded' and {lot.decision} = ''
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.
| Object | What changes | Interface |
|---|---|---|
| Inspection lot | usage decision posted as accept or reject through the inspection lot interface, with the stock posting from quality inspection to unrestricted, blocked or scrap | BAPI_INSPLOT_SETUSAGEDECISION · BAPI_INSPOPER_RECORDRESULTS |
| Batch | batch status set to released or blocked; certificate of analysis attached to the batch | BAPI_BATCH_CHANGE · BAPI_BATCH_SAVE_REPLICA |
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.
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.
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.
| Object | On S/4HANA | On SAP ECC |
|---|---|---|
| Batch | MCH1 · MCHA · MCHB | same tables |
| Inspection lot | QALS · QAMR · QAVE | same tables |
| Production order | AFKO · AFPO · AFVC | same tables |
| Quality notification | QMEL · QMFE · QMMA | same tables |
| Stock position | MARD · MCHB · MATDOC_EXTRACT | MARD · MCHB · MBEW |
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.
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.
Yes. The screens, criteria and roles stay; the handlers are re-bound to the other system's objects, listed above.
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.