Search Results wsh_document_number_s




Overview
Explore in AI Chat

Overview

The APPS.WSH_EXTERNAL_INTERFACE_SV package body is a server-side PL/SQL component that forms part of the Oracle Warehouse Management (WSH) external integration layer. Its principal business function is to support the validation and event-raising activities that occur when external systems, trading partners, or third-party logistics providers exchange shipping and delivery data with Oracle E-Business Suite. The package acts as a service-layer utility, coupling validation logic for items and ship-to addresses with the ability to raise business events through the Workflow event subsystem. It is classified under the API type "OTHER" and is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2. Its dependents include references into foundational EBS frameworks such as FND_API, FND_GLOBAL, FND_MESSAGE, and WF_EVENT, indicating that it conforms to standard EBS API error-handling, messaging, and workflow event conventions.

Key Procedures and Functions

The ETRM metadata documents four procedures and functions within this package body. Each serves a discrete validation or notification role within the external shipping interface:

  • GET_WAREHOUSE_TYPE — Resolves the type or classification of a warehouse, drawing on the inventory organization and parameter configuration stored in MTL_PARAMETERS. This information is used to determine the appropriate handling and validation path for the warehouse involved in an external interface transaction.
  • RAISE_EVENT — Publishes a business event through the Workflow event framework (WF_EVENT, WF_CORE, WF_PARAMETER_LIST_T). This allows external integration scenarios to signal downstream subscribers that a qualifying shipping activity, such as a delivery or interface event, has occurred.
  • VALIDATE_ITEM — Verifies that a specified item is valid and available for the shipping context, using the item master view MTL_SYSTEM_ITEMS_KFV and inventory parameters. This guards against invalid item references entering the external interface.
  • VALIDATE_SHIP_TO — Confirms the validity of a ship-to party, customer account, and site by combining data from the Oracle Receivables and Trading Community Model tables (HZ_PARTIES, HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, HZ_LOCATIONS, HZ_PARTY_SITES). This ensures that ship-to information received from external sources maps to a genuine, active customer address.

Tables Accessed

The package reads from a broad set of EBS base and interface tables through APPS synonyms. Customer and address validation relies on the HZ schema objects, including HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_RELATE_ALL, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, HZ_LOCATIONS, HZ_PARTIES, and HZ_PARTY_SITES. Item validation depends on MTL_PARAMETERS and MTL_SYSTEM_ITEMS_KFV. Carrier-related data is drawn from WSH_CARRIERS and WSH_CARRIER_SERVICES. Delivery and document context is obtained from WSH_DELIVERY_DETAILS, the documented WSH_DOCUMENT_NUMBER_S sequence — the object referenced in the originating search term — and WSH_LOCATIONS. Collectively these accesses support the package's role as a validator and event generator rather than as a data-entry mechanism.

Usage Notes

WSH_EXTERNAL_INTERFACE_SV is not a standalone user-facing program; it is a supporting service package invoked by other WSH packages, of which 24 are documented as referencing it. It is typically called from external shipping integration flows, outbound and inbound interface processing, and custom extensions that need standardized item, ship-to, and warehouse validation before external shipping transactions are accepted. Because it participates in workflow event delivery, it may also be triggered from workflow-enabled processes or concurrent programs that subscribe to or publish WSH events. Oracle's metadata notes that the package body is not referenced by any other standalone database object beyond the packaged callers listed, confirming its role as a downstream utility within the WSH external interface architecture. Developers extending or debugging external shipping interfaces should treat it as a validation and notification service, invoking its members only through the documented calling packages rather than directly.