Results for “sy_text_tkn”

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

Overview

APPS.SY_TEXT_TKN_VL is a multilingual (language-resolved) view owned by the APPS schema in Oracle E-Business Suite, and it is documented under FND Design Data reference GMA.SY_TEXT_TKN_VL. The view presents all Text Tokens stored in the underlying translation table, SY_TEXT_TKN_TL, resolving those rows to a single language per session so that consumers receive readable token descriptions without having to join translation tables explicitly. Its object status is VALID in both the 12.1.1 and 12.2.2 releases.

Text Tokens in EBS represent reusable placeholders that are embedded into message and text strings and later substituted at runtime. The view therefore acts as a reporting and integration access point for the token catalogue, exposing token keys, language codes, and human-readable token descriptions for downstream processes, custom reports, and interfaces that must understand which tokens exist and what they represent.

Underlying Base Objects

The view is defined over a single documented base object: SY_TEXT_TKN_TL, itself exposed to the APPS schema through a synonym. SY_TEXT_TKN_TL is the translation table holding the language-specific attributes of text tokens, and the _VL suffix indicates that the view filters those rows according to the current language environment, returning one resolved row per token. The view is referenced by several dependent objects, including the tables GMA_SY_TEXT_TKN_T1, GMA_SY_TEXT_TKN_T2, and GMA_SY_TEXT_TKN_T3, and by another view named SY_TEXT_TKN. This dependency pattern confirms that SY_TEXT_TKN_VL is a central, reusable definition relied upon by both storage structures and higher-level views in the same functional area.

Key Columns

• ROW_ID (ROWID): The physical row identifier of the underlying row in SY_TEXT_TKN_TL, useful for direct addressing and row-level operations.
• TEXT_KEY (VARCHAR2, 32): The unique key identifying the text token; this is the primary means by which application code and reports locate a token.
• LANG_CODE (VARCHAR2): The language code of the resolved row, derived from the multilingual view logic.
• TEXT_CODE (NUMBER, 10): The identifier that joins rows of text in this table to the Text Table for this module, linking a token to its associated text records.
• TOKEN_DESC (VARCHAR2, 70): The descriptive text explaining the token, and the column most commonly displayed in user-facing reports.
• Audit columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN provide standard EBS who/when auditing information.

Common Use Cases and Queries

Typical scenarios include building a bilingual or multilingual listing of available text tokens, validating that a token referenced by a custom message or concurrent program actually exists, and reconciling tokens against the text records they join to through TEXT_CODE. A simple query returning the core token information is shown below.

SELECT TEXT_KEY
     , LANG_CODE
     , TEXT_CODE
     , TOKEN_DESC
  FROM APPS.SY_TEXT_TKN_VL
 ORDER BY TEXT_KEY;

A targeted lookup for a single token, restricted to the resolved language, can be expressed as follows.

SELECT TEXT_CODE
     , TOKEN_DESC
     , LAST_UPDATE_DATE
  FROM APPS.SY_TEXT_TKN_VL
 WHERE TEXT_KEY = :p_text_key;

Because the view is a language-resolved definition, callers in a multilingual environment should be aware that the returned LANG_CODE and TOKEN_DESC reflect the session language resolution rather than a raw translation row. Customizations that need every translation of a token should query SY_TEXT_TKN_TL directly, while standard reporting and integration code should prefer the view to avoid duplicate language rows.