Results for “qc_hres_mst”

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

Overview

QC_HRES_MST is the Quality Control Hold Reason Code master table owned by the GMD schema (Process Manufacturing Product Development) in Oracle EBS 12.1.1 and 12.2.2. It stores the canonical list of reasons that can be applied when inventory, lots, or items are placed on quality hold. Each row defines one hold reason code and its descriptive text, and the table acts as the authoritative reference for hold-reason values consumed throughout inventory and process manufacturing transactions.

Under a heuristic Data Vault classification, QC_HRES_MST is hub-leaning. Its single-column primary key, QCHOLD_RES_CODE, behaves like a business key that multiple downstream tables reference, which is characteristic of a hub rather than a link or satellite. Any descriptive attributes carried on the row (for example QCHOLD_RES_DESC) could be modeled separately as satellite data if a formal Data Vault model were constructed.

Key Information Stored

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

• QCHOLD_RES_CODE — the hold reason code itself and the primary key column of QC_HRES_MST_PK. This is the value carried into every referencing table.
• QCHOLD_RES_DESC — the descriptive text shown to users when the reason is selected or reported.
• TEXT_CODE — a foreign key to QC_TEXT_HDR, linking the reason to a long text definition.
• TRANS_CNT — a transaction counter used for concurrency or audit tracking.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard Oracle EBS audit stamp columns.
• DELETE_MARK — the logical delete flag (0/1) governing whether the reason is active.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE30 — the flexfield descriptive columns available for client-specific extensions.
• MIGRATION_STATUS — a migration control column.

QCHOLD_RES_CODE is both the surrogate primary key and the business-key candidate referenced by all dependent tables. No additional unique index beyond the primary key is documented.

Common Use Cases and Queries

Typical uses include populating hold-reason list-of-values, validating hold reason codes during inventory hold transactions, and reporting on which reasons are being applied to lots, items, or locations. A common pattern joins the master to its consumers, for example:

• Retrieve active reasons: SELECT qchold_res_code, qchold_res_desc FROM gmd.qc_hres_mst WHERE NVL(delete_mark,0)=0 ORDER BY qchold_res_code;
• Report item-level holds: SELECT i.inventory_item_id, m.qchold_res_code, m.qchold_res_desc FROM ic_item_mst i, gmd.qc_hres_mst m WHERE i.qchold_res_code = m.qchold_res_code;
• Report lot hold reasons: join IC_LOTS_STS to QC_HRES_MST on QCHOLD_RES_CODE.
• Fetch the long description by joining QC_TEXT_HDR on TEXT_CODE.

These joins support quality dashboards, lot genealogy reports, and reconciliation of held inventory by reason.

Related Objects

The following objects reference QC_HRES_MST through QCHOLD_RES_CODE:

• IC_ITEM_MST — stores the default hold reason code at the item level.
• IC_ITEM_MST_B — item master base table carrying QCHOLD_RES_CODE.
• IC_LOCT_INV — location/inventory on-hand records holding a reason code.
• IC_LOTS_STS — lot status records referencing the reason applied to a lot.
• IC_PERD_BAL — period balance records carrying the hold reason code.

QC_HRES_MST itself references QC_TEXT_HDR through TEXT_CODE for extended descriptive text. Together these relationships make QC_HRES_MST a central reference hub for quality hold processing across inventory and process manufacturing.