Results for “vehicle_item_id”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

WSHFV_TRIPS is a read-only Business Intelligence System (BIS) business view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the WSH – Shipping Execution product module. It is a "full" BIS business view for trips, meaning it exposes the complete set of translated, key-flex, descriptive-flex, and security attributes associated with the WSH_TRIPS entity in a denormalized, reporting-friendly form. The view is registered as VALID in the ETRM 12.2.2 metadata and is available across 12.1.1 and 12.2.2 releases. Its principal role is to support Oracle Discoverer, BIS workbooks, and downstream integrations by presenting trips with decoded lookup meanings, descriptive flexfield context, and resolved foreign-key descriptions rather than raw coded identifiers. The embedded directives in the view text — such as _LA (lookup attribute), _KF (key flexfield), and _DF (descriptive flexfield) — are interpreted by the BIS layer to generate user-friendly column headings and joins automatically.

Underlying Base Objects

The view is defined over four base objects, all accessed via public synonyms in the APPS schema:

• WSH_TRIPS — aliased twice as WST1 (the driving trip) and WST2 (the predecessor trip joined via ARRIVE_AFTER_TRIP_ID).
• MTL_SYSTEM_ITEMS — joined on VEHICLE_ORGANIZATION_ID and VEHICLE_ITEM_ID to resolve the vehicle's inventory item description.
• MTL_PARAMETERS — supplies the organization code for the vehicle's owning organization.
• HR_ALL_ORGANIZATION_UNITS — supplies the organization name.

All joins to the vehicle-related tables are outer joins (indicated by the (+) operator), so a trip row is returned even when no vehicle item or organization is defined. The view is filtered with NVL(SHIPMENTS_TYPE_FLAG,'O') IN ('O','M') on both trip aliases, restricting output to outbound and miscellaneous shipment trip types. A row-level security predicate on VEHICLE_ORGANIZATION_ID enforces organization access, and the view is declared WITH READ ONLY.

Key Columns

The most frequently referenced columns include:

• VEHICLE_ITEM_ID — the inventory item identifier of the vehicle assigned to the trip, and the KF join key to MTL_SYSTEM_ITEMS. This is the column returned as _KF:VEHICLE_ITEM_ID.
• TRIP_ID and NAME — the primary key and human-readable trip name.
• _LA:STATUS_CODE — decoded trip status meaning from the WSH_LOOKUPS TRIP_STATUS lookup type.
• VEHICLE_DESCRIPTION and VEHICLE_NUMBER — the vehicle item description and its externally visible number, plus VEHICLE_NUM_PREFIX.
• ARRIVE_AFTER_TRIP_ID / ARRIVE_AFTER_TRIP_NAME — the predecessor trip in a chained trip sequence.
• _LA:SHIP_METHOD_CODE, _LA:PLANNED_FLAG — decoded ship method and Yes/No planned flag meanings.
• CARRIER_ID, ROUTE_ID, VEHICLE_ORGANIZATION_ID, ORGANIZATION_CODE, ORGANIZATION_NAME — carrier, routing, and organization context.
• ROUTING_INSTRUCTIONS, SHIPMENTS_TYPE_FLAG, _DF — free-text routing, shipment type, and descriptive flexfield context.

Common Use Cases and Queries

A typical integration or reporting query pivots on the vehicle item. To list trips for a given vehicle item:

• SELECT trip_id, name, vehicle_number, vehicle_description, vehicle_organization_id FROM wshfv_trips WHERE vehicle_item_id = :p_item_id;

To report active trips by status for a warehouse, filter on organization and the decoded status column. To trace trip chaining, self-join on ARRIVE_AFTER_TRIP_ID. Because the view enforces organization security and is read-only, it is safe for use in Discoverer workbooks, OBIEE extracts, and read-only integration interfaces without risk of DML.