Search Results wsh_itm_vendor_stylesheets




Overview
Explore in AI Chat

Overview

The WSH_ITM_VENDOR_STYLESHEETS table is a core data object within the Oracle E-Business Suite Shipping Execution (WSH) module, specifically supporting the Inbound Transportation Management (ITM) functionality. Its primary role is to manage the XML transformation logic for electronic communication with external carrier or vendor systems. When a vendor does not natively support the standard Oracle ITM XML API but Oracle maintains a specialized integration, this table stores the names of the XSL (Extensible Stylesheet Language) stylesheets. These stylesheets are applied to transform Oracle's standard ITM XML messages into a vendor-specific request format and, conversely, to transform the vendor's proprietary response format back into a structure Oracle can process. This enables seamless data exchange for functions like shipment tendering and status updates within the transportation lifecycle.

Key Information Stored

The table's structure is designed to link transformation rules to specific vendor services. The most critical column is VENDOR_SERVICE_ID, which serves as the primary key and a foreign key to the WSH_ITM_VENDOR_SERVICES table, uniquely identifying the carrier service. The table centrally stores the names of the two essential XSL stylesheets: one for transforming outbound requests to the vendor and another for processing inbound responses from the vendor. While the specific column names for the stylesheets are not detailed in the provided excerpt, they would typically be named to clearly indicate their purpose, such as REQUEST_STYLESHEET and RESPONSE_STYLESHEET. The presence of a record for a given VENDOR_SERVICE_ID indicates that a custom integration, rather than the standard ITM API, is required for that carrier service.

Common Use Cases and Queries

The primary use case is the configuration and troubleshooting of EDI or XML-based integrations with transportation carriers. An implementation consultant would query this table to verify the stylesheets assigned to a vendor service during setup. A common support query would involve joining to the vendor services table to get a full list of configured integrations. For example:

  • SELECT vs.vendor_service_code, vs.vendor_id, vst.request_stylesheet, vst.response_stylesheet FROM wsh_itm_vendor_stylesheets vst, wsh_itm_vendor_services vs WHERE vst.vendor_service_id = vs.vendor_service_id;

This data is critical during the shipment tendering process. When a user creates a delivery and selects a rated carrier service, the Shipping Execution engine consults this table. If a matching VENDOR_SERVICE_ID is found, the corresponding request stylesheet is applied to the shipment data to generate a vendor-compliant transmission.

Related Objects

The table has a direct and essential relationship with the WSH_ITM_VENDOR_SERVICES table, enforced by a foreign key constraint. WSH_ITM_VENDOR_SERVICES defines the specific services offered by a carrier (like "Ground" or "Next Day Air") and is the parent entity for the stylesheet definitions. The stylesheets themselves are physical files stored within the Oracle E-Business Suite file system or database, referenced by name in this table. This configuration is utilized by the underlying ITM XML API engine and the concurrent programs responsible for communicating with external vendor systems, forming a key component of the inbound transportation integration framework.