Results for “fnd_flexbuilder_functions”

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

Overview

FND_FLEXBUILDER_FUNCTIONS is a setup table owned by the APPLSYS schema within the FND – Application Object Library product of Oracle E-Business Suite, holding Flexbuilder functions setup information. It is documented as VALID across EBS 12.1.1 and 12.2.2. The table stores the registration records that associate a Flexbuilder function with a specific key flexfield, thereby defining which user-defined formula and reporting functions are available to the Flexbuilder engine for that flexfield context. Each row is scoped by an APPLICATION_ID and identified by a FUNCTION_CODE, with a FUNCTION_NAME providing the human-readable label.

Based on the foreign key structure mined from the schema, the object is classified heuristically as satellite-leaning in Data Vault terms. This reflects its role as a descriptive, versioned detail attached to parent reference entities such as the key flexfield definition (FND_ID_FLEXS) rather than an independent business hub. Treating it as satellite data is a modeling suggestion: its business keys are the composite of application and function identifiers, and it carries descriptive attributes plus standard audit columns.

Key Information Stored

The table exposes 11 documented columns. The surrogate primary key is FND_FLEXBUILDER_FUNCTIONS_PK, composed of APPLICATION_ID and FUNCTION_CODE. Two unique indexes are documented as business-key candidates:

• FND_FLEXBUILDER_FUNCTIONS_UK1 / U1 (APPLICATION_ID, FUNCTION_CODE) — This is the composite that also drives the primary key and confirms each function code is unique within its owning application.
• FND_FLEXBUILDER_FUNCTIONS_U2 (APPLICATION_ID, FUNCTION_NAME) — A second uniqueness constraint guaranteeing that a function name is unique within the application scope.

The most significant descriptive columns include:

• APPLICATION_ID — Owning application; the partitioning key shared with nearly all FND setup tables.
• FUNCTION_CODE — The programmatic function identifier used by Flexbuilder.
• FUNCTION_NAME — The user-visible name of the function.
• FLEXFIELD_APPLICATION_ID — Application owning the referenced key flexfield.
• ID_FLEX_CODE — The key flexfield code the function is bound to.
• DESCRIPTION — Free-text explanation of the function’s purpose.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN provide standard EBS who/when lineage.

Common Use Cases and Queries

Typical uses include auditing which functions are registered for a key flexfield, tracing a function to its parameters, and reporting on the set of available Flexbuilder functions. A basic lookup by function code:

• SELECT function_code, function_name, id_flex_code FROM apps.fnd_flexbuilder_functions WHERE application_id = :app_id AND function_code = :code;

Resolving functions for a key flexfield:

• SELECT f.function_code, f.function_name FROM apps.fnd_flexbuilder_functions f WHERE f.flexfield_application_id = :flex_app AND f.id_flex_code = :flex_code;

A join to parameters is useful when documenting function signatures:

• SELECT f.function_code, p.parameter_code FROM apps.fnd_flexbuilder_functions f, apps.fnd_flexbuilder_parameters p WHERE f.application_id = p.application_id AND f.function_code = p.function_code;

Because the table is a setup entity, queries are commonly used in migration validation, comparing function registrations between source and target instances during upgrades to 12.1.1 or 12.2.2, and in configuration reporting.

Related Objects

• FND_ID_FLEXS — Referenced via FND_FLEXBUILDER_FUNCTIONS.FLEXFIELD_APPLICATION_ID and ID_FLEX_CODE; the parent key flexfield definition.
• FND_FLEXBUILDER_PARAMETERS — Child table joining on APPLICATION_ID and FUNCTION_CODE; holds the parameter definitions for each function.
• FND_APPLICATION — Provides the application name for APPLICATION_ID values.
• FND_FLEXBUILDER_FUNCTIONS_PK / UK1 / U2 — The documented constraints and unique indexes enforcing identity and business-key integrity.
• FND_ID_FLEX_STRUCTURES — Related through the key flexfield code for structure-level reporting.
• FND_FLEX_VALIDATION — Frequently joined in flexfield-rule reporting scenarios.