Results for “fte_lanes”

50+ results




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

Overview

FTE_LANES is a core configuration and reference table within the Oracle E-Business Suite Transportation Execution (FTE) module. It stores services catalog lane descriptions, capturing the predefined transportation routes that carriers, logistics providers, and internal planners use to model the movement of goods between an origin and a destination. In Oracle EBS 12.1.1 and 12.2.2, the FTE schema underpins the Transportation Management and Freight Payment functionality, and FTE_LANES acts as the master definition of a "lane" — the directional service path over which freight moves, including the mode of transport, transit time, equipment and commodity expectations, and pricing references.

From a Data Vault modeling perspective, the heuristic classification of FTE_LANES is hub-leaning. It carries a single-column surrogate primary key (LANE_ID) and is referenced by a substantial number of dependent tables, giving it the shape of a hub in a hub-and-satellite design. Downstream attributes such as pricing, schedules, commodities, and equipment details conceptually behave as satellites or link records attached to the hub.

Key Information Stored

The table holds 40 documented columns. The following are the most significant:

Standard Oracle audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and concurrent request columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE) are also present.

Common Use Cases and Queries

Typical uses include lane master reporting, rate and freight cost derivation, and validation of transportation planning data. A common query lists active lanes between two regions:

  • Join FTE_LANES to WSH_REGIONS on ORIGIN_ID and DESTINATION_ID to translate region identifiers into names.
  • Filter on EFFECTIVE_DATE and EXPIRY_DATE (or SYSDATE) to restrict to currently valid lanes.
  • Join to FTE_LANE_RATE_CHARTS or FTE_LANE_SERVICES on LANE_ID to report available rates and service levels.
  • Join to OP_PRCE_MST on PRICELIST_ID to resolve pricing for the lane.
  • Aggregate FTE_MOVES or WSH_TRIPS on LANE_ID to measure actual volume and cost against the lane definition.

Because FTE_LANES is referenced by many interface and staging tables (FTE_MOVES_INTERFACE, WSH_TRIPS_INTERFACE, FTE_FREIGHT_COSTS_TEMP), it is frequently used in data conversion and integration validation to confirm that incoming lane identifiers resolve to valid master records.

Related Objects

The following objects are the most significant dependents and references of FTE_LANES:

  • WSH_REGIONS — referenced via FTE_LANES.ORIGIN_ID and FTE_LANES.DESTINATION_ID.
  • OP_PRCE_MST — referenced via PRICELIST_ID for pricing linkage.
  • FTE_LANE_RATE_CHARTS — rate charts attached to the lane (LANE_ID).
  • FTE_LANE_SERVICES — service definitions for the lane (LANE_ID).
  • FTE_LANE_COMMODITIES and FTE_LANE_EQUIPMENTS — commodity and equipment detail (LANE_ID).
  • FTE_SCHEDULES — schedules referencing the lane (LANE_ID).
  • FTE_MOVES and WSH_TRIPS — execution records that consume the lane definition (LANE_ID).
  • FTE_LOAD_CHARGES and FTE_PRC_PARAMETERS — charges and pricing parameters by lane (LANE_ID).