In this article I describe the option of confirming the movement of several handling units to one storage bin collectively.

 There are two collective confirmation options:

• A Confirm the number of HUs only in the last destination bin
• B Confirm the number of HUs in all relevant destination bins

Let us go through each of them with an example.

Suppose you have one warehouse order with five tasks for moving five handling units to the following two destination bins:

WT1 – SB1

WT2 – SB2

WT3 – SB1

WT4 - SB2

WT5 – SB1

With option A:

When confirming the putaway of the HUs into destination bin SB1, the system will first ask for each HU to be scanned (as in the normal mode), that is three times – for WT1, WT3 and WT5.

Then, when confirming into bin SB2, the system recognises that this is the last destination bin in this order. Two remaining HUs have to be put away into it, and the employee only needs to enter the number of HUs being put away:

With option B:

When confirming the putaway of the HUs, the system will not require the HUs to be scanned at all; it will only ask for the number of HUs being put away, first for bin SB1 and then for bin SB2. This case assumes that the employee has worked out outside the system, and knows, which HU goes into which bin, and in the system merely confirms the number of HUs being put away.

Now let us look at what determines which mode the system works in. For the time being this is configured only in SM30. There are just two maintenance views for it:

• The table that selects the option in use - /SCWM/V_MPHU_DET (table /SCWM/TPCKHUDET)
• The search sequence table for selecting the option - /SCWM/V_MPHU_DTS (table /SCWM/SPCKHUDET)

The choice of option depends on the following self-explanatory fields:

• Warehouse number
• Warehouse order creation rule
• Activity area of the warehouse order
• Warehouse process type (at warehouse order level)
• Type of the resource executing the warehouse order
• Source storage type (if there are several source storage types in one warehouse order, the system takes it from the first confirmed pick warehouse task)
• Destination storage type

The search sequence table is a standard one and needs no further explanation:

It is all quite simple and transparent. This functionality allows warehouse processes to be optimised at least a little, and it appeared in the following support packages:

Software Component Version	Support Package
SCMEWM 900	SAPK-90015INSCMEWM
SCMEWM 910	SAPK-91009INSCMEWM
SCMEWM 920	SAPK-92005INSCMEWM
SCMEWM 930	SAPK-93003INSCMEWM

You can read more about implementing this functionality in the SAP note:

2230367 - RF Picking allows collective confirmation of multiple HU tasks to the same destination

If you want to see how it works under the hood, take a look at the code in the class method /SCWM/CL_RF_SET_FCODE_PCKHU-GET_PICK_METHOD

Good luck!