Recipe Validity Rule API Does Not Set Status As Expected

(Doc ID 419038.1)

Last updated on AUGUST 04, 2015

Applies to:

Oracle Process Manufacturing Product Development - Version 11.5.10 to 11.5.10.2 [Release 11.5]
Information in this document applies to any platform.

Goal

We have developed a wrapper for for creating Recipe Validity Rules by calling "GMD_Recipe_Detail.create_recipe_vr" (file 'GMDPRCDB.pls').

This seems to be working fine, but even though we are passing in a Disposition value of '700' (Approved for General Use), the Validity Rule created has a status of '100' (New).

We believe that the API code is supposed to create the new Validity Rule with the specified Status provided that '100' to '700' is set up as a valid status change.

Solution

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