Search Results validate_bill_to

Overview

The APPS.OE_BULK_PROCESS_HEADER package is an internal Order Management validation and derivation library used by the Oracle E-Business Suite bulk import (Order Import) infrastructure. Its principal business function is to centralize the cross-attribute and referential validation logic that must be applied to order header records before those records are accepted into the order transaction tables. Rather than requiring each calling program to reimplement these rules, the package exposes a set of Boolean-returning validation functions that Order Import and related header-processing routines invoke during the import of staged order data.

The package is defined in the source file OEBLHDRS.pls and belongs to the broader OE_BULK family of packages that support high-volume order creation. In the 12.1.1 and 12.2.2 releases the package carries an API classification of OTHER, indicating it is not a published public API but an internal implementation unit. It is referenced by two other packages in the Order Management schema, confirming its role as a shared validation service rather than an entry point.

Key Procedures and Functions

The documented interface comprises sixteen procedures and functions. The validation functions return BOOLEAN and are organized around the major header-level entities of an order:

• VALID_TAX_EXEMPT_REASON — Verifies that a supplied tax exemption reason code is valid and usable for the order context.
• VALIDATE_AGREEMENT — Confirms that an agreement (blanket sales agreement) is consistent with the pricing date, price list, and sold-to customer supplied on the header.
• VALIDATE_PRICE_LIST — Checks that a price list is valid for the given currency and pricing date, with an option controlling whether pricing is calculated.
• VALIDATE_BILL_TO, VALIDATE_SHIP_TO, VALIDATE_DELIVER_TO, VALIDATE_SOLD_TO_SITE — Validate the relationships between the sold-to party and the respective bill-to, ship-to, deliver-to, and sold-to site-use records, ensuring the chosen site belongs to the correct customer hierarchy.
• VALIDATE_SITE_CONTACT — Confirms that a contact is associated with the supplied site use.
• GET_FREIGHT_CARRIER — Derives or returns the applicable freight carrier for a shipment, consulting carrier and carrier-service configuration. This is the function most frequently sought by users researching freight carrier derivation logic.
• VALIDATE_END_CUSTOMER, VALIDATE_END_CUSTOMER_CONTACT, VALIDATE_END_CUSTOMER_SITE_USE — Validate the end customer party, its contacts, and its site uses.
• VALIDATE_IB_OWNER, VALIDATE_IB_INST_LOC, VALIDATE_IB_CURRENT_LOCATION — Support installe d-base validations for owners, installed locations, and current locations.
• ENTITY — A utility member associated with the package's internal entity handling.

Tables Accessed

Through APPS synonyms the package reads and, where appropriate, writes the following tables:

• HZ_CUST_ACCOUNTS, HZ_CUST_ACCOUNTS_ALL, HZ_CUST_ACCOUNT_ROLES, HZ_CUST_ACCT_RELATE — Customer account master, role, and relationship data used by the sold-to, bill-to, ship-to and end-customer validations.
• HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, HZ_PARTY_SITES — Site and site-use records that underpin the address and contact checks.
• WSH_CARRIERS, WSH_CARRIER_SERVICES, WSH_CARRIER_SHIP_METHODS, WSH_ORG_CARRIER_SERVICES — Shipping execution carrier and service configuration consulted by GET_FREIGHT_CARRIER.
• OE_HEADERS_IFACE_ALL — The Order Import header interface table from which staged header data is read and validated.
• PLITBLM — A PL/SQL index-by table type synonym used for bulk collections.

Usage Notes

OE_BULK_PROCESS_HEADER is invoked internally during Order Import processing, typically when header records are read from OE_HEADERS_IFACE_ALL and passed through validation before insertion into OE_ORDER_HEADERS_ALL. It is not registered as a concurrent program and has no form-level user interface of its own; users interact with it indirectly through the Order Import concurrent request and through Order Management forms that trigger header validation.

Because the package is classified as OTHER and is not a published API, custom code should not call it directly. Oracle reserves the right to change its signature between releases. Developers requiring freight carrier or customer-site validation behavior are advised to use the supported public APIs in the Order Management and Trading Community architecture rather than relying on this internal package.