Search Results vehicle_organization_id




Overview
Explore in AI Chat

Overview

APPS.WSHFV_TRIPS is a read-only reporting view in Oracle E-Business Suite (12.1.1 / 12.2.2) that presents trip header information drawn from the Oracle Shipping (WSH) module. A trip is a logical grouping of shipments assigned to a single vehicle and driver for one or more delivery runs; the underlying transactional entity is stored in the WSH_TRIPS table. The view is designated "FV" (a translatable/descriptive Flexfield-like view) because several of its columns replace stored codes with their user-facing lookup meanings — a technique commonly used to support Oracle Discoverer and Oracle Business Intelligence (OBIEE) reporting, where raw codes are not meaningful to end users. Several columns (for example the ship method and status columns) are rendered as pseudo-formula tokens such as '_LA:WST1.STATUS_CODE:WSH_LOOKUPS:TRIP_STATUS:MEANING', which instruct the reporting layer to resolve a lookup meaning at runtime rather than exposing the code directly. The view applies a Read Only constraint and is typically queried through its synonym in the APPS schema.

Underlying Base Objects

The view is defined over four base tables, each referenced by a synonym under the APPS schema: WSH_TRIPS, MTL_SYSTEM_ITEMS, MTL_PARAMETERS, and HR_ALL_ORGANIZATION_UNITS. WSH_TRIPS is joined to itself — the self-join on WST1.ARRIVE_AFTER_TRIP_ID = WST2.TRIP_ID (outer) links a trip to the trip it follows, allowing the arrive-after trip name to be displayed alongside the primary trip. The vehicle item and its description come from MTL_SYSTEM_ITEMS, joined on organization and inventory item. MTL_PARAMETERS supplies the organization code, and HR_ALL_ORGANIZATION_UNITS supplies the organization name. All joins to the supporting master data tables are outer joins ((+)), so a trip row is returned even when the vehicle item, organization parameters, or organization unit are not defined.

Key Columns

The view exposes TRIP_ID and NAME as the primary identifiers. STATUS_CODE is resolved to the TRIP_STATUS lookup meaning, and SHIP_METHOD_CODE to the SHIP_METHOD meaning. The SHIPMENTS_TYPE_FLAG column is the field named in the user's search: it distinguishes the type of shipment the trip carries, historically used to differentiate outbound ('O') movements from manufacturing or movement-order type trips (commonly 'M'). The view's filter restricts results with NVL(WST1.SHIPMENTS_TYPE_FLAG,'O') IN ('O','M') and applies the same predicate to the self-joined WST2 row, meaning only trips whose (null-defaulted) shipments type flag is 'O' or 'M' are visible. Other notable columns include ARRIVE_AFTER_TRIP_ID and ARRIVE_AFTER_TRIP_NAME, VEHICLE_ITEM_ID, VEHICLE_NUMBER, VEHICLE_NUM_PREFIX, VEHICLE_ORGANIZATION_ID, CARRIER_ID, ROUTE_ID, ROUTING_INSTRUCTIONS, PLANNED_FLAG (resolved to the YES_NO meaning), and the standard audit columns CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN.

Common Use Cases and Queries

The view is ordinarily used for vehicle and trip reporting, printing trip manifests, and extracting trip data into downstream systems. Because it joins organization units and parameters, it also supports organization-level trip reporting. A typical query follows:

  • Listing active outbound trips with vehicle and status meaning:
    SELECT trip_id, name, vehicle_number, ship_method_code, status_code, planned_flag
    FROM apps.wshfv_trips
    WHERE vehicles_type_flag IS NOT NULL;
  • Filtering by shipments type flag:
    SELECT trip_id, name, shipments_type_flag, arrive_after_trip_name
    FROM apps.wshfv_trips
    WHERE nvl(shipments_type_flag,'O') = 'M';
  • Joining to trip stops or shipment details for manifest reporting, using TRIP_ID as the key, or eliminating self-joined rows by excluding records whose ARRIVE_AFTER_TRIP_ID is not null.

Note that because the view is Read Only and the shipment-type predicate is embedded in the view definition, records with a shipments type flag outside ('O','M') will never be returned, regardless of the WHERE clause supplied by the query.