SAP S/4HANA EHS — Customer-Operated
Customer-operated SAP S/4HANA environmental compliance and safety incident-management capabilities.
4 sources checked by an editor on · Product website ↗
Read this page as JSON or Markdown.
Deployment terms: BYOC · control plane · data plane · private offer
· Open requirements shortlist · Estimate operating costs
Compare this listing with another →
What lands where
Supplied by
Vendor or project
Install the licensed SAP S/4HANA on-premise edition and configure the selected EHS components using SAP implementation guides
Runs in
Documented customer environment
SAP S/4HANA application stack with SAP HANA database and EHS Fiori applications
- AWS: Customer cloud account
- Azure: Customer cloud account
- Google Cloud: Customer cloud account
- AWS
- Azure
- Google Cloud
Servers / containers
Operated by
Your team
Customer manages the application and database infrastructure, installation, upgrades, access, backups and EHS configuration; agree implementation and support arrangements.
Deployment boundaries by provider
- AWS: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Customer-provided SAP S/4HANA deployment on AWS ↗ · Source checked 2026-11-12
- Azure: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
SAP S/4HANA infrastructure deployment on Azure ↗ · Source checked 2026-11-12
- Google Cloud: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
SAP S/4HANA reference architecture on Google Cloud ↗ · Source checked 2026-11-12
Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.
| Install method | Install the licensed SAP S/4HANA on-premise edition and configure the selected EHS components using SAP implementation guides |
|---|---|
| Infrastructure | Servers / containers Customer-operated SAP application and HANA database services run on provisioned infrastructure. This is the on-premise edition, separate from SAP-managed cloud services. |
| Licensing model | Commercial Only The listed on-premise edition uses SAP commercial software licensing. The official deployment comparison describes its perpetual-license model; the customer agreement defines the exact component rights. |
| License | Commercial SAP S/4HANA on-premise licensing; verify EHS component entitlements |
Buyer diligence
Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.
How to read these facts
Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.
4 of 12 fields researched (33%) · 2 documented · 2 unresolved. Evidence coverage is not a feature score.
- Single sign-on
Not confirmedEvidence and scope for Single sign-on
The reviewed EHS and deployment material does not establish the selected application UI, release and complete identity configuration. SAP platform authentication options require the actual Fiori/ABAP/GUI entry points and compatible identity components; do not infer a ready EHS federation setup from a generic SAP capability.
Customer-operated S/4HANA EHS identity deployment remains unconfirmed · Source ↗ · Reviewed 2026-11-21
Sources checked — unresolved · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
AWS Launch Wizard can provision SAP landscapes and install customer-provided supported S/4HANA software, including separate multi-instance/HA patterns. Supply licensed installation media and validate supported releases. This is underlying S/4HANA platform automation; EHS activation, business configuration and data migration remain separate.
Provider-documented S/4HANA deployment supporting the EHS parent platform; not a packaged EHS solution · Deployment artifact ↗ (Current AWS Launch Wizard supported SAP deployment guide) · Reviewed 2026-11-21
Documented · Editor reviewed.
- Minimum footprint / sizing
Not confirmedEvidence and scope for Minimum footprint / sizing
Launch Wizard selects resources from supplied SAP requirements; it does not establish an EHS-specific capacity baseline. Obtain certified S/4HANA/HANA sizing for application/database memory, batch/analytics, data volume and HA rather than interpreting supported maximum memory as a minimum.
S/4HANA EHS workload sizing remains unconfirmed · Source ↗ · Reviewed 2026-11-21
Sources checked — unresolved · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
SAP distinguishes customer-managed S/4HANA on-premise perpetual licensing from subscription-based Private Edition with SAP technical managed services. Do not substitute a cloud subscription for the customer-operated scope; EHS module rights and implementation pricing require the actual agreement.
S/4HANA on-premise deployment model; not a module-specific EHS quote · Source ↗ · Reviewed 2026-11-16
Documented · Editor reviewed.
Show all fields (8 not researched)
- Marketplace delivery
- Not researched Supply a public source.
- Cloud commitment eligibility
- Not researched Supply a public source.
- SCIM provisioning
- Not researched Supply a public source.
- Compliance attestations
- Not researched Supply a public source.
- Security controls
- Not researched Supply a public source.
- Air-gapped operation
- Not researched Supply a public source.
- Operating cost estimate
- Not researched Supply a public source.
- Release snapshot / cadence
- Not researched Supply a public source.
Scope & considerations
The on-premise edition is explicitly customer-installed and customer-operated. This entry covers its EHS components, not SAP-managed Cloud Private Edition or Public Edition. Check the selected release, component entitlements and implementation scope. Environmental reporting still requires configured requirements and reliable source data.
Category fit
- Energy & environmental compliance
- Environmental requirements, emissions calculations, compliance scenarios, deviations and reports for environmental authorities.
- Incident & investigation management
- Safety incident and near-miss capture, investigations, root-cause classifications and follow-up actions. This is industrial EHS scope, rather than a general legal investigation platform.
Compare within Energy & environmental compliance
- EarthSoft EQuIS Enterprise — Self-HostedSelf-hosted environmental data management with compliance monitoring, data validation, workflow automation and reporting.
- Azure
- FormKiQ Energy and Environmental Compliance Directory PublisherManage regulatory filings, environmental assessments, permit applications, and compliance reports with governed workflows and audit-ready records.
- AWS
These products address related workflows; read their category-fit notes before comparing scope. See all of Energy & environmental compliance →
Installation outline
- Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
- Review the vendor's installation documentation, required permissions and outbound data flows.
- Deploy to a non-production environment; configure identity, networking and monitoring.
- Test backup recovery and upgrades before promoting to production.
Evidence trail
Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.
- Deployment sourcesChecked
- Customer-operated on-premise installation and operations ↗help.sap.com
- Environment Management scope ↗help.sap.com
- Current incident-investigation configuration ↗help.sap.com
- Commercial model and deployment responsibilities ↗learning.sap.com
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- Customer-provided SAP S/4HANA deployment on AWS ↗ · AWS
Provider guide · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
AWS Launch Wizard provisions customer resources and can install customer-provided SAP S/4HANA software. Evidence covers the underlying S/4HANA platform; confirm EHS licensing, supported sizing, database and SAP release before deployment.
- SAP S/4HANA infrastructure deployment on Azure ↗ · Azure
Provider guide · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
Microsoft documents S/4HANA infrastructure in a customer Azure subscription. Evidence covers the platform hosting option; confirm EHS modules, SAP licensing, supported operating systems and software installation separately.
- SAP S/4HANA reference architecture on Google Cloud ↗ · Google Cloud
Provider guide · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
Google documents S/4HANA on SAP-certified Compute Engine infrastructure. This is platform hosting evidence; EHS functionality, licenses and supported SAP configurations still require confirmation.
- Customer-provided SAP S/4HANA deployment on AWS ↗ · AWS
- Infrastructure evidenceChecked
- Licensing evidenceChecked