SAP modules: the main functional and technical modules explained

The main SAP modules are Financial Accounting (FI), Controlling (CO), Materials Management (MM), Sales and Distribution (SD), Production Planning (PP), Quality Management (QM), Plant Maintenance (PM), Human Capital Management (HCM), Extended Warehouse Management (EWM) and Project System (PS). Behind them sit the technical modules: Basis, ABAP, SAP Business Technology Platform (BTP) and SAP Integration Suite.

In SAP S/4HANA, SAP now groups these modules into lines of business such as Finance, Sourcing and Procurement, Manufacturing, Supply Chain and Sales. The old module codes have not gone away. Consultants, job ads and configuration menus still use them every day.

SAP modules fall into two groups.

1. Functional modules map to a business process. Finance closes the books, procurement buys, sales sells, production makes. Business users log in to these every day.
2. Technical modules run the system underneath. They cover administration, custom development, integration and extensions. Users rarely see them, but every functional module depends on them.

People also talk about industry modules, such as SAP S/4HANA Utilities or Retail. These sit on top of the core modules rather than replacing them. More on those below.

I've seen teams struggle not because the system didn't work, but because they didn't really know what each module was responsible for, or how changes in one could ripple into others. You don't need to learn every feature. You need to know enough to choose well.

The table below lists the core functional modules, what each one does, and where it sits in SAP S/4HANA today. The line of business names come from SAP's own Feature Scope Description for S/4HANA Cloud Public Edition 2608.

Module	Full name	What it does	S/4HANA line of business
FI	Financial Accounting	General ledger, accounts payable and receivable, asset accounting, financial close and statutory reporting	Finance
CO	Controlling	Cost centres, internal orders, product costing and margin analysis for internal reporting	Finance
MM	Materials Management	Purchase requisitions, purchase orders, goods receipt, inventory and invoice verification	Sourcing and Procurement, Supply Chain
SD	Sales and Distribution	Quotations, sales orders, pricing, deliveries and billing (order to cash)	Sales
PP	Production Planning	Material requirements planning (MRP), bills of material, routings and production orders	Manufacturing
QM	Quality Management	Inspection planning, inspection lots, results recording and quality notifications	Manufacturing
PM	Plant Maintenance	Maintenance notifications, work orders and preventive maintenance plans for equipment	Asset Management
HR / HCM	Human Capital Management	Employee records, organisation management, time management and payroll	Human Resources
SuccessFactors	SAP SuccessFactors	SAP's cloud HR suite: core HR (Employee Central), recruiting, learning, performance	Human Resources (separate cloud product)
EWM	Extended Warehouse Management	Bin-level storage, inbound and outbound processing, picking and warehouse tasks	Supply Chain (Warehousing)
PS	Project System	Work breakdown structures, networks, project budgets and costs	R&D / Engineering
TRM	Treasury and Risk Management	Cash management, liquidity forecasts, financial instruments and hedging	Finance

A few modules sit outside that core list but come up often. Customer Service (CS) handles service orders and contracts, now under the Service line of business.

Environment, Health and Safety (EHS) handles incidents and compliance, listed under Manufacturing. Transportation and delivery processing sit under Supply Chain.

How the core modules connect

No functional module works alone. A sales order in SD checks stock in MM, triggers production in PP if stock is short, and posts revenue to FI when it is billed. CO then picks up the cost and margin.

That chain is why a design decision in one module ripples into others. Change a pricing condition in SD and you change what lands in FI. Skip a quality inspection type in QM and goods may sit blocked in MM.

I've written separate guides on several of these modules:

1. SAP FICO: the seven things that break finance implementations
2. SAP SD: what it does and where implementations break
3. SAP PP: production planning in discrete, process and repetitive manufacturing
4. SAP EWM: what it does, how it works and what it costs

HR: SAP HCM or SuccessFactors

HR is the module where the packaging has changed most. On-premise customers can run SAP HCM for SAP S/4HANA, which SAP still teaches through its own learning courses on personnel administration, time management and payroll.

SAP's cloud direction for HR is SuccessFactors. In S/4HANA Cloud Public Edition, the Human Resources scope covers core HR and time recording, plus integration with an external HR system. SuccessFactors is SAP's own option for that external system.

Technical modules don't show up in a process map, but they decide whether the system stays stable, fast and connected. The common ones:

Module	What it does
Basis	System administration: installation, user and role management, transports between systems, patching and performance monitoring
ABAP	SAP's programming language for custom reports, forms, interfaces and enhancements inside the ERP
SAP BTP	SAP Business Technology Platform: builds extensions and apps outside the ERP core, plus data, AI and integration services
SAP Integration Suite	Connects SAP and non-SAP systems through APIs, events and integration flows. The successor to SAP PI/PO
SAP BW/4HANA	Data warehousing for reporting across SAP and non-SAP sources
SAP Analytics Cloud	Dashboards, planning and analytics in the cloud

Two dates matter here. SAP Learning states that SAP NetWeaver 7.5, the platform under SAP Process Orchestration, has mainstream maintenance until the end of 2027, with optional extended maintenance until the end of 2030.

SAP positions SAP Integration Suite as the target. My guide to SAP CPI and Integration Suite covers that move.

For reporting and planning on top of the modules, see my SAP Analytics Cloud guide.

I've seen projects stall not because Finance wasn't configured properly, but because someone underestimated the effort needed to manage transports or didn't plan for interface testing. It's the kind of thing you don't notice until it goes wrong. And then, it's all you notice.

In SAP ECC, the module was the unit everyone planned around. In SAP S/4HANA, SAP organises its scope by line of business, with the old modules sitting inside them.

SAP's Feature Scope Description for S/4HANA Cloud Public Edition 2608 (document version dated 8 October 2026) lists these lines of business:

1. Asset Management
2. Finance
3. Human Resources
4. Manufacturing
5. Professional Services
6. R&D / Engineering
7. Sales
8. Service
9. Sourcing and Procurement
10. Supply Chain

The same document lists industry scope separately, including Public Sector, Banking, Insurance, Oil and Gas, and Retail.

Three practical changes come with that packaging:

1. Finance and controlling share one journal. In S/4HANA, FI and CO postings land in the universal journal, so the reconciliation work between them shrinks. That is why many people now say "FICO" as one area.
2. Warehouse management moved. Classic Warehouse Management (WM) gave way to EWM, which runs embedded in S/4HANA or as a separate system.
3. The codes stayed. Line of business names are how SAP sells and documents the product. FI, MM and SD are still how project teams talk.

Why the ECC dates matter for module planning

SAP announced in February 2020 that mainstream maintenance for the core applications of SAP Business Suite 7, which includes SAP ECC, runs until the end of 2027, with optional extended maintenance until the end of 2030. SAP also committed to maintaining S/4HANA until the end of 2040.

If you run ECC today, your module choices are tied to that migration. My ECC to S/4HANA migration guide covers the paths, steps and deadlines.

The core modules show up in every implementation. Industry modules handle the processes they can't cover: utilities billing, oil and gas joint venture accounting, retail store operations, public sector budgets and grants.

I remember a utilities project where the client assumed SD would handle their billing. It didn't. Not even close.

We had to pivot fast to IS-U, which, honestly, should've been part of the discussion from day one.

Industry modules still run on FI, MM and the rest. They change how those pieces behave for your sector. If your industry has one, put it in scope early, even if you are not sure how deep you will go.

Most businesses don't switch on the full suite at once. In my experience, most companies start with finance, HR and procurement.

That makes sense. Every company needs to close its books, pay its people and buy what it uses. Sales, production, quality and maintenance follow once that base is stable, depending on what the business actually does.

When you choose, look at four things:

1. Your processes first. Map what the business does before you pick modules. A manufacturer needs PP and QM. A services firm may need PS far more.
2. Integration points. Every module you add creates interfaces with the others and with outside systems. Budget the testing.
3. Industry requirements. Regulated billing, grants or joint ventures may need an industry solution, not a core module.
4. Your team's capacity. Each module needs a process owner on the business side. If nobody owns it, it drifts.

Not every module needs to go live on day one. Trying to do everything at once rarely works out well.

What are the main SAP modules?

The main SAP functional modules are Financial Accounting (FI), Controlling (CO), Materials Management (MM), Sales and Distribution (SD), Production Planning (PP), Quality Management (QM), Plant Maintenance (PM), Human Capital Management (HCM), Extended Warehouse Management (EWM) and Project System (PS). The main technical modules are Basis, ABAP, SAP BTP and SAP Integration Suite.

What are the SAP core modules?

The core modules are the ones almost every company runs: FI and CO for finance, MM for procurement and inventory, and SD for sales. Manufacturers add PP and QM. In my experience, most companies start with finance, HR and procurement, then add the rest.

What are SAP technical modules?

Technical modules run the system rather than a business process. Basis administers the system, ABAP is the programming language for custom code, SAP BTP hosts extensions and apps outside the core, and SAP Integration Suite connects SAP to other systems. SAP BW/4HANA and SAP Analytics Cloud handle reporting and planning.

Do SAP modules still exist in SAP S/4HANA?

Yes. SAP now documents S/4HANA by line of business, such as Finance, Sourcing and Procurement, Manufacturing, Supply Chain and Sales. The module codes FI, CO, MM, SD and PP are still used by project teams, in job titles and in configuration.

Is SAP SuccessFactors a module of S/4HANA?

No. SuccessFactors is SAP's separate cloud HR suite. It integrates with S/4HANA. The HR scope of S/4HANA Cloud Public Edition covers core HR and time recording and integrates with an external HR system, such as SuccessFactors. On-premise customers can still run SAP HCM for SAP S/4HANA.

Can I implement just one SAP module?

Technically, yes. Many companies start with finance and expand later. You still need Basis, user management and usually some integration, so it is rarely a one-module setup in practice.

If you are working out which modules belong in your first phase, or how your ECC modules map to S/4HANA, start with your processes and your integration list. If you want a second view on the scope before a partner prices it, talk to me.

Official sources

1. SAP S/4HANA Cloud Public Edition 2608 Feature Scope Description (help.sap.com, document version 8 October 2026)
2. SAP Process Orchestration to SAP Integration Suite migration: understanding the rationale (SAP Learning)
3. Business Processes in SAP HCM on S/4HANA (SAP Learning)
4. SAP extends its innovation commitment for SAP S/4HANA, provides clarity and choice on SAP Business Suite 7 (SAP News, February 2020)