Honoring Split Constraints

The validates the LPN split constraints defined at the zone and PLA rule levels. These constraints determine whether a license plate can be split during inventory allocation. If split constraints are defined at the zone and PLA rule levels, the system chooses the most restrictive constraint to ensure that constraints defined are not violated.

The enables you to specify the UOM for products stored at a zone. If a UOM is specified:

For example, there is a demand for 25 units (1 case). The pallet quantity is 100 and case quantity is 25. If pallets with cases are stored in a location and the corresponding zone has a constraint for storing products in multiples of case, the enables you to break pallets and pick cases from that location. If the zone is configured to store products in multiples of pallet, then breaking pallets or picking cases from that zone is not allowed. However, in both scenarios, the enables you to pick the entire pallet from the zone.

If a split UOM constraint is defined at a zone level, the UOM must be defined for all items in that zone.

Split constraints defined at the PLA rule level allow you to configure different task types for picking from an LPN or pick full LPNs from the same zone. This is achieved by creating multiple PLA rules for different UOMs.

Although replenishment strategies are configured, the does not perform demand-based replenishment for zones that have split constraints defined at the PLA rule level or zone level. The existing pend in quantities are also not considered for allocation. This is to avoid violating a split constraint because the exact information about the incoming inventory is not available. However, you can replenish such zones using the location monitoring rules.