Search Results wsh_itm_response_rules




Overview
Explore in AI Chat

Overview

The WSH_ITM_RESPONSE_RULES table is a core data object within the Shipping Execution (WSH) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It plays a critical role in the In-Transit Inventory (ITM) or In-Transit Visibility (ITV) functionality, which provides real-time tracking of shipments. Specifically, this table serves as a configuration repository that defines how the system interprets status and error messages received electronically from logistics service providers (vendors). By mapping raw vendor error codes and types to standardized internal meanings, it enables the automated and intelligent processing of carrier responses, ensuring shipment statuses are updated accurately without manual intervention.

Key Information Stored

The table stores rule-based mappings for vendor response interpretation. While the full column list is not detailed in the provided metadata, its description and relationships indicate it holds several key fields. The primary columns include a VENDOR_ID, which links to the WSH_ITM_VENDORS table to identify the carrier. It also stores the raw ERROR_CODE and ERROR_TYPE values as provided by the vendor's electronic response. Most importantly, the table contains columns that define the system's interpreted meaning for each unique combination, such as the resulting internal status or action (e.g., mark as delivered, flag as exception, retry request). This mapping is essential for translating diverse carrier-specific messaging formats into a consistent, processable format within Oracle EBS.

Common Use Cases and Queries

The primary use case is the automated parsing of Electronic Data Interchange (EDI) or web service responses from shipping vendors during the shipment tracking process. When a status update is received, the system queries this table using the vendor's identifier and the received error/status code to determine the appropriate system action. A common reporting need is to audit or maintain these mapping rules. A typical query would join to the vendor table to list all configured rules:

  • SELECT v.VENDOR_NAME, r.ERROR_CODE, r.ERROR_TYPE, r.INTERPRETED_STATUS FROM WSH_ITM_RESPONSE_RULES r, WSH_ITM_VENDORS v WHERE r.VENDOR_ID = v.VENDOR_ID ORDER BY v.VENDOR_NAME;

Another critical scenario involves troubleshooting integration issues, where support personnel query this table to verify if a specific vendor code is mapped correctly, ensuring the system's interpretation aligns with the carrier's intended message.

Related Objects

The table has a direct and documented foreign key relationship, as per the provided metadata. This relationship is fundamental to its configuration.

  • WSH_ITM_VENDORS: This is the primary related table. The column WSH_ITM_RESPONSE_RULES.VENDOR_ID is a foreign key referencing WSH_ITM_VENDORS. This join ensures that response rules are defined in the context of a specific, registered logistics vendor. The WSH_ITM_VENDORS table likely stores detailed information about the carrier, such as name, account numbers, and integration endpoints.

While not listed in the excerpt, this table is intrinsically linked to the broader In-Transit Inventory transaction flow, potentially interacting with tables like WSH_ITM_SHIPMENTS or WSH_ITM_TRACKING_EVENTS that consume the interpreted statuses generated by these rules.