Search Results vehicle_description




Overview

APPS.WSH_DEPARTURE_TEMPLATES_V is an Oracle EBS shipping execution view that exposes departure template definitions together with a resolved vehicle description. Departure templates in Oracle Shipping represent reusable configurations for outbound departures, specifying the planned frequency, day and time, freight carrier, vehicle assignment, and routing instructions that govern how goods leave a warehouse or organization. This view provides a denormalized, report-friendly projection of the underlying WSH_DEPARTURE_TEMPLATES table, joining the vehicle inventory item to its master description in MTL_SYSTEM_ITEMS.

The view is owned by the APPS schema and is intended for reporting, inquiry, and integration purposes. Because it presents descriptive context (notably VEHICLE_DESCRIPTION) alongside the departure template attributes, it is well suited to reports and interfaces that must display human-readable vehicle information rather than just a vehicle item identifier. Reference to the object in the context of the search term "vehicle_description" is directly explained by the aliasing of MSI.DESCRIPTION as VEHICLE_DESCRIPTION in the view definition.

Underlying Base Objects

The view is defined over two documented base objects:

  • WSH_DEPARTURE_TEMPLATES (SYNONYM) — the primary table, aliased WDT in the view text, holding departure template definitions including organization, vehicle, carrier, and scheduling attributes.
  • MTL_SYSTEM_ITEMS (SYNONYM) — the item master, aliased MSI in the view text, supplying the vehicle item's description.

The join is an outer join: WHERE MSI.INVENTORY_ITEM_ID(+) = WDT.VEHICLE_ITEM_ID. The (+) operator on the MTL_SYSTEM_ITEMS side means the view retains departure template rows even when no matching vehicle item exists, in which case VEHICLE_DESCRIPTION is null. The view also exposes WDT.ROWID as ROW_ID, giving each row a stable identifier tied to the underlying base row.

Key Columns

Common Use Cases and Queries

The view is commonly used to report departure template configurations with readable vehicle descriptions, to validate that vehicle items are correctly assigned, and to drive downstream integrations that need carrier and scheduling detail. A typical listing query is:

SELECT departure_template_id, name, organization_id,
       vehicle_item_id, vehicle_description, vehicle_number,
       freight_carrier_code, planned_frequency, planned_day, planned_time
FROM   apps.wsh_departure_templates_v
WHERE  organization_id = :p_org_id;

To find templates whose vehicle description is missing (a symptom of an unassigned or invalid vehicle item), the outer-join semantics allow a simple filter:

SELECT departure_template_id, name, vehicle_item_id, vehicle_number
FROM   apps.wsh_departure_templates_v
WHERE  vehicle_description IS NULL;

Because flexfield and audit columns are exposed, the view also supports extracts for data migration or audit reporting, for example selecting the ATTRIBUTE columns alongside LAST_UPDATE_DATE to track recent configuration changes within a given organization.