Results for “wsh_itm_response_rules”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

WSH_ITM_RESPONSE_RULES is a Shipping Execution (WSH) configuration table that stores the business interpretation of vendor-specific error conditions returned by external integration or shipping execution partners. Each row associates a particular vendor with an error type and error code, and maps that combination to an interpreted value code that Oracle EBS can act upon. In effect, the table functions as a translation matrix between raw, externally supplied error signaling and internally meaningful outcome categories used by shipping and integration processing logic.

Because the table's grain is the combination of vendor and error attributes, and because it carries descriptive attributes plus standard audit columns rather than acting as a pure parent entity, the heuristic Data Vault classification is satellite-leaning. In a Data Vault model this would typically be represented as a satellite attached to a vendor hub (WSH_ITM_VENDORS), holding the versioned mapping attributes (error type, error code, interpreted value). The table does not contain a documented foreign key to any child table, reinforcing its role as a dependent, attribute-bearing object rather than a hub or link.

Key Information Stored

The table contains nine documented columns in the WSH schema. The most consequential are:

• VENDOR_ID — Foreign key to WSH_ITM_VENDORS identifying the party whose error signaling this rule interprets. This is the primary business-key component that binds the rule to a specific vendor.
• ERROR_TYPE — Categorizes the class or family of error being interpreted, allowing different rule sets to coexist for the same vendor across error categories.
• ERROR_CODE — The specific code value returned by the vendor; together with VENDOR_ID and ERROR_TYPE it forms the logical lookup key used to resolve an incoming response.
• INTERPRETED_VALUE_CODE — The internal, normalized meaning assigned to the (vendor, error type, error code) combination. This is the payload that downstream processing consumes.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN provide standard Oracle EBS who-did-what-when tracking and are used for change auditing and data lineage reporting.

No dedicated surrogate primary key column is documented; the effective key is the business combination of VENDOR_ID, ERROR_TYPE, and ERROR_CODE. Any uniqueness enforcement is therefore expected on that composite rather than on a single synthetic identifier.

Common Use Cases and Queries

The principal use case is runtime resolution of vendor error responses during shipping integration. When an external vendor returns an error during a shipping transaction, EBS looks up this table by vendor, error type, and error code to obtain the interpreted value code and drive corrective logic. Configuration and support teams use it to define and maintain those mappings.

A typical maintenance query lists all rules for a vendor:

• SELECT error_type, error_code, interpreted_value_code FROM wsh_itm_response_rules WHERE vendor_id = :vendor_id;

Diagnostic and impact queries identify unmapped or recently changed rules:

• SELECT r.vendor_id, v.vendor_name, r.error_type, r.error_code, r.interpreted_value_code FROM wsh_itm_response_rules r JOIN wsh_itm_vendors v ON r.vendor_id = v.vendor_id;
• SELECT * FROM wsh_itm_response_rules WHERE last_update_date > SYSDATE - 7;

Reporting uses include auditing coverage of error mappings per vendor, identifying duplicate or conflicting (vendor, error type, error code) entries, and tracking configuration drift over time.

Related Objects

The dominant relationship is the documented foreign key to the vendor master:

• WSH_ITM_VENDORS — parent table; joined via WSH_ITM_RESPONSE_RULES.VENDOR_ID = WSH_ITM_VENDORS.VENDOR_ID.

Adjacent Shipping Execution integration objects that consume or complement these rules include the shipping integration and error-handling tables and views within the WSH schema that surface vendor response processing, as well as interface and concurrent programs that populate interpreted results. Because the documented metadata exposes only one foreign key, related-object references beyond WSH_ITM_VENDORS should be validated against the specific 12.1.1 or 12.2.2 instance, as additional logical relationships may exist without enforced constraints.