Search Results maximum_load_weight




Overview
Explore in AI Chat

Overview

WSHFV_DEPARTURE is an APPS-owned reporting view in the Oracle E-Business Suite Order Entry (OE) product family. It is classified as VALID and carries the "Retrofitted" designation, indicating it was carried forward into the 12.1.1 and 12.2.2 code lines to preserve backwards compatibility for downstream reporting and integration artifacts that reference it. The view presents a denormalized, reporting-friendly representation of shipping departures managed by Oracle Shipping Execution (WSH). Rather than requiring report authors to join departure records against item master and report set data manually, WSHFV_DEPARTURE pre-assembles that information into a single queryable object.

Each row represents a single departure, identified by DEPARTURE_ID, enriched with the name of any predecessor departure it is scheduled to arrive after, the report set assigned to it, and descriptive attributes of the vehicle item used for the movement. The "FV" prefix follows Oracle's convention for reporting views distinct from base transactional tables.

Underlying Base Objects

The view is defined over four referenced objects, of which three are documented in the 12.2.2 metadata as synonyms: WSH_DEPARTURES, SO_REPORT_SETS, and MTL_SYSTEM_ITEMS. WSH_DEPARTURES appears twice in the FROM clause, aliased DEP1 and DEP2, producing a self-join. SO_REPORT_SETS and MTL_SYSTEM_ITEMS are both outer-joined, so a departure row is returned even when no report set or vehicle item is associated with it.

  • WSH_DEPARTURES (DEP1) — the driving table; supplies departure identity, status, dates, weights, volumes, seal code, and audit columns.
  • WSH_DEPARTURES (DEP2) — self-join on ARRIVE_AFTER_DEPARTURE_ID, supplying the predecessor departure's name and planned/actual departure dates.
  • SO_REPORT_SETS (SRS) — outer-joined on REPORT_SET_ID, supplying the report set name.
  • MTL_SYSTEM_ITEMS (MSI) — outer-joined on VEHICLE_ITEM_ID and ORGANIZATION_ID, supplying vehicle description, unit of measure, tare weight, maximum load weight and volume, and minimum fill percent.

Key Columns

Common Use Cases and Queries

The view supports departure-level reporting in shipping and transportation dashboards, freight audit extracts, and reconciliation reports. A frequent pattern is retrieving all departures associated with a specific report set:

SELECT departure_id, departure_name, report_set_name, status_code, planned_departure_date, vehicle_number, gross_weight FROM apps.wshfv_departure WHERE report_set_id = :p_report_set_id;

Another common scenario identifies departures lacking a valid report set assignment, which typically indicates incomplete setup:

SELECT departure_id, departure_name, organization_id FROM apps.wshfv_departure WHERE report_set_id IS NULL AND status_code = 'OPEN';

Vehicle utilization analysis joins the capacity columns against measured load:

SELECT departure_name, vehicle_description, maximum_load_weight, gross_weight, fill_percent FROM apps.wshfv_departure WHERE organization_id = :p_org AND planned_departure_date BETWEEN :p_from AND :p_to;

Because SO_REPORT_SETS and MTL_SYSTEM_ITEMS are outer-joined in the view definition, queries filtering on REPORT_SET_ID will implicitly exclude departures with no report set, which is generally the intended behavior for report-set-scoped extracts.