Search Results gmd_qc_eres_utils




Overview
Explore in AI Chat

Overview

GMD_QC_ERES_UTILS is a group-layer PL/SQL utility package owned by APPS within the Oracle E-Business Suite Process Manufacturing (OPM) Quality Management module. Its primary purpose is to support electronic records and electronic signatures (ERES) compliance for quality results entities, particularly specifications, specification versions, and their associated status transitions. The package provides the procedural plumbing required to enforce 21 CFR Part 11-style electronic signature rules, validate specification state changes, and resolve descriptive attributes (names, codes, descriptions) from primary key identifiers stored in the underlying Quality tables.

The package header comment identifies it as containing "group layer APIs for Results Entity," and its original authorship traces to Chetan Nagar in August 2002, with later additions by RLNAGARA in November 2005 covering three helper procedures. The package carries the standard Oracle copyright notice and was last modified under patchset 120.4. In EBS 12.1.1 and 12.2.2 the package remains classified as OTHER under the ETRM API registry, and it is referenced by zero other packages, indicating it is a terminal utility layer consumed directly by forms, workflows, or custom extensions rather than a shared API hub.

Key Procedures and Functions

The documented interface exposes 42 procedures and functions. The most prominent include:

Tables Accessed

The package operates on OPM Quality base tables accessed through APPS synonyms. Specification and version records are read and updated via GMD_SPECIFICATIONS, GMD_SPECIFICATIONS_B, GMD_CUSTOMER_SPEC_VRS, GMD_INVENTORY_SPEC_VRS, GMD_MONITORING_SPEC_VRS, GMD_STABILITY_SPEC_VRS, and GMD_STABILITY_STUDIES_B. Change and disposition workflow data resides in GMD_CHANGE_DISPOSITION and GMD_COMPOSITE_SPEC_DISP. Test definitions come from GMD_QC_TESTS, GMD_TEST_METHODS, and GMD_SPEC_TESTS, while overall QC state is tracked in GMD_QC_STATUS. User identity for signature capture is pulled from FND_USER.

Usage Notes

Because the package is referenced by no other package, it is invoked directly from Quality Management forms, ERES signature dialogs, and custom extensions rather than through a shared API stack. The status-transition procedures are typically called when a user signs a specification or version change, with ESIG_REQUIRED and CHEK_SPEC_VALIDITY_ERES evaluated first to determine whether a signature challenge is required. The GET_* functions are convenience resolvers used when constructing audit trail displays, validation messages, or report output, allowing forms to render descriptions from stored IDs without embedding direct SQL against the GMD_* tables. When extending the package, developers should preserve the ERES validation order — validity check, signature requirement check, then status update — to maintain regulatory audit integrity.