Search Results freight_cost_id




Overview
Explore in AI Chat

Overview

The WSH_FREIGHT_COSTS table is a core data object within the Oracle E-Business Suite (EBS) Shipping Execution (WSH) module, specifically for versions 12.1.1 and 12.2.2. It serves as the central repository for recording and managing freight cost transactions associated with the shipping lifecycle. This table is fundamental to the financial tracking of shipments, enabling organizations to capture, allocate, and analyze transportation expenses. Its role is to link specific freight costs to the logistical entities they pertain to, such as trips, stops, deliveries, and individual delivery lines, thereby providing a granular audit trail for logistics accounting and cost distribution.

Key Information Stored

The table's primary key is FREIGHT_COST_ID, which uniquely identifies each freight cost record. Its structure is defined by a series of foreign key relationships that anchor each cost to a specific point in the shipping hierarchy. The most significant columns include TRIP_ID, linking to WSH_TRIPS; STOP_ID, linking to WSH_TRIP_STOPS; DELIVERY_ID, linking to WSH_NEW_DELIVERIES; DELIVERY_LEG_ID, linking to WSH_DELIVERY_LEGS; and DELIVERY_DETAIL_ID, linking to WSH_DELIVERY_DETAILS. This allows a single cost to be associated at the most appropriate level of detail. Furthermore, the FREIGHT_COST_TYPE_ID column links to the WSH_FREIGHT_COST_TYPES table, classifying the cost (e.g., fuel surcharge, base freight, accessorial). The table is also referenced by OE_PRICE_ADJUSTMENTS, indicating its integration with the Order Management module for pricing and invoicing adjustments related to freight.

Common Use Cases and Queries

A primary use case is generating freight cost analysis reports for a specific delivery or trip. For instance, a query to summarize all freight costs by type for a given delivery would join WSH_FREIGHT_COSTS with WSH_FREIGHT_COST_TYPES. Another critical scenario involves auditing cost allocation by querying costs rolled up from the line level (DELIVERY_DETAIL_ID) to the delivery or trip level. Support and implementation teams often query this table to troubleshoot missing costs or validate the setup of automatic freight rating engines. A common diagnostic pattern is to find costs for a delivery that lacks a corresponding trip or stop assignment, which may indicate a data or process issue.

  • Sample Query (Costs by Type for a Delivery): SELECT fc.freight_cost_id, fct.name cost_type, fc.amount FROM wsh_freight_costs fc, wsh_freight_cost_types fct WHERE fc.freight_cost_type_id = fct.freight_cost_type_id AND fc.delivery_id = <delivery_id>;
  • Sample Query (Trip Cost Summary): SELECT trip_id, freight_cost_type_id, SUM(amount) total_amount FROM wsh_freight_costs WHERE trip_id IS NOT NULL GROUP BY trip_id, freight_cost_type_id;

Related Objects

The WSH_FREIGHT_COSTS table is a nexus within the Shipping Execution schema, with dependencies to multiple key entities. Its primary foreign keys establish direct relationships with the main shipping transaction tables: WSH_TRIPS, WSH_TRIP_STOPS, WSH_NEW_DELIVERIES, WSH_DELIVERY_LEGS, and WSH_DELIVERY_DETAILS. It is governed by the reference table WSH_FREIGHT_COST_TYPES for cost classification. A significant integration point is with the Order Management module via the OE_PRICE_ADJUSTMENTS table, where a freight cost record can be sourced to create customer-facing price adjustments or charges. This relationship underscores the table's role in bridging operational logistics with financial transactions.