What is SAP?
If you work in a large company, you’ve probably heard SAP mentioned in meetings. Perhaps HR told you to log your leave in SAP. Or finance said the invoice is “sitting in SAP.” Or IT warned you that next year’s big project is “an SAP migration.”
But what is SAP, exactly?
The simplest possible answer
SAP is software that helps large organisations run their business. It connects different departments — finance, HR, procurement, sales, manufacturing — so they share the same data and can see what’s happening across the company in real time.
Without something like SAP, a company with 10,000 employees might have 15 different systems that don’t talk to each other. SAP replaces that fragmentation with one integrated platform.
A brief history
SAP SE was founded in 1972 by five engineers who had been working at IBM’s German offices. They wanted to build software that could process business transactions in real time — a radical idea at the time, when most computing was done in overnight batches.
The company is headquartered in Walldorf, Germany, and its name comes from the German: Systemanalyse und Programmentwicklung (System Analysis and Program Development).
Today, SAP is the world’s largest enterprise software company by revenue. More than 400,000 organisations in 180 countries run on SAP — including most of the world’s largest corporations.
What does SAP actually do?
The best way to understand SAP is to follow a simple business transaction:
A customer orders 100 units of a product.
Here’s what happens across an SAP system:
- Sales (SD module): The order is captured. Pricing rules are applied. Customer credit is checked.
- Materials Management (MM): Inventory is checked. If stock is available, it’s reserved. If not, a purchase order may be triggered.
- Production Planning (PP): If the product needs to be manufactured, a production order is created.
- Finance (FI): Revenue is recognised. Accounts receivable is updated.
- Controlling (CO): Profitability is tracked. Cost centres are updated.
- Logistics (LE): A delivery is created and goods are shipped.
- Billing: An invoice is generated and sent to the customer.
All of this happens in one connected system. Every step updates the same database. Finance can see the order the moment it’s placed. Warehouse can see the delivery requirement without anyone sending an email.
That integration is what makes SAP powerful — and, admittedly, complex.
SAP is not just one product
This is where it gets confusing: SAP is both a company name and a generic term for enterprise software. When people say “we use SAP,” they usually mean one of these:
SAP ECC (ERP Central Component): The classic, on-premise SAP system that most large companies have been running for the past two decades. SAP has announced that mainstream maintenance ends in 2027.
SAP S/4HANA: The next-generation ERP, built on SAP’s in-memory HANA database. Faster, simpler data model, modern Fiori user interface. This is where SAP is taking everyone.
SAP BTP (Business Technology Platform): The cloud platform for integration, extension, and AI capabilities. Think of it as the technology layer that connects SAP systems to each other and to the wider world.
SAP SuccessFactors: Cloud-based HR suite — recruitment, performance management, payroll, learning.
SAP Ariba: Procurement and supply chain collaboration platform.
Who uses SAP?
SAP is almost exclusively used by medium-to-large organisations. The software is powerful but expensive to implement and maintain, which is why you mostly find it in:
- Global manufacturing companies
- Large retailers and consumer goods companies
- Banks and financial institutions
- Healthcare systems and pharma companies
- Government and public sector organisations
- Oil, gas, and energy companies
- Utilities
Why is SAP so complicated?
Two reasons: flexibility and integration.
SAP can be configured to match almost any business process in almost any industry. That flexibility is incredibly powerful — but it also means every SAP implementation is different, with thousands of configuration choices and customisations made over years.
Add to that the integration between modules: a change in one area ripples through others. An incorrect goods receipt in MM affects inventory, which affects production planning, which affects the financial statements. Nothing exists in isolation.
This is why SAP consultants exist, and why SAP projects tend to be large, expensive, and complex. Getting it right requires understanding both the software and the business.
SAP from a consultant’s perspective
I’ve spent 15 years implementing and architecting SAP systems — first in India, now in Finland. What I find most interesting about SAP isn’t the technology itself, but how it forces organisations to answer hard questions about their own processes.
When you implement SAP, you can’t hide behind “that’s just how we’ve always done it.” SAP requires you to define your processes clearly, standardise where possible, and make explicit decisions about how your business works.
Done well, an SAP implementation is as much an organisational transformation as a technology project. That’s what makes it challenging — and genuinely interesting.
This is part of an ongoing series on SAP fundamentals. Next: SAP BTP — what it is and why every SAP customer should understand it.