Results for “fnd_descr_flex_contexts_tl”

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

Overview

FND_DESCR_FLEX_CONTEXTS_TL is the translatable (TL) companion table to FND_DESCR_FLEX_CONTEXTS in the Oracle E-Business Suite Application Object Library (FND) schema, owned by APPLSYS. It stores the language-specific descriptive text — the context prompt and description — associated with each descriptive flexfield context defined in the base table. One row exists per context per installed language, enabling multilingual display of flexfield context labels without duplicating the structural definition. In EBS 12.1.1 and 12.2.2, this table is a core component of the Flexfields (Key and Descriptive) architecture and is frequently inspected when diagnosing context display issues or building multilingual setups.

From a Data Vault modeling perspective, the metadata heuristic classifies this object as satellite-leaning. It carries descriptive, language-dependent attributes that change over time and are functionally dependent on a parent business key, which aligns with satellite semantics. The base table FND_DESCR_FLEX_CONTEXTS would occupy the hub or structural role, with the TL table acting as a dependent descriptive satellite keyed by language.

Key Information Stored

The table contains 13 documented columns. The most significant are:

• APPLICATION_ID — Identifies the owning application; part of the composite business identifier.
• DESCRIPTIVE_FLEXFIELD_NAME — The internal name of the descriptive flexfield to which the context belongs.
• DESCRIPTIVE_FLEX_CONTEXT_CODE — The developer-facing code uniquely identifying the context within the flexfield.
• LANGUAGE — The NLS language code for the translated row.
• DESCRIPTIVE_FLEX_CONTEXT_NAME — The user-facing (translated) name displayed for the context.
• DESCRIPTION — Translated narrative text describing the context's purpose.
• SOURCE_LANG — The language of the source record from which the translation derives.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns used for change tracking and concurrency control.
• ZD_EDITION_NAME — Editioning support column used in 12.2.x online patching (Edition-Based Redefinition).

The surrogate primary key is FND_DESCR_FLEX_CONTEXTS_TL_PK, defined on APPLICATION_ID, DESCRIPTIVE_FLEXFIELD_NAME, DESCRIPTIVE_FLEX_CONTEXT_CODE, and LANGUAGE. The unique index FND_DESCR_FLEX_CONTEXTS_TL_U1 extends that set with ZD_EDITION_NAME, reflecting the edition-aware business-key candidate. The presence of LANGUAGE distinguishes TL rows from the single-row-per-context base table.

Common Use Cases and Queries

Typical scenarios include auditing translated context names, verifying that translations exist for every installed language, and joining to the base table to resolve a context's structure alongside its label. A common query pattern is:

• SELECT b.DESCRIPTIVE_FLEXFIELD_NAME, t.DESCRIPTIVE_FLEX_CONTEXT_CODE, t.DESCRIPTIVE_FLEX_CONTEXT_NAME, t.LANGUAGE FROM FND_DESCR_FLEX_CONTEXTS_TL t JOIN FND_DESCR_FLEX_CONTEXTS b ON t.APPLICATION_ID = b.APPLICATION_ID AND t.DESCRIPTIVE_FLEXFIELD_NAME = b.DESCRIPTIVE_FLEXFIELD_NAME AND t.DESCRIPTIVE_FLEX_CONTEXT_CODE = b.DESCRIPTIVE_FLEX_CONTEXT_CODE WHERE t.LANGUAGE = 'US';

Reporting use cases include generating flexfield context inventories per module, producing multilingual documentation of DFF structures for user training, and detecting missing or stale translations by comparing SOURCE_LANG with LANGUAGE and LAST_UPDATE_DATE values.

Related Objects

The primary relationship is to the base table through the documented foreign key:

• FND_DESCR_FLEX_CONTEXTS — joined on APPLICATION_ID, DESCRIPTIVE_FLEXFIELD_NAME, and DESCRIPTIVE_FLEX_CONTEXT_CODE; the TL table provides translated attributes for this structural parent.

Related flexfield definition and metadata objects in the FND schema that commonly appear alongside this table in queries and administration flows include FND_DESCRIPTIVE_FLEXS, FND_DESCR_FLEX_COL_USAGE, FND_DESCR_FLEX_CONTEXT_USAGES (context usage and validation), and FND_FLEX_VALUE_SETS for value-set-backed segments. Flexfield definition and deployment is also exposed through the FND Flexfields APIs used by the AOL flexfield administration forms, which read and write these TL rows during context definition and translation maintenance.