In this closing article I will sum things up and briefly go through the steps SAP EWM performs when creating a warehouse order once more. The steps are described in more detail in WOCR – part 1 and WOCR – part 2.

 As a reminder, a warehouse order is a document in SAP EWM that represents a package of work to be carried out by a warehouse worker. A warehouse order consists of one or several warehouse tasks. A warehouse task is a single activity in the warehouse, for example picking from a bin or counting it. To control the rules by which warehouse orders are created, SAP EWM provides the WOCR functionality. Put simply, these are the rules for selecting warehouse tasks and combining them into a single order so that a warehouse worker can execute it in the most efficient way.

So, when a warehouse order is created, all warehouse tasks are passed to the WOCR functionality. Based on rules, filters and limits, WOCR either puts all tasks into one order or splits them into several orders according to a certain logic.

The overall picture of the process looks like this:

Note: the picture is taken from the book «Fundamentals of SCM EWM A step by step Guide»

While being processed in WOCR, warehouse tasks are:

1. Sorted according to the inbound sorting rules
2. Filtered by warehouse task attributes
3. Filtered by consolidation groups
4. Split according to the limit values
5. Filtered and combined by matching packaging types
6. And as the last step, the tasks within the created orders are sorted

As you can see, the WOCR functionality allows warehouse worker assignments to be configured quite flexibly. And even when customer requirements are so specific that they cannot be met with standard functionality, you can make use of the various BAdIs in the /SCWM/ES_WHO enhancement spot:

That concludes the series of articles about WOCR. I hope it is now clearer what WOCR is and how to use it.