Search Results wsh_locations




Overview
Explore in AI Chat

Overview

WSH_LOCATIONS is a Shipping Execution (WSH) table that stores shipping location definitions used throughout the outbound logistics and transportation lifecycle in Oracle E-Business Suite Release 12.1.1 and 12.2.2. The object records the physical or logical points at which a shipment, trip, or stop originates, terminates, or is staged, including addresses, geospatial coordinates, and consolidation settings. Its primary key is WSH_LOCATIONS_PK, defined on the WSH_LOCATION_ID column, and the table is owned by the WSH schema with a VALID status in the ETRM registry.

The metadata classifies WSH_LOCATIONS as standalone under the heuristic Data Vault mining, meaning no foreign key dependencies were detected outbound from this table. In Data Vault modeling terms, this suggests the table behaves primarily as a hub, holding a durable keyed list of shipping location entities rather than acting as a link or satellite. Modeling teams may therefore treat WSH_LOCATION_ID as a business hub key, with descriptive attributes potentially modeled as satellites, though the standalone classification is heuristic and should be validated against actual FK behavior.

Key Information Stored

The table contains 49 documented columns. The most significant are:

Common Use Cases and Queries

WSH_LOCATIONS is queried when building trip plans, validating stop addresses, or reporting on consolidation behavior. A typical pattern joins the primary key to trip stops:

  • Active shipping locations: SELECT wsh_location_id, name, city, country FROM wsh_locations WHERE inactive_date IS NULL;
  • Trip stop enrichment: SELECT t.trip_id, t.stop_sequence, l.name, l.city FROM wsh_trip_stops t JOIN wsh_locations l ON t.wsh_location_id = l.wsh_location_id;
  • Consolidation candidates: filter on consolidation_flag = 'Y' for pooling analyses.
  • Owner mapping: join to WSH_LOCATION_OWNERS to determine which operating unit or carrier owns each location.

Reporting use cases include geospatial dashboards (LATITUDE/LONGITUDE), timezone-aware scheduling, and address-quality audits against external mapping data.

Related Objects

The documented foreign keys reveal the following dependent objects referencing WSH_LOCATIONS via WSH_LOCATION_ID:

  • WSH_TRIP_STOPS — the operational trip stop lines that reference each shipping location.
  • WSH_TRIP_STOPS_INTERFACE — the open interface staging table that carries WSH_LOCATION_ID during trip import.
  • WSH_LOCATION_OWNERS — associates locations with their owning parties or organizations.

Beyond the documented FK set, shipping execution logic typically also relates WSH_LOCATIONS to carrier, calendar, and delivery routing components through the LOCATION_ID and SOURCE_LOCATION_ID columns, but the three tables above are the primary referential dependents established in ETRM metadata.