WSH_TRIPS
Schema: WSHtransactionThe trip header — a carrier/vehicle journey over an ordered set of stops, with ship method, carrier, and vehicle attributes
Same OP/IT/CL status ladder as trip stops, from the same data-dictionary comment. Not org-striped — push operating-unit filters down to the delivery details.
What the badges mean
- Schema: INV
- Schema: the Oracle product schema that owns the table (INV, ONT, WSH, PO, BOM, WIP, MRP, MSC, AR, AP, GL, HR, APPLSYS) — tells you which product family the object belongs to, not who can query it.
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.
- OU-striped (ORG_ID)
- Rows are scoped to an operating unit. A landed extract carries every operating unit’s rows — filter or join on
ORG_ID, and don’t confuse it withORGANIZATION_ID(see the quirks guide). - Per inventory org
- Rows are scoped to an inventory organization (plant or warehouse) via
ORGANIZATION_ID— a different partition from OU-striped tables (see the quirks guide). - Language-striped
- The table carries a
LANGUAGEcolumn (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to oneLANGUAGEor a join multiplies rows (see the quirks guide). - View
- This is an APPS-schema convenience view, not a physical table. Extract the base tables it joins instead — views can be slow at scale and aren't guaranteed stable across patches.
Structural facts — how the table is partitioned, not a trap by itself
Join & extract hazards — verify before you rely on this
Fields
9 fields · 1 key
9 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | TRIP_ID | Surrogate key of the trip | NUMBER | Primary-key field |
| 2 | NAME | The trip name users see | VARCHAR2 | |
| 3 | STATUS_CODE | OP open, IT in transit, CL closed — same ladder as trip stops, from the same dictionary comment | VARCHAR2 | |
| 4 | PLANNED_FLAG | Whether the trip is planned | VARCHAR2 | |
| 5 | CARRIER_ID | Freight carrier running the trip | NUMBER | |
| 6 | SHIP_METHOD_CODE | Ship method | VARCHAR2 | |
| 7 | VEHICLE_ITEM_ID | The vehicle, modeled as an item | NUMBER | |
| 8 | VEHICLE_NUMBER | Vehicle identifier | VARCHAR2 | |
| 9 | ARRIVE_AFTER_TRIP_ID | Trip sequencing constraint — this trip arrives after that one | NUMBER |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading WSH_TRIPS on Databricks — real DATE columns need no conversion, and the org anchor is already in place. The optional LAST_UPDATE_DATE watermark is included. Set your Unity Catalog location, schema, and org values below; they’re substituted into the SQL and the copy button.
4 parameters not filled: <catalog>, <schema>, <TRIP_ID>, <watermark>
-- ============================================================
-- Table : WSH_TRIPS — The trip header — a carrier/vehicle journey over an ordered set of stops, with ship method, carrier, and vehicle attributes
-- Purpose: Column-selected read of WSH_TRIPS — auto-generated from field metadata
-- Grain : One row per TRIP_ID
-- Notes : Auto-generated skeleton for Oracle EBS R12 data landed in your lakehouse. Dates are real DATE/TIMESTAMP columns — no conversion needed. WHO audit columns omitted (see the quirks guide); the optional LAST_UPDATE_DATE watermark filter supports incremental extracts.
-- ============================================================
SELECT
t.TRIP_ID AS "Surrogate key of the trip",
t.NAME AS "The trip name users see",
t.STATUS_CODE AS "OP open, IT in transit, CL closed — same ladder as trip stops, from the same dictionary comment",
t.PLANNED_FLAG AS "Whether the trip is planned",
t.CARRIER_ID AS "Freight carrier running the trip",
t.SHIP_METHOD_CODE AS "Ship method",
t.VEHICLE_ITEM_ID AS "The vehicle, modeled as an item",
t.VEHICLE_NUMBER AS "Vehicle identifier",
t.ARRIVE_AFTER_TRIP_ID AS "Trip sequencing constraint — this trip arrives after that one"
FROM <catalog>.<schema>.WSH_TRIPS t
WHERE
1 = 1 -- no partition column on this table; the filters below are optional
-- AND t.TRIP_ID = <TRIP_ID>
-- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>' -- WHO watermark, bulk-stamped by batch jobs; see quirks guide #who-columns
ORDER BY t.TRIP_ID;Verified September 2026
Relationships
Diagram of 1-hop neighbors — join details below. FND lookup decode and translation edges are highlighted; they’re the joins newcomers most often get wrong.
Loading relationship diagram…
Join details
ON WSH_TRIP_STOPS.TRIP_ID = WSH_TRIPS.TRIP_ID
More Shipping & Deliveries tables
- WSH_DELIVERY_ASSIGNMENTSThe assignment bridge between delivery details and deliveries — also encodes container nesting, where a detail's parent row is the LPN it is packed into; a detail reaches its delivery only through this table
- WSH_DELIVERY_DETAILSThe atomic shipping line — one row per shippable unit of demand from order lines (or WIP/PO sources), plus container rows, tracking requested/picked/shipped quantities through pick release and ship confirm
- WSH_DELIVERY_LEGSDelivery legs — the mapping from a delivery to the trip stops where it is picked up and dropped off; the only path from deliveries to trips
- WSH_NEW_DELIVERIESThe delivery header — a named grouping of delivery details shipped together from one location toward one final drop-off, carrying the ship-confirm date, carrier, waybill, and weights
- WSH_TRIP_STOPSTrip stops — one row per pickup or drop-off point on a trip, with planned and actual arrival/departure timestamps; the actual departure at the pickup stop is the gate-out time ship confirm writes