No Matter What Value is Passed to the GME_API_PUB.INSERT_MATERIAL_LINE API for WIP Plan Quantity, the WIP Plan Quantity Ends Up NULL for Auto by Step Ingredients
Last updated on APRIL 04, 2018
Applies to:Oracle Process Manufacturing Process Execution - Version 12.1.3 and later
Information in this document applies to any platform.
On : 12.1.3 version, API Issues
When using the gme_api_pub.insert_material_line.sql API to insert an Auto by Step ingredient line in a WIP batch and associating it with a Pending step (by passing a value for the step number), no matter what you pass in as the WIP Plan Qty the line is inserted with WIP Plan Qty as Null. In addition, you can pass in a Plan Qty, which you cannot do in a WIP batch through the forms.
When doing this on the Batch Details form, the Plan Qty field is grayed out and the WIP Plan Qty field is required in a WIP batch, even for Auto by Step ingredients and even when the step number you enter is a Pending step, so it is expected that the API functions the same way. In addition, when you release a batch with an Auto by Step ingredient associated with a Pending step, the WIP Plan Qty gets defaulted. So the API behaves differently than all other scenarios.
The issue can be reproduced at will with the following steps:
1. In a WIP batch that contains a Pending step, use the gme_api_pub.insert_material_line.sql API to insert an ingredient, setting Consumption Type to Auto by Step (p_material_detail_rec.release_type := 3) and passing in the pending step number as p_batchstep_no
The issue has the following business impact:
Due to this issue, WIP Plan Qty is missing.
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