Search Results fte_trips_pk

Overview

FTE_TRIPS is a core table within the Oracle E-Business Suite Transportation Execution module (FTE). It stores transportation trip information, representing the top-level grouping of delivery legs and freight activities that are planned, executed, and tracked as a single logical journey. In EBS 12.1.1 and 12.2.2, the table resides in the FTE schema, which is owned by the Transportation Execution product and is used by carrier, planning, and freight cost processing functionality.

From a Data Vault modeling perspective, the metadata’s heuristic classification is standalone. This suggests FTE_TRIPS behaves as an independent hub-like object: it holds a durable business key (FTE_TRIP_ID) with descriptive attributes and status, but is not itself a dependent satellite of another hub within the documented FK structure. No parent foreign keys are recorded, meaning the table is a primary originating entity rather than a subordinate detail table.

Key Information Stored

The table contains 31 documented columns. The most significant are:

• FTE_TRIP_ID — The surrogate primary key and the value forming the FTE_TRIPS_PK constraint. It is also the sole documented candidate for the FTE_TRIPS_U1 unique index, meaning it functions as both surrogate and business key.
• NAME — The user-facing trip identifier or description.
• STATUS_CODE — Current lifecycle state of the trip (e.g., planned, in-transit, closed).
• PRIVATE_TRIP — Flag indicating whether the trip is privately managed rather than publicly visible or shareable.
• VALIDATION_REQUIRED — Indicator that the trip requires validation before execution or costing.
• ROUTE_ID — Reference to the route associated with the trip, linking execution to planned routing.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS who-columns for audit and concurrency control.
• PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID — Concurrent program context that created or last modified the row.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — The standard DFF (descriptive flexfield) column set for extensibility.

The surrogate key FTE_TRIP_ID is the technically enforced primary key, while FTE_TRIPS_U1 documents uniqueness on the same column, confirming it as the single documented business-key candidate.

Common Use Cases and Queries

Typical use cases include trip status reporting, freight cost attribution, delivery leg rollups, and DFF-based operational reporting. A representative query joining trips to their delivery legs:

• SELECT t.fte_trip_id, t.name, t.status_code, l.delivery_leg_id FROM fte.fte_trips t, wsh.wsh_delivery_legs l WHERE t.fte_trip_id = l.fte_trip_id;
• SELECT fte_trip_id, name, status_code, creation_date FROM fte.fte_trips WHERE status_code = :status ORDER BY creation_date DESC;
• SELECT t.fte_trip_id, SUM(c.freight_cost) FROM fte.fte_trips t, wsh.wsh_freight_costs c WHERE t.fte_trip_id = c.fte_trip_id GROUP BY t.fte_trip_id;

Because the DFF attributes (ATTRIBUTE1–15) are exposed, reporting teams frequently extract them for customer-specific trip classifications.

Related Objects

Documented foreign key relationships indicate that FTE_TRIPS is referenced by the following significant objects:

• WSH_DELIVERY_LEGS.FTE_TRIP_ID — Delivery legs that belong to the trip, joined on FTE_TRIP_ID.
• WSH_FREIGHT_COSTS.FTE_TRIP_ID — Freight costs charged against the trip, joined on FTE_TRIP_ID.
• WSH_FREIGHT_COSTS_INTERFACE.FTE_TRIP_ID — The interface/staging table through which freight costs are loaded and associated with the trip.

No additional tables are documented as referencing FTE_TRIPS in the provided metadata, but the WSH (Shipping Execution) family of tables is the primary downstream consumer of trip data.