Results for “profile_option_name”

50+ results




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

Overview

XDP_PROFILE_OPTIONS_V is a reporting and integration view owned by the APPS schema within the Oracle E-Business Suite environment. It belongs to the XDP — Provisioning product family, which encompasses the provisioning and service-activation functionality used across the Oracle EBS application stack. The view is documented with a VALID status and its stated purpose is to expose all profile options associated with the XDP and XNP applications. Rather than querying the underlying profile option tables directly, consumers of this view obtain a pre-joined, language-aware, and site-level-filtered result set that presents profile option names, translated user-facing names, descriptions, and current values in a single convenient structure.

Because profile options drive a substantial amount of provisioning and configuration behavior, this view is frequently used in diagnostics, audits, and integration scripts that must confirm how the XDP/XNP modules are configured. It also serves as a reference for translators and functional analysts who need to understand the descriptive text attached to each profile option.

Underlying Base Objects

The view is defined over three documented base objects, all referenced via synonyms in the APPS schema: FND_PROFILE_OPTIONS, FND_PROFILE_OPTIONS_TL, and FND_PROFILE_OPTION_VALUES. FND_PROFILE_OPTIONS holds the definition of each profile option, including its identifier, application, and effective dating. FND_PROFILE_OPTIONS_TL is the translation table that stores the user-facing name and description in each installed language. FND_PROFILE_OPTION_VALUES stores the values assigned at various hierarchy levels.

The join logic is significant. FND_PROFILE_OPTIONS is joined to FND_PROFILE_OPTIONS_TL on the profile option name, and to FND_PROFILE_OPTION_VALUES through an outer join on profile option ID. The view restricts results to two applications, identified by APPLICATION_ID 534 and 535, which correspond to XDP and XNP respectively. A further restriction of NVL(FPV.LEVEL_ID, 10001) = 10001 limits returned values to the Site level, while the end-date predicate ensures only currently active profile options are returned. Language selection is performed through USERENV('LANG'), so only the translated row matching the session language is displayed.

Key Columns

  • PROFILE_OPTION_NAME — the internal, system-level name of the profile option, used as the primary key for joining and referenced routinely in FND_PROFILE calls.
  • USER_PROFILE_OPTION_NAME — the translated, user-facing label derived from FND_PROFILE_OPTIONS_TL, suitable for display in reports and user interfaces.
  • DESCRIPTION — the translated explanatory text describing the purpose and expected values of the profile option.
  • PROFILE_OPTION_VALUE — the value currently assigned at the Site level, as resolved from FND_PROFILE_OPTION_VALUES. Where no site-level value exists, the outer join returns null.

Common Use Cases and Queries

The most frequent use is verifying current XDP and XNP provisioning configuration before an implementation or support engagement. A typical query lists all options with their names, values, and descriptions:

SELECT profile_option_name,
       user_profile_option_name,
       profile_option_value
  FROM   apps.xdp_profile_options_v
 WHERE  profile_option_name LIKE 'XDP%';

Because the user searched for FND_PROFILE_OPTIONS_TL, this view is a convenient alternative to joining that translation table manually; the language filtering is already applied. Analysts comparing configuration across environments can export the view and diff results, while support engineers may search by description text to locate an option whose internal name is unknown. Site-level values returned here represent the effective baseline before user, responsibility, or application overrides are considered.