Tracks every part of a new product through the readiness gates each function owns, reading the material, BOM, routing, source, inspection and price records live until launch.
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 |
| Bill of materials | MAST · STKO · STPO | MAST.MATNR (parent) · STPO.IDNRK (component) · STPO.MENGE (qty) · STPO.DATUV (valid from) | live; change capture where enabled |
| Routing | PLKO · PLPO · CRHD | PLKO.PLNNR (group) · PLPO.VORNR (operation) · CRHD.ARBPL (work center) · PLPO.VGW01 (setup) | 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 |
| Inspection lot | QALS · QAMR · QAVE | QALS.PRUEFLOS (lot) · QALS.MATNR (material) · QALS.HERKUNFT (origin) · QAMR.MBEWERTG (result) | live; change capture where enabled |
| Price condition | A004 · A005 · KONP (condition records) · PRCD_ELEMENTS | A004.MATNR (material) · A005.KUNNR (customer) · KONP.KBETR (amount) · KONP.KONWA (unit) | live; change capture where enabled |
In plain words: The launch lead registers a new product with its target launch date and part numbers on S01.
This app starts from a screen, so the first read happens when the instance opens; the criteria on the arrows use the fields above.
The launch lead registers a new product with its target launch date and part numbers on S01. The instance then reads its rows from S/4HANA through the handlers above.
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 | plant status set to active for the launch plant when the launch is signed | BAPI_MATERIAL_SAVEDATA |
| Bill of materials | the released structure's valid-from aligned to the launch date | CSAP_MAT_BOM_MAINTAIN |
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 |
| Bill of materials | MAST · STKO · STPO | same tables |
| Routing | PLKO · PLPO · CRHD | same tables |
| Supplier master | LFA1 · LFB1 · LFM1 (business partner in S/4) | LFA1/LFB1/LFM1 vendor master, XK01 via BAPI |
| Inspection lot | QALS · QAMR · QAVE | same tables |
| Price condition | A004 · A005 · KONP (condition records) · PRCD_ELEMENTS | KONV for conditions |
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.
