Search Results fnd_descr_flex_contexts

Overview

The FND_DESCR_FLEX_CONTEXTS table is a core repository table within the Application Object Library (FND) module of Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It serves as the master definition table for the structural contexts of descriptive flexfields (DFFs). A descriptive flexfield provides customizable expansion space on application forms. This table defines the specific context structures (or segments) available for a given DFF, enabling the creation of context-sensitive flexfields where the segments displayed depend on a value entered by the user. It is a critical component for the metadata-driven extensibility framework of Oracle EBS.

Key Information Stored

The table stores the unique definitions for each context within a descriptive flexfield. Its composite primary key, FND_DESCR_FLEX_CONTEXTS_PK, consists of APPLICATION_ID, DESCRIPTIVE_FLEXFIELD_NAME, and DESCRIPTIVE_FLEX_CONTEXT_CODE. The APPLICATION_ID links to the owning application, while DESCRIPTIVE_FLEXFIELD_NAME identifies the specific flexfield. The DESCRIPTIVE_FLEX_CONTEXT_CODE is the internal identifier for the context structure. Other significant columns include ENABLED_FLAG, which controls the availability of the context, and CONTEXT_PROMPT, which is the user-friendly name for the context. The table also holds metadata such as the LAST_UPDATE_DATE and CREATION_DATE for auditing purposes.

Common Use Cases and Queries

This table is central to queries that analyze or troubleshoot descriptive flexfield setups. A common use case is identifying all active contexts for a specific DFF to understand its configuration. Developers and functional consultants often query this table to validate setups before data migration or to generate documentation. For instance, to list all contexts for the 'Account Flexfield' (GL#) in the General Ledger application (APPLICATION_ID=101), one would use:

• SELECT descriptive_flex_context_code, context_prompt, enabled_flag FROM apps.fnd_descr_flex_contexts WHERE application_id = 101 AND descriptive_flexfield_name = 'GL#' ORDER BY 1;

Another critical pattern involves joining to FND_DESCR_FLEX_COLUMN_USAGES to list all segment columns defined for each context, which is essential for understanding the complete DFF structure.

Related Objects

The FND_DESCR_FLEX_CONTEXTS table exists within a tightly integrated schema. It references the parent FND_DESCRIPTIVE_FLEXS table via a foreign key on (APPLICATION_ID, DESCRIPTIVE_FLEXFIELD_NAME), which holds the header definition of the flexfield. Several key objects depend on it through foreign key relationships, as documented in the ETRM metadata. The FND_DESCR_FLEX_COLUMN_USAGES table, which defines the individual segments for each context, references it on the full primary key columns. The FND_DESCR_FLEX_CONTEXTS_TL table provides translated names for the contexts. Furthermore, application-specific tables like MTL_EAM_ASSET_ATTR_GROUPS reference it, demonstrating how product modules leverage the central flexfield metadata to manage their extensible attributes.