Search Results fnd_profile_options_pkg




Overview
Explore in AI Chat

Overview

FND_PROFILE_OPTIONS_PKG is a core Oracle E-Business Suite profile management package owned by the APPS schema. Profile options are the mechanism through which EBS controls application behavior at the site, application, responsibility, and user levels. This package provides the low-level data maintenance layer for the definition of profile options themselves — that is, the metadata rows describing each profile option, its application context, its value set, and its translatable display text.

The package is classified under ETRM as an "OTHER" API, meaning it is not a public, supported end-user API in the same sense as a business-facing interface such as FND_PROFILE. It functions primarily as an internal maintenance and loader package. Its most visible use is through the profile option definition forms in the Application Developer responsibility (Profile > Define), and through the translation and data-load paths used when profile option definitions are seeded, migrated, or localized.

Key Procedures and Functions

The ETRM documentation records 14 procedures and functions in this package. The primary maintenance procedures are:

  • INSERT_ROW — creates a new profile option definition row, including the base row and associated translated rows.
  • UPDATE_ROW — modifies an existing profile option definition.
  • DELETE_ROW — removes a profile option definition.
  • LOCK_ROW — acquires the row-level lock required before modifying a profile option definition, ensuring concurrent updates do not collide.
  • LOAD_ROW — the seed data loader, used to insert or update a profile option definition from a loader script or migration process.
  • TRANSLATE_ROW — maintains the translatable portion of the definition, populating the language-specific display text in the TL table.
  • ADD_LANGUAGE — inserts the language-specific rows for a profile option when a new language is installed or activated.

Together these procedures implement a standard Oracle Forms-based maintenance pattern: lock the row, insert, update, or delete the base entity, and propagate corresponding rows into the translation table so that translated display text remains consistent with the base definition.

Tables Accessed

The package operates against the profile option infrastructure tables, accessed through APPS synonyms:

  • FND_PROFILE_OPTIONS — the base table holding one row per profile option definition, including the profile option name, application, and value set.
  • FND_PROFILE_OPTIONS_TL — the translated table holding the user-facing prompt text for each profile option in each installed language.
  • FND_PROFILE_OPTIONS_S — the sequence used to generate unique identifiers for new profile option definitions.
  • FND_PROFILE_CAT_OPTIONS — associates profile options with profile categories, supporting category-level value assignment.
  • FND_APPLICATION — supplies application context and validation for the owning application.
  • FND_LANGUAGES — drives language handling for translation and the ADD_LANGUAGE operation.
  • DUAL — used for scalar evaluations and sequence-related queries.

Usage Notes

FND_PROFILE_OPTIONS_PKG is invoked almost exclusively by the Framework profile option maintenance forms and by seed data loaders. In a normal implementation it is not called directly by end users or by custom business code. The DEFINE PROFILE OPTIONS form in the Application Developer responsibility calls these procedures when a developer creates or edits a profile option definition, and the same procedures execute during patch application and language installation.

ETRM records that the package is referenced by AP_UTILITIES_PKG, FND_PROFILE_CAT_OPTIONS_PKG, and IEU_WORK_SOURCE_PVT, and that it references other packages in turn. Because it is internal and not a published API, custom code should not depend on its exact signature or call patterns where the public profile APIs can achieve the same result. Direct modification of profile option definitions through this package bypasses some of the validation a supported interface would provide, and should be limited to controlled migration or loader scenarios.