Search Results so_freight_charge_types




Overview
Explore in AI Chat

Overview

The SO_FREIGHT_CHARGE_TYPES table is a foundational reference data object within the Oracle E-Business Suite (EBS) Order Entry (OE) module. It functions as a master repository for defining the distinct categories or classifications of freight charges that can be applied to sales orders. This table is critical for standardizing freight cost calculations and ensuring consistent application of shipping-related fees across the order management lifecycle. By centralizing freight charge type definitions, it enables flexible configuration and reporting, allowing organizations to model various shipping cost structures, such as flat fees, weight-based charges, or destination-specific surcharges. Its role is integral to the accurate financial accounting of order fulfillment costs.

Key Information Stored

The table's structure is designed to uniquely identify and describe each freight charge type. The primary technical identifier is the FREIGHT_CHARGE_TYPE_ID column, which serves as the system-generated primary key for all records. The primary business identifier is the NAME column, which holds the unique, user-defined descriptive name for the charge type (e.g., 'STANDARD SHIPPING', 'OVERSIZE FEE', 'EXPRESS DELIVERY'). This column is enforced as a unique key. While the provided ETRM excerpt lists only these core columns, typical implementations of such reference tables often include additional descriptive columns like ENABLED_FLAG, DESCRIPTION, and CREATION_DATE, which facilitate application logic and auditing.

Common Use Cases and Queries

A primary use case is the setup and maintenance of valid freight charge types during system configuration. Administrators populate this table with the organization's specific charge categories. In operational and reporting contexts, the table is frequently joined to transactional data to categorize freight costs. Common SQL patterns include listing all active charge types or analyzing freight revenue by type. For example:

  • SELECT name, description FROM oe.so_freight_charge_types WHERE enabled_flag = 'Y' ORDER BY name;
  • SELECT fct.name, SUM(sc.charge_amount) FROM oe.so_freight_charges sc JOIN oe.so_freight_charge_types fct ON sc.freight_charge_type_id = fct.freight_charge_type_id GROUP BY fct.name;

These queries support critical processes like freight cost analysis, customer billing verification, and carrier performance reporting.

Related Objects

The SO_FREIGHT_CHARGE_TYPES table has a direct, documented parent-child relationship with the primary transactional table for freight charges. The foreign key relationship is explicitly defined in the ETRM metadata:

  • SO_FREIGHT_CHARGES: This transactional table stores the actual freight charge instances applied to sales orders. It references SO_FREIGHT_CHARGE_TYPES via the foreign key column SO_FREIGHT_CHARGES.FREIGHT_CHARGE_TYPE_ID, which joins to SO_FREIGHT_CHARGE_TYPES.FREIGHT_CHARGE_TYPE_ID. This relationship ensures that every applied freight charge is categorized according to a valid, predefined type.

This relationship is fundamental, meaning that SO_FREIGHT_CHARGE_TYPES records are referenced by potentially many rows in the SO_FREIGHT_CHARGES table, enforcing data integrity and enabling detailed freight analysis.