Results for “sy_text_tkn_tl”

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

Overview

SY_TEXT_TKN_TL is a translation-language table owned by the GMA schema within Oracle EBS Process Manufacturing Systems (OPM). It stores the language-specific definitions of OPM Text Tokens — named placeholders that are substituted into document and label text at runtime, such as header, footer, or compliance tokens used in quality specifications, labels, and process documentation. Because it is the "_TL" companion to the base token table, each token can carry one or more translated descriptions keyed by language, enabling multilingual OPM text generation in regulated manufacturing environments.

From a dimensional modeling perspective, the mined foreign-key structure suggests a satellite-leaning classification: the table carries descriptive, language-dependent attributes (notably TOKEN_DESC) attached to a parent business entity via the TEXT_CODE reference, with its own surrogate-style unique key. This classification is offered as a heuristic modeling suggestion rather than a documented architectural fact.

Key Information Stored

The table comprises 11 documented columns. The most significant include:

• TEXT_KEY — Surrogate identifier for the token definition; part of the composite primary key.
• LANG_CODE — Language code qualifying the translated row; part of the primary key and the business-key unique index.
• LANGUAGE — Language identifier accompanying LANG_CODE; also part of the primary key.
• TEXT_CODE — Foreign key to SY_TEXT_HDR, linking the token to its owning text header record.
• TOKEN_DESC — The translated token description, the principal descriptive payload of this satellite.
• SOURCE_LANG — Indicates the source language from which the translation was derived.
• CREATION_DATE, CREATED_BY — Standard audit trail recording row creation.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit columns tracking the most recent modification and the login session responsible.

The documented unique index SY_TEXT_TKN_TL_PK (TEXT_KEY, LANG_CODE, LANGUAGE) is the primary key and therefore the strongest business-key candidate; it guarantees one translated row per token per language. The TEXT_CODE column is the sole documented foreign key, providing the join path to the header table.

Common Use Cases and Queries

Typical usage centers on retrieving translated token descriptions for reporting, label printing, and localization diagnostics. A common pattern joins the translation rows to the header for a specific language:

• List all token descriptions for a language: SELECT t.text_code, t.token_desc FROM gma.sy_text_tkn_tl t WHERE t.lang_code = :lang;
• Join tokens to headers: SELECT h.*, t.token_desc FROM gma.sy_text_tkn_tl t JOIN gma.sy_text_hdr h ON h.text_code = t.text_code WHERE t.language = :lang;
• Audit recently changed translations using LAST_UPDATE_DATE and LAST_UPDATED_BY.
• Detect missing translations by comparing token counts across LANG_CODE values.
• Identify untranslated rows by testing whether SOURCE_LANG equals LANG_CODE.

Related Objects

• SY_TEXT_HDR — Parent header table; joined via SY_TEXT_TKN_TL.TEXT_CODE = SY_TEXT_HDR.TEXT_CODE. This is the only documented foreign key.
• SY_TEXT_TKN — Base (non-translated) token definition table, the presumed logical parent of this translation table.
• SY_TEXT_TKN_TL_PK — Primary key index enforcing uniqueness of TEXT_KEY, LANG_CODE, and LANGUAGE.
• OPM text-generation and label-printing programs that resolve tokens by TEXT_CODE and language at runtime.
• Quality specification and document templates that embed OPM text tokens for compliance content.