Search Results wsh_delivery_legs_ob_grp_v




Overview
Explore in AI Chat

Overview

The APPS.WSH_DELIVERY_LEGS_OB_GRP_V view is a Shipping Execution (WSH) reporting and integration object in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes delivery leg records that belong to outbound or internal outbound shipments, and it is primarily intended to serve Oracle Business Group (OB_GRP) style reporting and downstream integration requirements where delivery leg detail must be combined with shipment direction filtering.

The view is defined as a join between WSH_DELIVERY_LEGS and WSH_NEW_DELIVERIES. The join condition restricts the result set to deliveries where the shipment direction, taken through NVL(WND.SHIPMENT_DIRECTION,'O'), is either 'O' (Outbound) or 'IO' (Internal Outbound). Consequently, inbound deliveries are excluded from the view, and it presents a directional subset of delivery legs rather than the complete population held in the base table.

The view is listed in ETRM with status VALID, owner APPS, and product attribution to WSH — Shipping Execution, confirming it is a supported, active object rather than a deprecated or invalid artifact.

Underlying Base Objects

The documented referenced base objects are the synonyms WSH_DELIVERY_LEGS and WSH_NEW_DELIVERIES. The view text aliases them as WDL and WND respectively and joins them on WDL.DELIVERY_ID = WND.DELIVERY_ID. Because the objects are referenced through synonyms, the physical tables reside in their owning schemas while APPS exposes them in the standard EBS fashion.

WSH_DELIVERY_LEGS supplies the substantive leg-level attributes — identifiers, stops, weights, volumes, audit columns, tracking and proof-of-delivery fields, and quantity columns. WSH_NEW_DELIVERIES contributes only the shipment direction attribute used for filtering, but that single column governs which legs qualify for the view.

The view therefore represents a directional projection: every row corresponds to a delivery leg whose parent delivery is outbound or internal outbound. It does not introduce aggregation; cardinality matches the qualifying rows of WSH_DELIVERY_LEGS.

Key Columns

The columns most relevant to reporting and to the search term "delivered_quantity" include the following:

Common Use Cases and Queries

Typical uses include delivered-versus-loaded-versus-received quantity reconciliation, outbound delivery leg tracking, proof-of-delivery monitoring, and integration extracts feeding transportation or analytics systems that must ignore inbound shipments.

  • Extracting delivered quantities by leg or delivery.
  • Comparing loaded, delivered, and received quantities to identify discrepancies.
  • Reporting open legs by STATUS_CODE or LOAD_TENDER_STATUS.
  • Auditing proof-of-delivery state through POD_FLAG and POD_DATE.
SELECT delivery_leg_id,
       delivery_id,
       sequence_number,
       status_code,
       delivered_quantity,
       loaded_quantity,
       received_quantity
FROM   apps.wsh_delivery_legs_ob_grp_v
WHERE  status_code = 'CLOSED'
ORDER  BY delivery_id, sequence_number;

SELECT delivery_id,
       SUM (delivered_quantity) delivered_qty
FROM   apps.wsh_delivery_legs_ob_grp_v
GROUP  BY delivery_id;

Because the view filters on shipment direction, queries issued against it automatically exclude inbound legs, which simplifies reporting logic in outbound-oriented processes.