A common pattern in the last few years: the business converts ECC to S/4HANA, the finance and logistics teams sign off, and the warehouse keeps running on the LE-WM it has always used. Nothing on the floor changed, so nothing on the floor got a project. It ran under what SAP calls compatibility scope, a set of classic functions carried into S/4HANA so that conversions did not force every warehouse to move at once. This note is about what happens to that arrangement, and it is part of the wider WM migration series.
What actually changed.
SAP moved the end of Compatibility Pack usage rights for S/4HANA on-premise from 31 December 2025 to the end of May 2026. The compatibility scope matrix, including any item-specific dates, sits in SAP Note 2269324. That is the source to read, for your release, and it is more reliable than a summary from a consultant or a vendor, this one included.
We are not going to tell you what that date means for your contract. It depends on what you bought, when, and on which terms, and that is a conversation between you and SAP. What we can tell you is what it means for the floor, because that is the part we read for a living.
Where the exposure sits.
Stock Room Management is the continuation of LE-WM with a reduced function set. It has been available since S/4HANA 1909, it is part of the S/4HANA core, and it does not run in compatibility mode. So the question for a classic WM site is not whether warehouse management survives. It is which of your WM functions fall inside Stock Room Management, and which do not.
The functions outside it are the ones to look at. Stock Room Management does not include task and resource management, the warehouse control unit interface to automation, value-added services, yard management, cross docking, wave management or decentralised WM. SAP positions it for small warehouses with low automation, and SAP puts its development investment into EWM.
That list is short, but it is not a list of obscure features. Waves and cross docking are everyday tools in a busy distribution centre. The control unit interface is how a WM system talks to a conveyor or a shuttle. If your floor uses any of these, you have exposure. If it does not, you may have far less than you feared.
Start with an honest inventory.
The first job is not a licence review or a business case. It is a list of which WM functions the site uses on the floor today, set against what is merely configured. Those are different lists, and the gap between them is often large.
Classic WM systems collect configuration over fifteen or twenty years. Someone set up wave management for a customer who left in 2014. A cross docking movement type exists because a project once needed it for six weeks. The yard tables are populated and nobody has opened them since the consultant went home. None of that is exposure in any operational sense, because no operator depends on it, but it looks identical to live use in a configuration report.
So the inventory is done on the floor, not in the system alone. For each of the functions above, ask who uses it, on which shift, and what happens to the operation if it stops. Task and resource management: are operators being assigned work by queue and resource, or are people walking to a screen and picking their own transfer orders? Automation: is anything on site driven through the control unit interface? Waves: are pick waves released on a schedule the floor plans around? Cross docking, yard, value-added services and decentralised WM get the same questions.
Three paths from there.
Once the inventory is honest, the choices are fewer than they first appear.
Stay within Stock Room Management scope.
If the floor uses little beyond storage, putaway, picking and stock control, moving from compatibility scope to Stock Room Management may be all that is needed. It suits a small warehouse with modest automation, which is how SAP itself positions it. The trade-off is that you are staying on the part of the warehouse portfolio where SAP is investing least, so it is a considered holding position and not a destination. Our note on Stock Room Management or EWM goes through how to judge whether it fits.
Move to basic EWM in the core.
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, resource management, and integration to quality, production and transportation management. It also includes an IDoc interface to third-party material flow systems. For a site that has outgrown Stock Room Management but does not need the heavy automation and yard tooling, this is often the honest middle. Exact scope varies by release and contract.
Move to advanced EWM.
Advanced EWM is licensed separately as a supply chain product. It brings direct control of automation, wave management, yard management, labour management, cross docking, value-added services, slotting, cartonisation and decentralised EWM, among other things. If the inventory shows the floor depends on several of those, this is the path that matches the operation. The distinction between the two EWM levels is covered in basic or advanced EWM.
Whichever path fits, migration runs per warehouse number, so it can go one warehouse at a time. And EWM is designed, not translated: storage types, activity areas and process types are new structures, and open transfer orders should be finished or cancelled before the freeze, not counted on to carry across.
The exposure is not classic WM as a whole. It is the handful of functions your floor uses that sit outside Stock Room Management, and you cannot size that from a configuration report.
What to do about the paperwork.
Read SAP Note 2269324 for your release. Then confirm your position with your SAP account team, in writing. Luminar is not a licensing adviser and will not pretend to be one. What we bring to that conversation is a clear, floor-level statement of which functions you use, so your questions to SAP are specific instead of general. “Do we have a problem?” gets a vague answer. “We run wave management and a control unit interface to a sorter on this release, where do we stand?” gets a useful one.
If you are still on ECC.
ECC sites run a separate clock. Mainstream maintenance for EHP 6 to 8 ends on 31 December 2027, with optional extended maintenance to 2030. That is a different deadline with a different mechanism, and the two should not be blended into one. But the inventory is the same exercise and worth starting early, because it shapes the conversion approach itself: a site that knows it will land on EWM plans its conversion differently from one that assumes classic WM carries straight over. The broader picture is in our note on SAP WM end of life.
How Luminar reads it.
We are independent and we do not sell the build. A senior consultant spends a day on your floor, watches which functions people actually rely on, and writes it up in a memo you can hand to your SAP account team and your board. No proposal is attached. If the answer is that Stock Room Management will do, we will say so.