All topics
29 / 65
Functionaladvanced

SAP Warehouse Management (WM/EWM) Concepts

Storage bin structures, putaway/picking strategies, and the shift from classic WM to Extended Warehouse Management (EWM).

In MM, stock lives in a storage location — a plant and a code. That is enough for accounting and not nearly enough to run a warehouse, because it does not say where in the building anything is.

Classic WM is like a warehouse with numbered shelf locations and a basic "move this pallet from shelf A to shelf B" instruction sheet; EWM is the same warehouse upgraded with a full logistics command center that also schedules trucks in the yard, batches multiple orders into efficient picking rounds, and tracks how fast each picker works - far beyond just knowing where a pallet sits.

Key Concepts

1
Warehouse management adds that detail.
2
Classic WM's structure.
    warehouse number   the whole warehouse
      storage type     an area: high rack, bulk, picking area
        storage bin    one addressable location: 01-02-03
3
The working document is the transfer order (LT01), which instructs a move from one bin to another. Every physical movement inside the warehouse is one.
LT01
4
Strategies decide the bin automatically. Nobody chooses bins by hand at volume:
5
    putaway   fixed bin, next empty bin, add to existing stock
    picking   FIFO, strict FIFO, large/small quantities, partial pallets
6
The goals are competing: pack stock densely, and keep pickers walking as little as possible. A strategy is where that trade is configured.
7
EWM is the replacement, and it is not a rename. Available embedded in S/4HANA or as a separate system, it adds capabilities classic WM never had:
8
    wave management   group many deliveries into one optimised picking run
    yard management   track trailers in the yard, before a dock door
    labour management measure picker performance against standard times
    resource/task     drive conveyors, pick-to-light, voice picking
9
Why waves matter, concretely. Picking 200 deliveries one at a time means walking the warehouse 200 times. A wave groups them, sorts by location, and picks everything from one aisle in a single pass — then sorts into deliveries afterwards.
10
The same orders, a fraction of the walking. That is the kind of thing classic WM's per-delivery transfer order cannot express.
11
The document model differs too. EWM works with a warehouse request and warehouse tasks rather than transfer orders, which is a more flexible framework — one request can generate many tasks handled by different resources, including automated equipment.
12
The strategic point an interviewer is checking. SAP has announced the end of maintenance for classic WM. New S/4HANA implementations use embedded EWM, and existing WM customers face a migration.
13
So the answer should cover how classic WM works — bins, transfer orders, strategies — and why EWM exists, rather than treating them as alternatives of equal standing.
14
What the interviewer is probing.1. "What does EWM give you over classic WM?" Probing: the comparison. Stalls: "It is newer." Moves up: labour management, slotting, yard management, wave picking and far richer putaway and removal strategies.
15
2. "What is a storage type search strategy for?" Probing: the mechanics. Stalls: "Finding stock." Moves up: deciding in which order storage types are considered for putaway or removal, which is how FIFO or fixed-bin behaviour is configured.
16
3. "How does a warehouse task relate to a delivery?" Probing: the document flow. Stalls: "Directly." Moves up: the delivery creates a warehouse request, which generates warehouse tasks for physical movement — three levels, which is why troubleshooting needs all three.
17
4. "Decentralised or embedded EWM?" Probing: the deployment choice. Stalls: "The same." Moves up: embedded removes an interface and is simpler; decentralised isolates warehouse uptime from the ERP and suits very high volumes.
Use cases:wmewmwarehouse-managementlogistics