Search Results wsh_cc_response_lines




Overview
Explore in AI Chat

Overview

The WSH_CC_RESPONSE_LINES table is a core data object within the Oracle E-Business Suite Shipping Execution (WSH) module. It functions as the primary repository for detailed line-level information generated from the processing of carrier communications. This table is integral to the shipment lifecycle, specifically capturing the granular responses and statuses returned by external carrier systems or internal rating engines for individual shipping items or charges. Its role is to provide an auditable, granular record of carrier interactions, enabling accurate tracking, freight cost management, and exception handling for shipped orders.

Key Information Stored

The table's primary purpose is to store response details linked to a parent carrier communication response header. While the full column list is proprietary, the documented primary key structure reveals the most critical field. The RESPONSE_LINE_ID column is the unique identifier for every record in this table, enforced by the primary key constraint WSH_CC_RESPONSE_LINES_PK. Typical data stored in related columns would include identifiers linking the line to its parent response header, references to the original shipping document line (like a delivery detail line), specific charge amounts, service codes, negotiated rates, tracking numbers, and any error messages or status codes pertaining to that particular line item as returned by the carrier.

Common Use Cases and Queries

This table is essential for troubleshooting and reporting on carrier integration. Common use cases include auditing freight charges at a line level, reconciling quoted versus actual shipping costs, diagnosing errors for specific items in a multi-line shipment, and generating reports on carrier performance and service usage. A fundamental query pattern involves joining to the parent response header table to analyze full transaction context.

  • Sample Query Pattern: Retrieving line-level response details for a specific shipment transaction would typically involve a join using the foreign key to the response header table, filtering on a known delivery or shipment identifier from related shipping tables.
  • Reporting Use Case: A report to identify all shipment lines for which a carrier returned a discount or a specific surcharge would query this table, filtering and summing on charge type and amount columns.

Related Objects

The WSH_CC_RESPONSE_LINES table does not exist in isolation; it is part of a larger schema for carrier communications. The documented primary key relationship indicates it is a child table in a data model.

  • Parent Table (Implied): It must have a foreign key relationship to a carrier response header table (such as WSH_CC_RESPONSES or similarly named), where RESPONSE_LINE_ID is a unique child record of a parent RESPONSE_ID. This link is crucial for connecting line details to the overall carrier transaction.
  • Related Shipping Tables: For operational context, lines in this table are ultimately linked to core shipping entities like WSH_DELIVERY_DETAILS or WSH_DELIVERIES, likely through the parent response header or via dedicated reference columns (e.g., DELIVERY_DETAIL_ID).
  • Dependent APIs: Public interfaces in the WSH_CARRIER_CALLS package or similar would likely read from or write to this table when processing carrier responses.