Lesson 1 of 6
EHS in SAP S/4HANA
10 min
Listen to this lesson
Environment, health and safety (EHS) is where an ERP system meets regulators most directly. An injury must be recorded the way the occupational safety regulator requires; a chemical may only be used on site once it has been approved; an air permit limits emissions; a product may only be sold where it is marketable and shipped with the right hazard information. SAP covers these processes in SAP S/4HANA Environment, Health, and Safety and SAP S/4HANA for product compliance. This course introduces both from the angle that matters most in a program: what has to be proven, and how.
The running example is Contoso Motor Co.'s Detroit plant (1710). Winding stators at work center WIND-10 uses an insulating varnish that is a flammable liquid; the plant has forklifts, presses and end-of-line electrical testing at TEST-10; and the aftermarket business in 1810 has started selling an electrical contact cleaner aerosol, CMC-CLN-020, alongside alternators. Monique, the Detroit EHS manager, owns the EHS processes in this course; she, the aerosol and all EHS figures are illustrative course data.
The capability map
SAP Learning also describes an occupational health application delivered as a repeatable customer solution, and analytics through SAP Analytics Cloud and Smart Business dashboards. Contoso's program scope covers incident management, health and safety management, environment management for the Detroit air permit, and product compliance for the aerosol.
Classic EHS and the move to S/4HANA
Many ECC customers ran classic EHS components: product safety with safety data sheets, dangerous goods management, industrial hygiene and safety, waste management. In SAP S/4HANA, several of them were available only under the compatibility scope, whose use rights end on a fixed date: for most items, May 31, 2026 under an on-premise license, and longer under a cloud subscription such as Contoso's RISE contract (check SAP Note 2269324 for the current date); selected Customer Service, LE-TRA and PP-PI items run to the end of 2030 on premise. The forward path is the newer EHS components and SAP S/4HANA for product compliance. A conversion therefore often includes a functional move inside EHS, with data migration and new processes, even when the rest of the system converts unchanged. Check the compatibility scope matrix in SAP Note 2269324 for each classic component you use.
| Area | Classic (ECC) | SAP S/4HANA direction |
|---|---|---|
| Safety data sheets | Product safety with report generation (WWI) | Product compliance: SDS authoring and distribution scope items |
| Dangerous goods | Dangerous goods management (classic) | Product compliance: dangerous goods classification and checks in the value chain |
| Incidents | Industrial hygiene and safety incident handling | EHS incident management |
| Risk assessment | Industrial hygiene and safety | EHS health and safety management |
| Environment | Varies; often outside SAP | EHS environment management |
Why EHS testing is different
In most areas, a defect means a wrong number that finance can correct. In EHS, a defect can mean an injury not reported within a legal deadline, a chemical used without approval, an aerosol shipped without dangerous goods documents, or a permit limit exceeded unnoticed. Regulators expect records to be complete, accurate and retrievable, and investigators will ask what the system showed and when. That makes EHS a regulated process in the sense of sap-tst-403: tests need traceability from requirement to evidence, and evidence must survive an audit.
What would you do?
Contoso's ECC system uses classic dangerous goods management for a handful of products. The conversion team proposes to "just convert it" and look at product compliance later. What should the test lead raise?
What goes wrong in testing
| Pitfall | Effect | Prevention |
|---|---|---|
| EHS tested by the project team only | Field users meet the apps first at go-live | Supervisors and operators record test incidents on real devices |
| Regulations not mapped to tests | Gaps found by an inspector, not a tester | Scope document with a test per requirement |
| Classic data left behind | Historic incidents or SDS versions missing after the move | Migration reconciliation for EHS records, with counts by type and year |
| EHS out of regression scope | Releases break checks nobody retests | EHS controls in the standard regression pack |
Program-level EHS testing pitfalls.
EHS records also have long retention periods. OSHA requires the 300 log, 300A summary and incident reports to be kept for five years after the year they cover, and exposure and medical records are kept much longer. When classic records move to new components, or stay in an archived ECC system, the program must show how they remain retrievable for those periods. Treat that as a requirement with its own test.
- SAP S/4HANA EHS covers incidents, health and safety, environment and management of change.
- SAP S/4HANA for product compliance covers marketability, dangerous goods and safety data sheets.
- Classic EHS components often need a functional move, not just a conversion.
- EHS is regulated: tests need traceability and audit-ready evidence.
Check your understanding · not graded
Lesson check
1. Which SAP S/4HANA capability manages safety data sheets and dangerous goods checks?
2. Why is a classic EHS component a concern in a conversion?
3. What makes EHS testing a regulated-testing problem?
4. Which note lists the compatibility scope status of classic components?