Search Results fnd_profile_option_values_u1

Overview

APPLSYS.FND_PROFILE_OPTION_VALUES is the transactional repository that stores the actual values assigned to user profile options across every supported profile hierarchy level. Profile options are the primary mechanism by which Oracle E-Business Suite controls application behavior at runtime, and each row in this table represents a single profile option setting for a specific level, user, responsibility, or application. Because Oracle Application Object Library (AOL) reads these values at session initialization, the table is fundamental to how applications behave for a given user in a given responsibility.

The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 20. Its FND design data reference is FND.FND_PROFILE_OPTION_VALUES, and the object carries a VALID status in the EBS 12.1.1 and 12.2.2 releases.

From a data modeling perspective, the heuristic Data Vault classification for this object is link. The table does not hold descriptive attributes of a single business entity; instead it records relationships and assigned values that connect a profile option, a hierarchy level, and the level's identifying value (user, responsibility, or application). This link interpretation reflects the table's role as a junction that binds profile metadata to concrete assignments.

Key Information Stored

Each row captures one profile option setting at a single level for a single target. The most significant columns are:

• APPLICATION_ID — Identifies the application to which the profile option setting belongs.
• PROFILE_OPTION_ID — Foreign key reference to the profile option definition in FND_PROFILE_OPTIONS.
• LEVEL_ID — Identifies the profile hierarchy level (Site, Application, Responsibility, User, and Server/Responsibility variants).
• LEVEL_VALUE — The value of the profile level; for user-level settings this is the user_id, and for application-level settings it resolves to the application identifier.
• LEVEL_VALUE_APPLICATION_ID — The application identifier for the "Application" profile level, pinning a responsibility to its owning application.
• LEVEL_VALUE2 — Used within the Server/Responsibility (SERVRESP) hierarchy to store the server_id or the secondary level value.
• PROFILE_OPTION_VALUE — The actual assigned value, always stored as a CHAR string (VARCHAR2(240)), regardless of the option's logical datatype.
• Standard Who columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN provide audit and concurrency tracking.

The unique index FND_PROFILE_OPTION_VALUES_U1 spans APPLICATION_ID, PROFILE_OPTION_ID, LEVEL_ID, LEVEL_VALUE, LEVEL_VALUE_APPLICATION_ID, LEVEL_VALUE2, and (in 12.2.2) ZD_EDITION_NAME. This composite acts as the business-key candidate that guarantees only one value per option per level per target, while the documented primary key FND_PROFILE_OPTION_VALUES_PK covers the same columns minus ZD_EDITION_NAME. The nonunique index FND_PROFILE_OPTION_VALUES_N1 on LEVEL_ID, LEVEL_VALUE, LEVEL_VALUE_APPLICATION_ID, and LEVEL_VALUE2 accelerates reverse lookups.

Common Use Cases and Queries

Administrators and developers query this table to audit which profile values are set, to diagnose unexpected application behavior, and to verify that a profile option resolves to the intended value after hierarchy inheritance is applied. Reporting typically joins to FND_PROFILE_OPTIONS to obtain the option's user-visible name and to FND_USER or FND_RESPONSIBILITY to resolve level values into human-readable names.

A representative query retrieves all settings for a specific profile option:

• SELECT fpo.user_profile_option_name, fpov.level_id, fpov.level_value, fpov.level_value_application_id, fpov.profile_option_value FROM fnd_profile_option_values fpov, fnd_profile_options fpo WHERE fpov.profile_option_id = fpo.profile_option_id AND fpo.user_profile_option_name = 'GL_ACCESS_SET_ID';

Another common pattern resolves user-level assignments by joining LEVEL_VALUE to FND_USER.USER_ID, and responsibility-level assignments by joining LEVEL_VALUE and LEVEL_VALUE_APPLICATION_ID to FND_RESPONSIBILITY.RESPONSIBILITY_ID and APPLICATION_ID respectively. Migration or data-fix scripts frequently insert, update, or delete rows keyed on the U1 columns to enforce a single effective value per level.

Related Objects

The following objects are most significant to working with this table:

• FND_PROFILE_OPTIONS — Referenced via APPLICATION_ID; holds the profile option definitions and names.
• FND_RESPONSIBILITY — Referenced via LEVEL_VALUE_APPLICATION_ID; supplies responsibility context for responsibility-level settings.
• FND_USER — Referenced via LEVEL_VALUE for user-level profile settings.
• FND_APPLICATION — Referenced via LEVEL_VALUE; provides application-level context.
• FND_PROFILE_OPTION_VALUES is also accessed through the FND_PROFILE API package and the profile option maintenance forms, which insert and update rows on behalf of administrators.

Together these relationships position FND_PROFILE_OPTION_VALUES as the authoritative store that binds profile definitions to their assigned values across every level of the EBS security and configuration hierarchy.