Results for “fnd_profile”

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

Overview

FND_PROFILE is the core PL/SQL package through which Oracle E-Business Suite manages its profile option infrastructure. Profile options are the primary configuration mechanism in EBS: they govern everything from the user interface language and date format to the active organization context, concurrent manager behavior, and application-specific business rules. The FND_PROFILE package body in the APPS schema provides the runtime engine that stores, retrieves, caches, and invalidates these settings on behalf of virtually every other module in the application.

In ETRM 12.1.1 and 12.2.2, the object is documented as VALID with an API classification of OTHER. Its most striking characteristic is its pervasiveness: FND_PROFILE is referenced by 6,785 other packages, making it one of the most heavily depended-upon packages in the entire EBS data model. Its own dependency list spans cache-management utilities (FND_CACHE_VERSIONS_PKG), logging (FND_CORE_LOG), globalization and message handling (FND_GLOBAL, FND_MESSAGE), node and release metadata (FND_NODES, FND_RELEASE), profile storage tables, security (ICX_SEC), and the Workflow engine (WF_CORE, WF_EVENT, WF_ENGINE). A parallel synonym, FND_PROFILE, is also referenced within the body itself, supporting recursive lookups such as hierarchical profile resolution.

Key Procedures and Functions

The documented package exposes 17 procedures and functions. The principal retrieval interfaces are GET, GET_SPECIFIC, VALUE, VALUE_SPECIFIC, VALUE_WNPS, and GET_TABLE_VALUE, which resolve a profile option name to its effective value for the current or specified user, responsibility, and application context. DEFINED and GET_ALL_TABLE_VALUES support bulk introspection of which options are set and what values a table-validated profile option may legitimately take.

On the write path, PUT and PUTMULTIPLE persist profile values, while SAVE and SAVE_USER commit pending changes at the site and user level respectively, and DELETE removes stored values. INITIALIZE and INITIALIZE_ORG_CONTEXT prepare the session-level cache and establish the organization context, which is essential for multi-org (Operating Unit) security. Two cache-control routines are documented: BUMPCACHEVERSION_RF increments the cache version used by the runtime forms layer, and PUT_CACHE_CLEARED signals that a cached value set has been invalidated. Together these routines guarantee that profile changes made in one session propagate to others without requiring a full application restart.

Tables Accessed

The package reads and writes FND_PROFILE_OPTIONS, the definition table for profile option names, levels, and validation rules, and FND_PROFILE_OPTION_VALUES, the transactional store of actual values by level. It queries FND_USER and FND_USER_PKG for user-level resolution, FND_RESPONSIBILITY_VL for responsibility-level settings, and FND_NODES to determine the current application server node, which influences server-level profile caching. FND_RELEASE supplies version metadata. Workflow integration relies on WF_EVENT_T and WF_EVENT, while DBMS_UTILITY and PLITBLM provide generic PL/SQL and index-by-table support. FND_PROFILE_OPTION_VALUES_PKG, FND_CACHE_VERSIONS_PKG, FND_GLOBAL, FND_MESSAGE, FND_CORE_LOG, ICX_SEC, and the Workflow packages are invoked as supporting APIs.

Usage Notes

FND_PROFILE is invoked implicitly by Oracle Forms through the FNDSQF library and by concurrent programs through the FND_GLOBAL initialization path. Custom code should call the documented public interfaces (typically GET, VALUE, or PUT) rather than manipulating the underlying tables directly, because the package maintains an in-memory cache whose consistency depends on these entry points. Sessions that change profile values should call BUMPCACHEVERSION_RF or rely on the standard SAVE routines so that other sessions observe the new values.