From the Wave Exceptions page, you can track orders that cannot be part of a given wave rule and the reason for that. This article will cover the seven reasons why orders cannot be allocated within a wave rule that has been run.
The wave exceptions are as follows:
Shortage: There may not be enough inventory for the product or it does not match the algorithm rules.
Rule Order Condition: The order's criteria may not match the wave's criteria.
Eliminated by 'Single Item' Condition(s): The job type is for single orders and the selected orders are not single.
Eliminated by 'Identical Item' Condition(s): The job type is for identical orders and the selected orders are not identical.
Eliminated by 'Min N of Orders' Condition(s): The order may not be included in the jobs created with the order wave due to the minimum order quantity.
Eliminated by 'Min/Max N of Products' Condition(s): The order may not be included in the jobs created with the order wave due to the minimum or maximum product quantity.
Eliminated by Job Type 'Advanced' Condition(s): The order's criteria may not match the advanced conditions in the job type.
Shortage Example
In this example, there is no inventory from MRV-HB-THANOS-1, so id7045 has a shortage, and therefore products cannot be allocated with the wave named singleonly.
Order Code, Wave No, Wave Rule Set Name, Allocation Algorithm Rule Name, Shortage SKU, Shortage Quantity, Inventory Quantity, Order Detail Quantity, Allocation Algorithm, Explanation and Is Roll Backed columns can be seen above.
Eliminated by 'Single Item' Condition(s)
In this example, the criteria of 11621abcd do not match with the Single Item job type, so it cannot be allocated by the wave named singleonly.
Order Code, Wave No, Wave Rule Set Name, Explanation and Is Roll Backed columns can be seen above.
Couldn’t Find What You Were Looking For?
Visit our Help Center to search more documents!