Takes a safety or environmental incident from a report on a phone through classification, investigation and corrective actions to closure, with the regulator report where the rules require one.
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 |
|---|---|---|---|
| Employee | PA0001 · PA0002 (SAP HCM) or SuccessFactors | PA0001.PERNR (id) · PA0002.VORNA + NACHN (name) · PA0001.ORGEH (org unit) · PA0001.PLANS (position) | live; change capture where enabled |
| Equipment | EQUI · EQKT · ILOA | EQUI.EQUNR (id) · EQKT.EQKTX (desc) · ILOA.TPLNR (location) · EQUI.SERNR (serial) | live; change capture where enabled |
| Maintenance order | AUFK · AFIH · AFVC | AUFK.AUFNR (number) · AFIH.EQUNR (equipment) · AUFK.AUART (type) · AFIH.PRIOK (priority) | live; change capture where enabled |
| Cost center | CSKS · CSKT | CSKS.KOSTL (id) · CSKT.KTEXT (name) · CSKS.VERAK (owner) · CSKS.BUKRS (company) | 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 |
In plain words: Anyone on site submits S01 on the mobile screen, for an incident or a near miss.
This app starts from a screen, so the first read happens when the instance opens; the criteria on the arrows use the fields above.
Anyone on site submits S01 on the mobile screen, for an incident or a near miss. 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 |
|---|---|---|
| Maintenance order | maintenance order created for a corrective action on the equipment, with the incident number as reference | BAPI_ALM_ORDER_MAINTAIN |
| Equipment | equipment set to out of service when the site manager takes it off line | BAPI_EQUI_CHANGE |
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 |
|---|---|---|
| Employee | PA0001 · PA0002 (SAP HCM) or SuccessFactors | same infotypes |
| Equipment | EQUI · EQKT · ILOA | same tables |
| Maintenance order | AUFK · AFIH · AFVC | same tables |
| Cost center | CSKS · CSKT | same tables |
| Supplier master | LFA1 · LFB1 · LFM1 (business partner in S/4) | LFA1/LFB1/LFM1 vendor master, XK01 via BAPI |
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.