Search Results item_hazard_code




Overview
Explore in AI Chat

Overview

APPS.WSH_POD_CARGO_V is a PL/SQL view owned by the APPS schema and registered in FND Design Data under the application short name WSH (Shipping Execution). It presents Proof of Delivery (POD) cargo information in a denormalized, flat structure that combines container-level and item-level detail for a delivery. The view surfaces cargo identification, container attributes (number, seal, type, description, quantity, gross/net weight, volume), bill of lading, and delivery identifiers alongside line-item shipping attributes such as shipped quantity, delivered quantity, shipping tolerance, hazardous classification, country of origin, and customer PO number. In Oracle EBS 12.1.1 and 12.2.2 the object carries a VALID status and is documented within ETRM, making it a supported reference point for reporting and integration rather than a private implementation detail. Its principal role is to give downstream consumers—custom reports, interfaces, and analytics—a single queryable surface for POD cargo facts without requiring joins across the individual Shipping Execution base tables.

Underlying Base Objects

The ETRM metadata identifies five referenced base objects, each accessed through a synonym: WSH_DELIVERY_ASSIGNMENTS, WSH_DELIVERY_DETAILS, WSH_DELIVERY_LEGS, WSH_DOCUMENT_INSTANCES, and WSH_NEW_DELIVERIES. These are the canonical Shipping Execution tables. WSH_NEW_DELIVERIES supplies delivery-level context (delivery identifiers and related header data), WSH_DELIVERY_DETAILS supplies the line and item-level attributes, WSH_DELIVERY_ASSIGNMENTS links delivery details to their parent delivery, WSH_DELIVERY_LEGS provides the leg or routing context used to derive bill of lading and carrier-related information, and WSH_DOCUMENT_INSTANCES contributes document-instance data that supports the cargo and container-level identification. The view resolves these relationships into a single row-per-cargo structure, which is why columns such as DELIVERY_ID, ITEM_DETAIL_ID, ITEM_CONTAINER_ID, and CONTAINER_INSTANCE_ID appear together even though they originate from different base tables.

Key Columns

Common Use Cases and Queries

Typical usage includes POD reconciliation, container and cargo reporting, shipment tolerance analysis, and extraction into external systems. A frequent query pattern filters by delivery and selects the shipped quantity together with its UOM:

  • SELECT delivery_id, item_detail_id, item_shipped_quantity, item_ship_quantity_uom, item_delivered_quantity FROM apps.wsh_pod_cargo_v WHERE delivery_id = :p_delivery_id;
  • SELECT bill_of_lading_number, container_number, container_quantity, container_quantity_uom, container_gross_weight FROM apps.wsh_pod_cargo_v WHERE bill_of_lading_number = :p_bol;
  • SELECT cargo_pk, item_description, item_hazard_code, item_country_of_origin FROM apps.wsh_pod_cargo_v WHERE item_hazard_code IS NOT NULL;

Because the view is a read-only projection over Shipping Execution base tables, it is suitable for SELECT-based reporting and integration only; no DML should be directed against it. Consumers should be aware that row cardinality depends on the granularity of delivery details and container instances, and that UOM columns (including ITEM_SHIP_QUANTITY_UOM) return the code defined in the underlying Shipping Execution data rather than a converted value.