Results for “expected_arrival_date”

50+ results




Overview
Explore in AI Chat

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

Overview

The WSH_DELIVERIES_DPW_LOV_V view is an Oracle E-Business Suite database object owned by the APPS schema and classified under the OE – Order Entry product family. As its name and documented description indicate, it exposes open or planned deliveries created using the Departure Planning Workbench (DPW). The view functions as a List of Values (LOV) source, providing a filtered, joined result set suitable for value-selection UI elements, concurrent program parameters, and reporting queries that need to restrict delivery choices to those participating in departure planning.

Its role in EBS 12.1.1 and 12.2.2 is consistent: it presents a narrow, curated set of delivery attributes joined to the associated departure. Because the view surfaces ACTUAL_DEPARTURE_ID directly — the very column the user searched for — it serves as a convenient entry point for resolving which departure a planned or open delivery is tied to, without requiring direct navigation of the larger WSH_DELIVERIES table.

Underlying Base Objects

The documented metadata lists two referenced base objects, both resolved through synonyms in the APPS schema:

  • WSH_DELIVERIES (aliased DEL) — the primary driving table containing delivery header information.
  • WSH_DEPARTURES (aliased DEP) — the departure header table supplying the departure name.

The view text joins these with an outer join on the departure side:

  • DEL.SOURCE_CODE = 'D' restricts results to deliveries (as opposed to other source categories).
  • DEL.STATUS_CODE IN ('OP','PL') restricts results to Open (OP) and Planned (PL) deliveries.
  • DEL.ACTUAL_DEPARTURE_ID = DEP.DEPARTURE_ID(+) is an outer join, so deliveries without an assigned actual departure still appear, with departure attributes returned as null.

This structure means reporting against the view inherits Oracle's standard multi-org and security behavior as governed by the underlying base tables.

Key Columns

  • DELIVERY_ID — Primary key of the delivery; the join anchor to WSH_DELIVERIES.
  • DELIVERY_NAME — User-facing delivery name (from DEL.NAME).
  • ORGANIZATION_ID — Inventory organization that owns the delivery; drives multi-org filtering.
  • STATUS_CODE — Delivery status; constrained by the view to OP (Open) or PL (Planned).
  • SOURCE_CODE — Constrained to 'D'; confirms the record represents a delivery.
  • EXPECTED_ARRIVAL_DATE — Projected arrival date for the delivery.
  • ACTUAL_DEPARTURE_ID — Identifier of the departure to which the delivery is assigned; the outer-joined departure key.
  • DEPARTURE_NAME — Name of the departure, retrieved via the outer join to WSH_DEPARTURES.
  • CUSTOMER_ID, ULTIMATE_SHIP_TO_ID, INTERMEDIATE_SHIP_TO_ID — Party and location identifiers describing the shipment destination and consignee chain.
  • FOB_CODE, FREIGHT_TERMS_CODE, FREIGHT_CARRIER_CODE, CURRENCY_CODE — Commercial and logistics attributes carried on the delivery header.

Common Use Cases and Queries

Typical uses include populating an LOV for delivery selection within departure planning flows, reporting on open and planned deliveries that are or are not yet assigned to a departure, and validating the ACTUAL_DEPARTURE_ID linkage between a delivery and its departure.

List all open and planned departures with their assigned departure names:

  • SELECT delivery_id, delivery_name, status_code, actual_departure_id, departure_name FROM apps.wsh_deliveries_dpw_lov_v;

Identify deliveries not yet assigned to any actual departure (exploiting the outer join):

  • SELECT delivery_id, delivery_name, organization_id FROM apps.wsh_deliveries_dpw_lov_v WHERE actual_departure_id IS NULL;

Filter to a single departure, useful when resolving the search term actual_departure_id to tangible delivery records:

  • SELECT delivery_id, delivery_name, expected_arrival_date FROM apps.wsh_deliveries_dpw_lov_v WHERE actual_departure_id = :p_departure_id;

Because the view pre-filters on delivery source and status, consumers avoid re-implementing that logic and can rely on a consistent, departure-planning-scoped result set.