Search Results fte_trip_moves




Overview
Explore in AI Chat

Overview

FTE_TRIP_MOVES is a Transportation Execution (FTE) module table within Oracle E-Business Suite 12.1.1 and 12.2.2. It functions as an intersection or association table that links individual moves to trips, providing the sequencing and structural relationship between the two primary transportation entities. In practical terms, a trip represents a planned or executed journey (a vehicle, carrier, or shipment itinerary), while a move represents a discrete unit of movement associated with that trip. FTE_TRIP_MOVES records which moves belong to which trip, and in what order they occur along the trip's route or stop sequence.

The table resides in the FTE schema and is classified as VALID. Based on the foreign-key structure mined from the object relationships, the heuristic Data Vault classification is standalone. This suggests a modeling approach where the table can be treated as an independent construct rather than a pure link between two hubs, reflecting that it carries its own surrogate key (TRIP_MOVE_ID) and sequence attributes rather than merely resolving a many-to-many relationship. Developers modeling this object in a warehouse or reporting layer may still treat it as a link-style table joining the move and trip domains, but the presence of its own primary key and descriptive attributes supports a standalone treatment.

Key Information Stored

FTE_TRIP_MOVES contains 29 documented columns. The most important are:

Two additional unique indexes serve as business-key candidates: FTE_TRIP_MOVES_U1 on (MOVE_ID, TRIP_ID), which enforces that a given move appears only once per trip; and FTE_TRIP_MOVES_U2 on (MOVE_ID, SEQUENCE_NUMBER), which enforces unique sequencing of a move. Together these indexes confirm the table's role in maintaining consistent move-to-trip assignments.

Common Use Cases and Queries

Typical use cases involve retrieving the ordered list of moves for a trip, joining move details to trip headers, and reconciling trip-move associations during transportation planning or execution. A common query pattern joins FTE_TRIP_MOVES to both FTE_MOVES and WSH_TRIPS:

  • List all moves for a given trip in sequence: SELECT tm.SEQUENCE_NUMBER, tm.MOVE_ID FROM FTE_TRIP_MOVES tm WHERE tm.TRIP_ID = :trip_id ORDER BY tm.SEQUENCE_NUMBER;
  • Identify which trip a move belongs to: SELECT tm.TRIP_ID FROM FTE_TRIP_MOVES tm WHERE tm.MOVE_ID = :move_id;
  • Reporting on moves joined with trip headers via WSH_TRIPS for carrier and route analysis.
  • Reconciling interface data loaded through FTE_TRIP_MOVES_INTERFACE against the base table.

Related Objects

The most significant related objects are:

  • FTE_MOVES — Referenced via FTE_TRIP_MOVES.MOVE_ID; the parent entity for each move.
  • WSH_TRIPS — Referenced via FTE_TRIP_MOVES.TRIP_ID; the trip header holding routing and carrier context.
  • FTE_TRIP_MOVES_INTERFACE — The interface/staging table referencing FTE_TRIP_MOVES through TRIP_MOVE_ID, used for inbound data loading.
  • FTE_TRIP_MOVES_PK — Unique index on TRIP_MOVE_ID, the primary key constraint.
  • FTE_TRIP_MOVES_U1 and FTE_TRIP_MOVES_U2 — Unique indexes enforcing move-trip and move-sequence integrity.

Analysts querying transportation execution data should treat FTE_TRIP_MOVES as the central association object between trips and moves, paying particular attention to the sequence number when reconstructing route order.