Search Results fte_moves_interface




Overview
Explore in AI Chat

Overview

FTE_MOVES_INTERFACE is a staging and integration table within the Oracle E-Business Suite Transportation Execution (FTE) module. It resides in the FTE schema and holds inbound or outbound move records that are exchanged between the EBS transportation engine and external planning, execution, or third-party logistics systems. The table functions as a transient interface layer: records are loaded or generated here, validated, then promoted into or reconciled against the operational move tables. It is documented as VALID in both EBS 12.1.1 and 12.2.2, with a physical schema of 34 columns.

From a Data Vault modeling perspective, the metadata's heuristic classification places FTE_MOVES_INTERFACE as standalone. This suggests the object behaves as a self-contained staging entity rather than a classic hub, link, or satellite. In practice, its surrogate key and foreign-key references to FTE_MOVES and FTE_LANES give it satellite-like characteristics tied to move events, while the surrounding interface columns carry descriptive and audit payload normally associated with a transactional staging area.

Key Information Stored

The primary surrogate key is MOVE_INTERFACE_ID, enforced by the unique index FTE_MOVES_INTERFACE_PK. This column uniquely identifies each interface row and is the principal join target for dependent tables. The most operationally significant columns include:

  • MOVE_ID — foreign key to FTE_MOVES; links the interface row to the canonical move record.
  • LANE_ID — foreign key to FTE_LANES; identifies the transportation lane for the move.
  • MOVE_TYPE_CODE — classifies the movement type being interfaced.
  • SERVICE_LEVEL — the requested or planned service level for the move.
  • PLANNED_FLAG — indicates whether the move is a planned versus actual execution.
  • TP_PLAN_NAME — the transportation planning name associated with the movement.
  • CM_TRIP_NUMBER — the carrier management trip number for external tracking.
  • INTERFACE_ACTION_CODE — signals the intended processing action (for example, insert, update, or delete) during the interface run.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — standard audit columns.
  • PROGRAM_ID, PROGRAM_APPLICATION_ID, REQUEST_ID — identify the concurrent program and request that created or processed the row.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle EBS descriptive flexfield (DFF) columns for extensible, client-specific data captured at interface time.

The audit and DFF columns are essential for tracing interface activity and for supporting configurable extensions without schema changes.

Common Use Cases and Queries

FTE_MOVES_INTERFACE is typically queried during interface troubleshooting, reconciliation, and audit reporting. A common pattern retrieves unprocessed or recently loaded moves joined to their lane and canonical move records:

  • Reconciling staged interface rows against FTE_MOVES to detect moves that failed promotion.
  • Monitoring INTERFACE_ACTION_CODE distribution to confirm that inserts, updates, and deletes were applied as expected.
  • Auditing concurrent program activity by filtering on PROGRAM_ID, REQUEST_ID, or CREATION_DATE.
  • Reporting on planned versus actual moves using PLANNED_FLAG and SERVICE_LEVEL.
  • Extracting DFF attribute values (ATTRIBUTE1–15) for downstream analytics or third-party integration.

A representative query joins the interface to its parent move and lane using the documented foreign keys:

SELECT i.MOVE_INTERFACE_ID, i.MOVE_ID, m.MOVE_NAME,
       i.LANE_ID, l.LANE_NAME, i.MOVE_TYPE_CODE,
       i.SERVICE_LEVEL, i.PLANNED_FLAG, i.INTERFACE_ACTION_CODE
  FROM FTE.FTE_MOVES_INTERFACE i,
       FTE.FTE_MOVES m,
       FTE.FTE_LANES l
 WHERE i.MOVE_ID = m.MOVE_ID
   AND i.LANE_ID = l.LANE_ID;

Related Objects

The following objects are the most significant dependencies and references for FTE_MOVES_INTERFACE, based on the documented FK structure:

  • FTE_MOVES — referenced via MOVE_ID; the canonical move master holding operational move details.
  • FTE_LANES — referenced via LANE_ID; the lane definition used to route the movement.
  • FTE_TRIP_MOVES_INTERFACE — references this table through MOVE_INTERFACE_ID; links trip-level interface records to individual move interface rows.
  • FTE_MOVES_INTERFACE_PK — the unique index that enforces the primary key on MOVE_INTERFACE_ID and serves as the join anchor for dependent objects.

Together these objects form the interface and master-data spine used to load, validate, and reconcile transportation moves between EBS and external systems.