The gmd_status_pub.modify_status API Incorrectly Validates That There are No Converted FPO's, Errors if There Are
Last updated on MARCH 08, 2017
Applies to:Oracle Process Manufacturing Product Development - Version 12.2.4 and later
Information in this document applies to any platform.
On : 12.2.4 version, API Issues
When attempting to use the gmd_status_pub.modify_status API to change the status of a recipe validity rule that is Approved for General Use, if you have no Pending, WIP, or Completed batches and no Pending FPOs, but just a Converted Firm Planned Order (FPO), the API errors with the following error.
Could not change Validity Rule status because this validity rule is currently associated with a batch. Please set the parameter p_ignore_flag to TRUE to change the status.
This does not seem to make sense, since a Converted FPO is not an active document (I confirmed that if you partially convert an FPO the status remains Pending, so it appears to be only a fully converted FPO that has the status of Converted). It should be treated like a Closed batch and not be looked at in the validation.
If you pass TRUE to the parameter p_ignore_flag you can avoid this error, but then you might accidentally change the status of a validity rule that is used on an open batch.
The issue can be reproduced at will with the following steps:
1. Convert a batch to an FPO
2. Cancel or complete the batch
3. Try to use the API to change the recipe validity rule status from Approved for General Use to On Hold or Obsolete/Archived.
The issue has the following business impact:
Customer is in a controlled environment and follow GMP practices. All updates to Formula/Recipe/VR/Routing happens using API. They also use FPOs. This bug prevents them Obsoleting recipe validity rules.
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