Search Results wsh_itm_service_preferences




Overview
Explore in AI Chat

Overview

The WSH_ITM_SERVICE_PREFERENCES table is a core data structure within the Oracle E-Business Suite Shipping Execution (WSH) module. It functions as a configuration repository for managing service-level preferences within the In-Transit Inventory (ITM) or Oracle Transportation Management (OTM) integration framework. Its primary role is to define and store business rules that dictate which external logistics service provider (vendor) is selected for specific transportation services and the priority order for such requests. This configuration is scoped by a Master Organization and an Application, enabling granular control over shipping vendor assignments and request prioritization across the enterprise.

Key Information Stored

The table stores the relationships that map internal service requirements to external vendor services. The primary identifier is the ITM_SERVICE_PREFERENCE_ID. Key foreign key columns establish critical relationships: the APPLICATION_ID links to FND_APPLICATION to identify the EBS application context, while the VENDOR_SERVICE_ID links to WSH_ITM_VENDOR_SERVICES to specify the available service from a vendor. Additional columns, implied by the table's purpose, would typically store the MASTER_ORGANIZATION_ID for the inventory org scope, a SERVICE_TYPE or similar identifier for the required service (e.g., LTL, FTL, Air), and a PRIORITY column to sequence multiple vendor options for the same service. The configuration allows a business to define a primary and backup vendor for a given service type.

Common Use Cases and Queries

This table is central to the automated vendor service selection during shipping document creation or freight cost calculation. A common operational use case is troubleshooting why a specific carrier was automatically assigned to a shipment. Analysts may query this table to audit or report on the configured vendor service hierarchy. A typical reporting query would join to FND_APPLICATION and WSH_ITM_VENDOR_SERVICES to list all preferences.

Sample Query:
SELECT pref.ITM_SERVICE_PREFERENCE_ID,
app.APPLICATION_SHORT_NAME,
pref.MASTER_ORGANIZATION_ID,
vs.VENDOR_SERVICE_CODE,
pref.PRIORITY
FROM WSH.WSH_ITM_SERVICE_PREFERENCES pref,
WSH.WSH_ITM_VENDOR_SERVICES vs,
APPLSYS.FND_APPLICATION app
WHERE pref.VENDOR_SERVICE_ID = vs.VENDOR_SERVICE_ID
AND pref.APPLICATION_ID = app.APPLICATION_ID
ORDER BY pref.MASTER_ORGANIZATION_ID, pref.PRIORITY;

Related Objects

The table maintains defined foreign key relationships with other core EBS objects, as documented in the ETRM metadata:

  • FND_APPLICATION: Joined via WSH_ITM_SERVICE_PREFERENCES.APPLICATION_ID. This links the service preference to a specific EBS application module.
  • WSH_ITM_VENDOR_SERVICES: Joined via WSH_ITM_SERVICE_PREFERENCES.VENDOR_SERVICE_ID. This is the critical link to the defined services offered by external logistics vendors, which the preference record selects.

Furthermore, this table is logically a parent to shipping transaction data. While not listed in the provided FKs, shipment lines or freight charges would reference these preferences to determine the applied vendor and service.