Search Results fte_trips_u1

Overview

FTE.FTE_TRIPS is a transactional table in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 transportation and freight management schema (owner: FTE). It stores trip header records that group freight movements, delivery legs, and freight cost lines under a single transportation trip identifier. A trip represents a logical unit of transportation activity — which may be a single-leg or multi-leg movement — and serves as the parent for downstream delivery and cost detail. In the Oracle Transportation Management/FTE integration context, the table enables consolidated tracking of shipments from dispatch through closure.

From a heuristic Data Vault modeling perspective, FTE_TRIPS is classified as a hub candidate, since its primary key (FTE_TRIP_ID) is a surrogate identifier that is referenced by multiple downstream tables as a foreign key. It functions as an anchor for trip-level business events, with its descriptive attributes (Name, Status Code, Private Trip) behaving more like satellite-style context than rigid hub columns. The documented schema exposes 31 columns, of which many are standard EBS Who Columns and descriptive flexfield segments.

Key Information Stored

The most operationally significant columns include:

• FTE_TRIP_ID (NUMBER) — surrogate primary key, populated from sequence FTE_TRIPS_S. Also the single column of unique index FTE_TRIPS_U1 (business-key candidate) in tablespace APPS_TS_TX_IDX.
• NAME (VARCHAR2(30)) — transportation trip name used for user-facing identification.
• STATUS_CODE (VARCHAR2(30)) — trip lifecycle state; valid values are OP (Open), IT (In Transit), and CL (Closed), validated against lookup FTE_TRIP_STATUS.
• PRIVATE_TRIP (VARCHAR2) — boolean-style flag where Y denotes private trip and N denotes public trip.
• ROUTE_ID — link to the route definition associated with the trip.
• VALIDATION_REQUIRED (VARCHAR2) — reserved for future use.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard Who columns capturing audit trail.
• PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID — enhanced Who columns identifying the concurrent program and request that last modified the record.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 (VARCHAR2(150) each) — descriptive flexfield (DFF) segments for extensibility.

Common Use Cases and Queries

Typical uses include trip status reporting, freight cost reconciliation, and delivery leg tracking. A common query lists open trips with associated routes:

SELECT t.fte_trip_id, t.name, t.status_code, t.private_trip, t.route_id
FROM fte.fte_trips t
WHERE t.status_code = 'OP';

Freight cost analysts join FTE_TRIPS to WSH_FREIGHT_COSTS to reconcile trip-level charges. Dispatch reporting frequently filters on PRIVATE_TRIP = 'N' to isolate public transportation. Because ATTRIBUTE columns are DFF segments, reports often pivot DFF values into named business fields. Querying by the unique index FTE_TRIPS_U1 means filtering on FTE_TRIP_ID, which is the most selective access path.

Related Objects

• WSH_DELIVERY_LEGS — references FTE_TRIPS via FTE_TRIP_ID; stores the physical legs of each trip.
• WSH_FREIGHT_COSTS — references FTE_TRIPS via FTE_TRIP_ID; holds actual freight charges per trip.
• WSH_FREIGHT_COSTS_INTERFACE — references FTE_TRIPS via FTE_TRIP_ID; staging table for inbound freight cost data.
• FTE_TRIPS_S — sequence generating the FTE_TRIP_ID primary key.
• FTE_TRIP_STATUS — lookup governing STATUS_CODE values (OP, IT, CL).

Note the Oracle internal-use warning: FTE.FTE_TRIPS should be accessed only through standard Oracle Applications programs rather than direct DML, except in sanctioned reporting and integration scenarios.