Results for “process_requests_and_notify”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
OE_PORTAL_UTIL is a utility package in the Oracle Order Management (ONT) schema, owned by APPS and classified as a UTIL-type API. Its central purpose is to support the Oracle iStore / Customer Portal ordering flow, providing the server-side logic that backs order entry and order review pages presented to external or self-service users. Rather than exposing a full public business API, OE_PORTAL_UTIL acts as a convenience layer that retrieves, caches, and presents order header and line information in the shapes required by portal-facing interfaces, and then dispatches notifications when requests are processed.
The package is tightly coupled to the core Order Management infrastructure. Its documented dependencies include OE_ORDER_PUB and OE_ORDER_PVT (the primary order entry APIs), OE_HEADER_UTIL and OE_LINE_UTIL (header and line manipulation helpers), OE_ORDER_CACHE (caching of order structures), OE_GLOBALS, OE_MSG_PUB, OE_DEBUG_PUB, OE_ORDER_TYPES_V, OE_AK_ORDER_HEADERS_V, OE_OE_FORM_LINE, ONT_HEADER_DEF_UTIL, and the generic FND_API framework. It is not referenced by any other database object, confirming its role as a leaf-level consumer of the order APIs rather than a shared dependency.
Key Procedures and Functions
ETRM documents six procedures and functions within OE_PORTAL_UTIL:
- GET_VALUES — Retrieves a set of order attribute values, typically used to populate portal page fields from the underlying order structures.
- GET_HEADER — Returns the order header information for a given order, sourced from the header views and utility APIs.
- GET_LINE — Returns individual order line details, drawing on line utility logic.
- LINES — Returns the collection of lines associated with an order, supporting the multi-line display on portal pages.
- SET_HEADER_CACHE — Populates the order cache (via OE_ORDER_CACHE) so that repeated header access during a portal session avoids redundant database round-trips.
- PROCESS_REQUESTS_AND_NOTIFY — Processes pending order requests and triggers the appropriate notifications through OE_MSG_PUB, closing the loop between user submission and order status communication.
These routines are designed to be called together: a portal page loads header and line data, caches it, and then processes and notifies on submission.
Tables Accessed
The ETRM metadata does not enumerate base tables directly; instead, access is mediated through APPS synonyms and views. OE_PORTAL_UTIL references OE_AK_ORDER_HEADERS_V and OE_ORDER_TYPES_V for header and order type information, and OE_OE_FORM_LINE for form-style line retrieval. Header and line utility packages (OE_HEADER_UTIL, OE_LINE_UTIL) translate these reads into the OE_ORDER_HEADERS and OE_ORDER_LINES structures. No direct INSERT/UPDATE statements are documented, indicating that the package reads order data and delegates any write activity to the OE_ORDER_PUB/OE_ORDER_PVT layer.
Usage Notes
OE_PORTAL_UTIL is invoked from the Oracle iStore / Customer Portal application layer and from custom portal pages that need to display or submit Order Management data on behalf of a web user. It is not intended for direct ad-hoc SQL use. Because it depends on OE_ORDER_PUB, OE_ORDER_CACHE, and the FND_API error-handling framework, any custom code calling these routines must initialize the FND_API global variables and handle the standard return status and message stack.
The package is present and valid in both Oracle EBS 12.1.1 and 12.2.2, and is referenced by two other packages according to ETRM. When troubleshooting portal order display or notification issues, trace calls into PROCESS_REQUESTS_AND_NOTIFY and verify cache state set by SET_HEADER_CACHE, since stale or missing cache entries are a common cause of incorrect portal order presentation.
-
PACKAGE: APPS.OE_PORTAL_UTIL 12.2.2
-
PACKAGE: APPS.OE_PORTAL_UTIL 12.1.1
-
PACKAGE: APPS.OE_ORDER_PVT 12.1.1
-
PACKAGE: APPS.OE_ORDER_PVT 12.2.2