Finds stock with cover above a threshold or a long idle time, gives each position to its planner with the options, and posts the decision in the ERP.
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.LAEDA (last movement) · MARD.MATNR (material) | live; change capture where enabled |
| Material master | MARA · MARC · MAKT | MARA.MATNR (id) · MAKT.MAKTX (desc) · MARA.MTART (type) · MARC.WERKS (plant) | live; change capture where enabled |
| Forecast | PBIM · PBED (planned independent requirements) | PBED.PLNMG (qty) · PBIM.MATNR (material) · PBIM.WERKS (plant) · PBED.PDATU (period) | live; change capture where enabled |
| Sales order line | VBAK · VBAP · VBEP | VBAP.KWMENG (qty) · VBAK.VBELN (number) · VBAP.POSNR (line) · VBAK.KUNNR (customer) | live; change capture where enabled |
| Batch | MCH1 · MCHA · MCHB | MCH1.CHARG (batch) · MCH1.MATNR (material) · MCH1.VFDAT (expiry) · MCH1.HSDAT (produced) | live; change capture where enabled |
| Journal line | ACDOCA (universal journal) | ACDOCA.BELNR (document) · ACDOCA.RACCT (account) · ACDOCA.HSL (amount) · ACDOCA.RCNTR (cost center) | live; change capture where enabled |
In plain words: A stock position worth more than 5,000 whose on-hand quantity covers more than 12 months of forecast and open orders, or whose last movement is older than 180 days.
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 MBEW.SALK3 > 5000 and (MARD.LABST > 12 months of PBED.PLNMG + VBAP.KWMENG or MARD.LAEDA < today - 180) # the same criterion in canonical fields {stock.value} > 5000 and ({stock.on_hand} > 12 months of {forecast.qty} + {so.qty} or {stock.last_movement} < today - 180)
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 | transfer to another plant or scrap posted as a goods movement; quantity moved to blocked stock while a decision is open | BAPI_GOODSMVT_CREATE (transfer, scrap, block) |
| Material master | plant status set to phase-out so planning stops creating new orders | BAPI_MATERIAL_SAVEDATA |
| Journal line | the agreed reserve change posted as a journal at month end | BAPI_ACC_DOCUMENT_POST · BAPI_ACC_DOCUMENT_REV_POST |
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 |
| Material master | MARA · MARC · MAKT | same tables |
| Forecast | PBIM · PBED (planned independent requirements) | same tables |
| Sales order line | VBAK · VBAP · VBEP | same tables |
| Batch | MCH1 · MCHA · MCHB | same tables |
| Journal line | ACDOCA (universal journal) | BKPF and BSEG |
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.