People and compliance on S/4HANA

Health, safety and environment incident on SAP S/4HANA

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.

SCREENSDATA HANDLERSS/4HANA · READ IN PLACES01 ReportS02 ClassificationS03 InvestigationS04 ActionsS05 Regulator reportS06 HSE boarddh_employeeEmployeePA0001 · PA0002 (SAP HCM) orSuccessFactorsdh_equipmentEquipmentEQUI · EQKT · ILOAdh_maintenance_orderMaintenance orderAUFK · AFIH · AFVCdh_cost_centerCost centerCSKS · CSKTdh_supplier_masterSupplier masterLFA1 · LFB1 · LFM1 (business partner inS/4)WRITE BACK TO S/4HANAMaintenance order → BAPI_ALM_ORDER_MAINTAINEquipment → BAPI_EQUI_CHANGErows stay in S/4HANA · access rules applied at read time · each write acknowledged and logged
The screens of the app, the data handler behind each, and the S/4HANA object it reads in place. Writes below the line go through released interfaces with an acknowledgement.
5
objects read in place from S/4HANA
catalogue
6
screens on those rows
catalogue
6 days
to production-grade
estimate
2
objects written back
catalogue
0
rows copied to build it
product
What the app reads

The S/4HANA objects behind each handler

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.

ObjectRead fromFields the app usesFreshness
EmployeePA0001 · PA0002 (SAP HCM) or SuccessFactorsPA0001.PERNR (id) · PA0002.VORNA + NACHN (name) · PA0001.ORGEH (org unit) · PA0001.PLANS (position)live; change capture where enabled
EquipmentEQUI · EQKT · ILOAEQUI.EQUNR (id) · EQKT.EQKTX (desc) · ILOA.TPLNR (location) · EQUI.SERNR (serial)live; change capture where enabled
Maintenance orderAUFK · AFIH · AFVCAUFK.AUFNR (number) · AFIH.EQUNR (equipment) · AUFK.AUART (type) · AFIH.PRIOK (priority)live; change capture where enabled
Cost centerCSKS · CSKTCSKS.KOSTL (id) · CSKT.KTEXT (name) · CSKS.VERAK (owner) · CSKS.BUKRS (company)live; change capture where enabled
Supplier masterLFA1 · LFB1 · LFM1 (business partner in S/4)LFA1.LIFNR (id) · LFA1.NAME1 (name) · LFA1.LAND1 (country) · LFA1.SPERR (block)live; change capture where enabled
The trigger

The start criterion in S/4HANA's own fields

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.

Start

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.

What the app writes back

Through released interfaces

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.

ObjectWhat changesInterface
Maintenance ordermaintenance order created for a corrective action on the equipment, with the incident number as referenceBAPI_ALM_ORDER_MAINTAIN
Equipmentequipment set to out of service when the site manager takes it off lineBAPI_EQUI_CHANGE
Acknowledged and logged

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.

Access and prerequisites

What is in place before the first build

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.

  • An SAP user for the connector with read authorisation on the objects the app uses
  • The BAPIs the app writes with, enabled for that user
  • Network path to the application server (PrivateLink or VPN)
  • Change capture switched on for the objects that should refresh within minutes
Register the handlers5 objects from the catalog; each shows its rows at once.
Also on SAP ECC

The same app on SAP ECC

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.

ObjectOn S/4HANAOn SAP ECC
EmployeePA0001 · PA0002 (SAP HCM) or SuccessFactorssame infotypes
EquipmentEQUI · EQKT · ILOAsame tables
Maintenance orderAUFK · AFIH · AFVCsame tables
Cost centerCSKS · CSKTsame tables
Supplier masterLFA1 · LFB1 · LFM1 (business partner in S/4)LFA1/LFB1/LFM1 vendor master, XK01 via BAPI
Nearby

This app on other systems, and other apps on S/4HANA

Health, safety and environment incident on

Other apps on S/4HANA

Terms on this page

Near missAn event that could have caused injury or damage; reported and investigated like an incident.
Lost-time injuryAn injury that keeps the person away from work for at least 1 full shift; it usually requires a regulator report.
Read in placeThe rows stay in S/4HANA; the handler sends the filter and the columns and S/4HANA returns the matching rows.
Questions

Does this app copy data out of S/4HANA?

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.

What does S/4HANA need to allow?

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.

Can I run it on SAP ECC as well?

Yes. The screens, criteria and roles stay; the handlers are re-bound to the other system's objects, listed above.

See this app on your data

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.