Search Results validate_carrier

Overview

WSH_UTIL_VALIDATE is a shared PL/SQL utility package owned by APPS within the Oracle E-Business Suite Shipping (WSH) module. It provides a centralized library of validation routines used throughout the order-to-ship lifecycle to verify that inbound reference data — organizations, locations, customers, items, units of measure, currencies, and carrier-related attributes — conforms to the values held in the EBS reference tables before downstream shipping transactions are processed. The package is declared with AUTHID CURRENT_USER, meaning its SQL executes under the privileges of the calling schema rather than as the definer, which is consistent with its role as an internal helper library invoked by other application code rather than by end users directly.

The ETRM classification for this object is OTHER, reflecting that it is not a published business API with a formal interface contract, but an internal utility package. Its significance is demonstrated by the fact that it is referenced by 43 other packages across the Shipping application, making it a foundational validation layer.

Key Procedures and Functions

The package exposes 50 documented procedures, each targeting a specific validation domain. The core reference-data validators are:

• VALIDATE_ORG — validates an organization identifier or code against the organization definitions view. Where both an ID and a code are supplied, the ID takes precedence.
• VALIDATE_LOCATION — validates a location identifier or code against the HR locations view.
• VALIDATE_LOOKUP — confirms that a code exists as a valid value in a specified lookup type.
• VALIDATE_CUSTOMER and VALIDATE_CONTACT — confirm customer accounts and contact roles against the Trading Community Architecture (HZ) tables.
• VALIDATE_SHIP_METHOD — the procedure most commonly associated with this package in search, validating a ship method code against the carrier service definitions. Ship method is a required attribute on delivery and shipment records, so this routine ensures the method is legitimate for the carrier in context.
• VALIDATE_CARRIER-related routines (VALIDATE_SHIP_METHOD, VALIDATE_FREIGHT_TERMS, VALIDATE_FOB) — verify transportation and commercial terms used on shipments.
• VALIDATE_QUANTITY, VALIDATE_NEGATIVE, VALIDATE_CURRENCY, VALIDATE_UOM — numeric, monetary, and unit-of-measure checks.
• VALIDATE_ITEM — confirms inventory items against the master item tables, including customer items.
• VALIDATE_USER, VALIDATE_BOOLEAN, VALIDATE_RELEASED_STATUS, VALIDATE_DELIVERY_NAME, VALIDATE_REPORT_SET, VALIDATE_LOADING_ORDER, VALIDATE_FLEXFIELDS — supporting checks for user identity, flag values, delivery naming, report configuration, loading sequence, and descriptive flexfield segments.

Tables Accessed

The package reads from a broad set of reference tables through APPS synonyms. Organization and inventory validation draws on MTL_PARAMETERS, MTL_SYSTEM_ITEMS, MTL_CUSTOMER_ITEMS, and MTL_UNITS_OF_MEASURE. Location validation uses HR_LOCATIONS_ALL and HR_LOCATIONS_ALL_TL. Customer and contact validation uses HZ_CUST_ACCOUNTS, HZ_CUST_ACCOUNT_ROLES, HZ_PARTY_SITES, and HZ_PARTY_SITE_USES. Carrier and transportation validation uses WSH_CARRIERS, WSH_CARRIER_SERVICES, and WSH_LOCATIONS, while delivery-name checks reference WSH_NEW_DELIVERIES. User validation references FND_USER. These are predominantly read operations used to confirm the existence and correctness of values supplied by callers.

Usage Notes

WSH_UTIL_VALIDATE is not intended to be called directly by end users. It is invoked programmatically by the 43 packages that reference it, and indirectly by Shipping forms (such as the ship-confirm and delivery forms) and concurrent programs that process shipping transactions. Custom code extending Oracle Shipping should call these procedures to obtain consistent validation behavior — for example, invoking VALIDATE_SHIP_METHOD before writing a delivery or shipment record — rather than duplicating lookup logic. Because the package is AUTHID CURRENT_USER, callers must have appropriate privileges on the underlying tables, and validation outcomes are returned through OUT parameters defined in each procedure's own signature.