Results for “fnd_flexbuilder_assignments_u1”

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

Overview

FND_FLEXBUILDER_ASSIGNMENTS is a configuration table owned by the APPLSYS schema within the FND – Application Object Library product of Oracle E-Business Suite. It stores the assignment definitions produced by Oracle Flexbuilder, the metadata-driven utility used to generate and register descriptive and key flexfield structures across the EBS data model. Each row describes how a Flexbuilder parameter is bound to a flexfield, enabling the runtime and generation logic to resolve which parameter supplies conditional values, identifier values, or segment values for a given flexfield definition.

The table is classified heuristically as a link entity under a Data Vault modeling lens. This reflects its structure: it carries no independent business identity of its own, but rather associates a flexfield definition (ID_FLEX_NUM) with parameter definitions sourced from FND_FLEXBUILDER_PARAMETERS. The composite primary key and multiple foreign key relationships both point toward a junction or linkage role in the model, joining Flexbuilder parameter metadata to flexfield structure metadata.

Key Information Stored

The table contains twenty documented columns. The most significant for functional and technical analysis are:

• APPLICATION_ID – Identifies the application owning the flexfield and parameter; part of the composite primary key and the primary contributor to all three foreign key relationships.
• FUNCTION_CODE – Identifies the Flexbuilder function or generator context under which the assignment applies; part of the composite primary key.
• ID_FLEX_NUM – The flexfield definition identifier being assigned; part of the composite primary key.
• SEQUENCE – Ordering/identifier sequence within the assignment set; part of the composite primary key and shared with the FK join to FND_FLEXBUILDER_PARAMETERS.
• ASSIGNMENT_TYPE – Distinguishes the nature of the assignment (for example, segment parameter versus conditional parameter).
• PROTECTED_FLAG – Indicates whether the assignment is protected from regeneration or modification.
• DESCRIPTION – Human-readable text describing the assignment.
• CONDITIONAL_PARAMETER and CONDITIONAL_VALUE – Define conditional logic that gates whether the assignment is applied at runtime.
• ID_PARAMETER – References the parameter used to supply an identifier value for the assignment.
• SEGMENT_PARAMETER and SEGMENT_CONSTANTS – Supply segment-level parameter bindings and constant values.
• FLEXFIELD_SEGMENT_USAGES and SEGMENT_ATTRIBUTE_TYPE – Characterize how the segment is used and what attribute type it carries.
• SEGMENT_PARAMETER_PAIRINGS – Describes paired segment-to-parameter mappings.
• Audit columns – CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN track row-level changes.

The documented surrogate primary key is FND_FLEXBUILDER_ASSIGNMENTS_PK over (APPLICATION_ID, FUNCTION_CODE, ID_FLEX_NUM, SEQUENCE). The unique index FND_FLEXBUILDER_ASSIGNMENTS_U1 covers the same column set, making it the de facto business-key candidate for this table.

Common Use Cases and Queries

Typical diagnostic and reporting scenarios include auditing which parameters are bound to a flexfield, verifying conditional logic before regeneration, and tracing legacy Flexbuilder configurations during upgrade or cloning. A representative query joins the assignment to its parameter definition:

SELECT a.APPLICATION_ID, a.ID_FLEX_NUM, a.FUNCTION_CODE,
       a.SEQUENCE, a.ASSIGNMENT_TYPE, a.CONDITIONAL_PARAMETER,
       a.CONDITIONAL_VALUE, a.SEGMENT_PARAMETER
FROM   APPLSYS.FND_FLEXBUILDER_ASSIGNMENTS a
WHERE  a.APPLICATION_ID = :app_id
AND    a.ID_FLEX_NUM   = :flex_num
ORDER  BY a.SEQUENCE;

Analysts frequently filter on APPLICATION_ID and ID_FLEX_NUM to enumerate assignments for a single flexfield, or on PROTECTED_FLAG to identify assignments that will not be regenerated. Comparing ASSIGNMENT_TYPE distributions can reveal inconsistencies in parameter binding across environments.

Related Objects

The following objects are the most significant relatives of FND_FLEXBUILDER_ASSIGNMENTS based on documented relationships:

• FND_FLEXBUILDER_PARAMETERS – Referenced through three foreign keys from FND_FLEXBUILDER_ASSIGNMENTS using the shared columns APPLICATION_ID, FUNCTION_CODE, and SEQUENCE, combined with CONDITIONAL_PARAMETER, SEGMENT_PARAMETER, and ID_PARAMETER respectively. This is the primary dependency.
• FND_ID_FLEXS – Header table for key flexfield definitions; ID_FLEX_NUM in the assignments table points logically to a flexfield registered here.
• FND_ID_FLEX_STRUCTURES – Defines the segment structures corresponding to a given ID_FLEX_NUM.
• FND_DESCRIPTIVE_FLEXS – Descriptive flexfield definitions that may also receive Flexbuilder assignments.
• FND_FLEX_VALIDATION_TABLES and FND_FLEX_VALUE_SETS – Downstream consumers of segment parameter and constant assignments.
• FND_APPLICATION – Provides the application context referenced by APPLICATION_ID.
• FND_FLEXBUILDER_ASSIGNMENTS_PK / U1 – The primary key constraint and unique index that enforce uniqueness on the composite business key.

Because the table is a link entity, changes to its rows should be treated as configuration changes to flexfield generation metadata and should be coordinated with Flexbuilder regeneration runs.