Search Results fte_wsh_trips_pk

Overview

FTE_WSH_TRIPS is a Transportation Execution (FTE) table in Oracle E-Business Suite that records the many-to-many association between transportation trips and trip segments. It resides in the FTE schema and is classified as VALID across EBS 12.1.1 and 12.2.2. The table functions as a junction or cross-reference entity: a single trip may consist of multiple trip segments, and a given segment may be associated with more than one trip depending on the planning scenario being modeled. This design supports trip consolidation, load planning, and itinerary tracking within the transportation management workflow.

From a Data Vault modeling perspective, the mined FK structure suggests this object behaves as a link table — a standalone associative entity resolving a many-to-many relationship between two structural hubs (the trip and the segment). It carries no dependent satellite content of its own beyond audit and descriptive attributes, which is consistent with its role as a pure connector.

Key Information Stored

FTE_WSH_TRIPS contains 28 documented columns. The most significant are:

• FTE_TRIP_ID — Identifies the transportation trip (the FTE-owned trip header). Part of the composite primary key and the first column of the unique business key index.
• WSH_TRIP_ID — Identifies the associated WSH trip. Part of the composite primary key and the second column of the business key.
• SEQUENCE_NUMBER — Orders the segments or associations within a trip, supporting deterministic itinerary sequencing.
• CREATION_DATE, CREATED_BY — Standard audit columns recording who created the association and when.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Audit trail for the most recent modification.
• PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID — Concurrent program context identifying the process that created or last updated the record.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — The standard Oracle EBS descriptive flexfield (DFF) columns, available for client-specific extensions.

The surrogate-style composite primary key is FTE_WSH_TRIPS_PK (WSH_TRIP_ID, FTE_TRIP_ID). The unique index FTE_WSH_TRIPS_U1 (FTE_TRIP_ID, WSH_TRIP_ID) acts as the reverse-ordered business-key candidate, enforcing uniqueness of the association regardless of column order. Note that the two structures reference the same column pair in inverted sequence; effectively they guarantee one association row per trip/segment pair.

Common Use Cases and Queries

Typical usage involves reconciling trip headers with their constituent segments and reporting on trip composition.

• Enumerate segments for a trip: SELECT wsh_trip_id, sequence_number FROM fte.fte_wsh_trips WHERE fte_trip_id = :p_trip_id ORDER BY sequence_number;
• Find all trips referencing a segment: SELECT fte_trip_id FROM fte.fte_wsh_trips WHERE wsh_trip_id = :p_segment;
• Audit recent associations: filter on CREATION_DATE or LAST_UPDATE_DATE within a date range, joined to lookup for CREATED_BY.
• DFF extraction: query ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 after joining FND_FLEX_VALUES to interpret contextual segments.

Reporting use cases include trip consolidation analysis, carrier load utilization, and gap detection where segments exist without a parent trip association.

Related Objects

The metadata classifies this object as standalone, so FK definitions are not surfaced. Based on the documented keys and the FTE domain model, the following objects are significant:

• WSH_TRIPS — joined on FTE_WSH_TRIPS.WSH_TRIP_ID = WSH_TRIPS.TRIP_ID.
• FTE_TRIPS (or the FTE trip header) — joined on FTE_WSH_TRIPS.FTE_TRIP_ID = FTE_TRIPS.TRIP_ID.
• WSH_TRIP_STOPS — provides the stop-level detail for each linked segment.
• WSH_DELIVERY_ASSIGNMENTS — relates deliveries to the trips referenced here.
• FND_FLEX_VALUES / FND_FLEX_VALUES_TL — resolve the DFF attribute contexts.
• FND_USER — resolves CREATED_BY and LAST_UPDATED_BY.
• FND_CONCURRENT_REQUESTS — resolves REQUEST_ID and PROGRAM_ID audit context.