EBS Reference

WSH_TRIPS

Schema: WSHtransaction

The trip header — a carrier/vehicle journey over an ordered set of stops, with ship method, carrier, and vehicle attributes

Module: Shipping & DeliveriesNot org-partitioned

Notes

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

master: Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.

Fields

9 fields · 1 key

Table fields: position, field name, description, data type, and flags. 9 fields.
#	Field	Description	Type	Flags
1	TRIP_ID	Surrogate key of the trip	NUMBER	Key
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_TRIPSon Databricks — real DATE columns need no conversion, and the org anchor and the LAST_UPDATE_DATE watermark are already in place. Set your Unity Catalog location, schema, and org values below; they’re substituted into the SQL and the copy button.

Query parameters

CatalogSchemaTrip IDwatermark

Include optional filters (2)

-- ============================================================
-- 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;

4 parameters not filled: <catalog>, <schema>, <TRIP_ID>, <watermark>

Relationships

1-hop neighbors — click a table to navigate there. FND lookup decode and translation edges are highlighted; they’re the joins newcomers most often get wrong.

Join details

WSH_TRIP_STOPSWSH_TRIPSforeign key · N:1
ON WSH_TRIP_STOPS.TRIP_ID = WSH_TRIPS.TRIP_ID

Browse more Shipping & Deliveriestables →