Results for “charge_source_code”

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

Overview

FTE_FREIGHT_COSTS_TEMP is a transient staging table within the Oracle E-Business Suite Transportation Execution (FTE) module. It stores temporary freight cost records produced during rating and freight estimation processes before those records are validated, reviewed, or promoted into permanent freight cost storage. The table exists primarily to support rating estimates — the speculative calculation of charges against trips, stops, delivery legs, and lanes — without immediately committing those results to the transactional freight cost tables. The MOVED_TO_MAIN_FLAG column explicitly signals whether a given estimate has been transferred to the permanent freight cost repository.

The ETRM metadata does not assign a formal Data Vault classification to this table; a heuristic reading suggests a satellite-style modeling pattern, since the object is keyed by a single surrogate identifier (FREIGHT_COST_ID) and carries descriptive, measurable attributes tied to a parent business process rather than serving as a pure hub or link.

Key Information Stored

The table contains 59 documented columns. The most operationally significant are:

• FREIGHT_COST_ID — the surrogate primary key, defined by the unique index FTE_FREIGHT_COSTS_TEMP_PK1 and reinforced by the composite unique index FTE_FREIGHT_COSTS_TEMP_U1 (COMPARISON_REQUEST_ID, FREIGHT_COST_ID). This is the column users search when they search for "freight_cost_id."
• FREIGHT_COST_TYPE_ID, FREIGHT_CODE, and LINE_TYPE_CODE — classify the nature of the charge being estimated.
• UNIT_AMOUNT, QUANTITY, TOTAL_AMOUNT, UOM, and CALCULATION_METHOD — capture the rate, volume, extended amount, and computation logic.
• CURRENCY_CODE, CONVERSION_RATE, CONVERSION_DATE, and CONVERSION_TYPE_CODE — support multi-currency rating.
• TRIP_ID, STOP_ID, DELIVERY_ID, and DELIVERY_LEG_ID — tie the estimate to the transportation execution context.
• ESTIMATED_FLAG and MOVED_TO_MAIN_FLAG — distinguish provisional estimates from records already promoted to permanent freight cost tables.
• COMPARISON_REQUEST_ID — groups estimates generated within a single rate-comparison request.
• Standard audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, PROGRAM_ID, REQUEST_ID) — support traceability and concurrent program attribution.

Common Use Cases and Queries

A frequent scenario is retrieving the full rating estimate set for a comparison request to validate rates before promotion to main freight cost tables:

SELECT f.FREIGHT_COST_ID, f.FREIGHT_COST_TYPE_ID,
       f.UNIT_AMOUNT, f.TOTAL_AMOUNT, f.CURRENCY_CODE,
       f.ESTIMATED_FLAG, f.MOVED_TO_MAIN_FLAG
FROM   FTE.FTE_FREIGHT_COSTS_TEMP f
WHERE  f.COMPARISON_REQUEST_ID = :p_comparison_request_id
AND    f.MOVED_TO_MAIN_FLAG = 'N';

Another common query joins the template to the lane definition to analyse rate competitiveness across corridors:

SELECT l.LANE_NAME, SUM(f.TOTAL_AMOUNT) AS estimated_cost
FROM   FTE.FTE_FREIGHT_COSTS_TEMP f,
       FTE.FTE_LANES l
WHERE  f.LANE_ID = l.LANE_ID
GROUP  BY l.LANE_NAME;

Because the table is transient, purge or archival reporting is also typical: identifying stale estimate rows by CREATION_DATE for cleanup to avoid unbounded growth.

Related Objects

• WSH_FREIGHT_COST_TYPES — joined via FREIGHT_COST_TYPE_ID to resolve charge type descriptions.
• WSH_TRIPS — joined via TRIP_ID to associate estimates with the parent trip.
• WSH_TRIP_STOPS — joined via STOP_ID to attribute costs to individual stops.
• WSH_DELIVERY_LEGS — joined via DELIVERY_LEG_ID for leg-level costing.
• FTE_LANES — joined via LANE_ID to link estimates to predefined transportation lanes.
• FTE_FREIGHT_COSTS (conceptual) — the permanent destination referenced conceptually via MOVED_TO_MAIN_FLAG.