Results for “wsh_trips”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

WSH_TRIPS is the master table for trip records within the Oracle E-Business Suite Shipping Execution (WSH) module. A trip represents a planned movement of goods using one or more vehicles along a defined route, consolidating deliveries and shipments for transportation. This table is the central repository for trip-level attributes including carrier assignment, routing, equipment, and workflow state, and is used by both Oracle Shipping and Oracle Transportation Management (OTM) integration flows in EBS 12.1.1 and 12.2.2.

From a Data Vault modeling perspective, the metadata heuristic classifies WSH_TRIPS as a hub, since TRIP_ID acts as a surrogate key referenced by numerous downstream tables. This classification is a modeling suggestion rather than a physical designation — the table also carries descriptive business attributes typical of a satellite.

Key Information Stored

WSH_TRIPS contains 72 documented columns. The most significant include:

• TRIP_ID — Surrogate primary key (WSH_TRIPS_PK), also defined as unique index WSH_TRIPS_U1.
• NAME — Trip name; alternate unique key (WSH_TRIPS_U2).
• STATUS_CODE — Current lifecycle state of the trip.
• CARRIER_ID — Selected carrier for the trip.
• VEHICLE_ITEM_ID, VEHICLE_NUMBER, VEHICLE_NUM_PREFIX, VEHICLE_ORGANIZATION_ID — Equipment identity and ownership.
• ROUTE_ID, ROUTE_LANE_ID, LANE_ID — Routing definitions; LANE_ID references FTE_LANES.
• SHIP_METHOD_CODE, MODE_OF_TRANSPORT, FREIGHT_TERMS_CODE, SERVICE_LEVEL — Transport characteristics.
• LOAD_TENDER_STATUS, LOAD_TENDER_NUMBER, LOAD_TENDERED_TIME, CARRIER_RESPONSE — Tendering workflow state.
• PLANNED_FLAG, CONSOLIDATION_ALLOWED, IGNORE_FOR_PLANNING — Planning controls.
• WF_NAME, WF_PROCESS_NAME, WF_ITEM_KEY, TRIP_WF_PROCESS — Oracle Workflow integration.
• BOOKING_NUMBER, VESSEL, VOYAGE_NUMBER, PORT_OF_LOADING, PORT_OF_DISCHARGE — Ocean/booking details.
• RANK_ID — References AS_SALES_LEAD_RANKS_B.
• ATTRIBUTE1–15 — DFF extensibility.
• Audit columns such as CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE.

Common Use Cases and Queries

Typical reporting includes trip status tracking, tendering analysis, carrier performance, and OTM/FTE integration monitoring. A representative pattern joining trips to their stops:

• SELECT t.trip_id, t.name, t.status_code, t.carrier_id, s.stop_sequence FROM wsh_trips t JOIN wsh_trip_stops s ON s.trip_id = t.trip_id WHERE t.status_code = 'CLOSED';
• Exceptions by trip: SELECT e.trip_id, e.exception_type, t.name FROM wsh_exceptions e JOIN wsh_trips t ON t.trip_id = e.trip_id;
• Freight cost aggregation: SELECT trip_id, SUM(cost) FROM wsh_freight_costs GROUP BY trip_id;
• Picking batch linkage via WSH_PICKING_BATCHES.TRIP_ID.

Related Objects

WSH_TRIPS is referenced by many child tables through TRIP_ID, and references two parent tables.

• WSH_TRIP_STOPS (TRIP_ID) — Stop sequences and addresses for the trip.
• WSH_EXCEPTIONS (TRIP_ID) — Trip-level exceptions.
• WSH_FREIGHT_COSTS (TRIP_ID) — Freight cost allocations.
• WSH_PICKING_BATCHES (TRIP_ID) — Picking batch association.
• WSH_TRIPS_INTERFACE (TRIP_ID) — Inbound interface staging.
• FTE_TRIP_MOVES (TRIP_ID) — Transportation execution moves.
• FTE_LANES — Parent of LANE_ID.
• AS_SALES_LEAD_RANKS_B — Parent of RANK_ID.
• WMS_SHIPPING_TRANSACTION_TEMP (TRIP_ID) — Warehouse integration.