Results for “qchold_res_desc”

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

Overview

GMD_HOLD_REASONS_TL is the translation (language) table for OPM Quality Hold Reasons within the Oracle E-Business Suite Process Manufacturing Product Development module (GMD). In Oracle EBS, a "_TL" suffix denotes a table that stores the translated, language-specific descriptive text associated with a base entity. Here, GMD_HOLD_REASONS_TL holds the language-dependent description of each quality hold reason code used in process manufacturing quality operations. A hold reason identifies why a batch, lot, or material was placed on quality hold, and the translated table ensures that the reason description is presented in the appropriate session language.

From a data modeling perspective, the mined heuristic Data Vault classification for this object is standalone. This suggests the table functions independently and may be best modeled as a reference or satellite-style object rather than as part of a hub-and-link topology. Because it carries both the business key and the descriptive attributes without an independent parent hub in the documented relationship data, it is treated as a self-contained translation entity.

Key Information Stored

The table is owned by the GMD schema and contains nine documented columns. The most important columns are:

• QCHOLD_RES_CODE — The quality hold reason code. This is a business-key candidate and part of the composite primary key.
• LANGUAGE — The language identifier for the translation. This is the second component of the composite primary key (QCHOLD_RES_CODE, LANGUAGE).
• QCHOLD_RES_DESC — The translated description of the hold reason, rendered in the row's LANGUAGE.
• SOURCE_LANG — The source language from which the translation originates, indicating the base language of the record.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard Oracle EBS audit columns tracking who created and last modified each row and when.

The primary key is defined by the unique index GMD_HOLD_REASONS_TL_PK over (QCHOLD_RES_CODE, LANGUAGE). There is no separate surrogate key; the combination of reason code and language forms the row identifier. The business-key candidate is the same composite used in the unique index. The table does not include a party or organization identifier, reinforcing its role as a shared, global reference.

Common Use Cases and Queries

This table is principally queried to render hold reason descriptions in the user's language within quality workbenches, hold management screens, and batch disposition reports. A typical query joins the base reason table to its translation using the shared key:

• Retrieve the description in English for a specific reason: SELECT qchold_res_desc FROM gmd_hold_reasons_tl WHERE qchold_res_code = :code AND language = 'US';
• List all active translations for all reasons: SELECT qchold_res_code, language, qchold_res_desc FROM gmd_hold_reasons_tl ORDER BY qchold_res_code, language;
• Audit recently added or changed translations using LAST_UPDATE_DATE and LAST_UPDATED_BY for compliance and change-tracking reports.
• Detect missing translations by comparing base reason codes against available rows per language.

Reporting use cases include quality hold trend analysis by reason, multilingual shop-floor labels, and localization validation before global rollout.

Related Objects

The documented relationship data classifies GMD_HOLD_REASONS_TL as standalone, so no foreign-key dependencies were mined within the ETRM metadata. In practice, the table is referenced by the base OPM hold reason definition and by downstream quality and material hold transaction tables that store QCHOLD_RES_CODE. Relevant objects typically include the base quality hold reason table (joined on QCHOLD_RES_CODE), the material/lot hold transaction tables that carry QCHOLD_RES_CODE, and Oracle EBS language and territory reference tables keyed by LANGUAGE. Because the translation key is the reason code plus language, any application object that displays a hold reason must ultimately resolve its description here. Administrators should treat this as a foundational reference table for multilingual process-manufacturing quality documentation.