SAP area combinations that work well together

Written by an SAP Finance & Treasury practitioner working with SAP since 2008 · how the guides are written · Updated 10 October 2026

SAP module combinations are the pairs of areas that go together in one role because a document or a piece of master data crosses between them: a goods receipt becomes an accounting entry, a sales order becomes a delivery. The good combinations share that boundary; unrelated module labels collected on one CV do not.

Which SAP modules are commonly combined?

The common combinations are the ones the job market has turned into a single title. The table lists the ten you will meet most often, why each pair travels together, and how an advert usually names the person who covers both.

SAP module combinations and the roles built on them
Combination	Why they travel together	Typical role title
FI + CO	External and internal views of the same postings; in S/4HANA both write to the Universal Journal	SAP FICO consultant
MM + SD	Stock bought on one side is sold on the other; intercompany and third-party orders cross both	SAP MM/SD or logistics consultant
SD + LE	The order becomes a delivery, picking and goods issue in Logistics Execution before it can be billed	SAP SD consultant, often with shipping in scope
PP + QM	Inspection lots hang off production and goods receipts on the same shop floor	SAP PP/QM consultant
MM + WM/EWM	Inventory management counts the stock; the warehouse decides which bin it sits in and how it moves	SAP MM/WM or EWM consultant
FI + Treasury	Payments, bank statements and cash positions are fed by the ledger and post back to it	SAP Treasury or FI/TRM consultant
HCM + Payroll	Payroll runs on the employee master, organisational assignment and time data held in HCM	SAP HCM/Payroll consultant
Basis + Security	User administration, transports and system parameters sit with the same small team in many landscapes	SAP Basis and security consultant
ABAP + Fiori	A Fiori app needs an OData service, which ABAP and CDS views provide	SAP ABAP/Fiori developer
CPI + ABAP	Cloud Integration in SAP Integration Suite moves the message; ABAP builds the IDoc, proxy or API at the SAP end	SAP integration developer

Is FICO one module or two?

Two modules, staffed as one role. FI is financial accounting — general ledger, payables, receivables, assets and the close — and CO is controlling: overhead on cost centres and orders, product costs, and margin analysis. They were always tightly linked, and S/4HANA merged their line items into one table, so a consultant who knows only one side now struggles to explain a posting end to end. In practice most FICO consultants still lean towards one half: FI-heavy profiles come from accounting and audit, CO-heavy ones from controlling and cost accounting. Adverts say FICO; interviews find out which half you really own.

Which SAP module combinations does the market ask for?

Mostly the ones that remove a hand-off on a project. FICO is the largest single pairing because every customer runs finance. MM/SD and MM/EWM are common in distribution and manufacturing, SD with SAP's commerce and customer-experience clouds in online selling, and PP/QM in regulated industries where quality is part of the production process. Beyond the business pairs, three kinds of combination are consistently scarce:

Techno-functional. A functional consultant who debugs, reads ABAP and speaks interface removes a translation step, and so does a developer who understands one business area deeply (the functional and technical split).
Control-flavoured. Security plus GRC, with one functional area, usually finance, so that access rules and the process they protect are understood by one person.
Cross-cutting thirds.Data and analytics, MDG and BTP attach to any area, because every process needs its numbers, its master data and eventually an extension.

Combinations with no shared document — SD with Basis and payroll, say — read as drift rather than range, because the market prices depth.

How has S/4HANA changed these combinations?

It has tightened some pairs and moved others to new products. The Universal Journal made FI and CO one set of line items, so the old excuse for knowing only one side has gone. Classic WM was carried into S/4HANA only as a compatibility item whose usage right, as of October 2026, has run out for most customers; its basic functions continue as stock room management, and new warehouse designs use EWM, which turns MM/WM profiles into MM/EWM ones. Many HR landscapes have moved to SuccessFactors Employee Central, with payroll either kept on premise or run as Employee Central Payroll, so the HCM and payroll pair now often includes a cloud half. On the technical side, Fiori work increasingly means ABAP RESTful application programming and CDS views rather than hand-built services, and integration work happens in SAP Integration Suite. Each change rewards the person who already spans the pair, because the new product assumes both halves are designed together.

Which combination should you add next?

The one on the far side of a boundary you already work at, and only once you can run your first area alone. A second area learned before independence in the first gives two shallow specialisms; learned after it, it gives range. The sign is practical: you already answer tickets that fail after the hand-off and read the neighbouring stream's configuration to debug your own. An MM consultant in that position adds EWM or SD (and should expect the pricing and billing scenarios of an SD interview); a CO consultant adds FI or PS; an ABAP developer adds Fiori or integration. Grow into it on a project where both areas are in scope.