Results for “fte_lane_equipments”

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

Overview

FTE_LANE_EQUIPMENTS is a Transportation Execution (FTE) module table within the Oracle E-Business Suite 12.1.1 and 12.2.2 data model. Its documented purpose is to store equipment information for each lane. In transportation planning, a lane represents a recurring origin-to-destination movement of goods, and the equipment assigned to that lane defines the physical asset — such as a truck type, trailer configuration, container class, or carrier-specified transport resource — used when executing shipments along that route. The table therefore acts as an operational link between lane definitions and the equipment resources eligible for those lanes.

From a Data Vault modeling perspective, the heuristic classification derived from the foreign-key structure is satellite-leaning. The table has no outgoing dependency chain of its own beyond its parent, and its attribute set is descriptive rather than relational in character; this suggests treating it as a satellite hanging off the lane hub rather than as an independent hub or a many-to-many link.

Key Information Stored

The physical schema comprises eight columns owned by the FTE schema. The most significant documented columns are:

• LANE_EQUIPMENT_ID — the surrogate primary key, uniquely identifying each equipment assignment record. It is enforced through the FTE_LANE_EQUIPMENTS_PK constraint.
• LANE_ID — the foreign key to FTE_LANES, tying each equipment record to a specific transportation lane.
• EQUIPMENT_CODE — the business identifier for the equipment type or resource associated with the lane.
• CREATED_BY, CREATION_DATE — standard WHO-column audit attributes capturing record creation.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit attributes capturing the most recent modification and the login context of the change.

The documented unique index FTE_LANE_EQUIPMENTS_U1 covers (EQUIPMENT_CODE, LANE_ID), making that composite pair the business-key candidate. Practically, this means a given equipment code may be attached to a lane only once, while the surrogate LANE_EQUIPMENT_ID remains the technical row identifier referenced by downstream constraints.

Common Use Cases and Queries

Typical usage centers on validating and reporting which equipment is authorized for a lane. A frequent join retrieves lane and equipment detail for carrier or routing analysis:

• SELECT le.lane_equipment_id, l.lane_id, le.equipment_code FROM fte.fte_lane_equipments le JOIN fte.fte_lanes l ON le.lane_id = l.lane_id WHERE le.equipment_code = :equipment_code;
• Listing all equipment configured for a lane, used when auditing route setup or diagnosing missing equipment on a shipment plan.
• Referential-integrity checks confirming every LANE_ID in FTE_LANE_EQUIPMENTS resolves to FTE_LANES.
• Change-audit reporting on CREATION_DATE and LAST_UPDATE_DATE to identify recently modified lane-equipment configurations.

Related Objects

The documented foreign key establishes FTE_LANES as the parent table, joined on FTE_LANE_EQUIPMENTS.LANE_ID = FTE_LANES.LANE_ID. Additional objects that interact with lane equipment data in the Transportation Execution module include lane-related views, the FTE shipment and planning entities that consume lane equipment during routing, and the WHO/audit columns shared across FTE tables. The primary key constraint FTE_LANE_EQUIPMENTS_PK and unique index FTE_LANE_EQUIPMENTS_U1 are the principal documented structures layered on this table.