Search Results gme_text_table_tl




Overview
Explore in AI Chat

Overview

GME_TEXT_TABLE_TL is a translation (language) table in the GME schema, owned by the Process Manufacturing Process Execution product within Oracle EBS 12.1.1 and 12.2.2. It stores the descriptive text lines used throughout the Production Management module — the free-form narrative attached to business records such as process instructions, batch documentation, quality notes, and other module text blocks. The "_TL" suffix identifies it as a multilingual companion to the base GME_TEXT_TABLE, meaning each logical text line is held once per installed language so that operators can view Production Management text in their own session language.

The ETRM relationship metadata classifies this object heuristically as standalone from a Data Vault modeling perspective. In practice this means it is best treated as a descriptive satellite or reference table rather than a hub or link: its rows carry contextual attribute text keyed to a text/paragraph structure, not independent business entities or many-to-many relationships. Its documented physical schema in 12.2.2 comprises 13 columns and a single unique index, GME_TEXT_TABLE_TL_PK.

Key Information Stored

The primary key GME_TEXT_TABLE_TL_PK is a composite business key spanning TEXT_CODE, LANG_CODE, PARAGRAPH_CODE, SUB_PARACODE, LINE_NO, and LANGUAGE. Because the PK itself captures all of these, there is no separate surrogate sequence column in the documented design; the composite key is the identifier.

  • TEXT_CODE — identifies the text block or text set to which the line belongs.
  • LANG_CODE / LANGUAGE — the language of the stored line and its source-language indicator, distinguishing translations of the same text.
  • PARAGRAPH_CODE / SUB_PARACODE — the paragraph and sub-paragraph grouping that orders the text into logical sections.
  • LINE_NO — the sequence of the line within its paragraph, preserving reading order.
  • TEXT — the actual descriptive text content for that line and language.
  • SOURCE_LANG — the language from which the translation was derived.
  • Audit columns — LAST_UPDATED_BY, CREATED_BY, LAST_UPDATE_DATE, CREATION_DATE, and LAST_UPDATE_LOGIN provide WHO/WHEN tracking.

Common Use Cases and Queries

Typical usage retrieves the ordered text lines for a given text code in the user's language, filtering out other translations:

  • Fetch a single paragraph in one language:
    SELECT line_no, text FROM gme.gme_text_table_tl WHERE text_code = :code AND lang_code = USERENV('LANG') AND paragraph_code = :para ORDER BY line_no;
  • Compare translations of the same text: group by TEXT_CODE and PARAGRAPH_CODE, returning one column per LANG_CODE.
  • Identify untranslated content by comparing row counts across LANG_CODE values per TEXT_CODE.
  • Audit reporting on which text was created or last changed by which user, using CREATED_BY, LAST_UPDATED_BY, and the date columns.
  • Batch documentation or work-instruction printing, joining this table to the base text table to reconstruct full narratives.

Related Objects

The metadata classifies this table as standalone, with no enforced foreign keys mined. Functional dependencies nevertheless exist through the shared key columns:

  • GME_TEXT_TABLE — the base (non-translated) table, joined on TEXT_CODE and the paragraph/sub-paragraph identifiers.
  • GME_TEXT_TABLE_TL_PK — the unique index enforcing the composite key.
  • Production Management batch, recipe, and instruction tables that reference TEXT_CODE to attach narrative content.
  • Oracle language and FND language views that resolve LANG_CODE and LANGUAGE values.
  • Standard GME audit and translation views exposing this table for reporting.