Runs quality rules on live master data, routes each failing record to its steward with the fix options, and writes the correction back 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 | MARC.MMSTA (status) · MARC.PLIFZ (lead time) · MARA.MATNR (id) · MAKT.MAKTX (desc) | live; change capture where enabled |
| Supplier master | LFA1 · LFB1 · LFM1 (business partner in S/4) | LFM1.ZTERM (terms) · LFA1.LIFNR (id) · LFA1.NAME1 (name) · LFA1.LAND1 (country) | live; change capture where enabled |
| Customer master | KNA1 · KNB1 · KNVV | KNVV.VKORG (sales org) · KNA1.KUNNR (id) · KNA1.NAME1 (name) · KNA1.LAND1 (country) | live; change capture where enabled |
| Purchase order line | EKKO · EKPO · EKET · EKBE | EKKO.EBELN (number) · EKPO.EBELP (line) · EKKO.LIFNR (vendor) · EKPO.MATNR (material) | live; change capture where enabled |
In plain words: A record that fails one of the active quality rules, such as an active material with a lead time of 0, a supplier with empty payment terms, or a customer with an empty sales organisation.
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 (MARC.MMSTA = 'active' and MARC.PLIFZ = 0) or LFM1.ZTERM = '' or KNVV.VKORG = '' # the same criterion in canonical fields ({material.status} = 'active' and {material.lead_time} = 0) or {vendor.terms} = '' or {customer.sales_org} = ''
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 |
|---|---|---|
| Material master | field corrected through the material interface; exception flag recorded beside the record | BAPI_MATERIAL_SAVEDATA |
| Supplier master | payment terms, country or purchasing data corrected; duplicate flagged for deletion | BAPI_BUPA_CREATE_FROM_DATA · BAPI_VENDOR_* |
| Customer master | sales organisation data completed or corrected | BAPI_BUPA_* · BAPI_CUSTOMER_CHANGEFROMDATA1 |
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 |
| Supplier master | LFA1 · LFB1 · LFM1 (business partner in S/4) | LFA1/LFB1/LFM1 vendor master, XK01 via BAPI |
| Customer master | KNA1 · KNB1 · KNVV | same tables |
| Purchase order line | EKKO · EKPO · EKET · EKBE | 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.
