Manufacturing and quality on S/4HANA

Batch release on SAP S/4HANA

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.

SCREENSDATA HANDLERSS/4HANA · READ IN PLACES01 Batches awaiting releaseS02 Batch record reviewS03 DeviationsS04 Usage decisionS05 CertificateS06 Boarddh_batchBatchMCH1 · MCHA · MCHBdh_inspection_lotInspection lotQALS · QAMR · QAVEdh_production_orderProduction orderAFKO · AFPO · AFVCdh_quality_notificationQuality notificationQMEL · QMFE · QMMAdh_stock_positionStock positionMARD · MCHB · MATDOC_EXTRACTWRITE BACK TO S/4HANAInspection lot → BAPI_INSPLOT_SETUSAGEDECISION · BAPI_INSPOPER_RECORDRESULTSBatch → BAPI_BATCH_CHANGE · BAPI_BATCH_SAVE_REPLICArows 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.
5
objects read in place from S/4HANA
catalogue
6
screens on those rows
catalogue
6 days
to production-grade
estimate
2
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
BatchMCH1 · MCHA · MCHBMCH1.CHARG (batch) · MCH1.MATNR (material) · MCH1.VFDAT (expiry) · MCH1.HSDAT (produced)live; change capture where enabled
Inspection lotQALS · QAMR · QAVEQAMR.MBEWERTG (result) · QAVE.VCODE (decision) · QALS.HERKUNFT (origin) · QALS.PRUEFLOS (lot)live; change capture where enabled
Production orderAFKO · AFPO · AFVCAFKO.AUFNR (number) · AFPO.MATNR (material) · AFPO.PSMNG (qty) · AFKO.GSTRP (start)live; change capture where enabled
Quality notificationQMEL · QMFE · QMMAQMEL.QMNUM (number) · QMEL.QMART (type) · QMEL.MATNR (material) · QMEL.LIFNUM (vendor)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
The trigger

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

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} = ''
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
Inspection lotusage decision posted as accept or reject through the inspection lot interface, with the stock posting from quality inspection to unrestricted, blocked or scrapBAPI_INSPLOT_SETUSAGEDECISION · BAPI_INSPOPER_RECORDRESULTS
Batchbatch status set to released or blocked; certificate of analysis attached to the batchBAPI_BATCH_CHANGE · BAPI_BATCH_SAVE_REPLICA
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 handlers5 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
BatchMCH1 · MCHA · MCHBsame tables
Inspection lotQALS · QAMR · QAVEsame tables
Production orderAFKO · AFPO · AFVCsame tables
Quality notificationQMEL · QMFE · QMMAsame tables
Stock positionMARD · MCHB · MATDOC_EXTRACTMARD · MCHB · MBEW
Nearby

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

Batch release on

Other apps on S/4HANA

Terms on this page

Usage decisionThe decision recorded on an inspection lot that accepts or rejects the inspected quantity and posts its stock accordingly.
Quality inspection stockStock that waits for a usage decision; it becomes available for delivery once posted to unrestricted.
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.