Results for “mode_of_transport_code”

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

Overview

FTE_LANE_VEHICLES is a Transportation Execution (FTE) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the vehicle capabilities associated with transportation lanes and lane groups. It functions as the operational bridge between logistics routing definitions and the physical equipment that can service those routes, allowing planners to declare which vehicle types may operate on a given lane, in what quantity, at what frequency, and across which effective-dated validity window. The table resides in the FTE schema and is documented as VALID in the ETRM repository.

From a heuristic Data Vault modeling perspective, FTE_LANE_VEHICLES can be classified as a standalone entity, meaning the mined foreign-key structure does not naturally resolve it into a conventional hub, link, or satellite pattern. In practice, it behaves as an associative link, joining a lane or lane group to vehicle-type and destination references, while its effective-date and quantity columns give it satellite-like descriptive characteristics. This dual nature should be considered when designing downstream analytical or integration models.

Key Information Stored

The physical schema documents 17 columns in the 12.2.2 release. The most significant include:

• LANE_VEHICLE_ID – surrogate primary key, enforced by unique index FTE_LANE_VEHICLES_U1.
• LANE_ID – foreign key to FTE_LANES, identifying the specific lane being configured.
• LANE_GROUP_ID – foreign key to FTE_LANE_GROUPS, supporting group-level vehicle assignment.
• VEHICLE_TYPE_ID – reference to the vehicle type permitted on the lane or group.
• QUANTITY – number of vehicles of that type expected or required.
• FREQUENCY_UOM – unit of measure governing how quantity or schedule is interpreted.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE – date-ranged validity defining when the assignment applies.
• ORIGIN_ID / DESTINATION_ID – endpoints of movement; DESTINATION_ID joins to IGI_DOS_DESTINATIONS.
• CARRIER_ID – carrier responsible for the movement.
• MODE_OF_TRANSPORT_CODE – transport mode (e.g., truck, rail, air) for the assignment.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN – standard audit columns tracking record lifecycle.

LANE_VEHICLE_ID is the documented surrogate key; the unique index serves as the business-key candidate for identifying individual lane-vehicle assignments.

Common Use Cases and Queries

Typical scenarios include validating that every active lane has an approved vehicle type, reconciling carrier and mode assignments against lane definitions, and reporting upcoming expirations of vehicle-to-lane agreements. A representative query joining lanes and groups is:

• SELECT l.lane_name, v.vehicle_type_id, v.quantity FROM fte_lanes l, fte_lane_vehicles v WHERE l.lane_id = v.lane_id AND SYSDATE BETWEEN v.effective_start_date AND v.effective_end_date;

Additional use cases include audit reporting over creation and update audit columns, effective-dated change tracking for compliance, and integration extracts feeding load-tender or carrier-selection processes. Queries frequently filter on MODE_OF_TRANSPORT_CODE or CARRIER_ID to produce mode-mix and carrier-capacity summaries.

Related Objects

• FTE_LANES – joined on LANE_ID; parent lane definition.
• FTE_LANE_GROUPS – joined on LANE_GROUP_ID; group-level vehicle assignment.
• IGI_DOS_DESTINATIONS – joined on DESTINATION_ID; destination reference.
• Vehicle type reference tables in FTE – linked via VEHICLE_TYPE_ID.
• Carrier reference tables – linked via CARRIER_ID for carrier validation.
• FTE lane and scheduling APIs/views – consume this table when building lane-vehicle capability lookups.