Results for “put_cache_cleared”

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

Overview

APPS.FND_PROFILE is the foundational Oracle E-Business Suite PL/SQL package that implements the profile options framework. Profile options are the primary mechanism by which EBS stores and retrieves user-, responsibility-, application-, and site-level settings that control application behavior. Every EBS session relies on this package to resolve the effective value of a profile option for the current runtime context, whether that context is a Forms session, a concurrent program, an OAF page, or a background PL/SQL process.

The package is classified as OTHER in the ETRM metadata and is owned by the APPS schema with a VALID status in both 12.1.1 and 12.2.2. Its scope is essentially universal: the metadata records that it is referenced by 6,785 other packages, making it one of the most widely used public packages in the entire EBS codebase. It depends on the WF_EVENT_T workflow event type and standard SYS constructs, and it exposes 17 documented procedures and functions covering initialization, retrieval, persistence, and cache management of profile option values.

Key Procedures and Functions

• INITIALIZE and INITIALIZE_ORG_CONTEXT — Establish the runtime context (including Org context) against which subsequent profile lookups are resolved.
• GET and GET_SPECIFIC — Retrieve the effective value of a profile option for the current context; the SPECIFIC variant targets a precisely identified context.
• VALUE, VALUE_SPECIFIC, and VALUE_WNPS — Return profile values; VALUE_WNPS provides retrieval semantics intended for cases where a cached value is acceptable or no specific context is imposed.
• DEFINED — Indicates whether a profile option has been defined or has a value in the current context.
• PUT and PUTMULTIPLE — Set one or many profile option values in the session's profile cache.
• SAVE_USER and SAVE — Persist profile changes, with SAVE_USER handling the user-specific save path.
• DELETE — Remove a stored profile option value.
• BUMPCACHEVERSION_RF and PUT_CACHE_CLEARED — Manage profile cache versioning and invalidation so that cached values across sessions remain consistent.
• GET_ALL_TABLE_VALUES and GET_TABLE_VALUE — Resolve profile options whose allowed values are defined as a lookup table rather than a static list.

Tables Accessed

The package operates primarily against FND_PROFILE_OPTIONS, which stores the definitions, levels, and allowed values of profile options, and FND_USER, used to resolve user-level context. FND_NODES is referenced in multi-node or shared-configuration scenarios tied to cache versioning. WF_EVENT_T is used as the workflow event payload type for profile-related event propagation. The package also relies on DBMS_UTILITY and PLITBLM (the PL/SQL integer table type) for internal utility operations and collection handling.

Usage Notes

FND_PROFILE is invoked implicitly by virtually every EBS component: Forms triggers call GET and VALUE to resolve settings; concurrent programs and OAF controllers call the same APIs during runtime; and the Profile Options form in the System Administrator responsibility uses PUT, SAVE, and DELETE for administration. Because of its breadth, it is also called directly from custom PL/SQL to read values such as ORG_ID, USERNAME, or application-specific flags. Custom code should reuse the public APIs rather than query the underlying tables directly, and should be mindful of the profile cache, using BUMPCACHEVERSION_RF or PUT_CACHE_CLEARED when values are changed programmatically.