Search Results fnd_flexbuilder_functions




Overview
Explore in AI Chat

Overview

The FND_FLEXBUILDER_FUNCTIONS table is a core repository for metadata that defines FlexBuilder functions within Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. Owned by the APPLSYS schema and part of the Application Object Library (FND) module, it serves as the central setup table for the functions used by the FlexBuilder architecture. FlexBuilder functions are specialized routines that define the behavior and processing logic for descriptive flexfields (DFFs) and key flexfields (KFFs). This table's primary role is to register and manage these functions, linking them to specific flexfields and providing a foundation for their execution and parameterization within the application's flexfield framework.

Key Information Stored

The table stores the essential identifiers and attributes required to uniquely define and reference a FlexBuilder function. Its structure is governed by two primary keys, ensuring uniqueness and providing different access paths. The most critical columns include APPLICATION_ID and FUNCTION_CODE, which together form the primary key (FND_FLEXBUILDER_FUNCTIONS_PK). The APPLICATION_ID associates the function with a specific Oracle EBS application, while the FUNCTION_CODE is the internal short name for the function. The alternate unique key (FND_FLEXBUILDER_FUNCTIONS_UK1) is based on APPLICATION_ID and FUNCTION_NAME, where FUNCTION_NAME is the descriptive title of the function. Furthermore, the table contains foreign key columns FLEXFIELD_APPLICATION_ID and ID_FLEX_CODE, which link the function to its parent flexfield definition in the FND_ID_FLEXS table.

Common Use Cases and Queries

This table is primarily queried for diagnostic, reporting, and setup verification purposes by functional and technical consultants. A common use case is to identify all FlexBuilder functions registered for a particular flexfield or application to understand its customization capabilities. For instance, to list all functions for the Accounting Flexfield (key flexfield code 'GL#'), one might execute:

  • SELECT FUNCTION_CODE, FUNCTION_NAME FROM APPLSYS.FND_FLEXBUILDER_FUNCTIONS WHERE ID_FLEX_CODE = 'GL#';

Another typical query involves joining with FND_APPLICATION to get the application name for a more readable report:

  • SELECT FA.APPLICATION_NAME, FFB.FUNCTION_CODE, FFB.FUNCTION_NAME FROM APPLSYS.FND_FLEXBUILDER_FUNCTIONS FFB, FND_APPLICATION FA WHERE FFB.APPLICATION_ID = FA.APPLICATION_ID ORDER BY 1, 2;

This data is crucial when troubleshooting flexfield behavior or when documenting custom flexfield implementations that leverage these functions.

Related Objects

The FND_FLEXBUILDER_FUNCTIONS table maintains documented relationships with several other key flexfield metadata tables, as indicated by its foreign key constraints.

  • FND_ID_FLEXS: This is the primary parent table for flexfield definitions. The columns FLEXFIELD_APPLICATION_ID and ID_FLEX_CODE in FND_FLEXBUILDER_FUNCTIONS reference the APPLICATION_ID and ID_FLEX_CODE columns in FND_ID_FLEXS, establishing which flexfield the function belongs to.
  • FND_FLEXBUILDER_PARAMETERS: This is a child table that stores the parameters for each FlexBuilder function. Its columns APPLICATION_ID and FUNCTION_CODE reference the corresponding primary key columns in FND_FLEXBUILDER_FUNCTIONS, creating a one-to-many relationship where a single function can have multiple parameters.