A common moment in a SAP WM migration goes like this. The programme is choosing a destination for the warehouse, someone from procurement mentions that advanced EWM is a separate licence, and the conversation turns into a budget argument before anybody has described what the warehouse actually does. Two weeks later there is a slide with a licence line on it and no operational reasoning behind it at all. That order of events is backwards, and it is avoidable.
What you already own.
Basic warehouse management sits in the S/4HANA core, under the Enterprise Management licence. It covers inventory management, inbound and outbound processing, internal movements, physical inventory, the warehouse monitor and analytics, resource management, and the integration points into quality management, production and transportation management. It also includes an IDoc interface to third-party material flow systems, which matters more than it sounds, and we will come back to it.
For a large share of warehouses that is a real, working system: goods come in, get put away, get picked and shipped, stock is counted, and a supervisor can see the state of the building on a monitor. Plenty of sites moving off classic WM will find their whole operation describes itself in that list.
What sits on the other side of the line.
Advanced (extended) EWM is licensed separately, as a supply chain product. The list of what it adds reads like a catalogue of everything a busy, complicated building eventually wants: the material flow system for direct control of automation, wave management, transportation units, yard management, labour management, cross docking, value-added services, warehouse billing, kitting, dock appointment scheduling, slotting, cartonisation, just-in-time supply to production, work-in-progress tracking, decentralised EWM and advanced interleaving.
Two cautions before you plan around that list. Exact scope varies by release and by contract, and an on-premise agreement does not read the same as a RISE one. Check your own contract and SAP's feature scope description for the release you are actually landing on. Luminar reads the operation; we do not sell licences, and we will not tell you what your agreement says.
The second caution: none of this is the same as Stock Room Management, which is the reduced continuation of classic WM inside the S/4HANA core. If you are weighing that option too, that note sets out what it leaves out and who it suits.
The questions that tip a site into advanced.
Read the licence list as a set of operational questions and the decision becomes something you can walk a floor with. These are the ones that matter most.
Is there automation that needs direct control?
Conveyors, sorters, shuttles and cranes need a warehouse system that controls them directly, not one that hands them a message and waits. Basic gives you the IDoc interface to a third-party material flow system, so a site whose automation vendor runs its own control layer can be perfectly well served. A site that wants SAP to drive the equipment is asking for the material flow system, and that is on the advanced side.
Do people, not just stock, need managing?
If supervisors want to know who is doing what, measure it against standards and release work by workload, that is labour management. It is one of the clearer dividing lines, because a site either runs that way or it does not.
Does the building have a yard, a cross dock or value-added work?
A yard with trailers queuing, dock appointments to schedule, stock that moves from inbound door to outbound door without touching a bin, or kitting and labelling done on site: each of these has an advanced component behind it. A site that receives, stores and ships does not need any of them.
Is the pick profile complicated enough to want waves, slotting and cartonisation?
Releasing work in waves against carrier cut-offs, placing fast movers where they are cheapest to reach, and choosing the right carton for an order are optimisation features. They earn their place on a site with real order volume and a lot of small lines. On a slower, pallet-based operation they are decoration.
Will the warehouse run apart from the ERP, or across several sites?
Decentralised EWM is on the advanced list. If the group plans several sites on one template, or the warehouse has to keep working while the ERP is down, the embedded or decentralised question is already answering the licence question for you.
Why the licence conversation should come second.
There are two ways to get this wrong, and they cost differently. Buy advanced because it is what the integrator usually proposes, and you pay for a set of capabilities the floor never switches on. Settle for basic because it is already paid for, and a year after go-live you find the operation wants labour management or direct automation control that the licence never included. That second mistake is the expensive one, because it lands after the design is set.
A typical case is a site that has run classic WM for a long time with a lot of local workarounds. Half of those workarounds exist because WM could not do something the operation needs. Ask the floor which of those workarounds it would like to stop doing, and you have a shortlist of advanced features with a business reason attached to each one. That shortlist is what the contract discussion should start from, and it is worth having before anybody talks about the licence line, including what a rollout costs.
The licence tells you what you are allowed to switch on. Only the floor can tell you what you need to.
What this means for the migration.
Basic and advanced are not two products with a wall between them. Warehouse by warehouse, a group can take different sites to different depths (how the licence is written decides the commercial side of that), and the design work for each site is a different size. Structures like storage types, activity areas and warehouse process types are designed in EWM, not translated from WM, so the more of the operation you bring into scope, the more there is to design and test.
It also means a site can move first on what it owns and add the advanced features later, as long as the first design does not paint the operation into a corner. That is a design judgement, and it is the one worth paying an independent to make. We have seen what happens when a national operation goes live on EWM without the operation being read first (the EWM rescue is the short version), and we have seen a central template carry ten warehouses in one market (the APAC rollout).
How Luminar approaches the call.
We do not sell the build and we do not resell SAP, so we have nothing to gain from either answer. On a WM migration we spend a day on the floor with the operation, the shift pattern and the workarounds, and we map what we see to the basic and advanced lists above. Then we write it up in plain language: this site fits the core, this one has two features that need advanced, this one is unclear and here is the question that would settle it. You take that memo to your SAP account team and your contract, and the negotiation starts from the operation.