Results for “first_period_bill_amt”

7 results




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

Overview

APPS.OE_DELAYED_REQUESTS_UTIL is a utility package body in the Oracle Order Management (ONT) schema within Oracle E-Business Suite 12.1.1 and 12.2.2. As a UTIL-classified API, it does not expose a public transactional interface to external callers; instead it aggregates a large set of internal helper routines invoked during order import, order entry, and deferred processing flows. The package name reflects its origin: it supports delayed (deferred) request processing where work is queued and executed asynchronously rather than in the interactive user session.

The documented functionality spans sales credit validation, pricing validation, service and configuration item handling, RMA processing, hold management, and tax line derivation. The header comment in the source references version 120.23.12010000.4, dated 2008, indicating the package logic has been stable across the 12.1.1 and 12.2.2 releases with minimal structural change.

Key Procedures and Functions

The metadata documents 46 procedures and functions. The principal groups are described below.

Tables Accessed

The package reads and writes a defined set of APPS-synonym tables. Order data is concentrated in OE_ORDER_HEADERS, OE_ORDER_HEADERS_ALL, OE_ORDER_LINES, and OE_ORDER_LINES_ALL, which store the header and line records affected by validation and insertion routines. Acknowledgement processing uses OE_HEADER_ACKS and OE_LINE_ACKS, while OE_LINE_SETS supports line set grouping. Discount logic references OE_DISCOUNTS and OE_DISCOUNT_LINES. Hold management accesses OE_HOLD_SOURCES_ALL and FND_USER. Inventory interactions touch MTL_SYSTEM_ITEMS, MTL_LOT_NUMBERS, MTL_MATERIAL_TRANSACTIONS, and MTL_TRANSACTION_LOT_NUMBERS, primarily for RMA lot and serial handling.

Usage Notes

OE_DELAYED_REQUESTS_UTIL is referenced by eight other packages, confirming its role as a shared internal library rather than a directly called API. It is typically invoked from Order Management forms, order import concurrent programs, and RMA processing flows rather than from customer-written code. Customisations should avoid direct calls to these routines because the interface is not guaranteed stable across patches; the supported extension points remain the seeded ONT public APIs. Developers troubleshooting sales credit totals, fixed-price modifier validation, or deferred hold application can use the debug output emitted by OE_DEBUG_PUB to trace execution through this package.