Search Results gmo_instr_defn_tl




Overview
Explore in AI Chat

Overview

The GMO_INSTR_DEFN_TL table is the translatable (language-dependent) companion to the instruction definition entity within the Oracle E-Business Suite GMO module — Manufacturing Execution System for Process Manufacturing. In EBS 12.1.1 and 12.2.2, GMO supports shop-floor execution and process manufacturing workflows, and instruction definitions describe the operational instructions presented to operators at tasks and steps. Because instruction text and task labels must be presented in the operator's native language, the base instruction definition is stored once while its descriptive attributes are replicated per installed language through this _TL table. This is the standard EBS multilingual (MLS) design pattern, where the _TL table holds the translatable columns and the base table holds non-translatable, language-independent attributes.

Under the supplied Data Vault classification heuristic, the object is characterized as standalone. In Data Vault modeling terms this suggests treating GMO_INSTR_DEFN_TL as neither a classic hub nor a linking structure on its own; the true business hub is the instruction definition keyed by INSTRUCTION_ID, and this table behaves more like a multi-active satellite carrying descriptive, language-qualified attributes. The heuristic classification should be regarded as a modeling suggestion rather than a definitive design assertion.

Key Information Stored

The table is documented with ten columns in ETRM 12.2.2. The most significant are:

  • INSTRUCTION_ID — the surrogate identifier of the underlying instruction definition; the first component of the composite primary key and the join back to the base entity.
  • LANGUAGE — the language code identifying the translation row; the second component of the primary key.
  • INSTRUCTION_TEXT — the translatable instruction body displayed to the operator.
  • TASK_LABEL — the translatable short label for the instruction or associated task.
  • SOURCE_LANG — the source language from which the translation originated, supporting MLS maintenance and the "translated" versus "untranslated" state of a row.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard EBS audit columns recording who created and last modified the row and when.

The surrogate primary key is defined by the unique index GMO_INSTR_DEFN_TL_PK over (INSTRUCTION_ID, LANGUAGE). In MLS tables, the business-key candidate is effectively the same column pair, because a given instruction may have exactly one translation per language; the composite uniquely identifies a language-specific row.

Common Use Cases and Queries

Typical reporting and integration scenarios resolve instruction definitions in a requested language, joining the translation back to the base definition. A representative pattern filters the desired language with a fallback to the base language:

  • Retrieve instruction text for a specific instruction and language: SELECT instruction_text, task_label FROM gmo_instr_defn_tl WHERE instruction_id = :id AND language = USERENV('LANG');
  • List all translations for an instruction to audit coverage: SELECT language, source_lang, task_label FROM gmo_instr_defn_tl WHERE instruction_id = :id ORDER BY language;
  • Detect missing translations by comparing against the set of installed languages via FND_LANGUAGES.
  • Extract data for translation workbenches or external localization tools by selecting INSTRUCTION_ID, LANGUAGE, TASK_LABEL and INSTRUCTION_TEXT.
  • Audit changed translations using LAST_UPDATE_DATE and LAST_UPDATED_BY for compliance and traceability.

Related Objects

The relationship data supplied classifies this object as standalone with no explicitly documented foreign keys; the principal relationships are therefore inferred from the shared primary-key structure and standard GMO MLS design:

  • GMO_INSTR_DEFN_B — the base, language-independent instruction definition table, joined on INSTRUCTION_ID.
  • GMO_INSTR_DEFN_VL — the language view that typically joins the base and _TL tables to present a single logical instruction definition row.
  • FND_LANGUAGES — the language reference table validating the LANGUAGE column.
  • FND_TERRITORIES — supporting locale resolution for report and UI rendering.
  • GMO task and step definition tables that consume instruction identifiers to display operator instructions on the shop floor.

Because no explicit foreign keys are documented, implementers should confirm joins against the actual base-table definition and view definitions in their instance rather than assuming enforced referential integrity.