Search Results load_ship_from

Overview

The APPS.OE_BULK_CACHE package is an internal Oracle Order Management (OM) caching and data-loading utility that supports high-volume, bulk order entry operations within Oracle E-Business Suite 12.1.1 and 12.2.2. Its principal business role is to reduce the number of repetitive, expensive database round-trips required when validating and populating the many reference entities referenced during order capture and order import processing.

At its foundation, the package declares strongly typed PL/SQL record and table types — notably Order_Type_Rec_Type, Line_Type_Rec_Type, and Agreement_Rec_Type — that mirror the columns of key Order Management setup entities. The Order_Type_Rec_Type record, for example, encapsulates order type attributes such as order_type_id, name, order_category_code, default_attributes (defaulted to 'N'), quick_cr_check_flag (also defaulted to 'N'), cust_trx_type_id, and numerous pricing, shipping, and tax-related codes. These types are the vehicle by which setup data is bulk-fetched into PL/SQL memory and made available to callers without repeated queries against base tables. The package is classified under ETRM as an OTHER API rather than a public interfaces API, signalling that it is intended for internal use by Oracle's own Order Management code paths.

Key Procedures and Functions

The package exposes 17 documented procedures and functions, each acting as a loader that bulk-fetches or caches a specific entity into the package's in-memory structures. The loaders fall into several functional groupings.

• Order setup loaders: LOAD_ORDER_TYPE and LOAD_LINE_TYPE cache order type and line type definitions, including their associated defaults, category codes, and transaction type links.
• Agreement and pricing loaders: LOAD_AGREEMENT and LOAD_PRICE_LIST retrieve agreement and price list data used in pricing and order qualification logic.
• Party and customer loaders: LOAD_SOLD_TO, LOAD_SOLD_TO_SITE, LOAD_SHIP_TO, LOAD_INVOICE_TO, LOAD_END_CUSTOMER, LOAD_END_CUSTOMER_SITE, LOAD_SALESREP, and LOAD_PERSON cache the customer, site, contact, and sales representative entities referenced during order entry and validation.
• Item and location loaders: LOAD_ITEM, LOAD_SHIP_FROM, and LOAD_LOC_INFO cache inventory item definitions, shipping warehouse organizations, and location details.
• Tax loading: LOAD_TAX_ATTRIBUTES retrieves tax configuration attributes used in tax determination logic.
• Credit check utility: IS_CC_REQUIRED evaluates whether a credit check is required, referencing credit check rules cached or queried by the package.

Together these loaders populate the package's cache structures so that validation and defaulting logic can consult local memory rather than repeatedly querying reference tables.

Tables Accessed

The package accesses its documented reference tables through APPS synonyms. Customer and party data are drawn from HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES, HZ_CUST_SITE_USES_ALL, HZ_PARTIES, and HZ_PARTY_SITES. Location data is sourced from HZ_LOCATIONS and HZ_LOC_ASSIGNMENTS. Inventory item information is retrieved from MTL_SYSTEM_ITEMS, with the key-flexfield view MTL_SYSTEM_ITEMS_KFV providing concatenated item identification, while MTL_PARAMETERS supplies inventory organization parameters. Organization unit assignments come from HR_ALL_ORGANIZATION_UNITS. Tax configuration is drawn from AR_VAT_TAX. Credit check rules are retrieved from OE_CREDIT_CHECK_RULES to support IS_CC_REQUIRED. These tables collectively represent the Order Management reference and setup data that the cache is designed to hold.

Usage Notes

OE_BULK_CACHE is an internal utility and is not intended as a public API for customer extensions. It is referenced by 10 other packages within the Oracle Order Management schema, which typically call its loaders to prime the cache before processing batches of order lines — for example, during Order Import, high-volume order entry, or bulk validation routines where avoiding redundant per-line lookups is essential to performance.

Because the package maintains state in package-level PL/SQL memory that is scoped to a database session, callers must load the relevant entity types before invoking dependent logic, and cached values remain valid only until the session ends or the cache is refreshed. Customizations should not invoke these procedures directly unless mirroring Oracle's own usage pattern, since the cache structures and loader contracts are internal and may change between releases. Functional users encounter the package's effects indirectly, through the accelerated performance of bulk order capture, credit checking, and order import concurrent programs rather than through any direct interface.