Search Results item_shipped_quantity




Overview
Explore in AI Chat

Overview

APPS.WSH_POD_CARGO_V is a reporting view in the Oracle E-Business Suite Shipping Execution module (WSH). It exposes Proof of Delivery (POD) cargo information, presenting shipment contents in a flattened, query-ready format that combines container-level and item-level shipment detail. The view is registered under the FND design data path WSH.WSH_POD_CARGO_V, resides in the APPS schema, and is documented with a status of VALID in ETRM 12.2.2. Its principal role is to support shipment tracking, POD processing, and outbound logistics reporting, where consumers require visibility into what was shipped, in which container, and in what delivered quantity. Because the object is a view rather than a table, it holds no data of its own; it derives its rows at runtime from underlying Shipping Execution base objects and inherits the security and access model that APPS synonyms provide. Users searching for the column ITEM_DELIVERED_QUANTITY will find this view particularly relevant, as it is one of the item-level quantity columns the view exposes for reporting actual delivered amounts against a shipment line.

Underlying Base Objects

The documented base objects referenced by WSH_POD_CARGO_V are WSH_DELIVERY_ASSIGNMENTS, WSH_DELIVERY_DETAILS, WSH_DELIVERY_LEGS, WSH_DOCUMENT_INSTANCES, and WSH_NEW_DELIVERIES, all referenced through APPS synonyms. Each contributes a distinct layer of the shipment model:

  • WSH_NEW_DELIVERIES — the header-level delivery record, supplying delivery identifiers used to join shipments to their contents.
  • WSH_DELIVERY_DETAILS — the delivery line detail, the source of item-level attributes such as description, shipped quantity, and delivered quantity.
  • WSH_DELIVERY_ASSIGNMENTS — the association between delivery details and containers, linking item lines to the containers in which they are packed.
  • WSH_DOCUMENT_INSTANCES — document instance information, including bills of lading and customs or transportation documentation tied to the cargo.
  • WSH_DELIVERY_LEGS — the leg or routing information for a delivery, supporting transport and container movement context.

The view joins these objects to produce a single row per cargo or container-item combination, which is why both container-level columns (for example, CONTAINER_QUANTITY and CONTAINER_GROSS_WEIGHT) and item-level columns (for example, ITEM_SHIPPED_QUANTITY and ITEM_DELIVERED_QUANTITY) appear together in the output.

Key Columns

The view exposes identifiers and descriptive attributes that allow reporting at both container and item granularity:

Because the view flattens these attributes, ITEM_DELIVERED_QUANTITY is available alongside shipped quantity and container context without requiring the report author to reconstruct the joins manually.

Common Use Cases and Queries

Typical scenarios include POD reconciliation, shipment variance analysis, and container manifest reporting. The following query returns delivered versus shipped quantity for a delivery:

SELECT delivery_id,
       item_description,
       item_shipped_quantity,
       item_delivered_quantity,
       item_ship_quantity_uom
FROM   apps.wsh_pod_cargo_v
WHERE  delivery_id = :p_delivery_id;

To identify short deliveries or over-shipments, filter on a variance expression:

SELECT cargo_pk,
       container_number,
       item_description,
       item_shipped_quantity,
       item_delivered_quantity
FROM   apps.wsh_pod_cargo_v
WHERE  item_delivered_quantity < item_shipped_quantity;

For container-level manifests, group by container attributes:

SELECT container_number,
       container_type,
       bill_of_lading_number,
       SUM(item_delivered_quantity) delivered_qty
FROM   apps.wsh_pod_cargo_v
GROUP  BY container_number, container_type, bill_of_lading_number;

Because the view is exposed as an APPS synonym, it can be queried from custom reports, BI Publisher templates, and interface programs without direct grants to the underlying Shipping tables. Reports should be written defensively, since the view returns one row per container-item combination and aggregation is frequently required.