SAP logistics: one chain, six modules, one process

A sales order triggers a requirement, the requirement a purchase or production order; the goods are inspected, put away, picked, transported and billed. In SAP this one process is spread across six modules – and most problems arise exactly where one hands over to the next. That is why we do not look at a module, but at the chain.

Our roots are in MM and SD; from there the adjacent modules have been added over the years – PP and QM in chemicals projects, EWM and TM in transformation and implementation projects. Those who know the handovers find the error where it arises, not where it shows.

How you know you need this

When the chain gets stuck at the handovers, it usually shows like this:

Stocks in the warehouse, in purchasing and in accounting do not match, and every department has its own explanation.
Production orders wait for material that the system says is there – or material waits for a quality release that production knows nothing about.
Deliveries are picked before the transport is planned, or planned before the goods are ready.
Every module has its key users, but nobody feels responsible for the process from start to finish.

Six modules, one chain

We follow the process through the modules – and stop at the handovers where it pays off:

PP – Production Planning

Requirements planning, production orders, confirmations and the link to procurement: we make sure planning and execution see the same figures and material availability is never a surprise.

MM – Materials Management

Procurement, inventory management, invoice verification – our core module. This is usually where the master data lives on which the other modules depend.

QM – Quality Management

Inspection lots at goods receipt and in production, batch release, complaints. Especially in chemicals and pharmaceuticals, QM decides when goods are usable – and thus over stocks, delivery dates and documentation duties.

EWM – Warehouse Management

Goods receipt, putaway, picking, goods issue. The handover to transport and sales is where it shows whether warehouse and dispatch work with each other or side by side.

SD – Sales

Order-to-cash from pricing to credit memo. Sales triggers the chain – and at the end feels whatever did not run cleanly along the way.

TM – Transportation Management

Planning, execution and freight settlement, embedded in S/4HANA or standalone. Our current focus: in a client engagement we advise today on planning and execution.

Not every project needs all six modules. But every project needs someone who keeps an eye on the handovers – and that is exactly the task we take on, in a single process project as much as in a group template.

What a cross-module project additionally demands

The survey follows the entire chain, with the key users of every area involved – and marks the handovers where documents, stock or dates do not currently line up.
For each handover we settle who is responsible. That is the real work: not the individual transaction, but the question of who owns the document that leaves a module.
Where a group template or a group guideline applies, we align the solution with it rather than building a second version of the truth.
Because several areas are affected at once, the supported start takes longer than for a single module – the chain only settles in day-to-day operations.

The framework behind it applies to every implementation project of ours and is described on the SAP overview. How we work – the shared framework

From your side we need one key user with functional responsibility per module and – more importantly – a process owner who may decide across departmental boundaries. If that person is missing, we help you settle who in your organisation holds that responsibility.

What lies around the chain

Three topics come up in almost every S/4HANA programme with a logistics share and are easily confused with the modules. This is how we place them:

Planning: SAP IBP alongside the chain

Overarching planning – demand, inventory, supply, S&OP, control tower – SAP has bundled in SAP Integrated Business Planning, a cloud solution alongside S/4HANA that since 2025 has been gradually bringing time-series and order-based planning together in a single planning area. For your programme that means: planning is created in IBP, execution in S/4HANA, and the handover between the two is a handover of its own that someone has to own.

Availability: Advanced ATP

The availability check in S/4HANA is called Advanced Available-to-Promise and is not a separate application but a business function in the core: backorder processing, product allocation, alternative confirmation from other plants, substitution. It sits exactly at the handover from sales to warehouse and production – and whoever does not define in the programme which orders are confirmed first when supply is short leaves that decision to chance in day-to-day business.

Dangerous goods: Product Compliance

Dangerous goods live in S/4HANA under Product Compliance with Dangerous Goods Management: classification, dangerous goods documents, checks. Transportation Management checks freight orders, bookings and the building of freight units against it. What tends to be underestimated is the dependence on master data: without a maintained dangerous goods classification on the material, every check comes up empty – in chemicals that is a work package with its own deadline, not a customizing setting.

What you end up with

A documented end-to-end process from order to invoice, with clear responsibilities at every handover
Stocks, dates and documents that say the same thing in all modules involved
Cleansed master data that purchasing, production, quality, warehouse, sales and transport carry together
An integration test across the whole chain that you can reuse with every release
Key users who know their module and understand the process behind it

What we do not do

We do not take on pure detailed production scheduling, laboratory integration or plant connectivity alone; for these we bring in specialists from our network.
SAP Basis tasks and our own developments are not part of our offering. Our field is process and customizing – across module boundaries.
We do not set up a module as an island. If a project is meant to deliberately leave out the handovers, we tell you beforehand what the consequences are.

Typical questions

Do we have to touch all modules at once?: No, and usually that would not be wise. We start where it hurts most and keep an eye on the handovers to the neighbouring modules. Often a clean master data basis in MM already solves part of the problems in PP, QM and SD.
Do we need QM if we are not in a regulated industry?: Usually on a smaller scale, but rarely not at all. Goods receipt inspection and complaints handling affect almost every company. In chemicals and pharmaceuticals, batch release with documentation duties comes on top – there QM is a load-bearing module of the chain.
How does this fit with an S/4HANA transformation?: Very well, because the transformation is the moment when the chain is set up anew anyway. Those who define the handovers cleanly then save themselves many individual projects later. We bring the logistics view into the fit-to-standard workshops.
Do you also take on individual modules, say only PP or only QM?: Yes, if the process behind it is clear. We take on PP and QM above all in combination with MM and SD; for pure detailed scheduling or laboratory topics we bring in specialists from our network as needed.

Initial consultation on the SAP logistics chain

At which handover does it get stuck for you – between purchasing and production, warehouse and transport, sales and accounting? Describe the spot in two sentences and we will tell you how we would proceed. And if you are an implementation partner responsible for the whole chain and need experience from corporate programmes at one of the handovers: that is exactly where we come in.