WMS RULE CONSISTENCY NOT WORKING AS EXPECTED
(Doc ID 1284700.1)
Last updated on MARCH 09, 2023
Applies to:
Oracle Warehouse Management - Version 12.1.3 and laterInformation in this document applies to any platform.
Symptoms
=== ODM Issue Clarification ===
On : 12.1 version, Rules Engine
We've had a number of WIP Picking Rules working for nearly 6 months. Recently we decided to enhance the rules by including a 'Consistency' setting on rules where it would be appropriate.
For example; one of our rules picks Pill Bottles and we wanted it to pick lots that all came from the same supplier ... so we added 'Object Name: Lot' and 'Parameter Name: Supplier' to the 'Consistency' tab on this rule and several similar rules for other components.
Now we're finding that this setting is failing even when there are sufficient materials on hand. For example: If we need 100,000 bottles and we have the following inventory available:
* Lot AAA, Qty 60,000, Supplier: FRED
* Lot BBB, Qty 60,000, Supplier: WILMA
* Lot CCC, Qty 60,000, Supplier: FRED
* Lot DDD, Qty 60,000, Supplier: WILMA
(Assume the rule sorts only by Lot Number. Also, Partial Success is Allowed in the strategy.)
With this 'Consistency' setting in place the rule will fail to allocate anything ... but it should allocate all of AAA and 40,000 from CCC. If we disable the 'Consistency' setting the rule will allocate all of AAA and 40,000 from BBB ... which is not what we want and why we enable the consistency setting in the first place.
Either the consistency functionality is not working for this parameter or we're doing something wrong.
Please enlighten us as to the appropriate setting and/or what the Lot/Supplier setting is actually comparing to as it enforces consistency.
EXPECTED BEHAVIOR
-----------------------
Expect ... consistency functionality to allocate when Partial Success is Allowed in the strategy
but not allow materials from different suppliers to be allocated into the same job
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
see previous ...
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Unexpected results implementing consistency rule functionality
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |
References |