SAP Concepts: The SAP Module Landscape — FI, CO, MM, SD, PP and How They Hand Off

If you spend any time near an SAP system, you're going to notice that SAP people talk in two-letter codes. They'll say things like "the issue is in FI, not CO" or "we need to run an MM-SD integration check" and nobody will break stride.

That alphabet soup is the module landscape. It's the way SAP is organised internally, and it's the vocabulary that every SAP consultant carries. Learning it is the fastest way to stop feeling like an outsider in SAP conversations.

This is episode two of the SAP Concepts series. We're going to walk through the seven main modules — what each letter pair means, what the module does, and how they all integrate. By the end you'll be able to read a job description or a consultant's résumé and actually understand what they do for a living.

Why two letters?

First, a tiny bit of history. The two-letter codes are a relic of SAP's 1970s German origins. When the founders designed R/2 and later R/3, they organised the product around distinct application areas, each with a short internal code. FI for Finanzwesen (finance). CO for Controlling. MM for Materialwirtschaft (materials management). SD for Sales and Distribution. PP for Production Planning.

Those codes became the customer-facing vocabulary over time, and they've been remarkably durable. When SAP rebuilt the entire product as S/4HANA in 2015, they kept the two-letter codes even though the underlying architecture changed dramatically. Today you'll still hear consultants talking about FI and CO on S/4HANA, even though S/4 technically merged them into a single journal table (we'll get to that in episode three).

So the alphabet soup isn't arbitrary. It's a map to an organisation that's been developing the same seven or eight areas for five decades.

The finance half: FI and CO

Two of the most important modules sit on the finance side.

FI — Financial Accounting is the general ledger of the business. Every financial posting the company makes ends up here. Journal entries, accounts payable, accounts receivable, asset accounting, tax. FI produces the statutory financial statements — the balance sheet and P&L that the business submits to tax authorities and auditors. This is the module that keeps a company's books legally defensible.

CO — Controlling is the internal management accounting layer. Where FI is about external reporting, CO is about internal decision-making. Cost centres, profit centres, internal orders, activity-based costing, margin analysis by product line or customer or region. The CFO cares about FI because the regulators do; the COO and business unit heads care about CO because it tells them where the money is actually being made or lost.

In older versions of SAP (ECC and before), FI and CO lived in separate tables with their own postings, and the two had to be reconciled monthly. It was a whole ritual. In S/4HANA, that's gone — both share the Universal Journal, a single table. Episode three explains this in detail because it's one of the most important conceptual shifts in modern SAP.

The logistics side: MM, SD, PP

The physical operations of the business run through three modules.

MM — Materials Management handles procurement and inventory. Purchase requisitions, purchase orders, goods receipts, invoice verification, vendor master data, stock valuation. If you work in procurement or warehousing at a company that runs SAP, you live in MM.

SD — Sales and Distribution is the mirror of MM on the selling side. Sales orders, deliveries, shipping, billing, customer master data, pricing conditions. SD is where the revenue-generating transactions happen, and it's deeply integrated with FI (every invoice posts to Accounts Receivable automatically).

PP — Production Planning runs the manufacturing side for companies that make things. Bills of materials, routings, work centres, production orders, MRP runs, capacity planning, shop-floor confirmations. Pure distributors and services firms never touch PP — it's only relevant to companies that physically produce products. A food manufacturer, an automotive supplier, a chemicals company all live heavily in PP.

These three modules are tightly coupled. A sales order in SD triggers a stock reservation in MM. A production order in PP issues materials from MM. Every goods movement posts a finance consequence in FI. The modules are logical divisions, but in practice they behave as one integrated system.

The supporting cast: HR, PM, QM, PS

Beyond the main five (FI, CO, MM, SD, PP), SAP has a handful of other modules that companies use depending on their industry and scale.

HR — Human Resources (now branded SAP HCM, or in the cloud, SuccessFactors) covers employee master data, payroll, time management, benefits, and recruitment. For large companies, HR is one of the biggest datasets in the entire ERP — often second only to financial transactions.

PM — Plant Maintenance tracks maintenance orders for physical assets. Scheduled maintenance, breakdown repair, work orders, equipment history. Heavy in industries with lots of machinery — oil and gas, utilities, manufacturing, transportation.

QM — Quality Management handles inspection lots, quality notifications, batch management, and compliance workflows. Critical in pharma, food, aerospace, and medical devices.

PS — Project System supports project-based businesses — construction, engineering, consulting, custom manufacturing. Work breakdown structures, milestones, project cost tracking, revenue recognition by project.

These aren't in every SAP install. A services firm might run FI, CO, HR, and PS — no MM, no PP. A distributor might run FI, CO, MM, SD — no PP, maybe no HR. The module combination reflects the shape of the business.

How modules integrate

This is the part that trips people up the most. The modules aren't silos. They're deeply integrated, and that integration is what makes SAP valuable.

When a sales order is created in SD, it automatically reserves stock in MM. When the goods are shipped, MM records the inventory movement and FI receives a posting to Cost of Goods Sold. When the invoice is created in SD, FI creates an Accounts Receivable entry. When the customer pays, FI clears AR and posts to Cash.

Every transaction in SD has an MM and FI consequence. Every MM movement has an FI consequence. Every HR payroll run has an FI consequence. The modules communicate through the shared data model — especially the universal journal in S/4HANA — so actions in one module automatically ripple into the others.

This is why SAP consultants often specialise. An "MM consultant" isn't someone who only knows procurement; it's someone who knows how MM integrates with FI (invoice posting), with CO (cost centre assignment), with SD (stock availability), and with PP (materials for production). The integration points are where the real expertise lives.

What the big handoffs are

There are three big handoffs between modules that come up again and again. Worth naming them explicitly because they map to the three business processes we'll cover in episodes four through six.

MM to FI — Procure-to-Pay. MM drives the purchasing process; FI records every step. A goods receipt in MM automatically creates a GR/IR clearing entry in FI. An invoice verification in MM posts to Accounts Payable in FI.

SD to FI — Order-to-Cash. SD drives sales; FI records the financial consequence. Every billing document creates an AR entry. Every goods issue posts to COGS. Every payment clears AR.

PP to MM to FI — Plan-to-Produce. PP schedules production; MM issues raw materials and receives finished goods; FI posts the cost at each step and the variance at settlement.

These three handoffs are the beating heart of SAP. The rest of the product is scaffolding around them.

Where to start learning

If you're new to SAP and wondering which module to focus on first, the honest answer depends on the role you're aiming for. Finance-track careers start with FI/CO. Procurement-track with MM. Logistics and sales with SD. Manufacturing-track with PP. HR-track with HCM/SuccessFactors.

But regardless of focus, everyone benefits from understanding the FI layer, because every module eventually posts there. A sales consultant who doesn't understand FI can't explain why a pricing change affects revenue recognition. A procurement specialist who doesn't understand FI can't troubleshoot a GR/IR mismatch. Finance integration is the universal skill.

What's next

That's the module map, compressed into a single post. FI and CO for finance. MM, SD, PP for logistics and operations. HR, PM, QM, PS as the supporting cast. All of them integrated through a shared data model, with three big handoffs — Procure-to-Pay, Order-to-Cash, Plan-to-Produce — that run the business end-to-end.

Episode three goes deep on FI and CO, and specifically on the Universal Journal — the single most important concept in modern SAP. It's the change that redefined what FI and CO are.

See you there.