SAP EHS Public Cloud: Extending Your Existing Landscape Side-by-Side - Guidebook (Part 6)

[duynguyendeloitte]

Integrating SAP EHS Public Cloud: Extending Your Existing Landscape Side-by-Side - Guidebook

Part 6: Summary & Outlook

Table of Contents:

• 1. Summary
• 2. Benefits & Pitfalls
• 2.1 Benefits
• 2.2 Pitfalls
• 2.3 Summary of Benefits & Pitfalls
• 3. Outlook
• 4. 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. Summary

In this blog series, we shared our hands-on experience from multiple SAP EHS Public Cloud projects that were implemented in a hybrid, side-by-side landscape. Across Parts 1 to 5, we covered the integration of Employees, Business Partners, Materials, Functional Locations, and Equipment, as well as practical extensibility scenarios from real customer use cases.

What became very clear throughout these projects is that SAP EHS Public Cloud works best when three things come together:

• Consistent master data,
• Standardized integration content,
• And a disciplined clean-core extensibility strategy.

In practice, we saw that missing or inconsistent master data was the most common root cause for broken end-to-end EHS processes (far more critical than any technical limitation). Once HR data, business partners, materials and assets were properly aligned across systems, incident reporting, emissions calculations, and follow-up processes became significantly more stable and transparent.

Another key learning was that standard communication scenarios and scope items save a tremendous amount of time and risk. Whenever we were able to rely on delivered content instead of custom interfaces, implementation effort, testing effort, and long-term maintenance were reduced noticeably.

Finally, extensibility played an important role in every single project. While most requirements could be solved using in-app Key User Extensibility, it was essential to define clear governance early on to avoid country-specific deviations and long-term technical debt.

This final part summarizes the key benefits and pitfalls we repeatedly encountered and shares our outlook on how SAP EHS in the Public Cloud will continue to evolve based on what we see today in real projects.

2. Benefits & Pitfalls

Integrating SAP EHS as part of a hybrid SAP S/4HANA Public Cloud landscape delivers strong business value but it also introduces architectural and organizational challenges that need to be managed carefully. In this chapter, we summarize the most important benefits and pitfalls we encountered across different customer projects.

2.1 Benefits

Fast Access to Innovation through Public Cloud Releases & AI

One of the strongest benefits we experienced in our projects was the direct access to new EHS functionality without classical upgrade projects. Unlike on-premise systems with long release cycles, customers benefit immediately from:

• Regular Public Cloud releases and micro deliveries
• Fast availability of new EHS features and regulatory content
• Immediate access to SAP’s latest AI-driven innovations in EHS scenarios

This had a noticeable impact on time-to-value. Instead of waiting months for technical upgrades, functional improvements became available continuously. For several customers, this was also the first time AI-supported features in the EHS context could be evaluated productively.

Data Consistency and Compliance

A unified master data landscape turned out to be one of the biggest success factors across all projects. By integrating:

• Employee data from SAP SuccessFactors
• Business Partners & Materials from SAP MDG
• Functional Locations and Equipment from SAP S/4HANA On-Premise

We ensured that EHS processes consistently relied on harmonized and validated master data. In practice, this was essential for:

• Accurate incident reporting,
• Reliable emissions calculations,
• Correct assignment of responsibilities and workflows,
• Audit-proof regulatory documentation.

Where master data was incomplete or inconsistent, downstream EHS processes were immediately affected.

Hybrid Architecture without Disruption

The side-by-side approach allowed customers to adopt EHS innovations in the Public Cloud without shutting down their existing on-premise environments. This enabled:

• Gradual modernization instead of big-bang migrations,
• Reduced transformation risk,
• Protection of critical operational processes.

From a project perspective, this phased approach proved to be far more controllable than technical full-system replacements.

Standardized Interfaces and Scope Items

Whenever we could rely on standard SAP communication scenarios and scope items, the implantation became significantly faster and more stable. Examples include:

• SAP_COM_0001, 0008, 0009, 0395
• EHS scope items such as 3FP (Incident Management), 4XD (Emissions Management), and 54A (Health & Safety Management)

These accelerators reduced custom development effort, simplified testing, and aligned customer landscapes with SAP best practices.

Scalability and Future Readiness

The event-driven and API-first architecture of the Public Cloud supported scalable growth across all projects. Typical examples were:

• Near real-time updated via SAP Integration Suite and Event Mesh,
• Flexible replication cycles for HR and MDG data,
• Cloud-native extensibility for future EHS enhancements.

This ensured that the technical foundation remained adaptable as regulatory and sustainability requirements continued to evolve.

Extensibility for Business and Regulatory Needs

Across all customers, extensibility was required mainly for country-specific regulations, additional validations, or customer-specific reporting. In most cases, these requirements could be fulfilled using Key User (In-App) Extensibility, without breaking the clean core. This allowed customers to remain upgrade-stable while still meeting local compliance needs.

2.2 Pitfalls

Despite the strong benefits, several recurring challenges also appeared in almost every project.

System Landscape Complexity

Hybrid landscapes naturally involve multiple systems: SAP S/4HANA Public Cloud, SAP S/4HANA On-Premise, SAP MDG, SAP SuccessFactors, and SAP BTP / Integration Suite. Without clear integration ownership, defined interface responsibilities, and coordinated technical design, landscapes quickly became difficult to operate and monitor.

Dependency on Master Data Quality

EHS processes are extremely sensitive to master data issues. We repeatedly saw how missing materials, outdated organizational requirements, or incorrect functional locations immediately blocked emissions calculations, risk assessments, and incident follow-ups. High master data quality is mandatory.

Custom Development Where Standard Content Is Missing

For some integration scenarios, especially Plant Maintenance integration for Functional Location and Equipment, custom iFlows were still required. This introduced additional development effort, higher testing effort, and long-term maintenance overhead.

Monitoring Challenges

End-to-end monitoring must cover:

• SAP S/4HANA Public Cloud application logs
• SAP S/4HANA On-Premise applications logs
• SAP Master Data Governance application logs
• SAP SuccessFactors message monitoring
• SAP Integration Suite / iFlow monitoring

In several projects, missing monitoring initially led to delayed error detection and avoidable compliance risks.

Value Mapping and Harmonization

Incorrect or inconsistent value mappings between systems repeatedly caused replication failures. Early harmonization of organizational units, material types, equipment categories proved to be critical.

Validation of Services and Scope Items

Missing API activations or scope item assignments (e.g., API_EQUIPMENT or API_FUNCTIONALLOCATION) frequently caused delays late in the project. Early validation of all required services became a key project success factor.

Governance and Limitations of Extensibility

Extensibility offers flexibility but without governance it quickly leads to:

• Diverging country solutions,
• Misaligned business logic
• And long-term technical debt.

Additionally, Developer Extensibility is still limited to released APIs and BAdIs, which means that not every requirement can be solved purely with custom logic.

2.3 Summary of Benefits & Pitfalls

A successful EHS Public Cloud implementation balances the strengths of standardized integration content and clean-core extensibility with disciplined data governance and architectural planning. Organizations that manage this balance effectively can unlock the full potential of SAP EHS – enabling safe, compliant, and scalable EHS operations across the enterprise.

3. Outlook

Based on what we observe across current customer projects and SAP’s latest roadmap updates, SAP EHS in the Public Cloud is clearly evolving from a standalone compliance solution toward a central digital backbone for safety, risk, and environmental governance.

Many customers are already productive with core EHS scenarios today. At the same time, the functional scope continues to expand with each Public Cloud release. We see a strong move toward more standardized business content, broader regulatory coverage, and deeper support for environmental and sustainability-driven processes. As a result, future implementations will increasingly rely on configuration rather than custom development which significantly reduces implementation and upgrade effort.

Extensibility will nevertheless remain a key success factor. From our project experience, SAP is steadily increasing both the number and the quality of released APIs and cloud-compliant BAdIs. This allows customers to address local regulatory requirements and  compliant-specific validation logic in a clean-core compatible way. Especially Key User Extensibility is becoming more powerful, enabling business-driven adjustments without technical development.

In parallel, SAP BTP is gaining further importance for advanced EHS use cases. While this blog series focused on On-Stack Extensibility, we already see growing demand for advanced analytics and dashboards, cross-system workflow automation, and IoT-based hazard detection and emissions monitoring. These scenarios clearly go beyond standard transactional processing and position SAP BTP as a natural complement to SAP EHS in complex enterprise landscapes.

Another major trend we observe is the increasing convergence of EHS and sustainability. Environmental compliance, emissions management, and sustainability reporting are becoming tightly connected. From a solution perspective, this strengthens the integration between SAP EHS, SAP Sustainability Footprint Management, and SAP Sustainability Control Tower. Customers will benefit from more consistent emissions data, integrated compliance reporting, and harmonized master data across production, procurement, and asset management.

For customers, these developments reinforce one central message from our project work: Early architectural discipline pays off. Organizations that invest early in clean-core principles, standardized integration content, high master data quality, and clear extensibility governance are best positioned to benefit from future SAP innovations.

4. 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:

• @Westphal 
• @qkroiss 
• @asutoshmaharana2326 
• @kanwal_singh
• @Suraj_Ashray1 

Their contributions were instrumental in shaping the content of this blog post. I am truly grateful for their collaborations and support.