Search Results gmd_qc_test_values_grp




Overview
Explore in AI Chat

Overview

GMD_QC_TEST_VALUES_GRP is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite. It belongs to the Oracle Process Manufacturing (OPM) Quality Management module and is classified as a GRP-type API, indicating it functions as a group or utility package rather than a standalone business entity handler. Its role is to manage the values associated with quality control tests defined in the OPM Quality Management system. Quality control tests capture measurable characteristics such as assay percentages, viscosity, pH, or appearance attributes that are evaluated against specifications for raw materials, intermediates, and finished goods. The package encapsulates the logic for validating, describing, and transforming these test values, and it is referenced directly by five other database packages, confirming its position as a shared utility layer in the OPM quality data model. The package body is documented as VALID, and it is not referenced by any object outside the APPS schema, which is typical for internal group utilities in the OPM stack.

Key Procedures and Functions

  • NAME — Returns the package identifier, used primarily for diagnostic and error-reporting purposes so that messages can be attributed to the correct package.
  • VALIDATE_BEFORE_DELETE — Performs integrity checks before a single test value record is removed. It verifies that the deletion does not violate referential or business constraints, such as a value being referenced elsewhere in the quality workflow.
  • VALIDATE_AFTER_DELETE_ALL — Executes after a full set of test values has been deleted, confirming that the resulting state is consistent and that any downstream dependencies remain valid.
  • GET_TEST_VALUE_DESC — Retrieves a descriptive text for a given quality control test value, supporting display requirements in forms and reports where codes must be rendered as user-readable descriptions.
  • TEXT_RANGE_CHAR_TO_SEQ — Converts a character-based range specification into a sequence representation. This supports test value ranges that are expressed textually but must be processed numerically or in ordered sequence form.

The package is documented with seven procedures or functions in total; the remaining routines are not enumerated individually in the available metadata and should be inspected in the source for parameter-level detail. No parameter lists are presented here, in accordance with the documented interface.

Tables Accessed

The package reads and writes against the GMD_QC_TESTS, GMD_QC_TESTS_B, GMD_QC_TEST_VALUES, and GMD_QC_TEST_VALUES_B tables through APPS synonyms. The base tables (GMD_QC_TESTS and GMD_QC_TEST_VALUES) store the operational quality control test definitions and their associated values, while the _B variants hold the base-language definitions used by the multi-language translation framework. Accessing both base and translated tables allows the package to validate and describe test values consistently across language contexts. It also depends on the companion packages GMD_QC_TESTS_GRP and GMD_QC_TEST_VALUES_GRP itself, as well as the FND_API, FND_MESSAGE, and FND_MSG_PUB application framework utilities for error messaging.

Usage Notes

GMD_QC_TEST_VALUES_GRP is typically invoked indirectly rather than directly by end users. It is called from within the OPM Quality Management forms and from other OPM packages that manage quality test specifications, results entry, and specification validation. Because it is referenced by five other packages, it acts as a supporting utility layer rather than a top-level concurrent program entry point. Developers extending OPM quality functionality should treat this package as an internal API: it should be called to perform validation before and after value deletion and to obtain descriptive or range-transformed representations of test values, but callers should not bypass its validation logic by manipulating the underlying tables directly. In Oracle EBS 12.1.1 and 12.2.2, the package remains valid and available in the APPS schema, and any custom code invoking it must hold appropriate APPS privileges and account for the FND message framework dependencies.