Search Results fte_wsh_trips_u1

Overview

FTE.FTE_WSH_TRIPS is a cross-reference (intersection) table in the Oracle E-Business Suite 12.1.1 / 12.2.2 schema owned by the FTE module (Oracle Transportation Execution, part of the Logistics / Warehouse Shipping family). The table sits at the junction between Oracle's FTE trip entity, which models a transportation trip managed inside Transportation Execution, and the WSH (Shipping Execution) trip entity defined in the Oracle Shipping module. Each row records one linkage between an FTE trip and its corresponding WSH trip, with a sequence number that positions the trip segment within the transportation trip.

Because every row is pure association data — it holds foreign keys to both sides plus audit and descriptive flexfield columns — the heuristically mined Data Vault classification of this table is link. A link classification is a modeling suggestion only: it indicates the table's grain is the relationship between two business keys (FTE_TRIP_ID and WSH_TRIP_ID) rather than an independent business entity. The physical primary key, FTE_WSH_TRIPS_PK, is composed of (WSH_TRIP_ID, FTE_TRIP_ID), confirming that the pairing of the two trips is the row's identity. The design intent is to let Transportation Execution and Shipping Execution stay synchronized — one master trip in Shipping can map to one or more trips in FTE, and each mapping is tracked here.

Key Information Stored

The essential columns of FTE_WSH_TRIPS fall into four categories:

• FTE_TRIP_ID (NUMBER) — Foreign key to FTE_TRIPS. Identifies the trip record maintained in Oracle Transportation Execution.
• WSH_TRIP_ID (NUMBER) — Foreign key to WSH_TRIPS. Identifies the trip record maintained in Oracle Shipping Execution. Together with FTE_TRIP_ID this forms the physical primary key FTE_WSH_TRIPS_PK.
• SEQUENCE_NUMBER (NUMBER) — The sequence number of the trip segment within a transportation trip. This controls ordering when a single logical shipment is decomposed into legs.
• FTE_WSH_TRIPS_U1 — A unique index (columns FTE_TRIP_ID, WSH_TRIP_ID) created in the APPS_TS_TX_IDX tablespace. Along with the primary key it acts as a business-key candidate, enforcing that the same trip pair cannot be inserted twice.
• Standard Who columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN capture insert and change audit trails.
• Enhanced Who columns — PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, and REQUEST_ID identify the concurrent program or request that last modified the row, supporting traceability of background processing.
• Descriptive flexfield columns — ATTRIBUTE_CATEGORY plus ATTRIBUTE1 through ATTRIBUTE15 (all VARCHAR2(150)) provide the DFF storage used to extend the table without schema change.

Notably, the table does not store weights, quantities, dates, or statuses; all business attributes live in the referenced FTE_TRIPS and WSH_TRIPS tables. This keeps FTE_WSH_TRIPS narrow and its row count proportional to the number of trip pairings rather than shipment volume.

Common Use Cases and Queries

The table is primarily consumed by Oracle Applications programs rather than end users, but reporting and reconciliation queries on it are common when investigating integration problems between Transportation Execution and Shipping Execution. Typical scenarios include:

• Trip reconciliation — Verifying that every FTE trip has a corresponding WSH trip, or vice versa, often after a delivery interface or autopack run.
• Sequence validation — Confirming that SEQUENCE_NUMBER values are contiguous and correctly ordered within a logical trip.
• Duplicate detection — Comparing counts against FTE_WSH_TRIPS_U1 constraints when data is loaded through open interfaces or custom tools.
• Change auditing — Querying LAST_UPDATE_DATE, LAST_UPDATED_BY, or REQUEST_ID to identify which concurrent program created or altered a mapping.

A representative join pattern to resolve the two trips is:

SELECT f.FTE_TRIP_ID,
       f.WSH_TRIP_ID,
       f.SEQUENCE_NUMBER,
       t.TRIP_NAME
FROM   FTE.FTE_WSH_TRIPS f,
       FTE.FTE_TRIPS      t
WHERE  f.FTE_TRIP_ID = t.TRIP_ID
AND    f.WSH_TRIP_ID = :p_trip_id
ORDER  BY f.SEQUENCE_NUMBER;

Because the table sits in the APPS_TS_TX_DATA tablespace, transaction-oriented reports and BI Publisher extracts can use it directly. Any attempt to insert or update it outside standard Oracle Applications programs carries data-integrity risk and is not supported.

Related Objects

• FTE.FTE_TRIPS — The parent FTE trip header. Join on FTE_TRIP_ID = FTE_TRIPS primary key column.
• WSH.WSH_TRIPS — The Shipping Execution trip header. Join on WSH_TRIP_ID = WSH_TRIPS primary key column.
• WSH.WSH_TRIP_STOPS — Trip legs and stops; sequence alignment with FTE_WSH_TRIPS.SEQUENCE_NUMBER often matters here.
• WSH.WSH_DELIVERIES — Deliveries assigned to the WSH trip; indirect dependency through WSH_TRIP_ID.
• FTE.FTE_TRIPS_LEGS — FTE leg and stop detail for a transportation trip referenced by FTE_TRIP_ID.
• WSH.WSH_DELIVERY_ASSIGNMENTS — Links deliveries to trips and is frequently queried alongside FTE_WSH_TRIPS for full shipment tracing.
• FTE_WSH_TRIPS_U1 / FTE_WSH_TRIPS_PK — The unique index and primary key constraints that guarantee one row per trip pairing.

All of these objects belong to the FTE and WSH schemas and should be accessed only through supported Oracle Applications interfaces in 12.1.1 and 12.2.2.