Search Results gmd_status_tl




Overview
Explore in AI Chat

Overview

GMD_STATUS_TL is the status code translation table within the GMD schema, belonging to the Oracle Process Manufacturing Product Development (OPM PD) module. It stores language-specific translated text for status codes used throughout the Process Manufacturing suite. The object follows the standard Oracle EBS "_TL" translation table pattern, where the base table (GMD_STATUS_B) holds language-independent code information and the corresponding translation table supplies the human-readable MEANING and DESCRIPTION values for each installed language.

Following the heuristic Data Vault classification supplied in the metadata, this table models as a standalone satellite. It carries descriptive, language-dependent attributes (MEANING, DESCRIPTION) keyed to a parent business key (STATUS_CODE) rather than representing an independent hub or an associative link. This classification is a modeling suggestion; the table functions practically as a descriptive dimension record.

The table is particularly relevant in OPM Product Development, where status codes drive lifecycle states for formulas, recipes, specifications, quality results, and batch entities. Because status codes surface in user interfaces and reports across multiple languages, the translation table ensures consistent multilingual presentation without duplicating code logic in each language row.

Key Information Stored

The documented physical schema contains eleven columns in release 12.2.2. The most significant are:

  • STATUS_CODE — The business key representing the untranslated status identifier; part of the composite primary key.
  • LANGUAGE — The NLS language code identifying which translation this row provides; the second component of the primary key.
  • MEANING — The translated display text shown for the status code in user interfaces.
  • DESCRIPTION — A longer translated explanation of the status code.
  • SOURCE_LANG — Indicates the source language of the row, used by the translation framework to identify the base language record.
  • ZD_EDITION_NAME — The editioning column supporting Oracle EBS 12.2 online patching; part of the documented unique index GMD_STATUS_TL_PK (STATUS_CODE, LANGUAGE, ZD_EDITION_NAME).
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY — Standard EBS audit columns tracking who created or last modified the translation row and when.

The surrogate primary key constraint is named GMD_STATUS_TL_PK; the documented unique index includes the editioning column, so the true business-key candidate is the pairing of STATUS_CODE and LANGUAGE as scoped by the active edition.

Common Use Cases and Queries

Typical usage involves joining the translation table to the base status table or to transactional tables that carry a STATUS_CODE. A common query retrieves the translated meaning for a given language:

SELECT t.status_code, t.meaning, t.description FROM gmd_status_tl t WHERE t.language = USERENV('LANG');

Reporting scenarios include generating multilingual specification or formula status listings, validating that every status code has a translation in each installed language, and reconciling status codes used in batch or quality transactions against the valid code list. A completeness check for missing translations is useful during implementation:

SELECT b.status_code, t.language FROM gmd_status_b b, gmd_status_tl t WHERE b.status_code = t.status_code(+) AND t.meaning IS NULL;

Because the table participates in EBS 12.1.1 and 12.2.2, queries on 12.2.2 should be aware of the ZD_EDITION_NAME column and editioning behavior, filtering to the current edition where relevant.

Related Objects

  • GMD_STATUS_B — The base (non-translated) status table; joins on STATUS_CODE and is the primary parent of this translation table.
  • GMD_STATUS_VL — The standard EBS view combining base and translation columns; commonly queried instead of the raw tables.
  • GMD_FORMULAS_B — Formula definitions that reference status codes governed by these translations.
  • GMD_RECIPES_B — Recipe definitions carrying status codes resolved through GMD_STATUS_TL.
  • GMD_SPECIFICATIONS_B — Specification headers that use status codes for lifecycle state.
  • GMD_QUALITY_RESULTS_B — Quality result records referencing status codes.
  • GMD_BATCHES — Batch entities whose status values are translated via this table.
  • FND_LANGUAGES — The language repository validating the LANGUAGE column values.

These relationships are established through the STATUS_CODE business key rather than enforced foreign keys, consistent with the standalone satellite classification noted above.