Search Results load_order_header

Overview

The APPS.OE_ORDER_CACHE package body is a private utility package within the Oracle Order Management module of Oracle E-Business Suite. Its documented function is to serve as an in-memory caching mechanism for reference data required during order capture and order maintenance operations. Rather than repeatedly querying configuration and setup tables such as payment terms, sales representatives, order types, line types, price lists, and item attributes, the Order Management forms and APIs invoke OE_ORDER_CACHE to populate and retain these values for the duration of a session. This reduces redundant database round-trips and improves responsiveness in the Order Organizer, Sales Order form, and related order entry flows. The ETRM metadata classifies the package as OTHER with a VALID status in the APPS schema, and it is documented as referenced by 81 other database objects, confirming its role as a foundational dependency in the order capture stack. It is not, however, referenced by any object outside the Order Management and pricing dependency graph documented by ETRM.

Key Procedures and Functions

The package exposes 48 documented procedures and functions, the majority of which follow a LOAD_ naming convention indicating cache population. Documented examples include LOAD_PAYMENT_TERM and LOAD_SALESREP_REC, which seed payment terms and sales representative records respectively; LOAD_ORDER_TYPE and LOAD_LINE_TYPE, which cache order and line type definitions used to govern order processing behavior; LOAD_ITEM and LOAD_ITEM_COST, which retrieve item and cost attributes from inventory and costing tables; and LOAD_PRICE_LIST, which caches pricing information for order pricing calculations. Organizational context procedures include LOAD_SHIP_TO_ORG, LOAD_INVOICE_TO_ORG, LOAD_DELIVER_TO_ORG, and LOAD_SOLD_TO_ORG, each loading the relevant party or organization record for a transaction. LOAD_SET_OF_BOOKS, LOAD_SET, and LOAD_AGREEMENT populate financial and agreement reference data. Structural order data is handled by LOAD_ORDER_HEADER, LOAD_TOP_MODEL_LINE, LOAD_HEADER_DISCOUNT, and LOAD_LINE_DISCOUNT. CLEAR_ALL and CLEAR_ORDER_TYPE provide cache invalidation and reset behavior. No parameter signatures are documented in the ETRM metadata, so specific inputs are not reproduced here.

Tables Accessed

Documented table references resolved through APPS synonyms include OE_ORDER_HEADERS_ALL and OE_ORDER_LINES, the core transactional order tables loaded during order header and line caching. Configuration and setup sources include MTL_SYSTEM_ITEMS and MTL_PARAMETERS for item and inventory organization attributes, CST_ITEM_COSTS for item cost retrieval, and QP_LIST_LINES for price list detail. Customer and party data is sourced from HZ_CUSTOMER_PROFILES and HZ_CUST_ACCT_SITES_ALL. Terms and receivables references include RA_CUST_TRX_TYPES, RA_CUST_TRX_TYPES_ALL, and the OE_RA_TERMS_V view. Discount processing draws on OE_DISCOUNTS and OE_DISCOUNT_LINES, while OE_PRICE_BREAK_LINES and OE_SETS support pricing and set configuration. FND_DESCR_FLEX_COLUMN_USAGES is referenced for descriptive flexfield column metadata. The package additionally depends on numerous Order Management packages and views, including OE_ORDER_PUB, OE_HEADER_UTIL, OE_LINE_UTIL, OE_GLOBALS, FND_API, OE_MSG_PUB, and OE_INVOICE_PUB.

Usage Notes

OE_ORDER_CACHE is an internal implementation package rather than a public API. It is typically invoked indirectly by the Order Management forms, the OE_ORDER_PUB public APIs, and concurrent programs that process or validate orders, which call the LOAD_ procedures to build session state before executing order logic. Its dependency on OE_ORDER_CACHE itself and on OE_GLOBALS indicates session-scoped caching behavior. Custom extensions should not call the LOAD_ procedures directly unless mirroring Oracle's internal order processing sequence, as cache coherence is maintained by the standard Order Management code paths. Cache reset is available through CLEAR_ALL and CLEAR_ORDER_TYPE, which are useful when setup or reference data changes mid-session. Because the package is documented as not referenced by any database object outside the APPS dependency graph, its lifecycle is entirely governed by Oracle's Order Management application logic.