Warehouse Management (WM), Stock Room Management, embedded EWM or decentralized EWM - a colorful bouquet of possibilities
In this second part, we would like to provide you with further decision-making assistance on how to make a smooth changeover and go into more detail on additional functions.
EWM versus WM - process flows
In addition to the differences regarding master data, there is another significant one: The process flow or the communication between warehouse management and the adjacent modules.
“Embedded EWM” is not necessarily the same as “embedded”, as many customers assume. The difference lies in the fact that certain interface settings must be made. More precisely, certain documents must be exchanged to ensure a smooth process. In the following diagrams, I would like to contrast the SAP WM/EWM process flows.
Goods receipt for the order
Differences between WM and EWM regarding goods receipt
Currently, the customer is used to posting the goods receipt via MIGO, then receiving a transfer requirement and completing the putaway via the resulting transfer order. In contrast to SAP WM, SAP EWM requires inbound deliveries (VL31N) from SAP ERP so that the customer can complete the putaways.
The inbound delivery is replicated in SAP EWM. This represents the transfer requirement in SAP EWM to later start the putaway via warehouse tasks. And here is the crucial difference: the goods receipt takes place in SAP EWM for the inbound delivery (transaction /SCWM/PRDI) and is reported back to SAP ERP. Only after the goods receipt, the putaway is started, the goods are stored in the bin and the process is completed with a confirmation.
Alternatively, the goods receipt can be posted with the confirmation of the putaway. As a rule, however, the first case is used, since the two storage location strategies provided by SAP EWM would otherwise be redundant. Only with the “GR posting” an intermediate storage location is posted (Received on Dock), so that everyone in the system can see that these goods have already been received. However, it is not available for further processes until it is in the final storage bin. Then the system would automatically post a transfer to a second storage location (Available for Sales) when the warehouse receipt is confirmed. This has the benefit that the goods can only be accessed when the goods are actually available in the bin.
SAP EWM creates transparency
In contrast to SAP WM, SAP EWM can start earlier in the process and create more transparency. As early as the “unloading” of the truck, warehouse tasks can be mapped for the movements from the truck to the goods receipt area. In addition, the system recognizes mixed pallets, which are automatically routed to a deconsolidation station. The employee repacks these into pallets that are homogeneous in terms of material/batch, so that optimum use of storage space is also ensured.
Impact on personnel can be kept low
For many customers, the process with deliveries is unfamiliar territory at first, as questions immediately arise such as:
- “Who places the delivery?”
- “When do I create the inbound delivery?”
- “How does purchasing set up its order confirmation process?”
- “Which fields can I still change in the ERP for the inbound delivery?”
For the employees, the process is new at first, but it is not a reason to do without SAP EWM. On the contrary, the changeover could be a reason to persuade the supplier to process the inbound deliveries automatically via a DESADV in order to become more efficient in the supply chain as well. After all, there is also the chance to exchange pallet data in advance, so that the incoming goods department is less burdened. Alternatively, there are always ways and means to streamline the process and keep the impact on personnel as low as possible.
Releases bring gradually more integration
With the introduction of SAP’s S/4HANA system, EWM and all its features were embedded in S/4HANA at the beginning without being truly more integrated. Therefore, SAP is continuously working on creating more integration. Since the S/4HANA 2020 release, it is now possible to post a goods receipt for a purchase order without inbound deliveries (synchronous update). However, this function cannot be used with QM integration. It will only be available in a later release.
Goods receipt for production order
The SAP WM process works in the same way as for the “goods receipt for purchase order”. In SAP EWM, the goods receipt for the production order works very similarly. There is only one difference here. The starting point is not the inbound delivery, but the MIGO, which at the end creates the inbound delivery in SAP ERP in the background and replicates it again for SAP EWM. The rest of the process is exactly the same as for the purchase order. This means that even if you post the MIGO, no material document is created at first. This comes as usual from the inbound delivery in SAP EWM (/SCWM/PRDI). The MIGO initially triggers only the inbound delivery.
This procedure seems very unusual for customers, as they are usually used to a material document being created after a MIGO posting. Here, too, the material document is triggered from SAP EWM at the end, so that the process in SAP EWM can also be handled in the same way as the other processes. The synchronous booking can be used just like the GR for the purchase order.
Goods issue for customer delivery
Before the goods issue is posted for the customer outbound delivery, the transfer orders must be created and processed in SAP WM. After that, the goods issue posting for outbound delivery is possible.
In an EWM warehouse, an outbound delivery must first be created on the ERP side with the VL01N so that it can be replicated to EWM. Then, as usual, the warehouse tasks are created and confirmed via the transaction /SCWM/PRDO. The goods issue can then be posted in EWM for outbound delivery and transferred to the ERP system.
Subsequently, it would still be possible in EWM to map the loading onto the truck with the help of warehouse tasks in order to create transparency in the process here as well and, if necessary, to post the goods issue only with the loading onto the truck.
This process should be more familiar to most customers, as the sequence in WM is the same. However, the advantage of EWM clearly is the transparency of the downstream process of loading.
EWM versus WM - functions
SAP EWM basically offers more functionality than SAP WM. However, there are two features that are already available without an additional EWM license. These are on the one hand the layout-oriented storage control (LOSC) and on the other hand the process-oriented storage control (POSC).
The storage control can only be used if handling units are formed in the warehouse. It is also possible to use LOSC and POSC simultaneously, whereby all steps from POSC are always processed first. Afterwards, LOSC checks whether the process step is possible from the LOSC point of view.
EWM vs. WM - more insight with the warehouse monitor
It is often difficult for warehouse managers to have an overview of all processes and to be able to react correctly in a short time. In WM, stocks are checked using LX03, but transfer orders are created using LT10. Old documents are checked with LT24. In addition, there are many transactions to start certain actions. However, one does not have the possibility to act from a LX03.
With the EWM warehouse monitor (/SCWM/MON) one now has everything in sight and the possibility to act from the monitor. Everything that takes place in EWM can be accessed from here. It is possible to create storage tasks for stocks and also to confirm them from the monitor. It is also possible to start a mass confirmation of warehouse tasks. The monitor always helps to keep the overview and to be able to react accordingly. If the layout of the monitor does not suit you, it can be customized. With the help of a multi-split screen, it is possible for users to see a lot of information at a single glance.
EWM vs. WM - greater user-friendliness thanks to FIORI
With the introduction of S/4HANA, SAP is also taking a new approach to the user interface. The goal is to make it easier for users to work with SAP. For this purpose, FIORIs were established, which can be accessed in the web browser with the help of the FIORI Launchpad. This makes it possible to launch the applications on all modern end devices such as smartphones or tablets. They then automatically adapt to the screen. The apps are intended to liberate users from the SAP GUI, since every transaction in the SAP GUI is also available in the FIORI Launchpad. In this way, users can focus on browser-based work. Customers who still have an ECC6.0 can also benefit from FIORIS.
It is important to distinguish whether you are using a “real” FIORI or a “fiorized” app. A “real” one was newly developed by SAP with special regard to added value and user-friendliness.
A “fiorized” app represents an SAP GUI transaction rendered for the FIORI launchpad. The functions and layout mirror the SAP GUI transaction. However, users would not see any difference here. This step was necessary because it was not possible to provide new apps from the start for all the business processes required in SAP.
To keep track of which apps are currently available, you should work with the SAP FIORI Apps Reference Library. There you will find all the information you need to use an app. With each new release, more and more “real” FIORIs are offered.
Enclosed are layout examples for a “real” and a “fiorized” app.
Now we have learned that we can use Stock Room Management on an SAP S/4HANA system to replace the WM module from ERP ECC 6.0. However, there is some bad news here: there are no FIORI apps for Stock Room Management provided in the standard.
Since EWM is the strategic product for SAP, “real” and “fiorized” apps are only offered here. If the customer is now planning a FIORI strategy for himself, then they must think carefully about whether Stock Room Management matches this strategy. If the customer still decides in favor of FIORI and Stock Room Management, then the only option left is to develop their own FIORI apps.
EWM has a clear advantage here. There are already very good “real” FIORIs that also create real added value for users, and the range is constantly growing. Nevertheless, from my point of view, the standard FIORIs do not replace the well-known RF applications for mobile data collection. The FIORI apps are more suitable for desktops that also have a fixed workstation, such as for the “packing in goods issue” process. Nevertheless, my recommendation is to clarify beforehand which processes the customer has and then to decide whether an already available FIORI fits and can possibly be used mobile after all. This requires an exchange with the users.
EWM vs. WM - other important features
It is understandable that the customer struggles at first with a strategy in the jungle of warehouse management. We can help you with your decision making! We take a determined look at your needs and this includes a fair assessment of whether Stock Room Management might make sense after all, even if it is not SAP’s strategic product. We recommend not to reject EWM prematurely just because it seems more complex and unfamiliar. The important thing is to put the right resources in the right place. My opinion is that especially Basic EWM offers great added value for our customers – and that without additional costs!
We are here for You!
If you are thinking of making the switch, let us know. We hope this two-part blog series has helped you with your transition plans. We’re here to help you make your operations more efficient, transparent, and cost-saving to improve your supply chains. Have we sparked your interest? Then please feel free to contact us.
If you have any questions about this or any other topic on the blog, please contact us at firstname.lastname@example.org.
Senior Consultant SAP Logistics
Latest news and blog posts from the world of intelligent supply chain management.