Results for “descriptive_flex_context_code”

50+ results




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

Overview

FND_DESCR_FLEX_CONTEXTS is an Application Object Library (FND) table owned by the APPLSYS schema that stores the structure names, or context definitions, for descriptive flexfields in Oracle E-Business Suite 12.1.1 and 12.2.2. In Oracle EBS, a descriptive flexfield is a configurable set of attribute columns appended to a database table, allowing customers to capture additional information without modifying the underlying schema. The flexfield itself is defined in FND_DESCRIPTIVE_FLEXS, while FND_DESCR_FLEX_CONTEXTS defines each distinct context, or structural variant, under which a subset of those attribute columns applies. Examples include a global context, which is always displayed, and named contexts such as "India Tax Information" or "Asset Details" that are conditionally displayed based on entered values.

Because its primary key is a composite business key and it is referenced by numerous dependent tables, the heuristic Data Vault classification for FND_DESCR_FLEX_CONTEXTS is hub-leaning. In a Data Vault model this suggests treating the table as a hub keyed on application, flexfield name, and context code, with its descriptive attributes (such as ENABLED_FLAG and GLOBAL_FLAG) carried in a satellite.

Key Information Stored

The table contains eleven documented columns. The surrogate primary key, FND_DESCR_FLEX_CONTEXTS_PK, is composed of three business-key columns that also appear in the unique index FND_DESCR_FLEX_CONTEXTS_U1:

  • APPLICATION_ID — identifies the owning application, typically Application Object Library.
  • DESCRIPTIVE_FLEXFIELD_NAME — the internal name of the parent descriptive flexfield, such as "XX_CUSTOMERS" or a seeded value.
  • DESCRIPTIVE_FLEX_CONTEXT_CODE — the unique context code that, combined with the flexfield, defines each context structure.
  • ENABLED_FLAG — indicates whether the context is active and available for data entry.
  • GLOBAL_FLAG — marks the global context, which is always displayed regardless of other context values.
  • ZD_EDITION_NAME — an editioning column introduced with EBS 12.2 online patching, enabling edition-based redefinition of the flexfield definition.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard FND audit columns tracking who created and last modified each context and when.

The unique index FND_DESCR_FLEX_CONTEXTS_U1 extends the primary key with ZD_EDITION_NAME, confirming that the business key is edition-aware in 12.2.2.

Common Use Cases and Queries

Consultants and developers query this table to enumerate the contexts defined for a flexfield, to confirm whether a context is enabled, and to join context definitions to the individual attribute column usages stored in FND_DESCR_FLEX_COLUMN_USAGES. A frequent reporting pattern lists all enabled contexts for a given flexfield:

  • SELECT descriptive_flexfield_name, descriptive_flex_context_code, enabled_flag, global_flag FROM fnd_descr_flex_contexts WHERE application_id = :app_id AND enabled_flag = 'Y' ORDER BY descriptive_flex_context_code;

Another common pattern identifies the global context for a flexfield using GLOBAL_FLAG, or traces a context to its descriptive segments by joining to FND_DESCR_FLEX_COLUMN_USAGES on APPLICATION_ID, DESCRIPTIVE_FLEXFIELD_NAME, and DESCRIPTIVE_FLEX_CONTEXT_CODE. Translating context codes into user-facing prompts and titles requires a join to the translation table FND_DESCR_FLEX_CONTEXTS_TL on the same three key columns.

Related Objects

The most significant related objects, based on documented foreign key relationships, are:

  • FND_DESCRIPTIVE_FLEXS — parent table holding the flexfield definition; joined on APPLICATION_ID and DESCRIPTIVE_FLEXFIELD_NAME.
  • FND_DESCR_FLEX_COLUMN_USAGES — stores the segments and their properties for each context; references this table on APPLICATION_ID, DESCRIPTIVE_FLEXFIELD_NAME, and DESCRIPTIVE_FLEX_CONTEXT_CODE.
  • FND_DESCR_FLEX_CONTEXTS_TL — the translation table supplying language-specific context names and descriptions; references the same three key columns.
  • MTL_EAM_ASSET_ATTR_GROUPS — Enterprise Asset Management table that references a context to associate asset attribute groups with a flexfield context.

Together these objects form the definitional backbone of descriptive flexfields in Oracle EBS, linking flexfield definitions, contexts, column usages, and translations into a coherent, extensible model.