Search Results item_country_of_origin




Overview
Explore in AI Chat

Overview

APPS.WSH_POD_CARGO_V is a shipping execution view in Oracle E-Business Suite, owned by the APPS schema and registered under FND Design Data as WSH.WSH_POD_CARGO_V. It presents a consolidated, denormalized picture of cargo associated with outbound deliveries in the Warehouse Management and Shipping Execution (WSH) module. The view bridges container-level information (containers, seals, gross and net weights, volumes) with item-level shipment detail, including shipped quantities, delivered quantities, and units of measure. Its status is VALID at both the 12.1.1 and 12.2.2 releases, though the exact column set may vary slightly between releases; the 12.2.2 metadata is the reference used here.

Because it exposes a single, flat row containing both container and item attributes, the view is most commonly used for proof-of-delivery (POD) reporting, carrier documentation, and packing list generation. The naming prefix WSH_POD indicates its association with proof-of-delivery and cargo reporting rather than transactional workflow. The user's search term, item_shipped_quantity, maps directly to the ITEM_SHIPPED_QUANTITY column, one of the primary quantitative measures exposed by the view.

Underlying Base Objects

The view is defined over five WSH synonyms:

  • WSH_NEW_DELIVERIES — the delivery header table, supplying delivery identity and BILL_OF_LADING_NUMBER, which is derived from the delivery/leg attributes (e.g., the waybill or bill of lading).
  • WSH_DELIVERY_ASSIGNMENTS — links delivery details to their parent delivery, establishing the join between delivery header and detail rows.
  • WSH_DELIVERY_DETAILS — the delivery line/detail table, providing item-level attributes such as shipped quantity, delivered quantity, unit of measure, serial number, and item-level tolerances.
  • WSH_DELIVERY_LEGS — the delivery leg table, contributing routing/leg information, and typically the source of the bill of lading number when the leg is a shipment leg.
  • WSH_DOCUMENT_INSTANCES — holds document instance data such as container/cargo identifiers, container numbers, seal numbers, and container instance IDs.

The primary key exposed by the view is CARGO_PK, a concatenated VARCHAR2(120) surrogate key derived from the underlying container and item identifiers. CONTAINER_INSTANCE_ID and ITEM_DETAIL_ID provide the natural foreign-key references back to the container instance and delivery detail records respectively.

Key Columns

The view exposes approximately thirty-two columns organized into container-level and item-level groups.

Common Use Cases and Queries

Typical uses include POD reconciliation (comparing ITEM_SHIPPED_QUANTITY against ITEM_DELIVERED_QUANTITY), packing list and bill-of-lading reporting, and integration feeds to carriers or third-party logistics systems.

Example 1 — retrieve shipped quantity for a delivery:

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

Example 2 — container and item summary by bill of lading:

SELECT bill_of_lading_number, container_number, item_description,
       item_shipped_quantity, item_delivered_quantity
FROM   apps.wsh_pod_cargo_v
WHERE  bill_of_lading_number = :p_bol;

Example 3 — shipment variance analysis:

SELECT cargo_pk, item_shipped_quantity - item_delivered_quantity AS variance
FROM   apps.wsh_pod_cargo_v
WHERE  item_shipped_quantity <> item_delivered_quantity;

Because the view draws on multiple WSH tables, queries are usually restricted by DELIVERY_ID or BILL_OF_LADING_NUMBER to limit scan cost. Data is presented for reporting and integration; direct DML against the view is not supported.