From five founders and a real-time idea to the operating system of the world economy — and into the Cloud ERP era. Six eras, five decades, one recurring pattern: every architectural generation redefined not just the software but the commercial relationship between SAP and its customers. Every dated claim below carries a reference; where the evidence is a search extract of a page that could not be opened directly, the entry says so. The domain-level counterpart: the history of SAP transportation management.
Five engineers leave IBM with a conviction the industry does not yet share: enterprises should not each write their own software. Standard software, integrated processes, data processed as it happens — the founding idea is the product strategy SAP still runs on.
Dietmar Hopp, Hasso Plattner, Claus Wellenreuther, Klaus Tschira and Hans-Werner Hector start Systemanalyse Programmentwicklung in April 1972, working out of Weinheim and Mannheim — and, much of the time, out of the data centre of their first customer, the German subsidiary of Imperial Chemical Industries. The founding vision: standard enterprise software that integrates all business processes and processes data in real time.12
A financial accounting system built for real-time processing on the mainframe — the "R" that names three product generations stands for real-time. The design principle established here, one integrated system instead of many batch programs, carries through every generation that follows.2
The single-module accounting system becomes a suite. R/2 turns SAP from a project company into a product company — and the 1988 IPO turns the product company into a public one.
Development of the second software generation begins in 1979; by 1981 R/2 extends the accounting core to manufacturing, sales and distribution processes. International subsidiaries follow — Denmark, Sweden, Italy and, pivotally, the United States.3
In October 1988 SAP lists on the Frankfurt and Stuttgart exchanges, issuing 1.2 million bearer shares at DM 750. The employee count stands at roughly 940, annual revenue at DM 245 million.3
The release that made SAP a global company. R/3 moves the suite off the mainframe onto three-tier client-server architecture, rides the 1990s wave of business-process reengineering and Y2K replacement programmes, and becomes the reference model for what the industry now calls ERP.
Three tiers — database, application server, client — replace the mainframe monolith. R/3 smooths the path to a globalising economy and turns SAP into a global player with subsidiaries and development centres worldwide.4
SAP's answer to the new economy combines e-commerce solutions with the ERP applications on web technology. The branding did not last; the underlying question — how the suite meets the web — shaped the platform decade that followed.4
Two things happen in parallel: the R/3 line becomes SAP ERP on a technology platform, and SAP starts buying what it could not build fast enough. Both decisions define the landscape customers still operate today.
The NetWeaver platform finds an overwhelming market response — well over 1,000 customers in its first year — and SAP ERP Central Component 5.0 succeeds R/3 Enterprise.5 Its successor ECC 6.0 becomes the longest-serving workhorse in SAP's history — the installed base whose transition defines the current decade. That characterisation is editorial; the maintenance dates that make it consequential are in Era V.
Business Objects (2008) brings business intelligence, Sybase (2010) mobility and data management.5 Then the cloud pivot: SuccessFactors (announced end of 2011), Ariba (2012), hybris (2013) and Concur (2014) — at the time SAP's largest acquisition — assemble the cloud line-of-business portfolio around the ERP core; Qualtrics (2018) later extends it into experience data before its own spin-off.6
The business relevance: from here on, "SAP" no longer names one product lineage but a portfolio — and integration between the acquired clouds and the ERP core becomes a permanent architecture topic.
HANA starts as a faster database and becomes the forcing function for the biggest product decision since R/3: rebuild the suite on it. The era closes with the maintenance commitment that put an end date on the ECC world.
The in-memory appliance ships to customers worldwide on 21 June 2011, after first deliveries to select customers in November 2010.7
Unveiled on 3 February 2015 at the New York Stock Exchange: Business Suite 4 SAP HANA, engineered for the in-memory platform, with a simplified data model and the Fiori user experience, in cloud and on-premise editions.8
Announced in February 2020 and maintained since: mainstream maintenance for the Business Suite 7 core applications — the ECC world — runs to the end of 2027, with optional extended maintenance to the end of 2030; for SAP S/4HANA, SAP commits that at least one release remains in maintenance until the end of 2040.9 These three dates are the clock behind every transformation roadmap of the current decade — the decision they force is the subject of Why ECC Ends and Cloud Begins.
The product question becomes a commercial-model question. RISE and GROW replace the licence with the subscription, AI enters the suite first as an embedded capability and then as the suite's own organising idea, and — a first in SAP's history — the European Commission binds the maintenance aftermarket with formal commitments.
Introduced on 27 January 2021 as "business transformation as a service": one subscription contract bundling S/4HANA Cloud, infrastructure, tools and services, explicitly built to move the ECC installed base.10 The construct shifts the centre of gravity of SAP negotiations from licence purchase to long-run commercial governance — usage, entitlements, flexibility.
On 21 March 2023, GROW with SAP brings S/4HANA Cloud Public Edition to midsize customers as a preconfigured, rapidly deployable offering.11 The same year, S/4HANA on-premise and Private Cloud Edition move from yearly major releases to a two-year cycle with feature package stacks roughly every six months and seven years of mainstream maintenance per release; S/4HANA 2025, released October 2025, is the current major release.12
Announced on 26 September 2023: a natural-language generative AI copilot embedded across the cloud portfolio — the visible front end of SAP's broader Business AI strategy of shipping AI capabilities inside the applications rather than beside them.13
On 13 February 2025 SAP announces SAP Business Data Cloud, natively embedding Databricks technology for data engineering, machine learning and AI workloads, and unveils ready-to-use Joule agents across finance, service and sales — presented across the SAP Business Suite, a name returning to active duty a decade after S/4HANA succeeded the original suite.14 By October 2025 the repositioning is explicit: the Business Suite is pitched as AI, data and applications united — businesses, in SAP's words, "need more than a patchwork of disparate best-of-breed applications".15
The historical resonance: "Business Suite" was the name of the ECC-era portfolio whose 2027 maintenance clock defines this decade (Era V). The same name now brands its cloud successor — the circle the maintenance dates opened, the branding closes.
On 13 May 2026, at Sapphire, SAP unveils the Business AI Platform to power what it calls the Autonomous Enterprise: an Autonomous Suite spanning five domains — Finance, Spend, Supply Chain Management, HCM and CX — with more than 200 agents and over 50 assistants stated as available "in the coming months", and Joule repositioned from copilot to operating layer.16 A substantial part of the announcement is forward-looking; what was announced versus what ships, and the questions the material does not answer, are examined in SAP's Autonomous Suite — What Was Announced, and What to Check.
On 9 July 2026 the Commission accepts binding commitments from SAP addressing competition concerns in the aftermarket for maintenance and support of on-premise ERP software: reinstatement fees abolished, back-maintenance fees capped, clearer conditions for splitting a landscape across support providers — binding for ten years.17 SAP welcomed the decision as strengthening customer choice and predictability.18 What it changes for the ECC decision calculus: From Handcuffs to Sailboats.
This chronicle was compiled on 9 September 2026. Sources were verified at that date: support.sap.com, prnewswire.com and several news.sap.com pages were opened and read directly; SAP's corporate-history decade pages on sap.com and the European Commission's press-corner page are bot-blocked or JavaScript-rendered for automated access and are cited from their search extracts, marked accordingly.
Extended on 14 September 2026 with two Era-VI entries — the Business Suite's return with SAP Business Data Cloud (2025) and the Sapphire 2026 Autonomous Enterprise announcement — all three added references (14–16) opened and read directly that day.
Two limitations are worth naming. First, precise day-level dates in the early decades (the R/2 development start, the R/3 launch day) rest on SAP's own retrospective history pages and are cited at year granularity here. Second, revenue, valuation and deal figures are deliberately kept sparse; a company chronicle should record what happened and when, not compete with the annual report.
References are graded on the same four-level hierarchy as the TM history: primary product or regulatory authority, first-party SAP commentary, independent secondary sources, and tertiary community recollection.
Continue in Insights — or go where the history points: the decision the 2027 clock forces, and the same chronicle for one domain, transportation management.