Results for “gmd_operations_tl”

40 results




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

Overview

GMD_OPERATIONS_TL is the operations translation table within the Oracle EBS Process Manufacturing Product Development (GMD) module. It stores language-specific, translated descriptive text for the operational definitions captured in the base GMD_OPERATIONS_B table. In Oracle EBS globalization architecture, a table suffixed with _TL ("translation") accompanies a base _B or _F table and holds only the translatable attributes — in this case the operation description (OPRN_DESC#1) — keyed by the base entity identifier plus the LANGUAGE code. The object is registered under the GMD schema with VALID status and is documented in ETRM 12.2.2 with nine physical columns and a primary key of OPRN_ID and LANGUAGE.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign-key structure is standalone. This is a modeling suggestion rather than a physical classification: because GMD_OPERATIONS_TL carries no outgoing foreign keys within the mined set, it can be modelled as a satellite-like descriptor table attached to the operation hub, where OPRN_ID acts as the hub reference and LANGUAGE supplies part of the descriptive grain. Translators and implementation teams should treat the table as a dependent child of the base operations entity rather than as an independent business object.

Key Information Stored

The table's documented columns fall into four functional groups: the composite identifier, the translation payload, and two standard audit blocks.

  • OPRN_ID — The operation identifier. Part of the composite primary key and the business link back to the base operations record.
  • LANGUAGE — The language code for the translated row. Combined with OPRN_ID, it forms the primary key GMD_OPERATIONS_TL_PK and is the unique business-key candidate for the translation set.
  • SOURCE_LANG — Identifies the source language of the translation, supporting multilingual authoring workflows.
  • OPRN_DESC#1 — The translated operation description, the primary translatable attribute this table exists to hold.
  • CREATION_DATE, CREATED_BY — Standard "who created the row and when" audit columns.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard "most recent change" audit columns used by EBS concurrent programs, history tracking, and DBI reporting.

The surrogate key is the composite GMD_OPERATIONS_TL_PK (OPRN_ID, LANGUAGE); there is no additional unique index documented beyond this PK. The business-key candidate is therefore the same composite pair, distinguishing it from a single-column surrogate.

Common Use Cases and Queries

Typical scenarios include multilingual operation-name reporting, verifying translation completeness before a globalization rollout, and extracting operation descriptions for integration or label-printing interfaces.

  • Retrieve all translations for a single operation:
    SELECT language, oprn_desc#1 FROM gmd_operations_tl WHERE oprn_id = :oprn_id ORDER BY language;
  • List operations still missing a target-language row using an outer join to the base table on OPRN_ID.
  • Report on recently translated content using LAST_UPDATE_DATE and LAST_UPDATED_BY filters.
  • Feed downstream BI extracts that require locale-specific descriptions joined to process specifications.

Because the table is transactional and maintained by the Product Development UI, direct DML should be avoided; use the supported application forms or concurrent translation programs.

Related Objects

  • GMD_OPERATIONS_B — The base operations table; joined on OPRN_ID to obtain the untranslated operation attributes.
  • GMD_OPERATIONS_VL — The translated view, which typically unions the base and translation tables on OPRN_ID and LANGUAGE.
  • GMD_OPERATIONS_TL_PK — The primary key constraint enforcing uniqueness on (OPRN_ID, LANGUAGE).
  • FND_LANGUAGES — Reference table joined on LANGUAGE for language names.
  • GMD_RECIPE_OPERATIONS — Recipe-step usage details referencing OPRN_ID.
  • GMD_ROUTINGS — Routing headers that consume operations in process flow definitions.
  • FND_AUDIT-related views — Audit columns consumed by standard EBS audit reporting.