Search Results fte_trip_moves_interface




Overview
Explore in AI Chat

Overview

FTE_TRIP_MOVES_INTERFACE is an integration staging table in the Oracle E-Business Suite Transportation Execution module (FTE). It records the association between trip-level and move-level interface records as inbound transportation data is processed into the EBS data model. In releases 12.1.1 and 12.2.2 the table is owned by the FTE schema and carries a status of VALID, with a documented physical schema of 33 columns.

The table acts as a transient repository during the transformation of external trip and move data into their permanent counterparts. Each row links interface records derived from WSH_TRIPS_INTERFACE and FTE_MOVES_INTERFACE to the previously resolved WSH_TRIPS and FTE_MOVES records. It also references the FTE_TRIP_MOVES relationship table, which holds the persistent trip-to-move association once processing completes. The heuristic Data Vault classification mined from the foreign key structure is standalone. In practical terms, this suggests the table is best modeled as an independent interface or staging entity rather than as a strict hub, link, or satellite, reflecting its role as a transient landing structure rather than a durable business entity.

Key Information Stored

Among the 33 documented columns, the following are of principal importance:

The surrogate primary key is a system-generated identifier, distinct from any natural business key; the documented metadata lists no additional unique index beyond FTE_TRIP_MOVES_INTERFACE_PK.

Common Use Cases and Queries

This table is principally queried during transportation interface troubleshooting — for example, reconciling pending trip and move interface rows, verifying that sequence assignments were preserved, or diagnosing processing failures in the concurrent request chain. A representative join resolves interface rows to their permanent counterparts:

SELECT tm.TRIP_MOVE_INTERFACE_ID, tm.SEQUENCE_NUMBER, tm.INTERFACE_ACTION_CODE,
  t.TRIP_NAME, m.MOVE_ID, tm.REQUEST_ID
 FROM FTE.FTE_TRIP_MOVES_INTERFACE tm, WSH.WSH_TRIPS t, FTE.FTE_MOVES m
 WHERE tm.TRIP_ID = t.TRIP_ID
  AND tm.MOVE_ID = m.MOVE_ID
  AND tm.REQUEST_ID = :request_id;

Reporting use cases include auditing interface volume per concurrent request, monitoring unresolved rows where TRIP_ID or MOVE_ID remain null, and confirming ordering fidelity for multi-stop trips. Because records are transitional, queries should be scoped by REQUEST_ID or creation date rather than treated as a historical archive.

Related Objects

  • FTE_TRIP_MOVES — the persistent trip-to-move association, referenced via TRIP_MOVE_ID.
  • FTE_MOVES_INTERFACE — inbound move interface rows, referenced via MOVE_INTERFACE_ID.
  • WSH_TRIPS_INTERFACE — inbound trip interface rows, referenced via TRIP_INTERFACE_ID.
  • FTE_MOVES — the resolved move records, referenced via MOVE_ID.
  • WSH_TRIPS — the resolved trip records, referenced via TRIP_ID.
  • FTE_TRIP_MOVES_INTERFACE_PK — the primary key index enforcing uniqueness on TRIP_MOVE_INTERFACE_ID.