Search Results gmd_quality_grp




Overview
Explore in AI Chat

Overview

GMD_QUALITY_GRP is the group-level PL/SQL package body (API classification GRP) owned by the APPS schema in Oracle E-Business Suite, validated and available in both 12.1.1 and 12.2.2. It belongs to the Oracle Process Manufacturing (OPM) Quality family of PL/SQL APIs and provides the centralized logic used to retrieve quality specification values, test results, and approved sampling events for inventory, samples, and specifications. Its name follows the OPM GRP convention, indicating that it is a "group" package: it bundles related retrieval utilities rather than driving a single transactional workflow.

The package primarily serves as a read-and-resolve layer over the OPM quality data model. It reads specification values defined against inventory items and tests, resolves results recorded against samples, and identifies which sampling events have been approved for use in downstream calculation or reporting. This makes it a foundational dependency for higher-level quality processes, such as specification matching, result calculation, and composite result aggregation performed by sibling packages such as GMD_RESULTS_GRP and GMD_SPEC_MATCH_GRP.

Key Procedures and Functions

The ETRM documentation lists five documented program units in GMD_QUALITY_GRP:

  • GET_INV_TEST_VALUE — Returns the specification value associated with an inventory test. It supplies the expected or target value for a given test on an inventory item, used in comparisons against recorded results.
  • GET_INV_RESULT_TEST_VALUE — Returns the test value derived from or recorded against an inventory result. This supports result validation and deviation checks against specification limits.
  • GET_APPR_SAMPLING_EVENTS — Retrieves approved sampling events. It is used to identify sampling events that have passed approval and are therefore eligible for downstream quality processing.
  • GET_INV_SPEC_TEST_VALUE — Returns the specification test value defined for an inventory specification. It resolves the specification-level test value used when evaluating quality results for an item.
  • GET_LEVEL — Returns a level indicator used to classify or rank specification or test data. This is typically used to determine hierarchy or precedence within the quality specification structure.

Tables Accessed

The package accesses OPM quality and specification tables through APPS synonyms. Specification-side tables include GMD_QC_TESTS_B, GMD_SPEC_TESTS_B, GMD_INVENTORY_SPEC_VRS, GMD_SAMPLE_SPEC_DISP, GMD_COMPOSITE_SPEC_DISP, and GMD_EVENT_SPEC_DISP, which define tests, specifications, versions, and their display views. Result- and sample-side tables include GMD_RESULTS, GMD_SPEC_RESULTS, GMD_COMPOSITE_RESULTS, GMD_SAMPLES, and GMD_SAMPLING_EVENTS, which hold recorded results, composite results, sample records, and sampling events. The package also references PLITBLM, an Oracle-supplied PL/SQL table type, consistent with its use of collection-based "IN" lookups and value resolution. These tables are read to resolve specification limits and test values and to identify approved sampling events.

Usage Notes

Because GMD_QUALITY_GRP is a GRP-tier package, it is not invoked directly from a form or concurrent program UI. Instead, it is called by other PL/SQL packages and custom extensions: the ETRM metadata records that it is referenced by two other database objects and that it in turn references GMD_SPEC_MATCH_GRP, GMD_RESULTS_GRP, and its own specification, GMD_QUALITY_GRP. This dependency pattern places it within the OPM quality calculation chain, where specification matching and result-group processing invoke its retrieval functions to obtain test values, specification values, and approved sampling events.

It also depends on the standard EBS foundation utilities FND_API, FND_MESSAGE, FND_MSG_PUB, and FND_PROFILE, indicating use of the standard API error-handling and message stack and profile option lookups, plus GMD_DEBUG for diagnostic logging. Custom code should therefore invoke these functions within the standard OPM quality workflow context and honor the FND message stack when diagnosing failures; direct calls outside the supported quality flows are not recommended.