Search Results fm_text_tbl_tl




Overview
Explore in AI Chat

Overview

The GMD.FM_TEXT_TBL_TL table is a translation-language (TL) table within the Process Manufacturing Product Development module (GMD) of Oracle E-Business Suite. Its documented description identifies it as "FM Module Text Lines," storing the descriptive text associated with records across all tables in the module. Because Oracle EBS maintains multi-language support for Process Manufacturing development entities such as formulas, recipes, and quality specifications, the TL table preserves language-specific paragraph and line content keyed by language code, allowing the same underlying text block to exist in multiple installed languages without duplicating the base text record.

From a Data Vault modeling perspective, the metadata's heuristic classification places this object as standalone, meaning it is not linked through foreign keys into a parent hub or link structure in the mined dependency graph. This suggests that, for modeling purposes, the table may be treated as an independent text-reference table rather than a dependent satellite. Analysts should note that TL tables conventionally behave as satellites of their base table, so this classification should be validated against the actual base table (for example, FM_TEXT_TBL or FM_TEXT_TBL_B) before finalizing any dimensional or Data Vault design.

Key Information Stored

The table contains 13 documented columns. The primary key, FM_TEXT_TBL_TL_PK, is a composite business key rather than a single surrogate identifier, spanning TEXT_CODE, LANG_CODE, PARAGRAPH_CODE, SUB_PARACODE, LINE_NO, and LANGUAGE. The most significant columns include:

  • TEXT_CODE – Identifier of the parent text block that groups related paragraphs and lines.
  • LANG_CODE / LANGUAGE – The language of the stored line; together these drive translation selection.
  • PARAGRAPH_CODE and SUB_PARACODE – Hierarchical identifiers locating the line within a paragraph and sub-paragraph structure.
  • LINE_NO – Ordering sequence for lines within a paragraph, preserving presentation order.
  • TEXT – The actual descriptive or instructional content displayed for the language.
  • SOURCE_LANG – Language from which the current text was derived, supporting translation lineage.
  • LAST_UPDATED_BY, CREATED_BY, LAST_UPDATE_DATE, CREATION_DATE, LAST_UPDATE_LOGIN – Standard EBS WHO columns auditing who created or modified each line.

Note that only FM_TEXT_TBL_TL_PK is documented as a unique business-key candidate; no separate surrogate primary key column is present.

Common Use Cases and Queries

Typical uses include retrieving translated instructions for formula or recipe text, auditing translation completeness across languages, and feeding reporting layers that require display-ready text. A representative query retrieves all English lines for a given text code:

  • SELECT PARAGRAPH_CODE, SUB_PARACODE, LINE_NO, TEXT FROM GMD.FM_TEXT_TBL_TL WHERE TEXT_CODE = :p_code AND LANGUAGE = 'US' ORDER BY PARAGRAPH_CODE, SUB_PARACODE, LINE_NO;
  • A coverage report counts lines per language: SELECT LANGUAGE, COUNT(*) FROM GMD.FM_TEXT_TBL_TL GROUP BY LANGUAGE;
  • An audit query joins the WHO columns against FND_USER via LAST_UPDATED_BY to identify recent editorial changes.

Related Objects

The metadata documents this table as standalone, so no FK relationships were mined. In practice it is referenced alongside the following objects:

  • GMD.FM_TEXT_TBL (or its base text table) – parent entity keyed by TEXT_CODE; join on TEXT_CODE.
  • FND_LANGUAGES – validates LANG_CODE/LANGUAGE; join on the language code columns.
  • FND_USER – resolves CREATED_BY and LAST_UPDATED_BY.
  • Other GMD validation and specification tables that embed text blocks via TEXT_CODE.
  • The ETRM/TL conversion utilities that synchronize base-language rows into this TL table.