Results for “org_enabled_flag”

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

Overview

FND_PROFILE_OPTIONS is the foundational configuration table in Oracle E-Business Suite, owned by the APPLSYS schema within the FND — Application Object Library product. It stores the metadata definitions for every user profile option registered in an EBS instance, forming the central registry that determines which configuration values can be set, at which hierarchy levels they may be defined, and under what conditions end users may view or modify them. Profile options govern a broad range of runtime behaviors across EBS, including security, localization, concurrent processing, and functional defaults. The table is present and valid in both 12.1.1 and 12.2.2, with the 12.2.2 documentation exposing 31 physical columns plus the ZD_EDITION_NAME column introduced by the edition-based redefinition architecture.

From a Data Vault modeling perspective, the mined relationship structure suggests a hub-leaning classification. FND_PROFILE_OPTIONS acts as a durable business key registry — each profile option name is a stable, uniquely identifiable concept — with much of the descriptive, mutable state (hierarchy flags, enablement rules, validation logic) behaving satellite-like. Downstream tables such as FND_PROFILE_OPTION_VALUES and FND_PROFILE_OPTIONS_TL attach link and satellite-style detail to this hub.

Key Information Stored

The surrogate primary key is defined by FND_PROFILE_OPTIONS_PK on the composite of APPLICATION_ID and PROFILE_OPTION_ID. Two unique indexes act as business-key candidates: FND_PROFILE_OPTIONS_U1 (APPLICATION_ID, PROFILE_OPTION_ID, ZD_EDITION_NAME) and, more significantly, the original unique constraint FND_PROFILE_OPTIONS_UK2 on PROFILE_OPTION_NAME alone, which enforces global uniqueness of each profile option name.

• PROFILE_OPTION_NAME — the unique system identifier used by all APIs and forms to reference the option.
• APPLICATION_ID — the owning application, foreign-keyed to FND_APPLICATION, establishing which product defined the option.
• PROFILE_OPTION_ID — the internal surrogate identifier within the owning application.
• Hierarchy enablement flags — SITE_ENABLED_FLAG, APP_ENABLED_FLAG, RESP_ENABLED_FLAG, USER_ENABLED_FLAG, SERVER_ENABLED_FLAG, ORG_ENABLED_FLAG, and SERVERRESP_ENABLED_FLAG indicate at which levels the option may be set.
• Corresponding *_UPDATE_ALLOWED_FLAG columns — control whether the value may be changed at each level (for example SITE_UPDATE_ALLOWED_FLAG, USER_UPDATE_ALLOWED_FLAG, ORG_UPDATE_ALLOWED_FLAG).
• USER_CHANGEABLE_FLAG and USER_VISIBLE_FLAG — govern whether end users can alter or even see the option.
• READ_ALLOWED_FLAG and WRITE_ALLOWED_FLAG — control programmatic read/write access.
• SQL_VALIDATION — an optional validation statement used to constrain permissible values.
• HIERARCHY_TYPE — identifies the level-ordering model applied when resolving values.
• START_DATE_ACTIVE and END_DATE_ACTIVE — define the effective date window of the option definition.
• ZD_EDITION_NAME — the editioning column supporting online patching in 12.2.

Common Use Cases and Queries

DBAs and functional consultants query this table to audit which profile options exist, which levels are enabled, and how an option will resolve for a given user. A typical inventory query listing all user-visible, site-enabled options for a specific application would filter on APPLICATION_ID, USER_VISIBLE_FLAG, and SITE_ENABLED_FLAG. Reconciliation reports compare FND_PROFILE_OPTIONS against FND_PROFILE_OPTION_VALUES to detect options defined but never assigned. Migration and cloning exercises use PROFILE_OPTION_NAME as the join key to move configuration between environments. Support diagnostics frequently join this table to FND_PROFILE_OPTION_VALUES to trace why a particular runtime behavior differs between users, since the option's enablement flags determine the level at which an overriding value is honored.

Related Objects

• FND_APPLICATION — referenced via FND_PROFILE_OPTIONS.APPLICATION_ID; provides the owning application name.
• FND_PROFILE_OPTIONS_TL — the translated-language table joined on PROFILE_OPTION_NAME, supplying user-facing display names and descriptions.
• FND_PROFILE_OPTION_VALUES — joined on APPLICATION_ID and PROFILE_OPTION_ID; holds the actual assigned values at each hierarchy level.
• FND_PROFILE_CAT_OPTIONS — joins on PROFILE_OPTION_APPLICATION_ID and PROFILE_OPTION_ID to group options into categories.
• FND_PROFILE_OPTION_B and the FND_PROFILE PL/SQL package — the standard API layer for reading (FND_PROFILE.VALUE) and writing (FND_PROFILE.SAVE) option values, relying on this metadata at runtime.