Runs the daily shortage meeting on live projected stock: planning, sourcing, sales and the plant allocate scarce components to orders and write the decisions to 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 |
|---|---|---|---|
| Material master | MARA · MARC · MAKT | MARA.MATNR (id) · MAKT.MAKTX (desc) · MARA.MTART (type) · MARC.WERKS (plant) | live; change capture where enabled |
| Stock position | MARD · MCHB · MATDOC_EXTRACT | MARD.LABST (on hand) · MARD.MATNR (material) · MARD.WERKS (plant) · MARD.LGORT (sloc) | live; change capture where enabled |
| Purchase order line | EKKO · EKPO · EKET · EKBE | EKPO.MENGE (qty) · EKBE.MENGE where BEWTP = 'E' (received qty) · EKKO.EBELN (number) · EKPO.EBELP (line) | live; change capture where enabled |
| Production order | AFKO · AFPO · AFVC | AFPO.PSMNG (qty) · AFKO.AUFNR (number) · AFPO.MATNR (material) · AFKO.GSTRP (start) | 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 |
| Bill of materials | MAST · STKO · STPO | MAST.MATNR (parent) · STPO.IDNRK (component) · STPO.MENGE (qty) · STPO.DATUV (valid from) | live; change capture where enabled |
In plain words: Each working day at 07:00 the app projects stock for every component on the critical list; a component whose projected stock falls below 0 within 4 weeks is on that day's agenda.
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 MARD.LABST + (EKPO.MENGE - EKBE.MENGE where BEWTP = 'E' due within 28 days) < demand from AFPO.PSMNG and VBAP.KWMENG within 28 days # the same criterion in canonical fields {stock.on_hand} + ({po.qty} - {po.received_qty} due within 28 days) < demand from {prod_order.qty} and {so.qty} within 28 days
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 |
|---|---|---|
| Production order | start and finish dates changed to the allocation | BAPI_PRODORD_CHANGE · BAPI_PRODORDCONF_CREATE_TT |
| Purchase order line | pull-in date and quantity changed on the schedule line; premium buy added as a new line | BAPI_PO_CHANGE · BAPI_PO_CREATE1 |
| Sales order line | confirmed quantity and date updated on the customer order | BAPI_SALESORDER_CHANGE · BAPI_SALESORDER_CREATEFROMDAT2 |
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 |
|---|---|---|
| Material master | MARA · MARC · MAKT | same tables |
| Stock position | MARD · MCHB · MATDOC_EXTRACT | MARD · MCHB · MBEW |
| Purchase order line | EKKO · EKPO · EKET · EKBE | same tables |
| Production order | AFKO · AFPO · AFVC | same tables |
| Sales order line | VBAK · VBAP · VBEP | same tables |
| Bill of materials | MAST · STKO · STPO | 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.
