Recipe Validity Rules Standard Oracle API Setting/calculating Incorrect Inv Min And Max Quantities
Last updated on MARCH 30, 2018
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, API Issues
The Recipe Validity Rules API: GMD_RECIPE_DETAIL.CREATE_RECIPE_VR API setting/calculating incorrect Inv Min and Inv Max quantities (INV_MIN_QTY and INV_MAX_QTY in GMD_RECIPE_VALIDITY_RULES) is supposed to calculate INV MIN and MAX quantities in ORG level primary UOM of the item(product) whereas the API calculating quantities in master org primary UOM (most of the cases). Found that there is an issue in deriving primary UOM of the item within recipe validity rules standard API. The cursor which is fetching primary UOM has just select from MTL_SYSTEM_ITEMS without having organization and the first record from the cursor is considering as PUOM hence the INV quantities are calculated based on the first records (most of the time MASTER ORG "PUOM").
Expect this to work like the forms with the correct calculations
The issue can be reproduced at will with the following steps:
Note -Item at MASTER ORG has LBS as PUOM and for the same item ORG1 has KLG as PUOM.
1) Using the API- GMD_RECIPE_DETAIL.CREATE_RECIPE_VR
2) Create recipe validity rule in KLG, the standard API supposed to set INV_MIN_QTY and INV_MAX_QTY in KLG (org PUOM) but quantities are in LBS (Master PUOM).
3) Create recipe validity rule in LTR, the standard API supposed to calculate and set INV_MIN_QTY and INV_MAX_QTY in KLG (org PUOM) but quantities are in LBS (Master PUOM).
The issue has the following business impact:
Due to this issue, users cannot see the correct calculation which is causing production issues.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms