SAP evolution
SAP’s evolution is the story of enterprise computing itself: from mainframes to client-server, from on-premise to cloud, and from disk-based databases to in-memory computing. Understanding this arc explains why today’s SAP landscape looks the way it does and where it is heading.
SAP is steadily moving customers to the cloud, offering S/4HANA in private and public cloud editions and packaging migration under "RISE with SAP.
- The most important evolution for practitioners is ECC to S/4HANA.
- Mainframe (R/2): centralised, monolithic.
- Client-server (R/3): three-tier, scalable on commodity hardware.
- Watch out: Treating S/4HANA as just an upgrade, it is a re-platforming with real change.
Architectural evolution
- Mainframe (R/2): centralised, monolithic.
- Client-server (R/3): three-tier, scalable on commodity hardware.
- Web/NetWeaver: integration, portals, web services.
- In-memory (HANA): transactions and analytics on one engine.
- Cloud (S/4HANA Cloud, RISE): managed, subscription-based delivery.
From ECC to S/4HANA
The most important evolution for practitioners is ECC to S/4HANA. S/4HANA simplifies the data model (for example, one universal journal table, ACDOCA, replaces many separate finance tables), removes redundant aggregates that HANA can compute on the fly, and layers Fiori over the classic SAP GUI. This is not a cosmetic upgrade; it changes how you configure, extend and report.
The cloud shift and RISE with SAP
SAP is steadily moving customers to the cloud, offering S/4HANA in private and public cloud editions and packaging migration under "RISE with SAP." The direction is clear: subscription, managed infrastructure, faster innovation cycles, and a clean-core philosophy that keeps custom code out of the standard system.
Common pitfalls
- Treating S/4HANA as just an upgrade, it is a re-platforming with real change.
- Ignoring the clean-core principle, heavy custom code complicates cloud moves.
- Assuming on-premise is the future, the momentum is toward cloud.