SAP Supply Chain & Logistics explained

SAP Supply Chain & Logistics is the group of SAP areas that plan and execute the physical movement of goods: stock, warehousing, delivery processing, transportation and supply planning. It spans the classic Logistics Execution (LE) and Warehouse Management (WM) modules and their successors — Extended Warehouse Management (EWM), Transportation Management (TM) and Integrated Business Planning (IBP).

What the area covers

Inventory management (MM-IM) — goods movements, movement types, stock types and physical inventory: the stock truth every other process reads.
Warehouse management — classic WM with storage types, bins and transfer orders; EWM with warehouse tasks and orders, waves, RF scanning, handling units, value-added services and cross-docking; and the Material Flow System (MFS) driving conveyors in automated sites.
Delivery processing (LE-SHP) — inbound and outbound deliveries, picking, packing, goods issue: the document where sales, production and the warehouse meet.
Transportation — TM freight units, carrier selection, freight orders, tendering and settlement; the classic LE-TRA shipment documents where TM has not replaced them; yard logistics and dock appointment scheduling.
Availability and planning — advanced ATP with product allocation and backorder processing; IBP for sales and operations planning, demand and supply; PP-DS for detailed scheduling, the successor line to APO.

What does an SAP Supply Chain & Logistics consultant actually do?

The artefacts are concrete: a warehouse structure — warehouse number, storage types, activity areas, bin naming; determination settings nobody sees and everything depends on — storage type search, warehouse order creation rules, route and carrier determination; specs for what standard will not do, a label layout or an extra RF screen; test scripts carrying one document from order to goods issue; a cutover plan for moving stock without losing count.

The meetings are physical: fit-to-standard workshops, then a walk of the floor with the shift lead who runs the result; integration alignment with the MM, SD and PP consultants whose documents you inherit; carrier onboarding; cutover dry runs.

A week changes shape with the project phase: on site early, walking racks and writing process documents; then configuring and speccing the printing and scanning; then chasing one document across areas to find where it stops. Cutover has a loading dock in it — freeze movements, count, load the stock, go live over a weekend — and hypercare runs on warehouse shifts, not office hours. In AMS the tickets repeat: stuck deliveries, queue errors to a decentralised EWM, failed carrier IDocs, stock that disagrees with the count.

How do people get into SAP Supply Chain & Logistics?

From the domain — warehouse and transport operations, planners, forwarder and 3PL staff who know why a pick path matters.
From the key-user seat — the superuser who ran the warehouse screens and did the counts (the key-user route).
From an adjacent area — MM and SD consultants extend into deliveries and warehousing; PP consultants move towards PP-DS and IBP.
From the technical side — developers who built the RF screens and label output; integration people who kept the queues moving.

What gets someone hired is specific: which warehouse, embedded or decentralised EWM, which processes were in scope (inbound, outbound, internal moves, cross-docking), and whether you were there for the stock migration. Interviews test it: walk a document from sales order to goods issue and name every step (how experience is read).

What it pairs with

Logistics sits inside other processes: Procurement inbound, Sales outbound, Manufacturing for production supply, Quality for inspection and blocked stock, and Finance because every goods movement posts. Underneath sits master data: a material without weights breaks a warehouse before it breaks a report (more area combinations).

Where it is going

Conversion sets the direction: as companies move to S/4HANA, classic WM projects become EWM projects and the embedded-or-decentralised question turns up in every design; planning conversations that said APO now say IBP and PP-DS. Automation pulls MFS and interface work into scope, and clean-core rules push logistics extensions onto BTP. Floor knowledge keeps its value; carrying it into EWM, TM or IBP makes it scarce.