Search Results g_binary_limit

Overview

OE_BULK_CACHE is an internal PL/SQL package in the Oracle Order Management (OM) module of Oracle E-Business Suite, residing in the APPS schema. Its primary business function is to act as a high-performance caching and lookup layer that supports the bulk order import and order entry processing flows. During bulk import of sales orders — whether through Order Import, the Order Management API (OE_ORDER_PUB), or the e-commerce/order capture stack — the application must repeatedly resolve reference entities such as customers, sites, items, price lists, salespersons, and tax attributes. Rather than re-querying the base tables each time, OE_BULK_CACHE provides procedures that load and hold these values so downstream logic can retrieve them efficiently.

The package is classified as API classification OTHER, indicating it is a supporting internal utility rather than a public, callable business API. It is referenced by ten other packages in the OM/Advanced Pricing technical stack. The most recent source header indicates maintenance through release 12.1.1 (header version 120.5.12010000.4), and the object remains documented in the 12.2.2 ETRM repository, where it is still used by the order capture and bulk import infrastructure.

Key Procedures and Functions

The package exposes seventeen documented procedures/functions that collectively load the reference data needed to build an order. The LOAD_SOLD_TO_SITE procedure — the object of the user's search — is one of the customer-site loaders, resolving the ship-to/sold-to customer site context for the order. The remaining loaders can be grouped as follows:

• Order and line classification: LOAD_ORDER_TYPE and LOAD_LINE_TYPE load the transactional order and line type definitions, including their processing constraints and defaulting rules.
• Pricing: LOAD_AGREEMENT and LOAD_PRICE_LIST load agreement and price list information used during pricing and list-price derivation.
• Item data: LOAD_ITEM loads system item attributes for the ordered item.
• Customer/site loaders: LOAD_SOLD_TO, LOAD_SOLD_TO_SITE, LOAD_SHIP_TO, LOAD_INVOICE_TO, LOAD_END_CUSTOMER, LOAD_END_CUSTOMER_SITE, and LOAD_PERSON load the various party roles and their sites — sold-to, ship-to, invoice-to, and end customer — as well as person information.
• Shipping and location: LOAD_SHIP_FROM and LOAD_LOC_INFO load the ship-from warehouse and location details.
• Sales and tax: LOAD_SALESREP loads salesperson assignments; LOAD_TAX_ATTRIBUTES loads tax-determining attributes.
• Credit: IS_CC_REQUIRED evaluates whether credit checking is required based on applicable credit check rules.

The source excerpt further documents a Get_Address procedure that delegates to the ECE trading partner address derivation API (ece_trading_partners_pub.ece_Get_Address_wrapper) to return formatted address components such as address lines, city, county, state, zip, province, country, and regions.

Tables Accessed

The package reads from several core reference tables, accessed through APPS synonyms. Customer and site data is sourced from HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES, and HZ_CUST_SITE_USES_ALL, which hold customer accounts, account sites, and site-use assignments. Party and location data is read from HZ_PARTIES, HZ_PARTY_SITES, HZ_LOCATIONS, and HZ_LOC_ASSIGNMENTS. Item information is drawn from MTL_SYSTEM_ITEMS and the key-flexfield view MTL_SYSTEM_ITEMS_KFV, with warehouse/parameter context from MTL_PARAMETERS. Organizational data is read from HR_ALL_ORGANIZATION_UNITS. Tax data comes from AR_VAT_TAX, and credit checking rules from OE_CREDIT_CHECK_RULES, which supports IS_CC_REQUIRED.

Usage Notes

OE_BULK_CACHE is not typically invoked directly by end users. It is consumed internally by Order Management forms, the Order Import concurrent program, and bulk order-processing APIs, and its procedures are called by the ten dependent packages referenced during order entry and import. Customizations that need to replicate bulk order behavior should favor the supported OE_ORDER_PUB APIs rather than calling OE_BULK_CACHE directly, since its signature and caching strategy are internal and subject to change between patch levels. When debugging customer-site resolution issues in bulk import, developers may enable OE_DEBUG_PUB output, as the package emits diagnostic messages at the debug level.