Search Results gmdrvlap_wf_pkg




Overview
Explore in AI Chat

Overview

APPS.GMDRVLAP_WF_PKG is a PL/SQL package body in the Oracle E-Business Suite Process Manufacturing (OPM) schema. Its name derives from the OPM recipe development module (GMDRVLAP) and the Oracle Workflow engine (WF), indicating that the package coordinates Oracle Workflow activity around recipe validity rule approval. In OPM, a recipe or recipe version can be governed by validity rules that define the effective dates, status transitions, and organizational scope under which the recipe may be used. This package provides the programmatic driver that initiates, monitors, and responds to the workflow that routes such recipe validity rule changes for review and approval before they take effect.

The package is classified as OTHER in the ETRM documentation rather than as a public API, which reflects its role as an internal supporting component invoked by OPM forms and workflow processes rather than by external integrations. It remains VALID in both 12.1.1 and 12.2.2, and no other database object references it, confirming that it is a leaf-level dependency consumed primarily through Oracle Workflow activities. The package depends on core EBS infrastructure including FND_DATE, FND_PROFILE, FND_USER, WF_CORE, WF_ENGINE, WF_ITEMS, and GMA_WFSTD_P, alongside OPM data objects and the e-records utility package GMD_ERES_UTILS.

Key Procedures and Functions

The package exposes eight documented procedures and functions, each aligned to a stage of the recipe validity rule approval lifecycle:

  • WF_INIT — Initializes the workflow for a recipe validity rule approval event, establishing the item context and attributes needed by subsequent activities.
  • IS_APPROVAL_REQ — Determines whether the change in question actually requires approval, allowing the workflow to be short-circuited when no review is mandated.
  • REMINDAR_CHECK — Evaluates outstanding approval notifications and drives reminder processing for items awaiting response.
  • REQ_APPROVED — Handles the approved outcome, applying or advancing the recipe validity rule once all required approvals are obtained.
  • REQ_REJECTED — Handles the rejected outcome, terminating the workflow and leaving the underlying recipe validity rule unapplied.
  • NO_RESPONSE — Manages the timeout or no-response condition when an approver does not act within the allotted time.
  • MOREINFO_RESPONSE — Processes the request-for-more-information response, routing the item back to the originator for additional detail or comment.
  • APPEND_COMMENTS — Adds approver or originator comments to the workflow item history and to any associated e-records audit trail.

Tables Accessed

The package reads and writes the principal OPM recipe structures. GMD_RECIPES and GMD_RECIPES_B hold recipe header information, while GMD_RECIPE_VALIDITY_RULES stores the validity rule records whose approval state the workflow manages. GMD_STATUS_NEXT is used to resolve the next permissible status transition, and MTL_SYSTEM_ITEMS_KFV supplies the item key flexfield view for the products associated with the recipe. FND_USER resolves approver and originator identities, and WF_ITEMS, together with the workflow activity data table GMA_ACTDATA_WF, stores the workflow item state and activity attributes. ORG_ORGANIZATION_DEFINITIONS provides the operating unit context used to filter approvers and validity scope.

Usage Notes

GMDRVLAP_WF_PKG is typically invoked indirectly. The OPM recipe development forms raise a validity rule change, and the configured Oracle Workflow process calls WF_INIT to launch approval. Notification responses route to REQ_APPROVED, REQ_REJECTED, MOREINFO_RESPONSE, or NO_RESPONSE as appropriate, with REMINDAR_CHECK handling periodic reminder and timeout evaluation. Because the package is not referenced by other database objects, customizations that need to observe or extend this flow should hook into the workflow definition rather than calling the package directly. Any custom wrapper must respect the APPS schema, the standardized workflow attribute structures, and the e-records behavior delivered through GMD_ERES_UTILS, since bypassing these dependencies can break audit compliance and leave recipe validity rules in an inconsistent state.