SAP Concepts: What is SAP? A Seven-Minute Orientation

You've probably heard the name. It shows up in job ads that pay well, in conversations between accountants and auditors, and in awkward corporate town halls where someone says "we're moving to SAP" and everyone collectively winces. But if you're outside the tent, it's genuinely unclear what SAP actually refers to. A company? A product? A methodology? Some combination?

This is the first episode of our SAP Concepts series, and I'm going to answer that question before we go anywhere near modules, transaction codes, or migration paths. SAP is three things at once — a German software company, a family of ERP products, and an ecosystem of consultants and partners that represents one of the largest professional-services industries in the world. You need to understand all three.

SAP the company

Start with the company. SAP SE is based in Walldorf, Germany — a small town near Heidelberg — and was founded in 1972 by five former IBM engineers. The name originally stood for Systemanalyse Programmentwicklung (Systems Analysis and Program Development), though the company has long since dropped the expansion and now just uses the initials.

By revenue, SAP is the largest enterprise software company in Europe and one of the largest in the world. It serves more than 440,000 customers across 180 countries, and the overwhelming majority of the Fortune 500 runs SAP for at least part of its business operations. If you buy groceries, put petrol in a car, or turn on the lights, there's a high chance SAP software was involved in getting the transaction from the point of sale to the general ledger somewhere.

The company's culture is German-engineering in the best and most exasperating senses. The products are powerful, deeply configurable, and unforgiving. Consultants who've spent a decade inside SAP often describe it the way old Linux admins talk about emacs — a system that rewards years of patience with enormous productivity, but has no interest in being friendly to beginners.

SAP the product line

That brings us to the actual software. When people say "we run SAP", they're referring to one of the company's ERP products. The flagship has had different names over the decades.

R/2 launched in 1979 — a mainframe-era product. R/3 arrived in 1992 and became the dominant ERP of the 1990s and 2000s. R/3 was renamed to SAP ECC (ERP Central Component) in 2006. And in 2015, SAP launched S/4HANA, which is the current and future flagship product, built specifically to run on SAP's in-memory database HANA.

For this series, we're going to focus on S/4HANA. That's where the industry is heading — mainstream maintenance for the older ECC ends in 2027, so every existing SAP customer is either on S/4 or on the path to get there. All the newer concepts we'll discuss in later episodes — the Universal Journal, Fiori, the Business Partner — are S/4HANA features.

Underneath the flagship, SAP sells dozens of other products. SuccessFactors for HR. Ariba for procurement. Concur for travel and expense. Analytics Cloud for BI. Most of those came through acquisitions and have been integrated into the S/4HANA ecosystem. When someone says "we use SAP Concur", they're using SAP-the-company's product, but it's not "the SAP" most people mean when they say they run SAP.

SAP the ecosystem

Here's the part that's genuinely underappreciated. SAP isn't just software; it's a professional-services industry around that software.

A global SAP implementation project routinely costs tens of millions of dollars. Most of that goes not to SAP the company but to system integrators — Accenture, Deloitte, IBM, Capgemini, Infosys, Wipro — who employ thousands of specialists trained specifically in SAP configuration. There are roughly 400,000-plus certified SAP consultants in the world, and the community is unusually deep.

That ecosystem is part of why SAP is hard to dislodge. When a company commits to SAP, it commits to the product and to the consulting industry that supports it. Switching to Oracle or NetSuite later isn't just a software migration — it means rehiring consultants with different specialities, retraining internal teams, replacing middleware. The lock-in is social as much as technical.

This matters because it shapes how new concepts spread. When SAP announces a product change (like the shift from ECC to S/4HANA), the announcement is really just the starting gun. What actually happens next is thousands of consultants learning the new material, hundreds of thousands of companies budgeting multi-year migration projects, and a slow tidal shift that takes years to complete. The 2027 ECC end-of-support date, announced years ago, is still being worked toward by thousands of customers.

What SAP does, in plain terms

So the company and the ecosystem. What does the software actually do?

SAP is an ERP — Enterprise Resource Planning. Same category as Oracle, Microsoft Dynamics, NetSuite. It covers the back office of a business: finance, procurement, inventory, sales, manufacturing, HR, reporting. The same seven-module shape we'd recognise from any other enterprise software.

What makes SAP distinctive is depth. Where a mid-market ERP might have a serviceable manufacturing module, SAP has twenty years of manufacturing-specific development behind it. Where another vendor's finance module handles standard accounting, SAP's finance module handles the edge cases that only occur in multi-national, multi-currency, multi-entity corporations with regulatory requirements in forty countries. That depth is the reason enterprises run SAP — and the reason SAP implementations are long and expensive.

It's also why the learning curve is famously steep. SAP is not an app you sit down with and figure out in an afternoon. The vocabulary alone — transaction codes like MIGO and FB60, module abbreviations like FI/CO/MM/SD/PP, structures like company code and plant and storage location — takes weeks to absorb. Once you're inside, though, the conceptual framework is coherent, and the product rewards the investment.

Why we're making this series

SAP Concepts is meant to be the shortest path from "I've heard of SAP" to "I can hold a conversation about SAP with a consultant". Eight episodes, each a single concept. We're going to stay at the level of the mental model — no transaction codes to memorise, no ABAP code, no configuration paths. The goal is to build the vocabulary and the mental map, not the operational knowledge.

After this first episode, we'll go module by module. Episode two is the module landscape — FI, CO, MM, SD, PP, HR, and how they integrate. Episode three covers FI and CO — the finance-and-controlling money spine that sits underneath everything else. Episodes four through six walk through the three big business processes — Procure-to-Pay, Order-to-Cash, Plan-to-Produce — each one showing how multiple modules coordinate to run a real-world business flow.

Episode seven covers organisational structures — client, company code, plant, storage location, sales organisation — the hierarchy every SAP transaction hangs off. And episode eight, the finale, covers S/4HANA vs ECC: what changed in SAP's biggest rewrite, and why it matters for anyone working with the product today.

By the end of season one, you'll have the conceptual map. From there, the deep-dive work — learning specific modules, learning configuration, learning transaction codes — becomes much easier, because you have a frame to hang it all on.

SAP isn't a simple product. But the core ideas are graspable in a few hours, and the rest is just elaboration on those ideas. That's what we're going to build.

See you in episode two, where we'll tour the module landscape — the alphabet soup of two-letter codes that dominates every SAP consultant's LinkedIn profile, and how it all fits together.