Search Results gmd_qc_status_b




Overview
Explore in AI Chat

Overview

GMD_QC_STATUS_B is the OPM Quality Status base table within the Oracle Process Manufacturing Product Development (GMD) module. In Oracle EBS 12.1.1 and 12.2.2, it stores the seeded and user-defined quality status codes that drive quality control workflows across process manufacturing — such as released, quarantined, rejected, and pending disposition states — together with the entity types those statuses apply to (for example, lots, batches, or materials). The table is keyed by the composite primary key GMD_QC_STATUS_B_PK on (STATUS_CODE, ENTITY_TYPE), and it is delivered with 43 documented columns in the ETRM 12.2.2 physical schema under the GMD owner.

The metadata's heuristic Data Vault classification places this object as standalone, with no mined foreign-key dependencies. From a modeling perspective, GMD_QC_STATUS_B is best treated as a reference (lookup) table or a small hub-like dimension of quality status codes, rather than as a transactional link or a satellite carrying changing descriptive attributes. Its wide attribute column set (ATTRIBUTE1 through ATTRIBUTE30) technically permits satellite-style descriptive extension, but the documented relationship data provides no FK evidence to support that pattern.

Key Information Stored

Although 43 columns exist, the functionally significant ones are limited:

  • STATUS_CODE — the quality status identifier; part of the composite primary key and the primary business identifier for each status.
  • ENTITY_TYPE — the business object the status applies to; the second component of the composite primary key.
  • STATUS_TYPE — classifies the nature or category of the status, supporting grouping and filtering logic.
  • UPDATEABLE — flag indicating whether the status may be modified or user-extended.
  • VERSION_ENABLED — flag governing whether the status participates in versioning behavior.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE30 — the standard EBS descriptive flexfield (DFF) container columns.
  • DELETE_MARK — soft-delete indicator (0/1) used instead of physical row deletion.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard EBS audit ("WHO") columns.
  • ZD_EDITION_NAME — the editioning column used in the 12.2 online patching (ADOP) architecture; it appears in the unique index alongside the key columns.

The documented unique business-key candidate is GMD_QC_STATUS_B_PK on (STATUS_CODE, ENTITY_TYPE, ZD_EDITION_NAME). The inclusion of ZD_EDITION_NAME reflects the 12.2.2 edition-based redefinition model; under 12.1.1 the same logical uniqueness applies on (STATUS_CODE, ENTITY_TYPE) without the edition column.

Common Use Cases and Queries

Typical uses include validating and translating quality status codes in OPM quality and lot disposition reports, populating LOVs in inquiry screens, and joining status definitions to quality results or inventory records that reference a status code.

Retrieve the active statuses for a given entity type:

  • SELECT status_code, status_type, updateable FROM gmd.gmd_qc_status_b WHERE entity_type = :entity_type AND NVL(delete_mark,0) = 0 ORDER BY status_code;

Resolve a status description, accounting for editioning under 12.2:

  • SELECT status_code, entity_type FROM gmd.gmd_qc_status_b WHERE zd_edition_name = 'SET1' AND delete_mark = 0;

Report user-defined attributes stored on a status:

  • SELECT status_code, attribute_category, attribute1, attribute2 FROM gmd.gmd_qc_status_b WHERE status_code = :status_code;

Reporting should consistently filter on DELETE_MARK and, in 12.2.2, on ZD_EDITION_NAME to avoid reading stale editions.

Related Objects

Because the mined relationship data classifies this object as standalone, no foreign-key dependents are documented in the metadata. In practice within the GMD/OPM schema, the status codes defined here are referenced by quality and inventory objects that carry a quality status, including quality specification and quality results entities, lot and batch records, and OPM material/inventory transactions. The composite key columns STATUS_CODE and ENTITY_TYPE are the natural join columns for any such referencing table, and the DFF-backed ATTRIBUTE columns align with the standard FND descriptive flexfield infrastructure. Where a companion _TL translation table exists in the EBS convention, it would join on STATUS_CODE as well.