[SAP] SAP Logistics Modules Explained For People Who Use It Every Day Without Really Knowing What It Is
You use SAP. Maybe every day. You enter a goods receipt, you check a stock level, you confirm a transfer order. You know your transactions. You know what breaks when something goes wrong.
But if someone asked you to explain how the modules connect; what MM actually does versus EWM, where TM fits in, why SD exists; you'd probably struggle to give a clean answer.
That's not a gap in your competence. It's a gap in how SAP gets taught in most organizations. You get trained on your process, your screen, your T-code. Nobody sits you down and explains the architecture.
This post does that. No theory, no certification prep. Just a clear explanation of what each logistics module does, how they connect, and why it matters for your day-to-day work.
First: What Is SAP S/4HANA?
SAP S/4HANA is the current generation of SAP's ERP platform. ERP stands for Enterprise Resource Planning; which is a corporate way of saying: one system that manages everything, from procurement to finance to warehouse to transport, with all data connected in real time.
The "S/4HANA" part refers to the underlying database technology (HANA) that makes the system significantly faster than older SAP versions (ECC). If your company is still on SAP ECC, the modules are largely the same; the interface and performance differ.
SAP is organized into modules. Each module covers a specific business domain. They share the same database, which means a goods receipt posted in MM instantly updates stock in EWM, triggers an accounting entry in FI, and is visible in SD. That real-time integration is the core value of an ERP; and the reason data quality in one module affects every other module downstream.
The Logistics Modules : What Each One Actually Does
MM — Materials Management
MM is the procurement and inventory backbone of SAP. It covers everything related to buying materials and managing stock at the inventory level.
What it handles: purchase requisitions, purchase orders, goods receipt, invoice verification, stock management, inventory valuation, vendor master data, material master data.
In practice, MM is the module most operational staff interact with daily without realizing it. When you receive a delivery against a PO, you're in MM. When you check whether a material is in stock, you're reading MM data. When a buyer raises a purchase order, that's MM.
Key T-codes to know:
ME21N — Create Purchase Order
ME23N — Display Purchase Order
MIGO — Goods Movement (receipt, transfer, reversal)
MMBE — Stock Overview (where is my stock, in which plant, in which storage location)
MB51 — Material Document List (history of all stock movements for a material)
ME2M — Purchase Orders by Material
MM is where your inventory record lives. If MM data is wrong; wrong quantities, wrong storage locations, wrong units of measure; every downstream module inherits that error.
EWM — Extended Warehouse Management (WMS of SAP)
If MM manages stock at the inventory level, EWM manages it at the physical level. EWM knows not just that you have 500 units of a product; it knows exactly which bin they're in, in which aisle, on which rack level, and in which handling unit.
What it handles: inbound processing (goods receipt at bin level), putaway strategies, storage bin management, pick orders, wave management, packing, outbound processing, physical inventory at bin level, resource management (forklifts, operators).
EWM is the module warehouse operators and supervisors live in. Every scan, every transfer order confirmation, every bin-to-bin movement happens in EWM.
Key T-codes / Fiori tiles to know:
/SCWM/PRDI — Post Goods Receipt (inbound delivery processing)
/SCWM/TO_CONF — Confirm Transfer Order (confirm a physical movement)
/SCWM/MON — Warehouse Monitor (real-time view of everything happening in the warehouse)
/SCWM/PACK — Packing Workbench
Fiori tile: "Monitor Warehouse Tasks" — live view of open, in-progress, and completed tasks by zone and operator
Fiori tile: "Manage Storage Bins" — bin occupancy, blocked bins, empty locations
The key concept in EWM is the Warehouse Task (WT); every physical movement in the warehouse is represented as a warehouse task. Created by the system, confirmed by the operator. That confirmation is what keeps the physical reality and the system record aligned.
TM — Transportation Management (TMS of SAP)
TM covers everything that happens once the goods leave the warehouse and everything that needs to be planned before they arrive.
What it handles: freight order creation, carrier selection, route planning, load building, shipment tracking, freight cost calculation, proof of delivery, carrier performance.
In practice, TM is used by logistics coordinators, freight planners, and transport managers. It's less commonly touched by warehouse operators but understanding it matters because TM and EWM are tightly connected. An outbound delivery confirmed in EWM triggers or updates a freight order in TM. A TM shipment delay impacts dock planning in EWM.
Key T-codes / Fiori tiles:
Fiori tile: "Manage Freight Orders" — full visibility of outbound shipments, status, carrier, ETA
Fiori tile: "Track Shipments" — real-time shipment tracking integrated with carrier data
Fiori tile: "Analyze Freight Costs" — planned vs actual freight cost by lane, carrier, period
TM is the module most companies implement last or not at all, relying instead on standalone TMS tools. The argument for keeping it in SAP: all freight data stays connected to the same inventory and finance records, eliminating the reconciliation work that comes with external systems.
SD — Sales & Distribution
SD is the outbound commercial side of SAP. Where MM handles buying, SD handles selling. It manages customer orders, pricing, delivery creation, billing, and returns.
In a logistics context, SD is critical because it's where outbound deliveries originate. A sales order in SD triggers a delivery document, which EWM picks up to execute the physical pick and pack. Without SD, there's no outbound flow.
Key T-codes:
VA01 — Create Sales Order
VA03 — Display Sales Order
VL01N — Create Outbound Delivery
VL02N — Change Outbound Delivery (add picking quantities, confirm)
VF01 — Create Billing Document
PP — Production Planning
PP manages manufacturing production orders, bills of materials, work centers, capacity planning. In a pure distribution or 3PL environment, PP is often not relevant. But in any operation that combines warehousing with light manufacturing, kitting, or assembly, PP connects directly to MM and EWM.
A production order in PP triggers material reservations in MM. When components are issued to production, that's a goods movement in MIGO. When finished goods are received from production into the warehouse, EWM takes over for putaway.
Key T-codes:
CO01 — Create Production Order
CO03 — Display Production Order
MD04 — Stock/Requirements List (what's planned, what's confirmed, what's missing)
For logistics professionals who work alongside production teams, MD04 is the most useful transaction to understand it shows the full picture of supply and demand for a material at a given plant, including open POs, production orders, sales order reservations, and current stock.
WM — Warehouse Management (Legacy)
A quick note: SAP WM is the predecessor to EWM. Simpler, less granular, still running in many older SAP ECC environments. If your company is still on WM rather than EWM, the core logic is similar but the functionality is more limited no activity areas, no resource management, less flexible putaway strategies.
Key WM T-codes you may still encounter:
LT01 — Create Transfer Order
LT0A — Confirm Transfer Order
LS26 — Warehouse Stock per Storage Bin
LI01 — Create Inventory Document
If your company is on SAP ECC with WM, migration to S/4HANA with EWM is eventually on the roadmap. Understanding the gap between WM and EWM is worth knowing if you're involved in that conversation.
How the Modules Connect : A Simple Flow
Here's the end-to-end logistics flow across modules, from procurement to customer delivery:
Inbound flow: Purchase Order created in MM (ME21N) → Supplier delivers → Goods Receipt posted in MIGO (MM) → EWM receives the inbound delivery → Putaway task created and confirmed in EWM (/SCWM/TO_CONF) → Stock updated at bin level in EWM and inventory level in MM
Outbound flow: Sales Order created in SD (VA01) → Outbound Delivery created (VL01N) → EWM picks up the delivery → Pick task created and confirmed in EWM → Goods Issue posted → TM updates shipment status → Billing triggered in SD (VF01)
Every step feeds the next. Every error in one module creates a problem in the next. That's why understanding the full picture not just your own screen, changes how you work.
Why This Matters in 2026
SAP is not going away. S/4HANA adoption is accelerating across the GCC region in retail, logistics, manufacturing, government-linked entities. The companies investing in SAP right now are the ones hiring people who can operate in it, configure it, and improve it.
The professionals who will be most valuable in the next five years are not the ones who know one T-code in one module. They're the ones who understand how the modules connect who can sit in a project meeting, understand the cross-functional impact of a configuration decision, and translate between the warehouse floor and the system logic.
You don't need to be a consultant to get there. You need to understand the architecture. This post is the starting point.
Victor L. | Supply Tech Nexus | Logistics · WMS · SAP · GCC Region