Search Results set_spec_status

Overview

The APPS.GMD_QC_ERES_CHANGE_STATUS_PVT package is a private PL/SQL API within the Oracle E-Business Suite Process Manufacturing (OPM) Quality Management module. Its purpose is to manage electronic signature (e-signature) records and status transitions for quality specifications and their associated version/revision entities. The package name derives from "ERES" (Electronic Records and Electronic Signatures), reflecting its role in supporting 21 CFR Part 11 compliance for regulated industries such as life sciences and pharmaceuticals. It is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the invoking user rather than the definer.

The package is classified as PVT (private), indicating that it is an internal implementation building block rather than a published, supported public API. It is typically called by other OPM Quality packages, forms, or workflow processes rather than directly by end users or external integrations.

Key Procedures and Functions

The package exposes five documented program units. Public procedure parameter lists are not enumerated here, consistent with the guidance that only purposes be described.

• SET_SPEC_STATUS — Updates the status of a specification identified by a specification ID, moving it from a source status to a target status while recording the associated signature status. This is the object directly associated with the user's search term "set_spec_status."
• SET_SPEC_VR_STATUS — Parallel to SET_SPEC_STATUS, but operates on a specification version/revision entity, accepting an entity type to distinguish among the various specification revision tables (customer, inventory, supplier, and so on).
• UPDATE_VR_STATUS — Performs the underlying status update on a version/revision record, taking the entity type, the version/revision ID, and the target status. It encapsulates the low-level modification logic used by the higher-level status-change routines.
• CHEK_SPEC_VALIDITY_ERES (function) — Returns a Boolean indicating whether a specification is in a valid state to permit a given status transition for a specified event, serving as a validation gate before the change is applied.
• ESIG_REQUIRED (function) — Returns a Boolean indicating whether an electronic signature is required for the specified event, event key, and target status, enabling the caller to enforce e-signature capture where mandated.

Tables Accessed

The package reads and writes specification and version/revision data through APPS synonyms. GMD_SPECIFICATIONS_B holds the base specification header, the primary target of SET_SPEC_STATUS. The remaining tables store version/revision records for distinct specification categories: GMD_CUSTOMER_SPEC_VRS, GMD_INVENTORY_SPEC_VRS, GMD_SUPPLIER_SPEC_VRS, GMD_MONITORING_SPEC_VRS, GMD_STABILITY_SPEC_VRS, and GMD_WIP_SPEC_VRS. These are used by the version/revision routines to locate and update the appropriate revision record based on entity type. E-signature and status values are persisted against these entities.

Usage Notes

Because this is a private package, it is not intended for direct invocation by custom code. It is normally called from OPM Quality forms (such as specification maintenance or approval screens), from workflow-driven approval processes, or from other internal OPM packages that orchestrate status changes and e-signature enforcement. The ETRM metadata records zero other packages referencing it, reinforcing its role as an internal helper. Implementers extending or troubleshooting specification status and e-signature behavior in EBS 12.1.1 or 12.2.2 should treat this package as a supporting component of the broader OPM Quality framework and rely on the public specification APIs for supported customizations.