Search Results gmd_qmdsc




Overview
Explore in AI Chat

Overview

GMD_QMDSC is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. The name and dependency profile identify it as a quality management component within the Process Manufacturing (GMD) product family, specifically supporting disposition and approval-routing logic. The package participates in an Oracle Workflow-driven approval cycle: it evaluates approver eligibility and confirms whether an approval event has been satisfied before the workflow engine advances the disposition to its next state. Its classification in the ETRM repository is "OTHER," indicating a supporting utility package rather than a public or published API. The object is reported as VALID in the documented environment, and it is not referenced by any other database object, so it functions as a top-level entry point invoked by workflow activities, forms, or concurrent processes rather than as a shared library consumed by sibling packages.

Key Procedures and Functions

  • VERIFY_EVENT — Confirms the outcome of an approval or disposition event. In the context of the quality disposition workflow, this routine validates that a required event has been acted upon or completed so that processing can continue or be recorded. It is the package's primary control point for determining whether an event satisfies the workflow's expectations.
  • CHECK_NEXT_APPROVER — Determines the approver to whom the approval should proceed. This routine resolves approval routing, drawing on approver and workflow metadata so that the correct next participant can be identified. It supports sequential or hierarchical approval structures typical of disposition and release-to-use decisions.

Both procedures are documented in the package metadata; parameter signatures are not published in the ETRM extract and should be confirmed against the deployed source in the target instance.

Tables Accessed

  • FND_APPLICATION — Used to resolve application context and identify the owning application for records or configuration lookups.
  • FND_USER — Provides user identity information for approver resolution and validation of workflow participants.
  • WF_RESOURCES — Supplies Oracle Workflow resource and message definitions used when raising or handling workflow events.

Additional dependencies documented for the compiled body include AME_API and AME_UTIL (Approvals Management Engine), FND_PROFILE, PER_ALL_PEOPLE, WF_CORE, WF_ENGINE, and internal GMD objects such as GMD_DEBUG and GMD_RESULTS_GRP. The AME and HR dependencies reinforce that approver determination is delegated in part to EBS approval-management and person/assignment data rather than being computed solely from FND_USER.

Usage Notes

GMD_QMDSC is invoked indirectly through the quality disposition workflow rather than by direct end-user action. Typical call paths include workflow function activities that evaluate whether an approval event has completed and that select the next approver in the routing chain. The dependency on AME_API and AME_UTIL indicates that organizations using Oracle Approvals Management for quality disposition routing rely on this package during approval evaluation.

Because the package is not referenced by any other database object, changes carry limited compile-time blast radius but potentially significant runtime impact on in-flight workflows. Developers extending disposition or approval behavior should treat it as an integration point and avoid duplicating its approval logic. Tracing during troubleshooting is best performed with GMD_DEBUG enabled, since the package depends on that diagnostics utility. In multi-org environments, ensure profile-dependent behavior is validated per operating unit. Customers upgrading from 12.1.1 to 12.2.2 should verify the object remains VALID after patching, as workflow-related packages are frequently recompiled during Online Patching cutover.