Shows each supplier the forecast and open order lines for its parts, collects committed dates and quantities, and writes the confirmations onto the schedule lines 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 |
|---|---|---|---|
| Purchase order line | EKKO · EKPO · EKET · EKBE | EKES.EINDT (confirmed date) · EKET.EINDT (delivery date) · EKPO.MENGE (qty) · EKBE.MENGE where BEWTP = 'E' (received qty) | live; change capture where enabled |
| Forecast | PBIM · PBED (planned independent requirements) | PBIM.MATNR (material) · PBIM.WERKS (plant) · PBED.PDATU (period) · PBED.PLNMG (qty) | live; change capture where enabled |
| Supplier master | LFA1 · LFB1 · LFM1 (business partner in S/4) | LFA1.LIFNR (id) · LFA1.NAME1 (name) · LFA1.LAND1 (country) · LFA1.SPERR (block) | 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.MATNR (id) · MAKT.MAKTX (desc) · MARA.MTART (type) · MARC.WERKS (plant) | live; change capture where enabled |
In plain words: An open order line for the supplier's parts that is still awaiting a supplier confirmation, or whose confirmed date falls after the requested date; the Monday forecast release refreshes every part as well.
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 EKBE.MENGE where BEWTP = 'E' < EKPO.MENGE and (EKES.EINDT is blank or EKES.EINDT > EKET.EINDT) # the same criterion in canonical fields {po.received_qty} < {po.qty} and ({po.confirmed_date} is blank or {po.confirmed_date} > {po.delivery_date})
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 |
|---|---|---|
| Purchase order line | supplier confirmation written to the schedule line: committed date, committed quantity and reason | BAPI_PO_CHANGE · BAPI_PO_CREATE1 |
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 |
|---|---|---|
| Purchase order line | EKKO · EKPO · EKET · EKBE | same tables |
| Forecast | PBIM · PBED (planned independent requirements) | same tables |
| Supplier master | LFA1 · LFB1 · LFM1 (business partner in S/4) | LFA1/LFB1/LFM1 vendor master, XK01 via BAPI |
| Goods receipt | MATDOC (material documents) | MKPF and MSEG |
| Material master | MARA · MARC · MAKT | 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.
