Results for “get_specific”

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

Overview

IBU_FNDPROFILE is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, retained in both the 12.1.1 and 12.2.2 releases with a documented status of VALID. It belongs to the Oracle iProcurement / iStore family of "IBU" (Internet Business Unit) components, which support the storefront and self-service purchasing modules. The package encapsulates the interaction between the user interface layer and the FND profile option infrastructure, which is the mechanism Oracle EBS uses to expose configurable, hierarchical application settings at Site, Application, Responsibility, and User levels. By wrapping profile-option retrieval and persistence in a single package, IBU components avoid embedding direct FND_PROFILE calls throughout their forms and PL/SQL code, keeping configuration access consistent and maintainable.

The ETRM classification for this package is OTHER, meaning it is not registered as a public or private API in the formal sense. It is an internal helper package rather than a published interface intended for customer extension.

Key Procedures and Functions

• GET_SPECIFIC — Retrieves the value of a specific profile option for the current runtime context (typically the logged-in user and responsibility). It provides the read side of the package's functionality, allowing calling code to obtain a targeted configuration setting without invoking the broader FND_PROFILE.VALUE interface directly.
• SAVE — Persists profile option values, providing the write side of the package. This supports programmatic updates where a component needs to record or refresh a configuration setting on behalf of the application rather than through the standard Profile Options form.

No parameter lists are documented in the ETRM metadata; the signatures must be confirmed by inspecting the package specification in the target instance.

Tables Accessed

The documented ETRM record lists no tables referenced through APPS synonyms. In practice, profile-option functionality of this nature operates against the FND_PROFILE_OPTION_VALUES and FND_PROFILE_OPTIONS tables, typically through the supported FND_PROFILE API rather than direct DML. Because no base-table dependencies are documented, integrators should assume that all persistence is delegated to the FND profile infrastructure and that direct table access is not part of the supported behavior.

Usage Notes

IBU_FNDPROFILE references the SYS.STANDARD package, confirming that it uses standard PL/SQL language constructs. The documented dependency list shows no other APPS packages referencing IBU_FNDPROFILE, and the package itself is documented as referenced by zero other packages. This indicates it is a leaf-level utility: invoked directly by forms, Java/OC4J (or in 12.2.2, the WebLogic-hosted) middle-tier code, or bespoke customizations rather than being called by other shared PL/SQL APIs.

Typical invocation scenarios include iProcurement or iStore form logic that must read a profile setting at runtime, and custom extensions that need to set a profile value for a session. Because the package is classified as OTHER and is undocumented as an API, custom code that calls it should be treated as relying on an unsupported internal interface: the package may be changed or removed by Oracle patches without notice. Customers extending EBS should prefer the documented FND_PROFILE.GET and FND_PROFILE.PUT public APIs unless a specific IBU behavior requires this wrapper.