Search Results gmd_qc_status_next




Overview
Explore in AI Chat

Overview

GMD_QC_STATUS_NEXT is a configuration table in the Oracle E-Business Suite Process Manufacturing Product Development module (GMD). It defines the valid transitions between Quality Control status codes within Oracle Process Manufacturing (OPM) Quality. Each row establishes a permissible move from a current status to a target status for a specified entity type, thereby acting as the state-transition ruleset that governs how quality records advance, rework, or pend during the QC lifecycle. The table is the authoritative source consulted by OPM Quality workflows and status-change logic to determine which target statuses are legally attainable from a given current status.

The heuristic Data Vault classification for this object is standalone, meaning it does not participate in a traditional foreign-key hub or link structure. As a modeling suggestion, it is best understood as a reference or lookup table whose natural business key is the combination of current status, entity type, and target status, rather than as a hub, link, or satellite within a Data Vault design.

Key Information Stored

The table contains eleven documented columns. The most significant are:

  • CURRENT_STATUS — the originating QC status code from which a transition may occur.
  • TARGET_STATUS — the destination QC status code that is reachable from the current status.
  • ENTITY_TYPE — identifies the kind of quality entity (for example, specification, result, or sample) to which the transition rule applies.
  • REWORK_STATUS — designates the status to be applied when a record is routed for rework.
  • PENDING_STATUS — designates the status applied when a record is placed in a pending condition.
  • WORKFLOW_INDICATOR — flags whether the transition drives or participates in a workflow action.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY — standard Oracle EBS audit columns recording who created and last modified each rule and when.

The primary key is GMD_QC_STATUS_NEXT_PK, defined on the composite of CURRENT_STATUS, ENTITY_TYPE, and TARGET_STATUS. Because this unique index also encodes the business meaning of each row, it serves as the business-key candidate in addition to the primary key. The table therefore has no separate surrogate identifier column; the three-column composite functions as both the technical and the business key.

Common Use Cases and Queries

Typical usage centres on validating or presenting allowable QC status transitions. A frequent query retrieves all target statuses reachable from a given current status and entity type:

  • SELECT TARGET_STATUS, REWORK_STATUS, PENDING_STATUS, WORKFLOW_INDICATOR FROM GMD.GMD_QC_STATUS_NEXT WHERE CURRENT_STATUS = :p_current AND ENTITY_TYPE = :p_entity;
  • Reporting queries enumerate the complete transition matrix by joining CURRENT_STATUS and TARGET_STATUS to the status description lookup to render human-readable transition diagrams.
  • Validation logic checks whether a proposed status change exists as a row before permitting the update, preventing illegal transitions.
  • Workflow analysis filters on WORKFLOW_INDICATOR = 'Y' to isolate transitions that trigger workflow activity.

Because the table is static configuration, it is commonly extracted into reporting schemas to support QC audit and compliance documentation.

Related Objects

The metadata identifies GMD_QC_STATUS_NEXT as a standalone object with no outgoing foreign keys, so dependencies are primarily logical rather than enforced. The most significant related objects are the QC status code lookup tables that resolve CURRENT_STATUS, TARGET_STATUS, REWORK_STATUS and PENDING_STATUS to their descriptions, and the OPM Quality transactional and specification tables whose status columns are validated against the transition rules defined here. The composite key columns CURRENT_STATUS, ENTITY_TYPE, and TARGET_STATUS are the join columns most commonly used when linking this table to status-description and entity-type reference data. Application logic within the GMD Quality module and its associated workflow definitions consume these rows at runtime to enforce and drive status progression.