Search Results gmdqsvrs_approval_wf_pkg




Overview
Explore in AI Chat

Overview

GMDQSVRS_APPROVAL_WF_PKG is an Oracle Quality Management (formerly Oracle Process Manufacturing) PL/SQL package owned by APPS that implements the approval workflow for Specification Validity Rules (SVR) within Oracle E-Business Suite 12.1.1 and 12.2.2. The package is associated with the workflow process GMDQSVRS_ISAPROVAL_REQUIRED, whose purpose is to determine whether an approval is required for a given specification validity transaction and, where required, to drive that transaction through a routed approval path and to update the specification status accordingly.

The package couples the Quality specification model (customer, inventory, monitoring, stability, supplier, and WIP validity rules) with the Oracle Workflow engine. Its procedures act as standard Workflow function and notification activities, receiving the conventional Workflow context parameters (p_itemtype, p_itemkey, p_actid, p_funcmode, p_resultout) and returning standardized activity results. When the Spec Validity Rule Approval business event is raised, the package verifies whether approval is needed; if so, it moves the specification status to the pending status defined by GMD_QC_STATUS_NEXT and populates the workflow attributes so that notifications can be sent to the appropriate approvers.

Key Procedures and Functions

  • IS_APPROVAL_REQ — Evaluates whether the current specification validity rule transaction requires approval before it can proceed. It returns a Workflow activity result that gates the downstream routing.
  • ANY_MORE_APPROVERS — Determines whether any approvers remain in the configured approval list. This is the function most commonly referenced in custom troubleshooting ("any_more_approvers"), since it controls loop termination in the approval routing.
  • APPEND_COMMENTS — Appends approver comments (typically supplied through the notification response) to the accumulated comments on the approval transaction or specification record.
  • NO_RESPONSE — Handles the timeout path when an approver does not respond within the allotted notification period.
  • REQ_REJECTED — Processes a rejection response from an approver and updates the specification/transaction status accordingly.
  • REQ_APPROVED — Processes an approval response and advances the transaction to the approved state.
  • REMINDAR_CHECK — Handles reminder notifications for pending approvals (note the documented spelling).
  • GET_STATUS_MEANING — Retrieves the translated meaning of a specification status code, resolving the language-specific description from the status code table.
  • RAISE_SPEC_VR_APPR_EVENT — Raises the Spec Validity Rule Approval business event, which initiates the workflow and populates the workflow attributes required by the subsequent activities.

Tables Accessed

The package reads and writes the specification validity rule tables that store the approval target: GMD_CUSTOMER_SPEC_VRS, GMD_INVENTORY_SPEC_VRS, GMD_MONITORING_SPEC_VRS, GMD_STABILITY_SPEC_VRS, GMD_SUPPLIER_SPEC_VRS, and GMD_WIP_SPEC_VRS. Specification definitions come from GMD_SPECIFICATIONS_B, and status transitions are governed by GMD_QC_STATUS and GMD_QC_STATUS_TL (the translatable status descriptions used by GET_STATUS_MEANING). Organization and item context is resolved from HR_ALL_ORGANIZATION_UNITS, MTL_PARAMETERS, MTL_SYSTEM_ITEMS_KFV, and FND_USER. Workflow infrastructure tables WF_PARAMETER_LIST_T and WF_RESOURCES support attribute population and message/notification lookups.

Usage Notes

GMDQSVRS_APPROVAL_WF_PKG is invoked by the Oracle Workflow engine rather than being called directly by application forms. It executes when the Specification Validity Rule approval business event is raised from Quality specification maintenance and when a user responds to an approval notification through the Workflow Notification detail page. Rejections, approvals, forwards, transfers, timeouts, and reminder cycles all re-enter the package through the Workflow function activity interface.

The package is not referenced by any other PL/SQL package in the documented metadata, so customizations should avoid direct invocation; instead, custom code should raise the business event or query workflow status. Because the workflow loops through approvers using ANY_MORE_APPROVERS, misconfigured approval lists can cause stuck or prematurely terminated approval flows, and troubleshooting typically begins by inspecting WF_PARAMETER_LIST_T for the item key and verifying the returned activity result. No parameter lists should be assumed beyond the standard Workflow context and result conventions described in the header documentation.