Search Results oe_delayed_requests_util




Overview
Explore in AI Chat

Overview

OE_DELAYED_REQUESTS_UTIL is a utility package in the APPS schema of Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Oracle Order Management (OM) module and is classified under the ETRM (E-Business Suite Technical Reference Manual) as a UTIL-type API. In that taxonomy, utility packages provide low-level helper logic that supports higher-level public APIs, rather than exposing a user-facing or fully validated business interface of their own.

The package supports delayed request processing within Order Management, including service credit (SCREDIT) handling, hold management, and order line credit validation. Its procedures and functions centralize reusable processing that other OM components — particularly OE_DELAYED_REQUESTS_PVT and the order/lines utilities — rely on when an order or order line has been captured but whose dependent processing is deferred.

Key Procedures and Functions

According to the documented ETRM metadata, the package contains 46 procedures and functions. Representative entries include:

Parameter lists are not published in the ETRM excerpt, so signatures should always be confirmed against the live package specification before direct invocation.

Tables Accessed

The package reads and writes through APPS synonyms of the following base tables:

Usage Notes

OE_DELAYED_REQUESTS_UTIL is an internal helper, not a standalone public API. It depends on FND_API, OE_DELAYED_REQUESTS_PVT, OE_HOLD_SOURCES_ALL, and OE_ORDER_PUB, and is itself referenced by OE_DELAYED_REQUESTS_PVT, OE_HEADER_UTIL, OE_LINE_UTIL, OE_VALIDATE_LINE_SCREDIT, and OM_TAX_UTIL — eight referring packages in total. Invocation therefore typically flows indirectly: delayed request processing, order entry forms, hold application flows, and service credit validation routines reach these procedures through the public Order Management APIs (notably OE_ORDER_PUB). Customizations should prefer those supported entry points; direct calls should be limited to extension logic that mirrors an existing internal call path and must be re-tested against both 12.1.1 and 12.2.2, since utility packages are not covered by Oracle's compatibility guarantees.