Results for “value_specific”

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

Overview

FND_PROFILE_SERVER is a server-side PL/SQL package body in the APPS schema that provides a wrapper layer over the core FND_PROFILE API. Its business function is to expose the standard Oracle E-Business Suite profile option mechanism to server-side code, allowing developers to read, test for the existence of, and permanently persist profile option values without calling FND_PROFILE directly. The package was introduced as part of the base Applications Foundation technology stack and its header dates to release 11.5, remaining valid and shipped in Oracle EBS 12.1.1 and 12.2.2. In the ETRM classification the package is registered as API classification OTHER, meaning it is a technology-layer utility rather than a business-facing concurrent program interface.

Key Procedures and Functions

Nine documented entry points make up the package interface:

• PUT — Sets a profile option to a supplied value for the current session only. The change is held in session state and is not written to the database.
• DEFINED — Returns a boolean indicating whether a profile option has been stored in the current session's profile state.
• GET — Retrieves the value of a named profile option into an output variable.
• VALUE — Returns the value of a profile option as a varchar2, using the profile cache for performance.
• VALUE_WNPS — Returns a profile option value "without package state," i.e. without writing to the profile cache. It is intended for use inside SQL SELECT statements, where the cached variant VALUE is not permitted because it mutates package state. It resolves from the cache if present, otherwise hits the database on every call, so it is slower than VALUE under repeated invocation.
• SAVE_USER — Permanently stores a profile option value to the database at the user level for the current user. This is the routine most relevant to the "save_user" search: it is the supported server-side mechanism for user-level profile persistence.
• SAVE — Persists a profile option value at the appropriate profile level hierarchy.
• GET_SPECIFIC — Retrieves a profile option value for a specific level/context combination rather than resolving the normal hierarchy.
• VALUE_SPECIFIC — Returns a profile option value as a varchar2 for a specific level/context, bypassing normal hierarchical resolution.

Tables Accessed

The ETRM metadata records no directly referenced tables via APPS synonyms for this package. This is expected: FND_PROFILE_SERVER delegates all data access to the underlying FND_PROFILE package, which owns and maintains the profile option cache and executes the DML against the Applications Foundation profile option tables (FND_PROFILE_OPTION_VALUES, FND_PROFILE_OPTIONS and related definition tables) when SAVE, SAVE_USER and the level-specific routines are invoked. Any read or write of persisted profile data therefore occurs indirectly through FND_PROFILE rather than through table references declared in this package body.

Usage Notes

FND_PROFILE_SERVER is typically invoked from server-side PL/SQL: Forms triggers and program units, concurrent program packages, workflow function activities, and custom database packages that need profile option values. The package itself is documented as being referenced by three other packages, confirming its role as a shared utility in the dependency chain. Developers should prefer VALUE over VALUE_WNPS except when the call must appear inside a SQL statement, and should use PUT for session-scoped temporary overrides versus SAVE or SAVE_USER for persistent changes. Because SAVE_USER writes data, it should be reserved for deliberate configuration updates; ad-hoc custom code that merely reads a profile should use GET or VALUE.