Results for “default_context_value”

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

Overview

FND_DESCRIPTIVE_FLEXS is the registration repository for Descriptive Flexfields (DFF) within Oracle E-Business Suite, owned by the APPLSYS schema and delivered under the FND – Application Object Library product. Every descriptive flexfield defined in an EBS instance — whether a seeded Oracle flexfield or a customer-defined extension — must have a corresponding registration row in this table. The registration establishes the flexfield's identity, the underlying database table and context column that store the segment values, defaulting behavior for the context field, and control attributes governing freezing, protection, and runtime property functions.

From a data-modeling perspective, the mined foreign-key structure classifies FND_DESCRIPTIVE_FLEXS heuristically as a hub. Its two-column primary key, APPLICATION_ID and DESCRIPTIVE_FLEXFIELD_NAME, is a natural composite business key rather than a generated surrogate, and numerous dependent tables — context definitions, compiled flexfield metadata, translated names, and application tables such as SO_ATTRIBUTES — radiate from it. A Data Vault implementation would therefore model this as a hub keyed on the application-and-flexfield-name pair, with satellites capturing the mutable registration attributes such as context defaulting and freeze flags.

Key Information Stored

The primary key FND_DESCRIPTIVE_FLEXS_PK consists of APPLICATION_ID and DESCRIPTIVE_FLEXFIELD_NAME. A unique index, FND_DESCRIPTIVE_FLEXS_U1, extends these with ZD_EDITION_NAME, confirming the pair (plus edition) as the documented business-key candidate. The most operationally significant columns include:

• APPLICATION_ID — owning application, foreign key to FND_APPLICATION.
• DESCRIPTIVE_FLEXFIELD_NAME — the internal flexfield name used by APIs such as FND_FLEX_EXT.GET_SEGMENTS.
• APPLICATION_TABLE_NAME and TABLE_APPLICATION_ID — identify the database table whose columns hold the flexfield segments; these form a foreign key to FND_TABLES.
• CONTEXT_COLUMN_NAME — the table column that stores the structure/context code, the pivot for context-sensitive segments.
• CONTEXT_REQUIRED_FLAG and CONTEXT_USER_OVERRIDE_FLAG — govern whether a context value must be supplied and whether users may override defaulted values.
• DEFAULT_CONTEXT_FIELD_NAME, DEFAULT_CONTEXT_VALUE, CONTEXT_DEFAULT_TYPE, and CONTEXT_DEFAULT_VALUE — define the default context derivation logic.
• CONCATENATED_SEGMENT_DELIMITER and CONCATENATED_SEGS_VIEW_NAME — control how segment values are concatenated for reporting, including the generated view.
• FREEZE_FLEX_DEFINITION_FLAG and PROTECTED_FLAG — indicate whether the definition is locked against structural change.
• CONTEXT_OVERRIDE_VALUE_SET_ID, CONTEXT_RUNTIME_PROPERTY_FUNCT, and CONTEXT_SYNCHRONIZATION_FLAG — advanced context validation, runtime property, and synchronization controls.
• LAST_UPDATE_DATE, CREATED_BY, and related audit columns — standard WHO columns for change tracking.

Common Use Cases and Queries

The most frequent requirement is discovering which flexfield is attached to a given application table — for example, identifying the DFF registered against SO_ATTRIBUTES in Order Management. A representative query joins FND_DESCRIPTIVE_FLEXS to FND_APPLICATION to obtain both the internal and translated application names:

• Locate a flexfield by table: SELECT application_id, descriptive_flexfield_name, context_column_name FROM fnd_descriptive_flexs WHERE application_table_name = 'SO_ATTRIBUTES';
• List all contexts for a flexfield by joining FND_DESCR_FLEX_CONTEXTS on APPLICATION_ID and DESCRIPTIVE_FLEXFIELD_NAME.
• Audit frozen or protected flexfields using FREEZE_FLEX_DEFINITION_FLAG and PROTECTED_FLAG to assess change-control risk.
• Report defaulting configuration by selecting the CONTEXT_DEFAULT_* columns for a given flexfield.
• Reconcile registered flexfields against FND_COMPILED_DESCRIPTIVE_FLEXS to detect flexfields that have not been compiled after a definition change.
• Identify the concatenated segments view used for reporting via CONCATENATED_SEGS_VIEW_NAME.

Because this table is the registration hub, queries are commonly the starting point for dependency analysis before applying patches or extending a flexfield.

Related Objects

FND_DESCRIPTIVE_FLEXS sits at the center of the flexfield metadata model. Significant related objects include:

• FND_DESCR_FLEX_CONTEXTS — defines each context (structure) for a flexfield; joins on APPLICATION_ID and DESCRIPTIVE_FLEXFIELD_NAME.
• FND_COMPILED_DESCRIPTIVE_FLEXS — runtime-compiled segment metadata; same join columns. Essential when troubleshooting flexfield rendering.
• FND_DESCRIPTIVE_FLEXS_TL — translated flexfield names and descriptions, joined on the same composite key.
• FND_DEFAULT_CONTEXT_FIELDS — default context field definitions per flexfield.
• SO_ATTRIBUTES — Order Management's attribute table, referencing this table via DESCR_FLEX_APPLICATION_ID and DESCRIPTIVE_FLEXFIELD_NAME; this is the join relevant to the "so_attributes" search.
• FND_APPLICATION — parent application via APPLICATION_ID.
• FND_TABLES — registered table via TABLE_APPLICATION_ID and APPLICATION_TABLE_NAME.
• FND_REQUEST_SET_PROGRAM_ARGS — references flexfields through DESCRIPTIVE_FLEX_APPL_ID and DESCRIPTIVE_FLEXFIELD_NAME.

These relationships make FND_DESCRIPTIVE_FLEXS the authoritative starting point for any investigation into descriptive flexfield behavior in Oracle EBS 12.1.1 and 12.2.2.