Results for “token_desc”

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

Overview

SY_TEXT_TKN_VL is a read-only view owned by the APPS schema in Oracle E-Business Suite, belonging to the GMA – Process Manufacturing Systems product family. It presents all text tokens stored in the multilingual base table SY_TEXT_TKN_TL, filtered to the language of the current user session. Text tokens are the reusable symbolic placeholders that Oracle's process manufacturing and document generation facilities substitute with dynamic values at runtime—for example, when composing labels, batch documentation, or quality specifications that must merge production context into predefined text.

The view serves a localization purpose. Rather than exposing every language row held in the underlying translation table, SY_TEXT_TKN_VL applies a session-level predicate so that each consumer sees only the tokens relevant to its language environment. This makes it the appropriate access point for reports, concurrent programs, forms, and integration interfaces that need language-appropriate token definitions without embedding locale logic themselves. Its status is VALID, and it is documented across both 12.1.1 and 12.2.2 releases of EBS.

Underlying Base Objects

The view is defined over a single documented base object, SY_TEXT_TKN_TL, which appears as a SYNONYM in the APPS schema. The dependency is direct: SY_TEXT_TKN_VL is a projection of SY_TEXT_TKN_TL. Its defining query selects from SY_TEXT_TKN_TL, aliased as B, and restricts rows with the condition B.LANGUAGE = USERENV('LANG'). The view therefore inherits the translation table's multilingual structure, in which each text token is represented by one row per installed language, and narrows that set to a single locale per query.

Because the view is a simple, non-joined projection, it does not introduce its own storage. DML is not supported against it; token maintenance is performed against the underlying translation table through the supported process manufacturing setup or text administration functions. The view also exposes the ROWID of the base table row as ROW_ID, a technique common in EBS "VL" (view-language) constructs to provide a stable row identifier to forms and APIs.

Key Columns

• ROW_ID — The ROWID of the corresponding SY_TEXT_TKN_TL row, exposed as the unique row identifier.
• TEXT_KEY — The key identifying the text token grouping that the token entry belongs to.
• LANG_CODE — The language code of the token record.
• TEXT_CODE — The token code, i.e., the symbolic identifier that is substituted during text expansion.
• TOKEN_DESC — The description or resolved text associated with the token in the current language.
• CREATION_DATE, CREATED_BY — Standard audit columns recording when and by whom the token row was created.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit columns recording the most recent modification and the login that performed it.

Common Use Cases and Queries

A typical application of the view is token discovery: enumerating available tokens for a given text key so that a document template can be validated before generation. A second use is discrepancy analysis, comparing token codes across environments or releases to detect missing customizations during a migration or upgrade.

The following query lists token codes and descriptions for the current user's language:

• SELECT text_key, text_code, token_desc FROM apps.sy_text_tkn_vl ORDER BY text_key, text_code;

To restrict inspection to a specific token group:

• SELECT text_code, token_desc FROM apps.sy_text_tkn_vl WHERE text_key = :p_text_key;

To identify recently maintained tokens, the audit columns can be used directly:

• SELECT text_code, token_desc, last_update_date, last_updated_by FROM apps.sy_text_tkn_vl WHERE last_update_date > SYSDATE - 30;

Because the view is language-restricted, cross-language comparison requires either the base translation table or a session in which USERENV('LANG') is set to the desired locale. All queries should be issued with the APPS schema context or a synonym appropriately qualified.