Results for “fte_load_charges”

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

Overview

FTE_LOAD_CHARGES is a Transportation Execution (FTE) transaction table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the price components associated with the details of a tendered shipment. Each row represents an individual charge, accessorial, or pricing line applied against a load, load detail, or load schedule. The table acts as the persistent record of pricing outcomes generated for freight movements, tying together the operational shipment structure (loads, details, schedules, lanes) with the Oracle Advanced Pricing (QP) engine artifacts that produced the price (pricing list headers, list lines, and pricing phases).

From a Data Vault modeling perspective, the metadata's heuristic classification places FTE_LOAD_CHARGES as satellite-leaning. It primarily carries descriptive and numeric charge attributes attached to operational hubs such as loads and load details, while simultaneously owning several self-referencing and QP-referencing links. This dual nature reflects its role as both a detail store for shipment pricing and a junction between transportation execution and pricing engine entities.

Because the table is documented as "Not implemented in this database," DBAs should verify its presence in the target instance before relying on it; in some environments the pricing charge record is instead surfaced through QP or freight cost tables.

Key Information Stored

The primary key of FTE_LOAD_CHARGES is defined by the FTE_LOAD_CHARGES_PK constraint, backed by the surrogate key column LOAD_CHARGE_ID. Documented foreign keys imply the following significant columns:

• LOAD_CHARGE_ID — Surrogate primary key uniquely identifying a charge record.
• LOAD_ID — References FTE_LOAD_HEADERS, linking the charge to the parent load/tendered shipment.
• LOAD_DETAIL_ID — References FTE_LOAD_DETAILS, tying the charge to a specific shipment line or detail.
• LOAD_SCHEDULE_ID — References FTE_LOAD_SCHEDULES, associating the charge with a scheduled shipment leg.
• LANE_ID — References FTE_LANES, identifying the transportation lane used for rate determination.
• PRICING_LIST_HEADER_ID — References QP_LIST_HEADERS_B, the pricing list (price list) that supplied the rate.
• PRICING_LIST_LINE_ID — References QP_LIST_LINES, the specific line within the pricing list.
• PRICING_PHASE_ID — References QP_PRICING_PHASES, identifying which pricing phase produced or adjusted the charge.
• APPLIED_TO_LOAD_PRICE_ID — Self-referencing column indicating the base charge to which this charge applies (e.g., an accessorial on top of a base freight charge).
• BREAK_LINE_FOR_CHARGE_ID — Self-referencing column supporting break-line pricing structures.

These columns collectively capture the operational context, the pricing source, and the hierarchical relationship among charges on a single shipment.

Common Use Cases and Queries

The table is typically queried to audit how a tendered shipment was priced, to reconcile freight charges against pricing lists, and to report accessorial charges by lane, carrier, or phase.

• Listing all charges for a load: SELECT * FROM FTE_LOAD_CHARGES WHERE LOAD_ID = :load_id;
• Joining to pricing lists to identify the source rate: SELECT c.LOAD_CHARGE_ID, h.NAME, l.LIST_LINE_ID FROM FTE_LOAD_CHARGES c JOIN QP_LIST_HEADERS_B h ON c.PRICING_LIST_HEADER_ID = h.LIST_HEADER_ID JOIN QP_LIST_LINES l ON c.PRICING_LIST_LINE_ID = l.LIST_LINE_ID;
• Breaking down charges by pricing phase: joining PRICING_PHASE_ID to QP_PRICING_PHASES to attribute charges to list, formula, or qualifier phases.
• Identifying base-charge hierarchies using the APPLIED_TO_LOAD_PRICE_ID self-join.
• Extracting charge-level attributes through FTE_CHRG_PRC_ATTRIBUTES for detailed pricing component reporting.

Reporting use cases include freight cost analysis, accessorial spend by lane, and reconciliation of transportation charges against Oracle Payables invoice lines.

Related Objects

• FTE_LOAD_HEADERS — Parent load, joined on LOAD_ID.
• FTE_LOAD_DETAILS — Shipment detail lines, joined on LOAD_DETAIL_ID.
• FTE_LOAD_SCHEDULES — Scheduled shipment legs, joined on LOAD_SCHEDULE_ID.
• FTE_LANES — Transportation lanes, joined on LANE_ID.
• QP_LIST_HEADERS_B — Pricing list headers, joined on PRICING_LIST_HEADER_ID.
• QP_LIST_LINES — Pricing list lines, joined on PRICING_LIST_LINE_ID.
• QP_PRICING_PHASES — Pricing phase definitions, joined on PRICING_PHASE_ID.
• FTE_CHRG_PRC_ATTRIBUTES — Child attribute table referencing LOAD_CHARGE_ID; carries the granular pricing attributes for each charge.
• FTE_LOAD_CHARGES (self) — Self-references via APPLIED_TO_LOAD_PRICE_ID and BREAK_LINE_FOR_CHARGE_ID.