Skip to content
EBS Reference

WSH_TRIP_STOPS

Schema: WSHtransaction

Trip 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

Identity
Notes

STATUS_CODE values OP (open), IT (in transit), and CL (closed) are spelled out in the data dictionary's own column comment. PENDING_INTERFACE_FLAG = 'Y' marks stops awaiting the interface run — a backlog signal.

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.

Structural facts — how the table is partitioned, not a trap by itself

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 with ORGANIZATION_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 LANGUAGE column (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to one LANGUAGE or a join multiplies rows (see the quirks guide).

Join & extract hazards — verify before you rely on this

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.
In field listings, the Key chip marks a primary-key field.

Fields

11 fields · 1 key

11 fields.

Table fields: position, field name, description, data type, and flags. 11 fields.
#FieldDescriptionTypeFlags
1STOP_IDSurrogate key of the stopNUMBER
Primary-key field
2TRIP_IDThe trip the stop belongs toNUMBER
3STOP_SEQUENCE_NUMBEROrder of the stop within the tripNUMBER
4STOP_LOCATION_IDThe stop's locationNUMBER
5STATUS_CODEOP open, IT in transit, CL closed — spelled out in the data dictionary's column commentVARCHAR2
6PLANNED_ARRIVAL_DATEPlanned arrivalDATE
7PLANNED_DEPARTURE_DATEPlanned departureDATE
8ACTUAL_ARRIVAL_DATEActual arrivalDATE
9ACTUAL_DEPARTURE_DATEActual departure — at the pickup stop this is the gate-out time ship confirm writesDATE
The table's primary analysis date — a real DATE column, no conversion needed
10DEPARTURE_GROSS_WEIGHTGross weight at departureNUMBER
11PENDING_INTERFACE_FLAGY while the stop awaits the interface run — a backlog signalVARCHAR2

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading WSH_TRIP_STOPS 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.

Query parameters

6 parameters not filled: <catalog>, <schema>, <STOP_ID>, <DATE_FROM>, <DATE_TO>, <watermark>

-- ============================================================
-- Table  : WSH_TRIP_STOPS — Trip 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
-- Purpose: Column-selected read of WSH_TRIP_STOPS — auto-generated from field metadata
-- Grain  : One row per STOP_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.STOP_ID AS "Surrogate key of the stop",
  t.TRIP_ID AS "The trip the stop belongs to",
  t.STOP_SEQUENCE_NUMBER AS "Order of the stop within the trip",
  t.STOP_LOCATION_ID AS "The stop's location",
  t.STATUS_CODE AS "OP open, IT in transit, CL closed — spelled out in the data dictionary's column comment",
  t.PLANNED_ARRIVAL_DATE AS "Planned arrival",
  t.PLANNED_DEPARTURE_DATE AS "Planned departure",
  t.ACTUAL_ARRIVAL_DATE AS "Actual arrival",
  t.ACTUAL_DEPARTURE_DATE AS "Actual departure — at the pickup stop this is the gate-out time ship confirm writes",
  t.DEPARTURE_GROSS_WEIGHT AS "Gross weight at departure",
  t.PENDING_INTERFACE_FLAG AS "Y while the stop awaits the interface run — a backlog signal"
FROM <catalog>.<schema>.WSH_TRIP_STOPS t
WHERE
  1 = 1  -- no partition column on this table; the filters below are optional
  -- AND t.STOP_ID = <STOP_ID>
  -- AND t.ACTUAL_DEPARTURE_DATE >= DATE '<DATE_FROM>'
  -- AND t.ACTUAL_DEPARTURE_DATE <= DATE '<DATE_TO>'
  -- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>'  -- WHO watermark, bulk-stamped by batch jobs; see quirks guide #who-columns
ORDER BY t.STOP_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.

Join details

  • WSH_DELIVERY_LEGSWSH_TRIP_STOPSforeign key · N:1
    ON WSH_DELIVERY_LEGS.PICK_UP_STOP_ID = WSH_TRIP_STOPS.STOP_ID
  • WSH_DELIVERY_LEGSWSH_TRIP_STOPSforeign key · N:1
    ON WSH_DELIVERY_LEGS.DROP_OFF_STOP_ID = WSH_TRIP_STOPS.STOP_ID
  • WSH_TRIP_STOPSWSH_TRIPSforeign key · N:1
    ON WSH_TRIP_STOPS.TRIP_ID = WSH_TRIPS.TRIP_ID

Browse more Shipping & Deliveries tables

More Shipping & Deliveries tables

Maintained by Summit Analytics, a supply chain analytics practice. The tools and references are free — the consulting is selective.

Part of the Summit Analytics reference library.

Work with the practice

Not affiliated with or endorsed by Oracle. Oracle and Oracle E-Business Suite are registered trademarks of Oracle and/or its affiliates.