SAP editions
SAP S/4HANA comes in several editions, and choosing the right one shapes everything from cost and customisation to upgrade cadence. The main split is on-premise versus cloud, with cloud further divided into private and public.
Across all editions SAP pushes a "clean core" model: keep the standard system unmodified and build extensions on BTP or via approved in-app extensibility.
- On-premise and private cloud give you deep customisation but more responsibility; public cloud gives you a standardised…
- S/4HANA (on-premise): you run and manage everything; maximum control and customisation, full responsibility for infrastructure and…
- S/4HANA Cloud, private edition: a single-tenant cloud system managed by SAP (often via RISE), close to on-premise capability with…
- Watch out: Choosing public cloud for highly bespoke processes that need heavy customisation.
The main editions
- S/4HANA (on-premise): you run and manage everything; maximum control and customisation, full responsibility for infrastructure and upgrades.
- S/4HANA Cloud, private edition: a single-tenant cloud system managed by SAP (often via RISE), close to on-premise capability with cloud operations.
- S/4HANA Cloud, public edition: multi-tenant SaaS with standardised processes, quarterly innovation, and limited (extension-based) customisation.
The trade-off: control versus simplicity
On-premise and private cloud give you deep customisation but more responsibility; public cloud gives you a standardised, always-current system with far less to manage, at the cost of flexibility. The right choice depends on how unique your processes truly are.
Clean core and extensibility
Across all editions SAP pushes a "clean core" model: keep the standard system unmodified and build extensions on BTP or via approved in-app extensibility. This keeps upgrades smooth and is essential in the cloud editions where you cannot freely modify the core.
Common pitfalls
- Choosing public cloud for highly bespoke processes that need heavy customisation.
- Assuming cloud means no work, configuration and change management still apply.
- Ignoring clean core, over-customising complicates every future upgrade.