Search Results load_top_model_line

Overview

APPS.OE_ORDER_CACHE is an internal Order Management utility package that maintains a session-level or call-level cache of reference data used throughout the order capture and order import process. Rather than repeatedly querying foundational setup tables during order entry, order import, or Order Management API calls, the package loads the relevant rows into PL/SQL records and collection structures that consuming code can reference cheaply. This pattern reduces redundant SQL execution and improves performance on high-volume order flows, particularly where many lines are processed against the same header, customer, item, or price list.

The package defines several record and collection types in its specification, including Enforce_list_price_rec_type, Order_Type_Rec_Type, and Tax_Code_Cach (a tax code cache), which reflect the categories of data the package retains: order types, pricing enforcement flags, tax determination attributes, and related order defaults. The presence of procedure LOAD_TOP_MODEL_LINE confirms that the cache additionally supports configured item and top-model processing, so that model structures do not require repeated retrieval during configuration.

Key Procedures and Functions

The package exposes a set of LOAD_* procedures that populate the cache from specific source tables, and a pair of CLEAR_* procedures that reset cached state.

• LOAD_ORDER_TYPE — caches order type attributes such as invoicing and accounting rules, price list, shipping and freight defaults, and order numbering source, as reflected in the Order_Type_Rec_Type structure.
• LOAD_LINE_TYPE — caches line type definitions used to derive line-level processing behavior and pricing enforcement.
• LOAD_PAYMENT_TERM — caches payment term data applied to the order or customer.
• LOAD_SALESREP_REC — caches salesperson information associated with the order or line.
• LOAD_AGREEMENT — caches agreement and agreement type information used during pricing and order qualification.
• LOAD_SOLD_TO_ORG, LOAD_SHIP_TO_ORG, LOAD_INVOICE_TO_ORG, LOAD_DELIVER_TO_ORG — cache customer site and account data for the respective party roles, drawing on customer and site tables so that address and profile lookups are not repeated.
• LOAD_PRICE_LIST — caches price list header information applied to the order.
• LOAD_SET_OF_BOOKS — caches the set of books relevant to the operating unit and transaction context.
• LOAD_ITEM and LOAD_ITEM_COST — cache inventory item attributes and item cost information, supporting pricing and margin calculations.
• LOAD_ORDER_HEADER — caches the order header record for the transaction in progress.
• LOAD_HEADER_DISCOUNT and LOAD_LINE_DISCOUNT — cache discount definitions applicable at the header and line levels, including price break line information.
• LOAD_TOP_MODEL_LINE — caches top model line data for configured items, enabling model and option class processing without repeated queries against order line tables.
• LOAD_SET — caches set information from the OE_SETS table.
• CLEAR_ALL and CLEAR_ORDER_TYPE — reset the entire cache or only the order type portion, allowing callers to control cache lifecycle.

Tables Accessed

The package reads and, in some cases, writes through APPS synonyms. Order data is drawn from OE_ORDER_HEADERS_ALL and OE_ORDER_LINES. Discount information comes from OE_DISCOUNTS, OE_DISCOUNT_LINES, OE_PRICE_BREAK_LINES, and QP_LIST_LINES. Set data is read from OE_SETS. Item and cost information is retrieved from MTL_SYSTEM_ITEMS, MTL_PARAMETERS, and CST_ITEM_COSTS. Customer and site data is sourced from HZ_CUST_ACCT_SITES_ALL and HZ_CUSTOMER_PROFILES. Transaction type and accounting rule data comes from RA_CUST_TRX_TYPES and RA_CUST_TRX_TYPES_ALL. Key flexfield usage information is read from FND_DESCR_FLEX_COLUMN_USAGES.

Usage Notes

OE_ORDER_CACHE is not a public API. It is invoked internally by Order Management forms, by the Order Import concurrent program, and by other Order Management packages that need repeatable, low-cost access to setup and transaction data. According to the documented metadata, it is referenced by 81 other packages, which underscores its role as a shared internal facility rather than a callable business interface. Custom code should not call these procedures directly, because the cache structures and lifecycle are tightly coupled to Oracle's own processing and are subject to change across patches and releases.