Search Results spec_vr_status




Overview
Explore in AI Chat

Overview

GMD_QC_ERES_CHANGE_STATUS_PVT is a private PL/SQL package body in the Oracle E-Business Suite Process Manufacturing (OPM) Quality module. Its business function is to manage the electronic signature (e-signature / ERES) driven status transitions applied to quality specifications and specification validity rules. When a user performs a status change on a specification or a specification validity rule that requires an electronic signature, the Oracle E-Records (EDR) signature flow determines whether the transaction succeeded, is pending, or was rejected. This package translates that signature outcome into the appropriate status value on the underlying specification records.

The package is classified as a private (PVT) API, meaning it is intended for internal use by the Quality/e-Records framework rather than as a public integration interface. The header comment (GMDVEREB.pls 120.1) indicates the source file is associated with the OPM specification e-records functionality.

Key Procedures and Functions

  • SET_SPEC_STATUS — Applies a status transition to a specification header record. It resolves the effective signature status (either the value supplied by the caller or the current value held in EDR_PSIG_PAGE_FLOW.signature_status) and then updates the specification accordingly. On a successful signature it moves the specification to the requested target status; on a pending signature it derives a pending status; and on rejection it derives a rework status.
  • SET_SPEC_VR_STATUS — The specification validity rule counterpart of the above. It performs the same signature-status resolution and dispatches the resulting status change for a validity rule identified by p_spec_vr_id and an entity type, delegating the actual update to UPDATE_VR_STATUS.
  • UPDATE_VR_STATUS — Performs the physical status update on the appropriate validity rule table, selected according to the entity type supplied. It is invoked by SET_SPEC_VR_STATUS once the target status has been determined.
  • CHEK_SPEC_VALIDITY_ERES — Determines whether a validity rule operation requires an electronic signature under the configured e-record rules, providing the gating check before the signature flow is engaged.
  • ESIG_REQUIRED — Indicates whether an e-signature is required for the operation in question, supporting the decision logic of the calling flow.

The status derivation for pending and rework outcomes relies on GMD_QC_STATUS_NEXT_PVT (get_pending_status and get_rework_status), passing an entity type of 'S' for specifications.

Tables Accessed

The package reads and writes specification and validity rule data through APPS synonyms. GMD_SPECIFICATIONS_B is updated by SET_SPEC_STATUS to change spec_status at the specification level. The validity rule tables — GMD_CUSTOMER_SPEC_VRS, GMD_INVENTORY_SPEC_VRS, GMD_MONITORING_SPEC_VRS, GMD_STABILITY_SPEC_VRS, GMD_SUPPLIER_SPEC_VRS, and GMD_WIP_SPEC_VRS — are accessed by UPDATE_VR_STATUS. The specific table used depends on the entity type supplied by the caller, which is why the package references the full family of validity rule tables rather than a single one. These tables therefore cover the customer, inventory, monitoring, stability, supplier, and WIP specification validity rule contexts.

Usage Notes

Because this is a private package referenced by no other documented packages, it is not intended for direct customer invocation. It is driven by the Oracle Quality e-records specification flow, typically when a user changes the status of an OPM specification or specification validity rule from a form and an electronic signature is required. The package is invoked after the signature page flow completes, using the signature outcome to set the final, pending, or rework status. Custom code should not call these procedures directly; standard integration should use the public Quality specification status APIs or the concurrent programs and forms that wrap them. Organizations implementing 21 CFR Part 11 compliant e-signatures on specification changes rely on this package indirectly through that standard flow.