Search Results so_freight_charges_v




Overview
Explore in AI Chat

Overview

SO_FREIGHT_CHARGES_V is a reportable view owned by the APPS schema in Oracle E-Business Suite, catalogued under the Order Entry (OE) product family. Its documented description in ETRM is narrow — "10SC Only" — which identifies the view as a legacy construct retained primarily for backward compatibility with the 10SC (discrete/process manufacturing freight charge) reporting lineage rather than as a general-purpose order management interface. The view is marked VALID, meaning it compiles and is queryable in both 12.1.1 and 12.2.2, though it is not exposed in the standard Oracle Order Management user interface and is not referenced by mainstream concurrent programs.

Functionally, the view presents freight charge records enriched with their charge type definition and a lookup-derived meaning. It is denormalized for read convenience: consumers receive the freight charge amount, currency, conversion attributes, and invoice status in a single row alongside descriptive text, avoiding the multi-table joins that would otherwise be required. This makes it suitable for custom reports, reconciliation extracts, and integration staging where a flat freight charge record is preferred over normalized data.

Underlying Base Objects

The view is defined over three base tables, all accessed through public synonyms in the APPS schema: SO_FREIGHT_CHARGES, SO_FREIGHT_CHARGE_TYPES, and SO_LOOKUPS. The join logic is deterministic and uses two equi-join predicates plus a lookup filter:

Because the lookup join is an inner join without a lookup-code uniqueness guard, the view can return multiple rows per freight charge if duplicate lookup codes exist within the FREIGHT_CHARGE_TYPE lookup type. FND_GLOBAL is documented as a referenced object at the package level, reflecting the standard WHO-column conventions used throughout Oracle EBS.

Key Columns

The view exposes thirty-eight columns, which fall into four functional groups.

CHARGE_TYPE_MEANING is the most commonly referenced column for reporting because it carries the user-facing translation rather than the internal code.

Common Use Cases and Queries

Typical usage includes freight charge reconciliation against picking headers, invoice status monitoring for un-invoiced charges, and audit extracts of currency conversion details. A representative query follows.

SELECT freight_charge_id, freight_charge_type_name, charge_type_meaning, picking_header_id, amount, currency_code, invoice_status FROM apps.so_freight_charges_v WHERE invoice_status = 'N' AND creation_date >= SYSDATE - 30;

Because the object is documented as 10SC Only, consumers should validate results in the target environment and avoid treating it as a supported public interface in new development.