Results for “fnd_descr_flex_col_usage_tl”

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

Overview

FND_DESCR_FLEX_COL_USAGE_TL is the translation (TL) table for the base table FND_DESCR_FLEX_COLUMN_USAGES within the Oracle Application Object Library (FND) product. It is owned by the APPLSYS schema and stores the language-specific, user-facing text associated with descriptive flexfield column usages — the metadata that governs how a descriptive flexfield segment maps to a database column and how that segment is labeled to the end user at runtime. In Oracle EBS 12.1.1 and 12.2.2 this table is populated for each installed language so that descriptive flexfield prompts can be displayed in the session's language.

The table forms part of the descriptive flexfield definition infrastructure. Every row is keyed by the combination of the flexfield definition, its context, the specific application column, and the language, meaning that the same segment can carry distinct prompts and descriptions for every translated language. Because it depends on and enriches the base definition table rather than existing independently, the heuristic Data Vault modeling suggests a satellite classification: it is a descriptive, attribute-bearing child of the core flexfield column usage entity, not a standalone hub or a linking table between two business keys.

Key Information Stored

The primary key, enforced by FND_DESCR_FLEX_COL_USAGE_TL_PK, is the composite of APPLICATION_ID, DESCRIPTIVE_FLEXFIELD_NAME, DESCRIPTIVE_FLEX_CONTEXT_CODE, APPLICATION_COLUMN_NAME, and LANGUAGE. A parallel unique index, FND_DESCR_FLEX_COL_USAGE_TL_U1, extends the same set of columns with ZD_EDITION_NAME, identifying it as an additional business-key candidate that supports the edition-aware data model used in 12.2.x environments.

• APPLICATION_ID — identifies the application that owns the descriptive flexfield definition.
• DESCRIPTIVE_FLEXFIELD_NAME — the internal name of the descriptive flexfield to which the column usage belongs.
• DESCRIPTIVE_FLEX_CONTEXT_CODE — the context (segment) code that qualifies the usage within the flexfield.
• APPLICATION_COLUMN_NAME — the underlying application table column that the flexfield segment stores its value in.
• LANGUAGE — the NLS language code for the translated text held in the row.
• FORM_LEFT_PROMPT — the translatable label displayed to the left of the segment in the flexfield window.
• FORM_ABOVE_PROMPT — the translatable label displayed above the segment where the layout requires it.
• DESCRIPTION — a translated narrative describing the column usage, shown in setup and administrative forms.
• SOURCE_LANG — the base language from which the translation was derived, used by the translation and language-loading utilities.
• ZD_EDITION_NAME — the edition identifier used by the 12.2 online patching and editioning architecture.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN record who created and last changed the translation row.

Common Use Cases and Queries

The most frequent requirement is to retrieve the correct prompt text for a given flexfield segment in a specific language, typically for reporting, diagnostics, or reconciliation between the flexfield definition and what users actually see on screen. A representative query joins the translation table back to its base table and filters by language:

• SELECT t.DESCRIPTIVE_FLEXFIELD_NAME, t.DESCRIPTIVE_FLEX_CONTEXT_CODE, t.APPLICATION_COLUMN_NAME, t.FORM_LEFT_PROMPT, t.FORM_ABOVE_PROMPT FROM FND_DESCR_FLEX_COL_USAGE_TL t WHERE t.LANGUAGE = USERENV('LANG') AND t.DESCRIPTIVE_FLEXFIELD_NAME = :flexfield_name;
• Detecting segments that are missing a translation for a given language by comparing the distinct LANGUAGE values across rows for a segment.
• Auditing which columns a descriptive flexfield writes into, by listing APPLICATION_COLUMN_NAME values for a flexfield and context.
• Administrative review of SOURCE_LANG to confirm that a translated prompt was seeded from the correct base language after a patch or language install.

Because the table is edition-enabled in 12.2.2, queries in that release should generally be prepared to account for ZD_EDITION_NAME where the editioning views are queried directly.

Related Objects

The translation table is tightly coupled to the descriptive flexfield definition model. The most significant related objects are:

• FND_DESCR_FLEX_COLUMN_USAGES — the base (non-translated) table; the foreign key from FND_DESCR_FLEX_COL_USAGE_TL joins on APPLICATION_ID, DESCRIPTIVE_FLEXFIELD_NAME, DESCRIPTIVE_FLEX_CONTEXT_CODE, and APPLICATION_COLUMN_NAME.
• FND_DESCRIPTIVE_FLEXS — defines the descriptive flexfield itself and is referenced by DESCRIPTIVE_FLEXFIELD_NAME.
• FND_DESCR_FLEX_CONTEXTS — defines the context codes that qualify each segment usage.
• FND_DESCR_FLEX_CONTEXTS_TL — the translation table for flexfield contexts, mirroring the same TL pattern.
• FND_FLEX_VALIDATION_TABLES — supplies validation metadata for the segments defined through column usages.
• FND_APPLICATION — resolves APPLICATION_ID to the owning application short name and description.
• FND_LANGUAGES — maps LANGUAGE and SOURCE_LANG values to installed language names.

These relationships make FND_DESCR_FLEX_COL_USAGE_TL indispensable when tracing how a descriptive flexfield segment is labeled and where its value is physically stored.