Results for “qc_text_hdr”

50+ results




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

Overview

QC_TEXT_HDR is a table owned by the GMD schema within the Oracle E-Business Suite Process Manufacturing Product Development module (GMD). It serves as the central repository for text types defined for the Quality Control (QC) module. In practical terms, this table acts as a reference or lookup master that enumerates the various text code classifications available to QC-related entities, allowing quality specifications, tests, grades, units, and results to be consistently categorized across the Process Manufacturing data model.

The table is defined with a documented physical schema of six columns and carries the primary key constraint QC_TEXT_HDR_PK, built on the TEXT_CODE column. From a Data Vault modeling perspective, the heuristic classification suggests this object is hub-leaning, meaning it functions primarily as a business-key hub that anchors several dependent satellite and reference tables rather than acting as a transactional link. This classification is a modeling suggestion derived from the foreign-key topology, where many child tables point back to this central text-code identifier.

Key Information Stored

The table's documented columns are limited but strategically significant. The most important column is TEXT_CODE, which serves both as the business key and the column underpinning the primary key constraint QC_TEXT_HDR_PK. This attribute uniquely identifies each text type and is the value propagated to all referencing tables throughout the QC and GMD schemas.

The remaining documented columns are standard Oracle EBS audit and WHO columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN. These record the identity of the user who inserted or modified a row, the timestamps of those actions, and the login context. While these columns are not business-meaningful in the functional sense, they are essential for auditability, data lineage, and troubleshooting in a regulated quality environment.

  • TEXT_CODE — primary key and business key; the canonical identifier for a QC text type.
  • CREATED_BY / CREATION_DATE — audit trail for row creation.
  • LAST_UPDATED_BY / LAST_UPDATE_DATE — audit trail for the most recent modification.
  • LAST_UPDATE_LOGIN — the login session associated with the last update.

No surrogate sequence-driven identifier beyond TEXT_CODE is documented; the primary key is the natural business key itself.

Common Use Cases and Queries

The most frequent use of QC_TEXT_HDR is as a validation and lookup source during QC specification setup and result entry. Because thirteen documented child tables carry a TEXT_CODE foreign key to this header, any query that resolves a text code to its descriptive context must ultimately join through QC_TEXT_HDR.

A typical pattern retrieves all defined text types:

SELECT text_code, creation_date, last_update_date
FROM   gmd.qc_text_hdr
ORDER BY text_code;

Equally common is joining a dependent table, such as QC_SPEC_MST, to resolve the text classification referenced by a specification:

SELECT s.spec_id, s.text_code, h.last_update_date
FROM   qc_spec_mst  s,
       gmd.qc_text_hdr h
WHERE  s.text_code = h.text_code;

Reporting scenarios include quality audit extracts that list which text types are in active use, impact analysis before retiring a text code, and reconciliation of text code assignments across grades, tests, units, and results. Analysts also use this table to build value-set or LOV definitions for QC data entry forms.

Related Objects

The documented foreign-key relationships show that QC_TEXT_HDR is referenced by a broad set of QC and GMD base tables, confirming its role as a shared reference hub. The most significant related objects include:

Because these relationships all hinge on TEXT_CODE, referential integrity is enforced at the database level, and any change to QC_TEXT_HDR rows must be evaluated against every dependent table listed above.