Search Results so_attributes

Overview

The FND_DESCRIPTIVE_FLEXS table is a core metadata repository within the Oracle E-Business Suite Application Object Library (FND). It serves as the central registration table for all descriptive flexfields (DFFs) across the application. A descriptive flexfield is a key extensibility feature that allows implementers to add custom, context-sensitive attributes to standard Oracle EBS forms and tables without modifying the base application code. This table, owned by the APPLSYS schema, defines the existence, basic properties, and the underlying database table to which each DFF is attached. It acts as the parent record for all subsequent DFF configuration, including contexts, segments, and compiled metadata.

Key Information Stored

The table's structure is designed to uniquely identify and describe a flexfield. Its primary key is a composite of APPLICATION_ID and DESCRIPTIVE_FLEXFIELD_NAME, ensuring uniqueness within the application. Key columns include APPLICATION_ID, which links to FND_APPLICATION to identify the owning product, and DESCRIPTIVE_FLEXFIELD_NAME, which is the internal name of the flexfield (e.g., 'PER_POSITIONS_F'). Crucially, the TABLE_APPLICATION_ID and APPLICATION_TABLE_NAME columns define the specific database table (referenced in FND_TABLES) that the DFF extends. Other columns manage descriptive information, title prompts, and technical flags controlling the flexfield's behavior and validation.

Common Use Cases and Queries

This table is primarily queried for metadata analysis, impact assessment, and troubleshooting during customization or upgrade projects. Common scenarios include identifying all DFFs attached to a specific base table, auditing DFF usage across modules, or diagnosing issues with flexfield registration. A typical query retrieves DFF details for a known table:

• SELECT fdf.descriptive_flexfield_name, fdf.title, fat.application_name FROM apps.fnd_descriptive_flexs fdf, apps.fnd_application_tl fat WHERE fdf.table_application_id = fat.application_id AND fdf.application_table_name = 'PO_HEADERS_ALL' AND fat.language = USERENV('LANG');

Another frequent use is joining to FND_DESCR_FLEX_CONTEXTS to list all contexts defined for a specific flexfield, providing a complete view of its configuration setup.

Related Objects

As indicated by its foreign key relationships, FND_DESCRIPTIVE_FLEXS is the cornerstone of the DFF metadata model. Key dependent objects include FND_DESCR_FLEX_CONTEXTS, which stores the individual context codes and their structures, and FND_DESCRIPTIVE_FLEXS_TL for translated titles. The FND_COMPILED_DESCRIPTIVE_FLEXS table holds the runtime, compiled version of the flexfield definition for performance. Furthermore, it is referenced by FND_DEFAULT_CONTEXT_FIELDS for defaulting logic, and by modules like Order Management (SO_ATTRIBUTES) and Concurrent Processing (FND_REQUEST_SET_PROGRAM_ARGS), demonstrating its integration across the suite for argument and attribute management.