AGVs in production supply
Read more
Migration of SAP WM and SAP TRM to SAP EWM Alternative solution for discontinued components
SAP is cancelling support for two important logistics modules. For all users, this means that they will have to start looking for a replacement for SAP Warehouse Management (SAP WM) and SAP Task and Resource Management (SAP TRM). These modules were fully integrated into the SAP ERP system R/3, the end of which has been a foregone conclusion for some time now. But don't worry, we are happy to help you find alternatives. In this blog post, we look at the background and present the prospects.
But how did the current situation come about?
Support for the old and proven SAP R/3 ERP system ends on 31 December 2027, with the option of a fee-based extension until 2030 (also applies to SAP ECC). This means that support will also end for all available logistics modules such as WM, LE-TRA, XSI and SAP TRM. For all companies that are still using SAP R/3 modules or SAP ECC, the countdown is running for a switch to the new SAP S4/HANA platform. This is the latest ERP generation from SAP and the successor to SAP ERP R/3, which has been available for decades.
Let's take a look at the current situation and the options that are available:
FAQs
SAP Warehouse Management is a solution for warehouse management and is responsible for processing goods movements. SAP WM can be used to manage storage bin stocks and divide warehouses into areas (storage zones). SAP transfer orders are also generated, which map the transport of goods in the warehouse. This old module has been discontinued and support for it will also expire in 2027. SAP Stock Room Management (SAP SRM) is being considered as the direct successor to SAP WM (as an ERP-integrated solution). But more on this later.
To refine the transfer orders in SAP WM, there was the SAP TRM module, which could break down the transfer orders into smaller units (tasks). This made it possible to fine-tune internal warehouse orders. SAP TRM was there to control warehouse requirements such as putaway, picking, forklift transport orders and material flow. SAP TRM was an integral part of the SAP WM module (later also called SAP LES) and was designed to optimise and manage tasks and resources in the warehouse. The SAP LES and SAP TRM components have also been discontinued in the meantime. There is no successor solution in SAP Stock Room Management. Customers who previously used SAP TRM therefore need an alternative solution for this scope of services that will be discontinued in the future.
Can be used instead of SAP WM: SAP Stock Room Management
The replacement for SAP WM is the aforementioned warehouse management component SAP Stock Room Management (SAP SRM). However, it should be noted that SAP Stock Room Management is not a new warehouse management module from SAP. Rather, it is a technical option for continuing to use the "old" SAP Warehouse Management module (with the "old" ABAP coding) in the new SAP S/4 ERP environment. This means that no new SAP WM functions are included in this "module". On the contrary: Stock Room Management even restricts certain SAP WM functions, as picking waves can no longer be used, for example. RF transactions and the IDOC interface WM-LSR are also no longer available or are no longer technically supported.
Furthermore, SAP Stock Room Management in the SAP S/4HANA environment will only be available until 2027 (or 2030). SAP is therefore planning to look for another (more sustainable and new) solution by then.
Solution component instead of SAP TRM
The situation is even worse for the SAP TRM module. This component is no longer available in SAP Stock Room Management. So if you want to use SAP SRM for stock room management, you have to do so without SAP TRM. And since the WM-LSR interface is also no longer supported, customers have to look for completely new solutions and (in the worst case) switch to an external (non-SAP) material flow computer - including all dependencies and interfaces to such a third-party system.
So what can you do?
SAP recommends switching to one of the now diverse SAP EWM implementation variants as a successor solution. SAP EWM is available both as SAP S4/HANA Cloud in the "Private Edition" variant as a private cloud and in other data centre variants.
But first things first: SAP S/4HANA Cloud Private Edition is a private cloud variant that is provided as Software-as-a-Service (SaaS). It is a cloud ERP solution that can be flexibly adapted to the company's individual transformation. Further information on the migration options for the SAP S/4HANA Supply Chain component can be found on our IGZ information page on SAP S/4HANA Supply Chain.
Embedded SAP EWM and decentralised SAP EWM
SAP EWM can also be used as an embedded version or as a decentralised version. SAP defines embedded as the use of warehouse management functions directly in the ERP system (similar to the previous, old SAP WM solution), even if EWM has internal interfaces to the ERP. One of the advantages is that the same database is used as in the ERP. The disadvantage is that both scalability and performance are reduced to small to medium-sized warehouses.
The decentralised setup means that a separate S/4HANA system is used exclusively for the SAP EWM functionality. This refers to the full and powerful scope, including the control of complex logistics systems with a high level of automation. This is realised with the integrated SAP EWM module, SAP MFS.
Sensible intermediate steps
Migrating to a new SAP EWM solution is obviously the most sustainable solution, even if it involves larger investments (e.g. new SAP licences, implementation of new processes). For many customers, however, there are dependencies (especially with the embedded version) on their „RISE-with-SAP“ project, i.e. the implementation project of the SAP S/4HANA ERP system. As a result, many customers often opt for a quick interim solution and want to use the SAP Stock Room Management mentioned above.
In our experience, however, the associated limitations are often underestimated. We have already highlighted this in the paragraph above. However, there are also elegant "interim steps" that serve both as transitional scenarios and also represent a sustainable investment in the future SAP EWM architecture.
Particularly in connection with automated systems (high-bay warehouses, small parts warehouses, shuttles), the IGZ service portfolio includes various possible solutions - from SAP add-on solutions for material flow (in addition to Stock Room Management) to SAP EWM as a material flow system (with and without SRM). Individual migration paths with a mixed utilisation of the aforementioned SAP components also often lead to a better result than a "hard" big-bang changeover.
In our view, the target scenario for automated warehouses is always the use of SAP MFS. It is mainly used to control the material flow in automated warehouse systems such as automated small parts warehouses and high-bay warehouses. SAP MFS enables the efficient control of highly dynamic, fully automated shuttle AS/RS storage systems, sorting systems and sequencers. It is also used in complex, highly automated logistics centres - because this is exactly what SAP built this software for.
In contrast, the (transitional) use of non-SAP systems, e.g. as material flow computers, would be a step backwards and create unnecessary external interfaces and, in the worst case, data inconsistencies, risks and dependencies.
Conclusion
The major advantage of the replacement variant with SAP "board resources" is clearly that with this maximum SAP integration, no external middleware or subsystems need to be used to maintain the performance of the system. Interfaces are reduced and at the same time planning and investment security is increased. Nothing stands in the way of a smooth transition from the "old" to the "new" world even before the end of support.
Do you have any questions or would you like more information on the subject of migration? If you are currently dealing with the digitalisation of your logistics processes, please contact us! We will be happy to advise you on your individual migration path and provide you with helpful tools for test automation, for example (e.g. Automated Rapid Validation), to enable a secure migration. Migration cockpits are also part of the IGZ service portfolio.
We look forward to hearing from you!
