Search Results freight_charge_id




Overview
Explore in AI Chat

Overview

The SO_FREIGHT_CHARGES table is a core data object within the Oracle E-Business Suite (EBS) Order Entry (OE) module. It serves as the central repository for recording and managing freight charges associated with the fulfillment of sales orders. Its primary role is to capture the financial details of shipping costs that are generated during the pick release, shipping, and delivery execution processes. By maintaining a distinct record for each freight charge, the table enables accurate freight cost allocation, auditing, and integration with the broader financial and logistics systems. It is a critical component for businesses that need to track, report on, or potentially invoice freight expenses separately from the cost of goods sold.

Key Information Stored

While the full column list is not provided in the excerpt, the documented foreign key relationships and primary key define its essential structure. The central identifier is the FREIGHT_CHARGE_ID, which serves as the primary key. The table stores foreign keys that link each freight charge record to its associated transactional and master data. These include the PICKING_HEADER_ID, which ties the charge to a specific pick release batch; the DELIVERY_ID, linking it to a shipment in the Shipping Execution (WSH) module; and the CONTAINER_ID for granularity at the packed container level. Crucially, it holds the FREIGHT_CHARGE_TYPE_ID, which categorizes the charge (e.g., standard freight, handling fee, fuel surcharge) by referencing the SO_FREIGHT_CHARGE_TYPES table. The table would also typically contain columns for the monetary amount, currency, and potentially the associated PICKING_LINE_DETAIL_ID for line-level freight tracking.

Common Use Cases and Queries

This table is central to freight-related reporting and analysis. A common use case is auditing freight costs accrued for a specific delivery or a range of shipments. Analysts may query this table to reconcile total freight charges against carrier invoices or to analyze freight costs by customer, sales channel, or geographic region. Another key scenario involves troubleshooting, where support personnel trace a freight charge appearing on an invoice back to its originating delivery and order line. A sample query to retrieve freight details for a specific delivery would be:

  • SELECT sfc.freight_charge_id, sfc.amount, sfct.name charge_type
  • FROM oe.so_freight_charges sfc,
  •      oe.so_freight_charge_types sfct
  • WHERE sfc.delivery_id = :p_delivery_id
  • AND sfc.freight_charge_type_id = sfct.freight_charge_type_id;

Related Objects

The SO_FREIGHT_CHARGES table has defined integration points with several key EBS tables, as per the provided metadata. Its primary relationships are:

  • SO_FREIGHT_CHARGE_TYPES: Joined via FREIGHT_CHARGE_TYPE_ID. This provides the descriptive name and classification for the type of charge recorded.
  • SO_PICKING_HEADERS_ALL: Joined via PICKING_HEADER_ID. Links the freight charge to the pick release batch that initiated the fulfillment task.
  • WSH_DELIVERIES: Joined via DELIVERY_ID. Connects the charge to the specific delivery/shipment created in the Shipping Execution module.
  • WSH_PACKED_CONTAINERS: Joined via CONTAINER_ID. Allows freight charges to be associated with a specific physical container within a delivery.
  • SO_PICKING_LINE_DETAILS: Joined via PICKING_LINE_DETAIL_ID. Provides a granular link to the specific picked order line detail, enabling line-level freight cost assignment.