Flexible template - virtual handling units

The bottom-level node of a handling unit template can be virtual. This means that the quantity of bottom-level handling units and the quantity of items contained in them can vary, but the total item quantity of the bottom-level node cannot exceed the quantity of the parent node.

Consequently, the quantity of bottom-level handling units and items can differ every time handling units are generated based on the template during the shipment process. If the bottom-level node of a handling unit template is virtual, LN selects the Virtual check box in the Handling Units (whwmd5130m000) session for the generated bottom-level handling units.

The advantage of using virtual handling units is that fewer handling unit templates are requited to create efficient handling unit structures for different ordered quantities, provided that the generated bottom-level handling units need not exactly reflect the handling units actually used.

Note

Restrictions such as multi-item and single reference apply to both virtual and nonvirtual nodes. See the example in Sequencing.

Setup

To set up virtual bottom-level handling units:

Define a variable package definition. See To define package definitions.
For the bottom-level node of the handling unit template, select the Virtual Node check box in the Handling Unit Templates (whwmd4160m000) session. Because the bottom node is virtual, specifying an item quantity and a packaging item quantity is not allowed.

Note

The Virtual Node check box is unavailable for validated package definitions. If the package definition is validated, you must undo the validation before you can select the Virtual Node check box.

Example of non-virtual template node

This handling unit template is defined for package definition PCKD10:

Parent Node	Node	Virtual Node	Packaging Item	Packaging Item Quantity	Item Quantity in Storage Unit	Allow Multi Item for Shipping
0	1		Pallet	1	0	Selected
1	2		Crate	2	0	Selected
2	3	Cleared	Box	6	120	Cleared

These outbound order lines are created:

Order	Order line	Item	Quantity	Package definition
SLS001	10	1011	20	PCKD10
	20	1012	30
	30	1013	10

Order	Order line	Item	Quantity	Package definition
SLS022	10	1011	20	PCKD10
	20	1012	20
	30	1013	20

For order SLS001, this handling unit structure is generated:

Level	Node	Handling unit	Multi-item	Item	Quantity
1	Pallet	HU001	Selected
2	Crate	HU002	Selected
3	Box	HU004	Cleared	1011	20
3	Box	HU005	Cleared	1012	20
3	Box	HU006	Cleared	1012	10
2	Crate	HU003	Selected
3	Box	HU007	Cleared	1013	10

Because a Box cannot contain more than 20 items according to the template, item 1012 is put in two Boxes. The second crate and Box HU007 is created because a crate cannot contain more than three Boxes, and the Box level is single-item. In everyday practice, the picker is bound to put all boxes in one crate anyway.

For order SLS022, this handling unit structure is generated:

Level	Node	Handling unit	Multi-item	Item	Quantity
1	Pallet	HU008	Selected
2	Crate	HU009	Selected
3	Box	HU010	Cleared	1011	20
3	Box	HU011	Cleared	1012	20
3	Box	HU012	Cleared	1013	20

Example of virtual template node

If the handling unit template of package definition PCKD10 has a virtual bottom-level node, these handling unit structures are created for orders SLS001 and SLS022:

SLS001
Level	Node	Handling unit	Multi-item	Item	Quantity
1	Pallet	HU013	Selected
2	Crate	HU014	Selected
3	Box	HU015	Cleared	1011	20
3	Box	HU016	Cleared	1012	30
3	Box	HU017	Cleared	1013	10

Because the Box-level is virtual, LN can put as many items in a Box as required to build an efficient handling unit structure, as long as the maximum quantity allowed for the Crate node is not exceeded. Consequently, 30 items 1012 are all put in Box HU016 and all Boxes can be put in one Crate. Items 1011 and 1013 cannot be put together in one box because the Box level is single item.

SLS022
Level	Node	Handling unit	Multi-item	Item	Quantity
1	Pallet	HU018	Selected
2	Crate	HU019	Selected
3	Box	HU020	Cleared	1011	20
3	Box	HU021	Cleared	1012	20
3	Box	HU022	Cleared	1013	20

The use of a virtual bottom-level node results in a more efficient handling unit structure for SLS001, whereas the resulting structure for SLS022 is identical for both templates. If the virtual bottom level node is not used, an additional package definition is required to create equally efficient handling unit structures for both orders.