- SAP Managed Tags
Integrating SAP EHS Public Cloud: Extending Your Existing Landscape Side-by-Side - Guidebook
Part 1: Introduction & Overview
Table of Contents:
- 1. Introduction: SAP EHS in the Public Cloud
- 1.1 Objective & Approach
- 1.2 What can you expect from this Blog Series?
- 1.3 Why SAP Environment, Health & Safety (EHS) Matters?
- 1.4 Why SAP EHS in the Public Cloud?
- 2. Integrating SAP EHS Public Cloud Side-by-Side (Guidebook)
- 2.1 Scope
- 2.1.1 Incident Management
- 2.1.2 Risk Management
- 2.1.3 Emissions Management
- 2.1.4 Lessons Learned
- 2.2 System Landscape
- 2.2.1 Current State
- 2.2.2 Architectural Approach
- 2.3 Prerequisites
- 2.3.1 Technical Prerequisites
- 2.3.2 Organizational & Functional Prerequisites
- 2.3.3 Scope Activation
- 3. Engage with Us
Related Content:
Below is an overview of the planned blog series – each post focusing on a specific integration topic. Once published, the titles will be linked for direct access:
Integrating SAP EHS in the Public Cloud: Extending Your Existing Landscape Side-by-Side – Guidebook
| Part 1: Introduction & Overview | Link |
| Part 2: Integration of Employees from SAP SuccessFactors | Link |
| Part 3: Integration of Business Partners & Material from SAP Master Data Governance (MDG) | Link |
| Part 4: Integration of Functional Locations & Equipment from SAP S/4HANA On-Premise System | Link |
| Part 5: Extensibility Scenarios & Further Implementation | Link |
| Part 6: Summary & Outlook | Link |
1. Introduction: SAP EHS in the Public Cloud
SAP Environment, Health & Safety (EHS) helps organizations establish and maintain safe, sustainable, and compliant operations. The SAP EHS Public Cloud solution provides an integrated platform to manage environmental, occupational health, and safety processes more efficiently and transparently.
1.1 Objective & Approach
With the growing relevance of SAP Environment, Health & Safety (EHS) in the Public Cloud, the objective of this blog series is to support the SAP Community by sharing our practical insights, lessons learned, and best practices from real project experience at Deloitte. We aim to provide a hands-on, experience-based guide that highlights both opportunities and key considerations for integrating SAP EHS Public Cloud into existing system landscapes.
We have implemented and extended SAP EHS Public Cloud across multiple customer environments. Based on this experience, we outline a step-by-step approach to help organizations successfully set up and integrate SAP EHS Public Cloud side-by-side with existing SAP solutions such as SAP S/4HANA On-Premise, SAP Master Data Governance (MDG), and SAP SuccessFactors.
This guidebook forms the foundation for the blog series. It demonstrates the architecture and approach we used in our internal proof-of-concept setup together with SAP, where we tested core EHS use cases – Incident Management, Risk Management, and Emissions Management – in a hybrid system landscape. Each part of the series focuses on one integration area, including practical implementation steps, lessons learned, and recommendations for EHS practitioners, architects, and sustainability professionals.
1.2 What can you expect from this Blog Series?
This blog series provides a structured, step-by-step guide on how to integrate SAP Environment, Health & Safety (EHS) Public Cloud side-by-side with existing SAP landscapes. Each article focuses on one key integration scenario, combining technical setup with practical, real-life application examples.
You will gain:
- Hands-on integration guidance
- Architectural best practices
- Real-world lessons learned from project experience
- End-to-end scenarios across the most relevant EHS use cases
1.3 Why SAP Environment, Health & Safety (EHS) Matters?
Sustainability, regulatory compliance, and employee well-being have become key drivers for long-term business success. At the same time, organizations face increasing challenges from business disruptions caused by regulatory changes, workplace incidents, and a continuously changing environment – requiring them to constantly adapt and adjust their operations. SAP EHS ensures that companies not only meet legal requirements but also foster a culture of responsibility and care. A well-implemented EHS strategy helps minimize risks, reduce incidents, and protect both people and the environment.
For a detailed overview of SAP EHS capabilities and features, we recommend exploring the official SAP documentation and Learning Journey (read more).
1.4 Why SAP EHS in the Public Cloud?
Transitioning SAP Environment, Health & Safety (EHS) to the SAP Public Cloud provides organizations with a modern and continuously evolving platform to manage sustainability, compliance, and safety processes more efficiently. With frequent feature and regulatory updates delivered by SAP, companies benefit from the latest innovations without the need for complex upgrades or custom maintenance.
A key advantage of SAP EHS in the Public Cloud is its ability to integrate seamlessly with existing SAP system landscapes. Organizations can extend their current on-premise or private cloud environments without disruption, connecting SAP EHS Public Cloud side-by-side with core ERP solutions such as SAP S/4HANA, SAP Master Data Governance (MDG), or SAP SuccessFactors. This ensures consistent data flows, unified reporting, and a holistic view of environmental, health, and safety performance across the enterprise.
From a business perspective, SAP EHS in the Public Cloud accelerates implementation, reduces total cost of ownership, and supports standardized processes and global compliance frameworks. At the same time, it offers the flexibility needed to adapt to evolving local regulations and sustainability requirements.
SAP Environment, Health & Safety (EHS) supports a wide range of processes that help organizations manage safety, health, and environmental requirements in an integrated and efficient way. Leveraging the Public Cloud, companies can standardize processes, ensure continuous compliance, and gain transparency across locations. The core capabilities range from incident reporting and risk assessment to chemical and emissions management.
2. Integrating SAP EHS Public Cloud Side-by-Side (Guidebook)
Now that we have introduced SAP EHS and its value in the Public Cloud, this chapter explains how SAP EHS Public Cloud can be integrated into an existing enterprise system landscape side-by-side.
This section provides a practical guide on how to extend current on-premise or hybrid EHS capabilities with SAP Public Cloud innovations – without disrupting existing business processes.
We outline the system setup, architectural approach, and key technical prerequisites required for a successful implementation. The guide is based on our internal proof-of-concept, developed together with SAP and validated across three core EHS use cases.
By following this approach, organizations can understand how to seamlessly connect SAP EHS Public Cloud with their existing SAP solutions and build a scalable, future-ready, and compliant EHS environment.
2.1 Scope
In this guidebook, we focus on three core use cases that represent the most common and business-relevant EHS scenarios for our clients, making it ideal to demonstrate the side-by-side integration approach:
- Incident Management
- Risk Management
- Emissions Management
For detailed feature descriptions and configuration guidance, please refer to the official SAP EHS documentation and Learning Journey (read more).
By concentrating on these use cases, we provide a clear overview of how SAP EHS Public Cloud can be integrated with an existing SAP landscape. Each scenario highlights key integration touchpoints, master data synchronization, and cross-process reporting requirements – without adding unnecessary complexity.
To illustrate these use cases in a practical and relatable way, we will refer to a fictional company, Mike Machineries, throughout this guidebook. This example helps demonstrate process flows, integration touchpoints, and system interactions in a realistic business context.
Fictional Organization: Mike Machineries
Mike Machineries is a growing producer of high-quality coffee machines, headquarted in the United States with expanding operations in Europe. Founded in 2024, the company focuses on delivering premium engineering, advanced brewing technology, and an elegant product design for professional coffee environments.
The company is committed to:
- delivering exceptional product quality and reliable performance,
- providing state-of-the-art technology for consistent brewing results, and
- ensuring safe and sustainable operations across all production sites.
As part of its cloud-first strategy, Mike Machineries is investing in operational excellence, compliance, and digital transformation – including the adoption of SAP EHS Public Cloud.
2.1.1 Incident Management
Incident Management in SAP EHS supports organizations in capturing, assessing, and tracking workplace incidents, near misses, and safety-related events. Standardized workflows enable structured investigations and help define corrective and preventive actions. With SAP EHS in the Public Cloud, incident data becomes centrally, accessible, improving transparency, responsiveness, and cross-site collaboration (read more).
Business Process
User Scenario (A) - Incident Management
During a routine maintenance task at the Mike Machineries production facility in Hamburg, an internal maintenance technician slipped on spilled oil near a coffee machine assembly unit and suffered a minor injury. A nearby colleague witnessed the incident and immediately reported the event in SAP EHS Public Cloud via the Initial Incident Entry.
As the Incident involved a workplace injury, a First Aider on site recorded the medical details in an Injury/Illness Log Entry. Based on these entries, the system automatically created an Incident Report and notified the responsible Incident Manager, who reviewed the information and initiated the incident process.
As part of the investigation, relevant statements were collected, the work environment was assessed, and supporting evidence such as photos and maintenance instructions was documented. The root cause analysis revealed that the injury occurred due to an oil spill caused by a minor leak at the test station and insufficient signage during maintenance activities.
Corrective and preventive actions were defined, including immediate cleaning and leak repair, improved floor marking around the test station, and reinforcing safety instructions for technicians handling maintenance tasks. Once the actions were completed and validated, the Incident Manager finalized the documentation and completed the required reporting in SAP EHS Public Cloud.
2.1.2 Risk Management
Risk Management is a key element of proactive safety and environmental protection. SAP EHS provides tools to identify potential hazards, assess their severity and likelihood, and define appropriate mitigation measures. Using structured risk matrices and standardized assessment logic, organizations can continuously evaluate and minimize risks across their operations, strengthening safety awareness and accountability (read more).
Business Process
User Scenario (B) - Risk Management
At Mike Machineries production facility in Stuttgart, a new industrial cleaning solvent named “Precision Parts Cleaning Solvent X42” was introduced for maintaining high-precision coffee machine components. During a routine safety walk, a supervisor noticed a strong chemical vapors in the maintenance area and observed that technicians were not consistently using the required personal protective equipment (PPE) when handling the solvent. The hazard was reported in SAP EHS Public Cloud, including the supplier details and safety data sheet (SDS) for traceability.
The hazard was added to an existing Risk Assessment Project on “Chemical Handling and Storage Safety”. An Industrial Hygienist conducted the risk assessment, reviewing the solvent’s properties, exposure, risks, flammability, and current working conditions. Based on these factors, the inherent risk was classified as “high”, and several mitigation measures were defined including:
- improving ventilation in the chemical handling area,
- enforcing mandatory PPE usage for all employees handling the solvent,
- updating SDS documentation and conducting refresher training for technicians,
- implementing stricter storage and labelling requirements, and
- arranging a follow-up with the supplier to explore safer substitute products.
A Control Inspection was performed to verify the implementation of the safety measures. Once completed, the residual risk was reduced to “medium-to-low” and considered acceptable. The risk assessment was formally closed in SAP EHS Public Cloud. Key learnings and updated chemical-handling procedures were shared across all Mike Machineries sites to strengthen preventive safety practices.
2.1.3 Emissions Management
With Emissions Management, SAP EHS provides a comprehensive solution to record, calculate, and monitor environmental impacts such as air emissions, wastewater, or waste generation. Companies can track key environmental indicators, meet regulatory reporting requirements, and ensure ESG compliance with confidence. By integrating production and logistics data, emissions reporting becomes more accurate, consistent, and audit-ready (read more).
Business Process
User Scenario (C) - Emissions Management
At the Mike Machineries production facility in Dublin, the Environmental Manager is responsible for ensuring compliance with local air emission regulations. One of the main emission sources on site is a gas-fired roasting unit used to treat metal components before assembly. The unit operates at a designated Functional Location and requires regular monitoring of nitrogen oxide (NOx) emissions. To ensure compliance, the Environmental Manager prepared the annual emissions monitoring plan, including sampling intervals, measurement methods, and required documentation.
An Environmental Technician carried out the data collection, sampling exhaust gases from the roasting unit and recording gas consumption and operating hours. The supplier-provided material data was included to support emission factor calculations. The Environmental Manager then calculated and aggregated the emissions data in SAP EHS Public Cloud. During data monitoring, a deviation was identified: the recorded NOx emissions exceeded the permitted limit for the quarter.
An investigation was initiated to determine the cause of the deviation, revealing that a burner component had degraded over time, reducing combustion efficiency. A Corrective Action Plan was defined, including:
- replacing the defective burner component
- requesting additional guidance from the supplier regarding optimal combustion settings,
- training operating staff to monitor early signs of inefficient combustion, and
- updating maintenance schedules for more frequent inspections.
Once the actions were completed and verified, a follow-up measurement confirmed that emissions had returned to compliant levels. The case was formally closed in SAP EHS Public Cloud. Key findings were shared with the Sustainability and Operations teams across all sites to support continuous improvement and maintain alignment with environmental objectives.
2.1.4 Lessons Learned
Based on the user scenarios A, B, and C, four core integrations play an essential role in enabling end-to-end EHS processes:
- Human Resources (HR) – employee & organizational data
- Business Partner (BP) – business entity information
- Material Management (MM) – material & product data
- Plant Maintenance (PM) – technical objects such as Functional Locations & Equipment
The upcoming blog posts will focus on these four integration areas and demonstrate how SAP EHS Public Cloud can seamlessly embed into a hybrid SAP landscape.
2.2 System Landscape
To successfully integrate SAP EHS Public Cloud into an existing SAP environment, it is essential to understand the current system landscape and define a clear architecture. A well-designed setup ensures seamless data exchange, process consistency, and scalable integration that supports both cloud innovation and existing on-premise operations.
2.2.1 Current State
These environments often run mature EHS capabilities such as incident tracking, risk assessments, and compliance reporting. As companies move toward more agile and innovation-driven operating models, many are now exploring hybrid landscapes that combine existing on-premise EHS processes with SAP EHS Public Cloud.
This approach allows organizations to retain existing configurations and data while gradually adopting modern cloud capabilities – without disrupting operations. It provides a flexible transition path towards a scalable and future-ready EHS solution.
To simulate this real-world scenario, we have built an integrated demo landscape that reflects a typical enterprise setup and supports the side-by-side integration of SAP EHS Public Cloud. The landscape includes the following key components:
SAP S/4HANA Public Cloud
SAP S/4HANA Public Cloud is the core platform for SAP EHS. It provides standardized and continuously updated EHS capabilities for incident management, risk assessments, and emissions tracking – without the need for technical upgrades.
SAP S/4HANA On-Premise
SAP S/4HANA On-Premise remains the established backbone for many customers with existing ERP modules and processes. Integrating EHS Public Cloud side-by-side allows organizations to keep their current setup while gradually adopting cloud innovations.
SAP Master Data Governance (MDG)
SAP MDG ensures consistent, high-quality master data across the landscape. For EHS, MDG plays a key role in harmonizing Business Partner and Material data to support accurate reporting, risk assessments, and compliance processes.
SAP SuccessFactors
SAP SuccessFactors provides the HR foundation for EHS. By integrating SuccessFactors with EHS Public Cloud, organizations can leverage employee and organizational data for incident reporting, safety roles, and occupational health-related processes.
SAP Business Technology Platform (BTP) / SAP Integration Suite
SAP Business Technology Platform (BTP) provides the foundation for integration and extension in a side-by-side EHS scenario. Within BTP, the SAP Integration Suite enables secure data exchange between SAP EHS Public Cloud and existing SAP systems such as SAP S/4HANA On-Premise, SAP MDG, and SAP SuccessFactors. This setup ensures smooth interoperability in hybrid landscapes, supports process automation, and allows innovations through extensions and APIs.
2.2.2 Architectural Approach
Our demo landscape follows a side-by-side integration model that connects SAP EHS Public Cloud with existing SAP systems through the SAP Integration Suite within the SAP Business Technology Platform (BTP). This architecture enables end-to-end EHS processes across cloud and on-premise environments, covering Incident Management, Risk Management, and Emissions Management.
In this setup, SAP EHS Public Cloud acts as the central application layer where the core EHS processes are executed.
Employee data is retrieved from SAP SuccessFactors through standard integration scenarios via SAP Integration Suite / Cloud Platform Integration (CPI), ensuring alignment of roles, responsibilities, and reporting hierarchies with SAP EHS Public Cloud. This supports consistent approval flows and clear accountability in EHS processes.
Foundational master data such as Business Partner and Material Master is governed in SAP Master Data Governance (MDG) and replicated to SAP EHS Public Cloud to ensure consistency of key business information across the landscape. For the MDG integration, organizations can use either IDoc or Web Service interfaces:
- IDoc-based integration is typically used for older SAP release versions or existing, established integration landscapes (generally prior to the SAP S/4HANA 2020 FPS02 release).
- Web Service-based integration is considered best practice for more recent releases, offering a more flexible, scalable, and service-oriented data exchange approach (SAP S/4HANA 2020 FPS02 and onwards).
If additional mapping, transformation, or orchestration of API data is required, companies may optionally introduce the SAP Integration Suite / CPI as middleware. In our demo landscape, we implemented a direct Web Service integration between SAP MDG and SAP EHS Public Cloud.
Technical objects, including Functional Location and Equipment, originate from SAP S/4HANA On-Premise (Plant Maintenance) and are integrated into the cloud using a customized iFlow via SAP Integration Suite / CPI as there is currently now standard interface available. This allows customers to reuse existing maintenance structures and align technical object data with EHS processes in the Public Cloud.
Overall, this side-by-side setup reflects a realistic enterprise architecture and demonstrates how SAP EHS Public Cloud can be embedded into an existing SAP system landscape without disruption – enabling scalability, transparency, and continuous innovation.
2.3 Prerequisites
Before integrating SAP EHS Public Cloud side-by-side with an existing SAP landscape, a number of technical and organizational prerequisites should be in place to ensure a smooth setup, secure connectivity, and reliable end-to-end process execution.
2.3.1 Technical Prerequisites
The following components are required to enable a stable and secure integration setup:
- SAP Business Technology Platform (BTP) as the central foundation for integration and extension, providing services such as API Management, Event Mesh for even-driven communication, and hosting the SAP Integration Suite.
- SAP Integration Suite – Cloud Platform Integration (CPI) subscription and configuration to support exchange between SAP S/4HANA On-Premise, SAP EHS Public Cloud, SAP MDG, and SAP SuccessFactors. Standard and/or custom integration flows should be aligned with the intended scope.
- Activation of the required scope items within – Central Business Configuration (CBC) – to enable the corresponding integration scenarios:
- JB1 – Employee Integration from SAP SuccessFactors
- 1RO – Business Partner and Material Master Integration from SAP MDG
- 4HH – Functional Location & Equipment Integration (Plant Maintenance) from S/4HANA On-Premise
- Compatible system release levels across all connected solutions must be ensured to support the intended integration scenarios. For our demo setup, the following release versions were successfully used:
- SAP S/4HANA Public Cloud – 2508 release (current release)
- SAP S/4HANA On-Premise – SAP S/4HANA 2023 FPS02 release
- SAP Master Data Governance (MDG) – SAP S/4HANA 2023 SP00 release
- SAP SuccessFactors – 2505 release
- Secure connectivity and authorizations in place, including certificates, communication arrangements, and technical users for safe data transfer (Note: For our demo test landscape, certificates were not mandatory and Basic Authentication was used. For productive environments, certificate-based authentication is strongly recommended.)
2.3.2 Organizational & Functional Prerequisites
Several organizational aspects should be clarified early to avoid complexity during the implementation:
- Clear definition of the integration scope, including the selected EHS use cases to be included in the initial rollout (e.g., Incident Management, Risk Management, Emissions Management). For our demo, the following scope items were activated within SAP S/4HANA Public Cloud:
- 3FP for Incident Management
- 54A for Health & Safety Management (Risk Management)
- 4XD for Emissions Management
If further use cases are required, can be activated: (4C8 for Compliance Management / 4YX for Management of Change / 60H for Waste Management)
Note: Relevant organizational structures such as Company Code, Plant, and other required organizational units must be set up and maintained to ensure end-to-end process execution.
- Early stakeholder alignment between EHS process owners, IT architecture, and data governance to ensure technical decisions support business needs.
- Master data governance framework, particularly for Business Partner and Material data, to ensure consistent and high-quality master data across all systems.
- Test and validation strategy to confirm that end-to-end process flows function correctly after integration, including replication, authorization, and reporting.
2.3.3 Scope Activation
In SAP S/4HANA Public Cloud, only users with the Lead Configuration Expert role have authorization to view and maintain the solution scope. This role is responsible for managing the activation of scope items during the configuration phase using the SAP Central Business Configuration (CBC) tool or the Manage Your Solution app.
To enable the EHS integration scenarios described above, the relevant scope items must be activated in the system. This includes both EHS process scope items (3FP, 54A, 4XD) and the integration-related scope items (JB1, 1RO, 4HH).
The activation can be verified and performed as follows:
- Manage Your Solution: In the SAP S/4HANA Public Cloud, open the Manage Your Solution app from the SAP Fiori Launchpad and select View Solution Scope to review which scope items are currently active.
- SAP Central Business Configuration (CBC): Alternatively, in the Scope and Organizational Structure phase, navigate to the Activities tab and search for Define Scope. Choose Open to view and maintain scope settings directly in CBC.
- Requesting Activation: If a required scope item is not yet active, request its activation via BCP – Ticket Component: XX-S4C-OPR-SRV.
For a detailed explanation of the scope activation process and the responsibilities of the Lead Configuration Expert, refer to the SAP Learning Journey “Implementing SAP S/4HANA Cloud Public Edition” (topic area: Deploying Content in the SAP S/4HANA Cloud Starter System).
By fulfilling these prerequisites, organizations can establish a solid foundation for a reliable and scalable integration between SAP EHS Public Cloud and their existing SAP landscape – supporting a seamless transition towards a hybrid and future-ready EHS architecture.
3. Engage with Us
To follow the series, make sure to subscribe to the SAP EHS Public Cloud blog tag.
We welcome your thoughts and feedback in the comments!
Acknowledgements
This blog post series is the result of close collaboration within our EHS implementation team. I would like to express my sincere appreciation to my colleagues, whose expertise, insights, and project experience significantly contributed to the depth and quality of this guide.
A special thank you goes to:
Their contributions were instrumental in shaping the content of this blog post. I am truly grateful for their collaborations and support.
Bluesky| User | Count |
|---|---|
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
