Search Results wsh_itm_vendor_services




Overview
Explore in AI Chat

Overview

The WSH_ITM_VENDOR_SERVICES table is a core data structure within the Oracle E-Business Suite Shipping Execution (WSH) module, specifically designed to support integration with partner In-Transit Management (ITM) applications. Its primary role is to serve as a master repository for the specific services offered by external logistics vendors or partners. This table enables the system to model and manage the discrete capabilities—such as real-time tracking, proof of delivery, or rate shopping—that a third-party vendor's system provides. By maintaining this catalog of available services, Oracle EBS can configure and execute precise electronic communications and data exchanges with partner systems, forming a critical component of the extended logistics and supply chain integration framework.

Key Information Stored

While the provided ETRM metadata does not list individual columns, the documented primary and foreign key relationships define its essential structure. The table is uniquely identified by the VENDOR_SERVICE_ID primary key. A critical foreign key, VENDOR_ID, links each service record to its parent vendor in the WSH_ITM_VENDORS table, establishing which partner provides the service. Typical columns in such a table would include SERVICE_CODE and SERVICE_NAME to identify the type of offering (e.g., "TRACKING," "RATES"), along with descriptive columns and status flags (e.g., ENABLED_FLAG) to control active usage. The table acts as the central hub from which detailed service configurations, such as parameters and communication preferences, are defined.

Common Use Cases and Queries

This table is primarily accessed during the setup and operational phases of ITM integrations. A common use case is generating a list of all active services for a specific vendor to configure inbound or outbound interfaces. For reporting, administrators may query the table to audit vendor capabilities. A typical SQL pattern involves joining to the vendor master table:

  • SELECT v.VENDOR_NAME, s.* FROM WSH_ITM_VENDOR_SERVICES s, WSH_ITM_VENDORS v WHERE s.VENDOR_ID = v.VENDOR_ID AND s.ENABLED_FLAG = 'Y';

Another critical operational use case is during transaction processing, where the system must determine if a vendor supports a particular service (like shipment status update) before initiating an API call to the external system, often queried by a service code.

Related Objects

The WSH_ITM_VENDOR_SERVICES table sits at the center of a key relationship hierarchy within the ITM integration schema, as confirmed by the ETRM metadata.

  • Parent Reference: The table references WSH_ITM_VENDORS via the VENDOR_ID column, linking a service to its provider.
  • Child Dependencies: Three key tables reference WSH_ITM_VENDOR_SERVICES via its primary key (VENDOR_SERVICE_ID):

This structure indicates that WSH_ITM_VENDOR_SERVICES is a mandatory setup step; a service must be defined here before its detailed parameters, preferences, or communication stylesheets can be configured.