Turns a count that differs from the book quantity by more than the tolerance into a case: recount, investigate the movements, post the adjustment from the floor.
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 |
|---|---|---|---|
| Stock position | MARD · MCHB · MATDOC_EXTRACT | MARD.LABST (on hand) · MBEW.SALK3 (value) · MARD.MATNR (material) · MARD.WERKS (plant) | live; change capture where enabled |
| Goods receipt | MATDOC (material documents) | MATDOC.MBLNR (document) · MATDOC.EBELN (po) · MATDOC.MATNR (material) · MATDOC.MENGE (qty) | live; change capture where enabled |
| Material master | MARA · MARC · MAKT | MARA.MTART (type) · MARA.MATNR (id) · MAKT.MAKTX (desc) · MARC.WERKS (plant) | live; change capture where enabled |
| Delivery | LIKP · LIPS | LIKP.VBELN (number) · LIKP.KUNNR (customer) · LIKP.WADAT (planned gi) · LIKP.WADAT_IST (actual gi) | live; change capture where enabled |
In plain words: A count entered on the mobile screen that differs from the book quantity by more than the tolerance for the material's value class; illustrative tolerances are 2 percent in quantity or 250 in value.
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 abs(counted_qty - MARD.LABST) > tolerance_qty(MARA.MTART) or abs(counted_qty - MARD.LABST) * unit_value(MBEW.SALK3) > 250 # the same criterion in canonical fields abs(counted_qty - {stock.on_hand}) > tolerance_qty({material.type}) or abs(counted_qty - {stock.on_hand}) * unit_value({stock.value}) > 250
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 |
|---|---|---|
| Stock position | difference posted as an inventory adjustment through the goods movement interface (movement types 701 and 702) with reason code and cost center, or a transfer between bins when the goods are found elsewhere | BAPI_GOODSMVT_CREATE (transfer, scrap, block) |
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 |
|---|---|---|
| Stock position | MARD · MCHB · MATDOC_EXTRACT | MARD · MCHB · MBEW |
| Goods receipt | MATDOC (material documents) | MKPF and MSEG |
| Material master | MARA · MARC · MAKT | same tables |
| Delivery | LIKP · LIPS | same tables |
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.