Search Results get_warehouse_type

Overview

WSH_EXTERNAL_INTERFACE_SV is a public PL/SQL package in the Oracle EBS Shipping (WSH) module, owned by the APPS schema and declared with AUTHID CURRENT_USER. It functions as an external-facing server-side validation and integration layer for Shipping data. Its primary purpose is to expose reusable validation utilities that external systems, third-party logistics integrations, and custom extensions can call when pushing or validating shipping-related data — most notably item and ship-to address validation, warehouse type resolution, and event raising against the transaction history model.

Consistent with its "SV" (server validation) naming convention, the package encapsulates business validation logic that would otherwise need to be duplicated across interfaces. It is classified under API classification OTHER in the ETRM repository and is referenced by 24 other packages, indicating it is a broadly reused dependency within the Shipping application family rather than a standalone entry point. The package header dates from the 11i/12.0 era ($Header: WSHEXINS.pls 120.1.12010000.1) but remains documented and active in the 12.1.1 / 12.2.2 code line.

Key Procedures and Functions

• GET_WAREHOUSE_TYPE — A function returning the warehouse type classification for a given organization. It accepts an organization identifier along with optional delivery, delivery detail, carrier, and ship method context, and returns the resolved warehouse type while setting a return status. It supports conditional message display.
• RAISE_EVENT — A procedure that writes or raises an event using a transaction history record structure, together with a CBOD (Change-Based Order Data / business object document) status. It propagates an IN OUT return status to the caller.
• VALIDATE_ITEM — A procedure that validates an inventory item identified by concatenated key flexfield segments within a given organization, returning the resolved inventory item ID and a return status.
• VALIDATE_SHIP_TO — A procedure that validates a ship-to address combination (customer name plus location) and returns the corresponding customer ID, location ID, and site use ID. It accepts a site use code defaulting to 'SHIP_TO' and an optional operating unit (org_id), enabling callers to confirm or resolve a valid ship-to destination.

Tables Accessed

The package resolves customer and site data through the Trading Community Architecture (TCA) model. It reads HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_RELATE_ALL, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, HZ_PARTIES, HZ_PARTY_SITES, and HZ_LOCATIONS to validate ship-to combinations and derive customer, location, and site use identifiers. MTL_PARAMETERS and MTL_SYSTEM_ITEMS_KFV support warehouse type resolution and item validation against concatenated segments. WSH_CARRIERS and WSH_CARRIER_SERVICES provide carrier and service context for warehouse type logic. WSH_DELIVERY_DETAILS, WSH_LOCATIONS, and WSH_DOCUMENT_NUMBER_S supply delivery and location context, while WF_PARMETER_LIST_T (WF_PARAMETER_LIST_T) supports event parameter handling used by RAISE_EVENT.

Usage Notes

WSH_EXTERNAL_INTERFACE_SV is typically invoked from custom PL/SQL interfaces that import or validate shipping data from external systems, and from other Shipping packages within the application. VALIDATE_SHIP_TO and VALIDATE_ITEM are the most commonly called routines for pre-import data cleansing, since they translate human-readable key flexfield or name/location inputs into surrogate IDs required by downstream shipping APIs.

Callers should always inspect the returned status variables rather than assuming success, and should treat the package as a read-oriented validation service. Because it uses AUTHID CURRENT_USER, privileges are resolved against the invoking schema, and grants must be managed accordingly. The package is generally not invoked through a standard concurrent program or form directly; it serves as a programmatic building block referenced by the broader Shipping integration framework.