Results for “gmd_qc_status_next_pvt”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The APPS.GMD_QC_STATUS_NEXT_PVT package body is a private (PVT-classified) PL/SQL implementation object within the Oracle E-Business Suite Process Manufacturing (OPM) quality module. It provides the internal logic that determines the next applicable quality control status for a given QC record or specification, supporting the status transitions enforced by the Quality Control framework. The package is classified as an API of type PVT, indicating that its members are intended for internal consumption by other packages rather than for direct invocation by external or customer-written code. In Oracle EBS 12.1.1 and 12.2.2, this package belongs to the APPS schema, is currently reported as VALID, and forms part of the underlying program unit structure that governs QC status progression logic used by OPM quality operations.

Key Procedures and Functions

The documented package body exposes two procedures or functions, each responsible for resolving a specific status category:

• GET_REWORK_STATUS — Determines the QC status that applies when a material, lot, or quality result is directed to rework. It encapsulates the business rule that maps the current QC condition to the appropriate rework-oriented status value.
• GET_PENDING_STATUS — Resolves the QC status that applies while a quality decision is still pending. It provides the status identifier used when a record has not yet received a final disposition.

These members are helper routines whose purpose is to centralize and standardize status determination so that calling programs do not embed the mapping logic themselves. Per the ETRM metadata, no further public interface details are documented.

Tables Accessed

The package body references a single documented table through an APPS synonym:

• GMD_QC_STATUS_NEXT — The Quality Control status transition table. This table holds the rules that define which status follows a given QC state for each transition scenario (for example, pending or rework outcomes). The routines GET_REWORK_STATUS and GET_PENDING_STATUS read this table to look up the appropriate next-status value.

In addition to the table reference, the package body depends on the package specification GMD_QC_STATUS_NEXT_PVT and the standalone object GMD_QC_STATUS_NEXT, together with the SYS STANDARD package. The metadata notes that this package body is not referenced by any database object, confirming its role as an internal implementation unit.

Usage Notes

Because GMD_QC_STATUS_NEXT_PVT is classified as a private package, it is not intended to be called directly by customer extensions, Oracle Forms personalizations, or concurrent programs. Instead, it is typically invoked indirectly through the public packages that reference it; the ETRM documentation indicates that two other packages reference this object. Those higher-level packages absorb the status-resolution logic and present the supported entry points to the OPM Quality application.

In practice, the routines GET_REWORK_STATUS and GET_PENDING_STATUS are exercised whenever OPM quality functionality must advance or assign a QC status—such as during QC result entry, disposition processing, or rework handling. Developers reviewing or troubleshooting QC status behavior in 12.1.1 or 12.2.2 should trace calls to the public OPM quality APIs rather than invoking this private package directly. Any customization should likewise target the documented public API layer, preserving the integrity of the internal status-resolution logic encapsulated here.