SAP Extended Warehouse Management vs. Shiraz WCS

Well suited: Warehouses with similar large volume SKUs defined processes that just needs digitization and automation Not suited: Warehouse with multiple small volume SKUs, non-uniform ways of workings, lack of resources - basically not suitable for functions like R&D or smaller organization dealing in a lot of small volume SKUs like e-commerce

Incentivized

• Physical Inventory
• Inbound Process
• Trailer close
• Inventory Management

Incentivized

• Batch management must be more flexible
• Queues which gets stuck, there must be much more details to fix it
• KBA must be published and available to support customer fix the issues by themselves
• Once the IBD gets distributed to SAP Extended Warehouse Management we will not be able to edit anything in S4H this makes it complex to handle it, it must be flexible

Incentivized

I think it's a good WMS product providing end to end features from basic to advanced - I have reduced 30% for lack of usability for smaller organizations, multi sku smaller volume cases, lack of free training material, lack of inbuilt guidance and training, heavy reliance on external consulting firm. So, this result in lack of proper adoption post implementation.

Incentivized

We are using Max attention, which is a perfect (but costly) extension for prod support.

Incentivized

Typically, we recommend eWM to clients for following reasons: 1. Clients are mostly using SAP as their core ERP and eWM becomes a natural choice coming embedded with SAP Extended Warehouse Management 2. SAP Extended Warehouse Management is feature heavy and fulfills the needs for any larger operation for which BY and Manhatten might not be suitable 3. Multiple consulting vendors or partners for support and maintenance

Incentivized

• We just started to use it so the benefits are not yet clearly visible
• In the future I see that we can save work hours when we get all the functionalities working as we want

Incentivized