Search Results fnd_flex_validation_events_u1

Overview

APPLSYS.FND_FLEX_VALIDATION_EVENTS is a seed-data table in Oracle E-Business Suite that stores the configuration of validation events associated with special validated key and descriptive flexfield value sets. Each row defines a discrete event — an entry point at which Oracle Application Object Library (AOL) executes a user exit routine when a user enters a flexfield segment or supplies a report parameter. The table therefore acts as the bridge between a value set definition and the compiled user exit code that enforces custom validation logic at runtime.

From a Data Vault modeling perspective, the object is classified heuristically as satellite-leaning. This classification is a modeling suggestion only: the table carries descriptive attributes of the value set event (the user exit call and its context), keyed by a business composite rather than by an independent surrogate. It does not function as a hub of new business keys nor as a many-to-many link, but rather as configuration detail dependent on FND_FLEX_VALUE_SETS.

The object is owned by APPLSYS, has an FND Design Data equivalent (FND.FND_FLEX_VALIDATION_EVENTS), and is stored in the APPS_TS_SEED tablespace, consistent with its role as seeded, non-transactional configuration data. It is documented as VALID in both EBS 12.1.1 and 12.2.2.

Key Information Stored

The table is narrow, comprising nine documented columns in the 12.2.2 physical schema. The most significant are:

• FLEX_VALUE_SET_ID — NUMBER(10), the flexfield value set identifier. This is the leading column of the primary key and the foreign key to FND_FLEX_VALUE_SETS.
• EVENT_CODE — VARCHAR2, the type or name of the validation event. Together with the value set it forms the composite business key.
• USER_EXIT — LONG, the user exit call string invoked for the event. This is the functional payload of the row and explains its LONG datatype, which constrains certain SQL operations.
• ZD_EDITION_NAME — the editioning column present in the 12.2.2 online patching architecture, appended to the unique key.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard WHO audit columns.

The primary key is FND_FLEX_VALIDATION_EVENTS_PK on (FLEX_VALUE_SET_ID, EVENT_CODE). The unique index the user searched for, FND_FLEX_VALIDATION_EVENTS_U1, is documented in 12.1.1 as UNIQUE on (FLEX_VALUE_SET_ID, EVENT_CODE) in APPS_TS_SEED, and in 12.2.2 additionally includes ZD_EDITION_NAME. The unique index columns represent the business-key candidate, while the table remains a satellite of the value set.

Common Use Cases and Queries

Administrators and developers query this table to audit which user exits are attached to a special value set, to troubleshoot validation failures at segment entry, or to migrate event configuration between environments.

• Retrieve all events for a given value set: SELECT event_code, user_exit FROM fnd_flex_validation_events WHERE flex_value_set_id = :id;
• Locate value sets referencing a particular user exit by joining to FND_FLEX_VALUE_SETS on FLEX_VALUE_SET_ID.
• Compare configuration across instances during a 12.1.1 to 12.2.2 upgrade.

Because USER_EXIT is a LONG column, direct string comparison is not permitted; use PL/SQL or DBMS_SQL instead of WHERE clauses on that column.

Related Objects

• FND_FLEX_VALUE_SETS — the parent table; joined on FLEX_VALUE_SET_ID.
• FND_FLEX_VALIDATION_EVENTS (APPS synonym/view) — the APPS-layer access point.
• FND_FLEX_VALUES / FND_FLEX_VALUES_TL — the values validated by the events.
• FND_FLEX_VALIDATION — companion validation metadata for special value sets.
• FND_DESCR_FLEX_COLUMN_USAGES — links flexfield segments to value sets.