Results for “response_header_id”

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

Overview

WSH_ITM_RESPONSE_HEADERS is a Shipping Execution (WSH) table that stores the general header-level information for responses generated against outbound integration requests. Within Oracle E-Business Suite 12.1.1 and 12.2.2, the table implements the header portion of the request/response messaging model used by the Order-to-Cash integration layer — most notably the Oracle Transportation Management (OTM) and Carrier Connect integration flows. For every request issued, a corresponding response header record is created to capture the outcome, status, timing, and any error diagnostics returned by the external system. The table is defined in the WSH schema with 15 documented columns and is classified as VALID in the ETRM data dictionary.

From a Data Vault modeling perspective, the heuristic classification for this object is satellite-leaning. Its dependency chain — anchored on a request control identifier and a vendor identifier — positions it as descriptive context attached to a request hub rather than a standalone business hub or an associative link.

Key Information Stored

The physical key of the table is RESPONSE_HEADER_ID, enforced by the primary key constraint WSH_ITM_RESPONSE_HEADERS_PK and a matching unique index, WSH_ITM_RESPONSE_HEADERS_U1 (RESPONSE_HEADER_ID). This is the surrogate identifier and the sole documented business-key candidate; no composite natural key is exposed in the metadata.

The most operationally significant columns include:

• RESPONSE_HEADER_ID — surrogate primary key uniquely identifying each response.
• REQUEST_CONTROL_ID — foreign key to WSH_ITM_REQUEST_CONTROL, tying the response back to the originating request.
• VENDOR_ID — foreign key to WSH_ITM_VENDORS, identifying the external party or service provider that produced the response.
• SERVICE_TYPE_CODE — classifies the service invoked for the request/response exchange.
• MESSAGE_ID — the external message reference used for correlation and reconciliation.
• RESPONSE_DATE — timestamp of when the response was received or recorded.
• ERROR_TYPE, ERROR_CODE, and ERROR_TEXT — structured diagnostic fields for fault classification and human-readable failure detail.
• EXPORT_COMPLIANCE_STATUS — compliance disposition associated with the response.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns.

Common Use Cases and Queries

Typical reporting focuses on response success rates, error trending by vendor and service type, and latency between request issuance and response receipt. A common join pattern links the response header to its request control and vendor:

• Query all failed responses: filter on ERROR_TYPE or non-null ERROR_CODE, ordered by RESPONSE_DATE.
• Reconcile a specific integration run by joining REQUEST_CONTROL_ID to WSH_ITM_REQUEST_CONTROL and MESSAGE_ID for external correlation.
• Drill into line-level detail by joining RESPONSE_HEADER_ID to WSH_ITM_RESPONSE_LINES.
• Vendor-level error reporting by joining VENDOR_ID to WSH_ITM_VENDORS.
• Timeout analysis comparing RESPONSE_DATE against the corresponding request timestamp.

Related Objects

The table participates in a well-documented foreign key network:

• WSH_ITM_REQUEST_CONTROL — joined via REQUEST_CONTROL_ID; also holds a reciprocal RESPONSE_HEADER_ID reference.
• WSH_ITM_VENDORS — joined via VENDOR_ID.
• WSH_ITM_RESPONSE_LINES — child lines joined via RESPONSE_HEADER_ID.
• WSH_CC_RESPONSE_HEADERS — references RESPONSE_HEADER_ID.
• WSH_CC_RESPONSE_LINES — references RESPONSE_HEADER_ID.
• WSH_CC_TRANS_CONTROL — references RESPONSE_HEADER_ID.