Results for “load_charge_id”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

FTE_LOAD_CHARGES_V is a reporting and integration view within the Oracle E-Business Suite Transportation Execution (FTE) module. It exposes load-level and load-detail-level charge, price, and pricing information associated with transportation loads and their schedules. The view consolidates data from the FTE_LOAD_CHARGES base table and the FTE_LOAD_SCHEDULES base table, filtering out records whose associated load schedule carries a status of OBSOLETE. This filtering ensures that downstream consumers — reports, interfaces, and external integrations — see only current, active charge data.

The view is particularly relevant for organizations that need to report on transportation costs and pricing breakdowns by load, lane, and schedule without navigating the normalized structure of the underlying charge and schedule tables. It presents charge identifiers, pricing attributes, unit prices, and aggregate charge values in a single denormalized result set. The user search term "load_charge_id" corresponds directly to the primary charge identifier column exposed by this view, which is commonly used to join to other FTE charge-related objects.

Underlying Base Objects

The view is defined over two documented base objects:

• FTE_LOAD_CHARGES (aliased C) — the primary source of charge, pricing, and load association data, supplying most columns in the view.
• FTE_LOAD_SCHEDULES (aliased S) — joined on LOAD_SCHEDULE_ID to supply schedule context and to enable the OBSOLETE status filter.

The join condition is C.LOAD_SCHEDULE_ID = S.LOAD_SCHEDULE_ID, combined with the predicate UPPER(S.STATUS_CODE) <> 'OBSOLETE'. Documented metadata indicates no additional referenced base objects beyond these two tables. Note that the documented metadata reports the view as "Not implemented in this database" in the ETRM excerpt, meaning availability depends on whether the FTE module and its charge objects are licensed and installed in the target environment.

Key Columns

• LOAD_CHARGE_ID — unique identifier for the load charge record; the primary key referenced by the user's search.
• LOAD_CHARGE_TYPE_CODE — distinguishes charge types such as 'PRICE' versus 'CHARGE', and drives the conditional logic applied to CHARGESUBTYPE.
• SUMMARY_FLAG — indicates whether the charge is a summarized record.
• SOURCE_SYSTEM_CODE — identifies the originating system for the charge, useful for integration reconciliation.
• UNIT_PRICE — exposed as PRICING_UNIT_PRICE in the base table and renamed to UNIT_PRICE in the view.
• LOAD_ID, LOAD_DETAIL_ID, LOAD_SCHEDULE_ID — foreign keys linking the charge to the load, load detail, and schedule.
• PRICING_UOM_BASIS, PRICING_UOM — define the unit-of-measure basis for pricing calculations.
• PRICING_LIST_LINE_TYPE_CODE, PRICING_LEVEL_CODE, PRICE_BREAK_TYPE_CODE — pricing configuration attributes describing the pricing structure applied.
• CHARGE_TOTAL_VALUE — the total monetary value of the charge.
• CHARGESUBTYPE — derived via DECODE: NULL when LOAD_CHARGE_TYPE_CODE is 'PRICE', otherwise V_ATTRIBUTE2.
• LANE_ID — the transportation lane associated with the charge.

Common Use Cases and Queries

Typical scenarios include transportation cost reporting by load or lane, charge reconciliation against source systems, and integration extracts for freight payment or analytics. The following query retrieves charges for a specific schedule with active status filtering already applied by the view:

• SELECT load_charge_id, load_id, load_schedule_id, load_charge_type_code, chargesubtype, unit_price, charge_total_value FROM fte_load_charges_v WHERE load_schedule_id = :p_schedule_id;
• SELECT lane_id, SUM(charge_total_value) FROM fte_load_charges_v WHERE load_charge_type_code = 'CHARGE' GROUP BY lane_id;
• SELECT load_charge_id, load_detail_id, pricing_uom, pricing_level_code FROM fte_load_charges_v WHERE source_system_code = :p_source;

Because the view pre-filters OBSOLETE schedules, consumers avoid stale schedule data. Joins to FTE_LOAD_CHARGES on LOAD_CHARGE_ID should be used when columns not exposed by the view are required.