Search Results gmo_instr_instance_tl_pk

Overview

GMO_INSTR_INSTANCE_TL is the instruction translation table within the Oracle E-Business Suite Manufacturing Execution System for Process Manufacturing (GMO) module. It stores language-specific translations of instructions that are presented to operators at execution time on the shop floor. In process manufacturing environments, work instructions, task labels, and operator guidance must be delivered in the native language of the production personnel. This table provides the multilingual rendering layer that supports that requirement, decoupling the base instruction definition from its translated presentation.

The object resides in the GMO schema and is classified as VALID in the ETRM 12.1.1 / 12.2.2 repository. From a Data Vault modeling perspective, the heuristic classification is standalone, meaning it does not participate in a documented foreign-key-driven hub, link, or satellite structure visible through mined FK relationships. A modeler would typically treat this as a descriptive satellite keyed on the instruction and language, holding translated textual attributes rather than a hub of independent business entities.

Key Information Stored

The table is keyed by a composite primary key, GMO_INSTR_INSTANCE_TL_PK, defined on INSTRUCTION_ID and LANGUAGE. Both columns are also the documented unique index and therefore serve as the business-key candidates. INSTRUCTION_ID references the base instruction record, while LANGUAGE identifies the specific translation locale.

The most significant attribute columns are:

• INSTRUCTION_TEXT — the translated instruction body displayed to the operator during execution.
• COMMENTS — translated supplementary remarks associated with the instruction instance.
• TASK_LABEL — the translated short label or caption for the task.
• SOURCE_LANG — the language of the originating (source) instruction text, enabling translation traceability.
• LANGUAGE — the target language of this translation row.
• CREATION_DATE, CREATED_BY — audit columns capturing when and by whom the translation was inserted.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — audit columns capturing the most recent modification and the responsible session.

The table carries 11 documented columns in the ETRM 12.2.2 physical schema.

Common Use Cases and Queries

Typical scenarios include resolving the correct translated instruction for a given operator language, auditing which instructions lack a translation for a required locale, and reporting translation coverage across the instruction catalog. A common retrieval pattern joins the translation to the base instruction and filters by language:

• Language-specific fetch: SELECT instruction_text, task_label, comments FROM gmo_instr_instance_tl WHERE instruction_id = :id AND language = :lang;
• Translation coverage audit: SELECT instruction_id, COUNT(DISTINCT language) FROM gmo_instr_instance_tl GROUP BY instruction_id HAVING COUNT(DISTINCT language) < :required_count;
• Source-vs-target comparison: SELECT instruction_id, language, source_lang FROM gmo_instr_instance_tl WHERE language <> source_lang;
• Change tracking: filter on LAST_UPDATE_DATE to identify recently revised translations for downstream synchronization.

Related Objects

The table is documented as standalone, so few FK relationships are mined. The principal logical relationships are:

• GMO_INSTR_INSTANCE_B — the base instruction instance table joined on INSTRUCTION_ID, supplying the untranslated definition.
• GMO_INSTR_INSTANCE_TL itself is the translation companion to the base entity; the INSTRUCTION_ID joins back to the parent instance.
• GMO_INSTR_INSTANCE_VL — the view layer exposed to application UIs and LOVs, resolving the operator's session language.
• FND_LANGUAGES — joined on LANGUAGE to obtain the installed language description.
• GMO_INSTRUCTIONS / execution APIs — consume INSTRUCTION_ID to render operator instructions at run time.

Maintenance is performed through the GMO execution interfaces rather than direct DML, and changes should respect the audit columns and the composite primary key constraint.