Search Results charge_type_meaning




Overview
Explore in AI Chat

Overview

APPS.SO_FREIGHT_CHARGES_V is a reporting and integration view in Oracle E-Business Suite (applicable to 12.1.1 and 12.2.2) that presents freight charge records associated with order picking headers. It denormalizes data from the freight charge transaction table, the freight charge type setup table, and the Order Management lookup repository, so that consumers obtain descriptive values — notably the charge type meaning — without performing the joins themselves.

The view is particularly relevant when the reported value for charge_type_meaning is required. In the underlying transaction table, freight charges reference a freight charge type identifier; the human-readable label resides in the lookup definition. This view resolves that relationship at definition time, returning the lookup meaning under the alias CHARGE_TYPE_MEANING. It is therefore a convenient source for freight cost analysis, invoicing reconciliation, and outbound interfaces that must display or transmit a meaningful charge type rather than a code.

Underlying Base Objects

The view is owned by APPS and is defined over the following documented objects: the synonym SO_FREIGHT_CHARGES (transaction table), the synonym SO_FREIGHT_CHARGE_TYPES (freight charge type setup), and the synonym SO_LOOKUPS (Order Management lookups). The FND_GLOBAL package is listed as a referenced object in the view's metadata.

The join structure is explicit and important. SO_FREIGHT_CHARGES (aliased FC) is the driving entity, supplying the charge identifier, amount, currency, conversion details, invoice status, and descriptive flexfield attribute columns. SO_FREIGHT_CHARGE_TYPES (aliased FT) is joined on FT.FREIGHT_CHARGE_TYPE_ID = FC.FREIGHT_CHARGE_TYPE_ID, contributing the type name, code, and description. SO_LOOKUPS (aliased L) is joined on FT.FREIGHT_CHARGE_TYPE_CODE = L.LOOKUP_CODE with the filter L.LOOKUP_TYPE = 'FREIGHT_CHARGE_TYPE', supplying the lookup meaning surfaced as CHARGE_TYPE_MEANING. Because all three joins are equi-joins, only freight charges whose type resolves to a defined lookup are returned; charges lacking a matching lookup row are excluded.

Key Columns

Common Use Cases and Queries

Typical uses include freight cost reporting by charge type, reconciliation of freight charges against picking activity, and integration extracts that publish freight charges with their descriptive charge type. The following query lists freight charges for a picking header, returning the human-readable charge type:

  • SELECT freight_charge_id, picking_header_id, charge_type_meaning, amount, currency_code, invoice_status FROM apps.so_freight_charges_v WHERE picking_header_id = :p_picking_header_id;
  • SELECT charge_type_meaning, SUM(amount) FROM apps.so_freight_charges_v WHERE creation_date >= :p_from_date GROUP BY charge_type_meaning;
  • SELECT freight_charge_id, freight_charge_type_code, charge_type_meaning FROM apps.so_freight_charges_v WHERE charge_type_meaning LIKE 'Fuel%';

Because the view is read-only and enforces the lookup join described above, queries against it are best suited to descriptive reporting. Where freight charges without a valid FREIGHT_CHARGE_TYPE lookup must be included, querying SO_FREIGHT_CHARGES with an outer join to SO_LOOKUPS is preferable.