Search Results gross_weight




Overview
Explore in AI Chat

Overview

WSH_DEPARTURES_V is an APPS-owned database view in Oracle E-Business Suite, classified under the OE (Order Entry) product family, though its functional scope spans the Shipping Execution module. The view consolidates departure records used in departure planning and ship confirm processes, presenting a denormalized, reporting-friendly projection of the WSH_DEPARTURES entity together with supporting descriptive attributes. Its stated purpose, per the ETRM documentation, is to expose "Departures for departure planning or ship confirm."

The view is marked VALID and is defined on the base object WSH_DEPARTURES (accessed via a synonym in 12.2.2) along with several lookup and item master sources. Because it joins in interpretable values such as status meanings and report set names, it is well suited for operational reporting, ad hoc querying, and integration extracts where raw foreign keys would otherwise require additional lookups. In both 12.1.1 and 12.2.2 the view retains the same owner and structure, making it a stable reference point for departure-related reporting.

Underlying Base Objects

The ETRM 12.2.2 metadata documents the following referenced base objects for WSH_DEPARTURES_V:

  • WSH_DEPARTURES (SYNONYM) — the primary departure table, self-joined as DEP1 (the departure itself) and DEP2 (the preceding departure referenced by ARRIVE_AFTER_DEPARTURE_ID).
  • MTL_SYSTEM_ITEMS (SYNONYM) — the item master, used to derive vehicle attributes such as description, primary UOM, maximum load weight, maximum volume, and minimum fill percent.
  • SO_LOOKUPS (SYNONYM) — the Order Entry lookup source, resolving STATUS_CODE against the 'SHIPPING_STATUS' lookup type to produce a readable STATUS meaning.
  • SO_REPORT_SETS (SYNONYM) — the report set definition source, surfacing REPORT_SET_NAME from REPORT_SET_ID.
  • FND_GLOBAL (PACKAGE) — the standard EBS context package referenced for session and responsibility context.

The joins on DEP2, SO_LOOKUPS, and SO_REPORT_SETS are implemented as outer joins (the (+) syntax), ensuring departure rows are retained even when no arriving departure, status meaning, or report set is present. This confirms the view is designed for completeness of the departure population rather than for inner-join filtering.

Key Columns

The view exposes an extensive column set. Notable columns include:

Common Use Cases and Queries

A frequent scenario is reporting departures together with their assigned report set name, which is the attribute implied by the "report_set_name" search. Because the view already resolves this value, no additional join to SO_REPORT_SETS is required.

  • Departures by report set: SELECT departure_id, departure_name, report_set_name, status, planned_departure_date FROM wsh_departures_v WHERE report_set_name = :p_report_set ORDER BY planned_departure_date;
  • Active departures with vehicle utilization: SELECT departure_name, vehicle_number, fill_percent, gross_weight, tare_weight FROM wsh_departures_v WHERE status = 'Open';
  • Departure sequencing review: SELECT departure_name, arrive_after_departure_name, planned_departure_date FROM wsh_departures_v WHERE arrive_after_departure_id IS NOT NULL;
  • Carrier and BOL extracts for ship confirm: SELECT bill_of_lading, freight_carrier_code, seal_code, routing_instructions FROM wsh_departures_v WHERE organization_id = :p_org;

Filtering by ORGANIZATION_ID is advisable in multi-organization environments, and report set queries should account for rows where REPORT_SET_ID is null, since the outer join permits departures without an assigned report set.