Search Results oe_profile




Overview
Explore in AI Chat

Overview

The APPS.OE_PROFILE package body is a foundational utility within the Oracle Order Management (OM) module of Oracle E-Business Suite, present and valid in both release 12.1.1 and 12.2.2. Its principal responsibility is to centralize the retrieval, caching, and resolution of Order Management system profile option values that govern the behavior of order entry, pricing, scheduling, and fulfillment processes.

Rather than requiring every OM program to query profile options individually, OE_PROFILE provides a controlled interface that interprets profile settings against a specific operating context, such as an operating unit, responsibility, user, or organization. This abstraction ensures consistent interpretation of configuration across the order-to-cash flow and reduces redundant calls to the underlying profile infrastructure. The ETRM metadata classifies this package as an OTHER API, reflecting its role as an internal supporting utility rather than a public integration interface.

Key Procedures and Functions

The package body exposes nine documented procedures and functions, organized around two themes: direct profile retrieval and cached context handling.

  • GET — Primary entry point for retrieving an Order Management profile option value; it encapsulates the logic used throughout the module to resolve configuration settings.
  • VALUE — Returns the value of a specified profile option, typically applying defaulting and context resolution rules.
  • VALUE_WNPS — A specialized variant of VALUE; the suffix indicating handling for a specific profile scenario, used where standard defaulting behavior must be adjusted.
  • VALUE_SPECIFIC — Retrieves a profile value for an explicitly supplied context rather than relying on the ambient runtime context.
  • GET_CACHED_CONTEXT — Returns the currently cached context information maintained by the package for performance optimization.
  • PUT_CACHED_CONTEXT — Establishes or refreshes the cached context used by subsequent retrieval calls.
  • GET_CACHED_PROFILE_FOR_CONTEXT — Retrieves a previously cached profile value for a designated context, avoiding repeated resolution overhead.
  • PUT_CACHED_PROFILE_FOR_CONTEXT — Stores a resolved profile value against a context so that later lookups are served from the cache.

Tables Accessed

The package body references three database objects through APPS synonyms:

  • OE_ORDER_HEADERS_ALL — The core order header table; accessed to support context determination and profile resolution tied to specific orders.
  • OE_ORDER_LINES_ALL — The order line table; referenced for line-level context and attribute-driven profile behavior.
  • PLITBLM — A standard Oracle-supplied table-type utility used internally for PL/SQL collection handling.

The package additionally depends on a substantial set of OM and foundation packages, including FND_API, FND_PROFILE, OE_DEBUG_PUB, OE_GLOBALS, OE_INSTALL, OE_MSG_PUB, OE_SYS_PARAMETERS, WF_ENGINE, and the OE_PROFILE specification itself. These dependencies confirm its position as a low-level configuration service layered above the Oracle Application Object Library and Workflow engines.

Usage Notes

OE_PROFILE is invoked indirectly by a large number of OM components; the metadata records that it is referenced by 57 other packages, while it is not itself referenced by any database object, confirming its role as a leaf-level utility. It is typically called from Order Management forms, concurrent programs, and workflow activities whenever a profile-governed decision is required. Custom extensions and integrations that need to honor the same profile semantics as standard OM functionality should call OE_PROFILE rather than querying FND_PROFILE directly, ensuring consistent context handling and benefiting from its caching mechanisms. Because cached context entries are session-scoped and can become stale if profile options change mid-session, callers should refresh context after significant configuration changes.