Supply Chain Management Blogs by SAP
Expand your SAP SCM knowledge and stay informed about supply chain management technology and solutions with blog posts by SAP. Follow and stay connected.
Showing results for 
Search instead for 
Did you mean: 
Active Participant
A couple of weeks ago, we have released our innovations in the area of Warehouse Management in SAP S/4HANA Cloud 2011. You can find the overview of this release in this presentation:


This release brings with it features and enhancements in the areas of inbound processing, mobile warehousing and a number of cross-process functionalities.

I would like to mention four highlights of this release:

Synchronous Goods Receipt Postings for External Procurement

In previous releases we have provided functionalities for synchronous goods movement postings from production. Now, with the 2011 release we take one step further in this direction by providing the synchronous postings also for goods receipt from external procurement. Via the Post Goods Movement app we support now goods receipt postings for purchasing documents (standard purchase orders, scheduling agreements, purchase orders referencing value or quantity contracts and stock transfer orders) to a WM managed storage location, goods receipt postings with handling units as well as an (optional) automatic putaway warehouse task creation. Furthermore cancellations of goods receipt documents are supported via this app. The WM document number is displayed in the Post Goods Movement app and allows navigation to the goods movement document in WM as well as to the warehouse task.

This improved integration between S/4 and WM helps to avoid hanging queues between ERP components of S/4HANA and WM and guarantees synchronous stock updates in MM-IM and WM. Error messages are displayed directly in the Post Goods Movements app. One big advantage is the fact that this allows now to mix goods receipt for MM-IM and WM managed storage locations in one posting.

Looking at the data traffic in the system, it leads to less documents as no inbound deliveries or warehouse request documents are needed anymore:

Enhanced API to Process Warehouse Tasks

Another highlight I would like to mention is the enhancement of the already existing API to process warehouse tasks by the functionality to create warehouse tasks. This new feature does not only allow the creation of warehouse tasks for deliveries but also the creation of ad-hoc warehouse tasks for products and handling units.

All available APIs can be found via the SAP API Business Hub.

Enhancements in Handling Unit Management

In the area of handling unit management, we have shipped a number of enhancements with the 2011 release. I would like to draw your attention to one highlight: the replication of HUs from the LE delivery to WM.

Before the 2011 release, handling units could only be created locally in WM, for example via the packing app. Now with the 2011 release, handling units in LE can be created with reference to an inbound delivery, e.g. via an Advance Shipping Notification, and replicated to the delivery in cloud WM where they can be used for further processing. Alternatively they can be deleted in cloud WM.

For now, this is supported for one-level handling units but we are planning to provide this functionality for nested handlings units with a future release.

To get more details on the above-mentioned highlights, or to explore our other features and enhancements of the Warehouse Management Cloud 201 release, please access our presentation.

Completely pick warehouse requests

Compared to the previously mentioned highlights this one is a rather small one but with a big effect: in the SSCUI to change the warehouse process type settings, you will find as of the 2011 release a new flag called “completely pick” which you set for certain process types. Setting this flag results in a system behavior for picking warehouse task creation that only creates warehouse tasks for an outbound delivery if all warehouse tasks for the delivery can be created. Without this flag, i.e. before 2011, delivery splits and consolidation efforts were necessary if e.g. an outbound delivery had 3 items but only warehouse tasks for 2 items could be created (due to not available quantities at the time of task creation).

As always, more content to come in the next releases, so please stay tuned.

You may also want to check out the blog post about Manufacturing and Digital Supply Chain in SAP S/4HANA Cloud 2011 by Gerhard Welker.

To make sure you are notified of new blog posts, please follow our assigned tag, SAP Extended Warehouse Management

For more information about SAP Extended Warehouse Management, please follow us on social media, our YouTube channel or our community pages:

SAP S/4HANA Cloud Community ->

SAP EWM Community ->

SAP Digital Supply Chain Channel ->

EWM LinkedIn Community ->

For a complete list of Q&A from the EWM community, please access this link:

In case you do not find your specific question there, feel free to post your question via the following form: