Search Results fte_moves




Overview
Explore in AI Chat

Overview

The FTE_MOVES table is a core transactional data object within the Oracle Transportation Execution (FTE) module of Oracle E-Business Suite (EBS) releases 12.1.1 and 12.2.2. It serves as the central repository for recording and managing all planned and executed freight moves. A "move" in this context represents a discrete segment of a shipment's journey, such as a truck haul from a warehouse to a port or an ocean leg between two terminals. The table is fundamental to the operational tracking of freight activities, linking shipment planning with actual carrier assignments, equipment, and execution events. Its data underpins critical FTE processes, including freight cost accruals, carrier performance analysis, and real-time shipment visibility.

Key Information Stored

While the provided ETRM excerpt is concise, standard FTE table structures and functional knowledge indicate the table stores comprehensive move-level details. The primary key is the MOVE_ID, a unique system-generated identifier for each freight move record. Essential columns typically include SHIPMENT_ID to link to the parent shipment in FTE_SHIPMENTS, and LEG_ID to associate the move with a specific itinerary leg. The table also holds critical operational data such as the planned and actual dates for departure and arrival, the assigned CARRIER_ID and VEHICLE_ID, and references to the origin and destination locations (FROM_LOCATION_ID, TO_LOCATION_ID). Status fields (e.g., MOVE_STATUS) track the progression from planned to in-transit to completed, while columns for rate and cost information facilitate financial tracking.

Common Use Cases and Queries

This table is central to operational reporting and process automation. A common use case is generating a shipment progress report by querying move statuses and dates. For instance, to identify all delayed moves for a specific carrier, one might query planned versus actual arrival dates. Another critical use is in interfaces with transportation management systems (TMS) or mobile driver applications, where move records are updated with real-time tracking events. Sample SQL patterns often involve joins to related master data tables:

  • Open Move Analysis: SELECT m.move_id, s.shipment_number, m.move_status, m.planned_departure_date FROM fte_moves m, fte_shipments s WHERE m.shipment_id = s.shipment_id AND m.move_status NOT IN ('COMPLETED', 'CANCELLED');
  • Carrier Performance: Aggregating move data by carrier to measure on-time pickup and delivery performance against service commitments.

Related Objects

The FTE_MOVES table is a hub within the FTE schema, with numerous dependencies. Its primary relationship is with the FTE_SHIPMENTS table via the SHIPMENT_ID foreign key. It is also closely linked to FTE_LEGS for itinerary planning and FTE_VEHICLES for equipment assignment. Key transactional tables like FTE_MOVE_COSTS and FTE_ACC_RECONCILIATION likely reference MOVE_ID for financial processing. For reporting and application access, standard EBS practice suggests the existence of public views such as FTE_MOVES_V. The table is also integral to APIs within the FTE_PUB package for creating and updating move data programmatically.