Last updated on MARCH 08, 2017
Applies to:Oracle Process Manufacturing Product Development - Version 12.1.3 and later
Information in this document applies to any platform.
On : 12.1.3 version, Product Development Validity Rules
When a validity rule is created for a recipe based on a formula that disallows scaling, the min_qty, max_qty, and std_qty are all supposed to be saved with the qty of the product from the formula, and the inv_min_qty and inv_max_qty should be the min_qty and max_qty converted to the item's primary UOM. No other quantities should be allowed, as the formula is for only one quantity. If the validity rule UOM is the same as the item's primary UOM, then what should happen is that inv_min_qty = min_qty = max_qty = inv_max_qty.
This works correctly on the Recipe Validity Rule Details form, GMDRVRED.fmb, but not if you create the validity rule on the Recipe Validity Rules form, GMDRVRSM.fmb. The min_qty, max_qty, and std_qty get set correctly, but the inv_min_qty defaults to 0 and the inv_max_qty defaults to 999999999.
Expect the Recipe Validity Rules form to work the same as the Recipe Validity Rule Details form, and to set the inv_min_qty and inv_max_qty correctly.
The issue can be reproduced at will with the following steps:
1. Create a formula with scaling disallowed on the formula header
2. Create a recipe
3. Create a couple of validity rules on the Recipe Validity Rule Details form (necessary in order to get the Recipe Validity Rules form to be accessible), and then create a validity rule on the Recipe Validity Rules form.
The issue has the following business impact:
Due to this issue, the validity rule data is wrong, which can cause problems when creating batches or doing other things that use the validity rule.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms