Search Results qchold_res_code




Overview
Explore in AI Chat

Overview

The GMD_HOLD_REASONS_B table is a core master data table within the Oracle Process Manufacturing (OPM) product development module (GMD) of Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It serves as the definitive repository for defining and storing quality hold reasons. These reasons are critical for managing quality control processes in manufacturing, where materials, batches, or products may be placed on a temporary hold status pending quality inspection, test results, or disposition decisions. The table's role is to provide a standardized, validated list of codes that can be consistently applied across the quality management lifecycle, ensuring traceability and compliance in regulated manufacturing environments.

Key Information Stored

The primary data element stored in this table is the quality hold reason code. As defined by the provided ETRM metadata, the table's structure is anchored on the column QCHOLD_RES_CODE, which serves as the table's primary key. While the full column list is not detailed in the excerpt, a table of this nature in the GMD schema typically includes descriptive and control columns. One can reasonably expect complementary fields such as a description (DESCRIPTION), an enabled flag (ENABLED_FLAG), creation and last update date columns (CREATION_DATE, LAST_UPDATE_DATE), and corresponding user ID columns. The QCHOLD_RES_CODE itself is a unique, user-defined identifier for a specific hold reason, such as 'PENDING_ANALYSIS' or 'AWAITING_APPROVAL'.

Common Use Cases and Queries

This table is primarily referenced in transactional and reporting contexts related to quality holds. Common use cases include the configuration of valid hold reasons during system setup, the assignment of a reason when placing a batch on hold via the quality module interface, and reporting on hold history and analysis. A fundamental query retrieves the active list of reasons for a user interface LOV (List of Values).

  • Sample Query for Active Hold Reasons:
    SELECT qchold_res_code, description FROM gmd_hold_reasons_b WHERE enabled_flag = 'Y' ORDER BY 1;
  • Reporting Use Case: This table is joined to transactional hold tables (e.g., GMD_QC_HOLDS) to generate reports that show the count or duration of holds broken down by the reason code, providing insights into quality process bottlenecks.

Related Objects

Based on the provided relationship data, the QCHOLD_RES_CODE column is the primary key for the table GMD_HOLD_REASONS_B (constraint GMD_HOLD_REASONS_B_PK). This key is almost certainly referenced by foreign key constraints in other transactional tables within the GMD schema that need to record a hold reason. While the specific related tables are not listed in the excerpt, typical foreign key relationships would exist with quality hold transaction tables. For example, a table like GMD_QC_HOLDS or GMD_QC_HOLD_DTLS would contain a column such as HOLD_REASON_CODE that joins to GMD_HOLD_REASONS_B.QCHOLD_RES_CODE. This ensures data integrity by preventing the use of undefined reason codes in transactions.