Logistics and warehouse on S/4HANA

Cycle count exception on SAP S/4HANA

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.

SCREENSDATA HANDLERSS/4HANA · READ IN PLACES01 Count listS02 DifferencesS03 InvestigationS04 RecountS05 PostingS06 Boarddh_stock_positionStock positionMARD · MCHB · MATDOC_EXTRACTdh_goods_receiptGoods receiptMATDOC (material documents)dh_material_masterMaterial masterMARA · MARC · MAKTdh_deliveryDeliveryLIKP · LIPSWRITE BACK TO S/4HANAStock position → BAPI_GOODSMVT_CREATE (transfer, scrap, block)rows 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.
4
objects read in place from S/4HANA
catalogue
6
screens on those rows
catalogue
4 days
to production-grade
estimate
1
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
Stock positionMARD · MCHB · MATDOC_EXTRACTMARD.LABST (on hand) · MBEW.SALK3 (value) · MARD.MATNR (material) · MARD.WERKS (plant)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
Material masterMARA · MARC · MAKTMARA.MTART (type) · MARA.MATNR (id) · MAKT.MAKTX (desc) · MARC.WERKS (plant)live; change capture where enabled
DeliveryLIKP · LIPSLIKP.VBELN (number) · LIKP.KUNNR (customer) · LIKP.WADAT (planned gi) · LIKP.WADAT_IST (actual gi)live; change capture where enabled
The trigger

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

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
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
Stock positiondifference 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 elsewhereBAPI_GOODSMVT_CREATE (transfer, scrap, block)
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 handlers4 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
Stock positionMARD · MCHB · MATDOC_EXTRACTMARD · MCHB · MBEW
Goods receiptMATDOC (material documents)MKPF and MSEG
Material masterMARA · MARC · MAKTsame tables
DeliveryLIKP · LIPSsame tables
Nearby

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

Cycle count exception on

Other apps on S/4HANA

Terms on this page

Cycle countCounting a small set of bins each day, so that every location is counted several times a year.
ToleranceThe difference in quantity or value below which a count is accepted as it is.
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.