Search Results append_comments

Overview

APPS.GMDRVLAP_WF_PKG is the Oracle Process Manufacturing (OPM) workflow integration package responsible for driving the approval lifecycle of recipe validity rules. In EBS 12.1.1 and 12.2.2, recipe validity rules defined in GMD_RECIPE_VALIDITY_RULES govern when a given recipe version is considered effective, and changes to those rules frequently require managerial or quality approval before they take effect. This package bridges the OPM recipe validity rule data model and the Oracle Workflow engine, providing the callback procedures that the workflow item type invokes at each activity node.

The package is declared with AUTHID CURRENT_USER, so all unqualified references to tables such as GMD_RECIPE_VALIDITY_RULES resolve through the invoker's schema and the APPS synonyms, consistent with standard EBS PL/SQL security practice. Its header carries the legacy OPM source identifier (GMDRVLAS.pls), confirming it originated in the process manufacturing code family and remains part of the ETRM (Engineering and Recipe Management) module in Release 12.

Key Procedures and Functions

The package exposes eight documented procedures. WF_INIT initializes and launches the workflow for a specific recipe validity rule, taking the rule identifier, its recipe, the starting status, the requested target status, the requester, and the last update date — thereby establishing the item key and the initial routing context. IS_APPROVAL_REQ is a workflow function that determines whether approval is required before the next activity proceeds, returning a result through p_resultout. REMINDAR_CHECK supports reminder and notification escalation handling for outstanding approval activities.

The remaining procedures are event callbacks that respond to approver actions. REQ_APPROVED handles the approval outcome — the specific path referenced by the search term "req_approved" — and typically advances the recipe validity rule to its approved target status while clearing any rejection state. REQ_REJECTED processes a rejection, returning the rule to its prior status. NO_RESPONSE manages timeout or non-response conditions, and MOREINFO_RESPONSE handles requests where the approver has asked for additional information. APPEND_COMMENTS records approver comments against the workflow item and the underlying rule.

All callback procedures share the standard Oracle Workflow signature: item type, item key, activity identifier, function mode, and an output result. These are registered as function activities or notification callbacks within the OPM recipe validity rule workflow item type.

Tables Accessed

The package reads and writes GMD_RECIPE_VALIDITY_RULES, the master table holding each rule's status and approval attributes, and joins to GMD_RECIPES and GMD_RECIPES_B for the recipe header and description used in notifications. GMD_STATUS_NEXT supplies the valid status transitions that govern routing, while GMA_ACTDATA_WF stores workflow activity data such as approver responses and comments. FND_USER resolves approver and requester identities for notification addressing, and MTL_SYSTEM_ITEMS_KFV provides item descriptions where recipe items are referenced. WF_ITEMS and related Workflow views are used to read and update the workflow item state as processing proceeds.

Usage Notes

GMDRVLAP_WF_PKG is not intended for direct invocation by end users. It is called by the Oracle Workflow engine when a recipe validity rule is submitted for approval from the OPM Recipe Validity Rules form, and by concurrent or background processes handling the OPM recipe approval workflow. It is referenced by at least one other documented package in the ETRM schema, and workflow administrators register its procedures as activity functions within Workflow Builder. Customizations that change recipe approval routing should extend the underlying workflow definition rather than altering this package, and any direct calls must run in the APPS schema context with appropriate privileges on the GMD and FND objects.