SAP Modules

SAP organizes its software into specialized areas called modules. Each module covers one business function. The finance team uses one module. The warehouse team uses another. HR uses a third. All modules share the same central database, so every team always sees up-to-date information from the others.

Think of SAP modules like departments in a hospital. The radiology department, the pharmacy, and the emergency ward all serve patients in different ways, but they all access the same patient records. No one has to call another department to find out a patient's history. SAP modules work the same way.

Why Modules Matter for Integration

When you build an integration, you always connect to a specific SAP module. A customer order integration touches the SD (Sales and Distribution) module. A payroll integration touches the HCM (Human Capital Management) module. Knowing which module you are integrating with tells you which data objects, APIs, and IDocs you need to use.

The Core SAP Modules

FI – Financial Accounting

FI manages the company's external financial records — invoices, payments, balance sheets, and tax reports. It produces the numbers that go to banks, auditors, and government bodies.

Integration example: A bank sends a payment file every night. An integration flow picks up that file and posts the payments automatically into FI, matching them to open invoices.

CO – Controlling

CO tracks internal costs. Where did the company spend money, and was it within budget? CO helps managers understand profitability by product, department, or project.

FI and CO work closely together. FI records a vendor invoice. CO allocates the cost to the correct department automatically.

MM – Materials Management

MM handles purchasing and inventory. It covers the full process from creating a purchase order to receiving goods in the warehouse.

Integration example: A supplier portal sends an invoice electronically. An integration flow converts it into an SAP MM invoice document automatically, removing manual data entry.

SD – Sales and Distribution

SD manages the sales process end to end — from a customer placing an order to the product being shipped and billed.

Integration example: An e-commerce website (Shopify, for instance) sends new orders to SAP SD every five minutes. The integration flow maps the Shopify order fields to SAP sales order fields and posts them automatically.

PP – Production Planning

PP handles manufacturing. It plans what to produce, when to produce it, and what raw materials are needed. It communicates with MM to ensure materials are available on time.

Integration example: A manufacturing execution system (MES) on the factory floor sends production confirmations every hour. An integration flow posts these confirmations into SAP PP, updating the production order status.

QM – Quality Management

QM manages quality inspections for incoming goods and finished products. It holds stock that fails inspection and releases stock that passes.

PM – Plant Maintenance

PM tracks maintenance of equipment and machines. It schedules preventive maintenance, records repair history, and manages spare parts inventory.

Integration example: IoT sensors on factory machines send alerts when vibration levels exceed safe limits. An integration flow creates a PM maintenance order automatically so a technician gets assigned before the machine fails.

HCM – Human Capital Management

HCM (also called HR) manages everything to do with employees — hiring, payroll, leave management, performance reviews, and training.

Integration example: A company uses Workday for HR functions but SAP for payroll. An integration flow syncs employee master data from Workday to SAP HCM every morning.

WM / EWM – Warehouse Management

WM manages inventory inside a warehouse — exactly where each item sits, how it moves, and how orders get picked and packed. EWM (Extended Warehouse Management) is the more powerful, modern version.

PS – Project System

PS tracks complex projects with milestones, budgets, and resource planning. Consulting firms and construction companies use PS to manage client projects inside SAP.

Module Interaction Diagram

Customer places order
        ↓
[SD] Creates Sales Order
        ↓
[MM] Checks Inventory
        ↓        ↓
[PP] Schedules  [WM] Picks goods
  Production     from warehouse
        ↓              ↓
[QM] Inspects goods
        ↓
[SD] Creates Delivery & Billing
        ↓
[FI] Posts Invoice & Receives Payment
        ↓
[CO] Allocates Costs to Profit Center

This diagram shows why modules cannot work independently. A sales order in SD triggers inventory checks in MM, which may trigger production in PP. All of this happens automatically because the modules share one database.

SAP S/4HANA Module Names

In SAP S/4HANA, SAP rebranded many modules. Here are the key name changes to know:

• FI + CO is now called SAP S/4HANA Finance
• MM + SD is part of SAP S/4HANA Sourcing and Procurement and SAP S/4HANA Sales
• HCM is now called SAP SuccessFactors in the cloud version
• EWM stays as SAP Extended Warehouse Management

The underlying concepts remain the same. The data structures, the process flows, and the integration points are all very similar. The branding changed, but the knowledge you build in this course applies to both ECC and S/4HANA environments.

Which Module You Will Integrate With Most

As an integration developer, you will encounter SD, MM, FI, and HCM most frequently because these modules exchange the most data with external systems. Customer portals talk to SD. Supplier portals talk to MM. Payment systems talk to FI. HR platforms talk to HCM.

You do not need to become an expert in each module's business process. You need to know what data structures each module uses, which APIs it exposes, and what triggers messages in and out of it. The topics ahead in this course will cover all of that in detail.