Search Results net_weight




Overview
Explore in AI Chat

Overview

APPS.WSH_LOAD_TENDER_CARGO_V is a Shipping Execution (WSH) view in Oracle E-Business Suite 12.1.1 and 12.2.2 that presents delivery cargo information in a denormalized, container-oriented structure suitable for load tendering and shipment reporting. The view flattens the relationship between a delivery, its assigned container instances, and the individual items packed within those containers into a single row per cargo combination. This design supports outbound integration with transportation management systems, carrier load-tender messages, and ad hoc reporting where the container-to-item hierarchy must be exposed without navigating the underlying assignment tables directly. The view is owned by the APPS schema and holds VALID status in the ETRM metadata. A distinctive feature is the computed CARGO_PK column, which concatenates the delivery identifier, container name, and item delivery detail identifier to produce a synthetic primary key for cargo records. The user search term item_serial_number maps directly to a column exposed by this view, making it a common entry point for serial-number-driven shipment queries.

Underlying Base Objects

The view is defined over three documented base objects, all referenced as synonyms in the APPS schema:

Both joins to WSH_DELIVERY_DETAILS are outer joins ((+)), so deliveries without an assigned container or item detail still appear in the result set. The container alias WDD1 provides container attributes such as CONTAINER_NAME, SEAL_CODE, SERIAL_NUMBER, and weight/volume figures, while WDD2 provides item attributes including SERIAL_NUMBER (aliased as ITEM_SERIAL_NUMBER), ITEM_DESCRIPTION, hazard classification, and shipped/delivered quantities.

Key Columns

Common Use Cases and Queries

The view is typically queried to report container contents, trace serially controlled items within shipments, and feed load-tender interfaces. A representative query retrieving items by serial number is:

  • SELECT cargo_pk, delivery_id, container_number, item_detail_id, item_serial_number, item_shipped_quantity FROM wsh_load_tender_cargo_v WHERE item_serial_number = :serial_number;
  • SELECT delivery_id, container_number, item_description, item_shipped_quantity FROM wsh_load_tender_cargo_v WHERE delivery_id = :delivery_id ORDER BY container_number;
  • SELECT container_number, item_hazard_code, item_country_of_origin FROM wsh_load_tender_cargo_v WHERE delivery_id = :delivery_id AND item_hazard_code IS NOT NULL;

Because the view applies outer joins, queries should account for NULL container or item columns when a delivery has not yet been fully packed. Filtering on ITEM_SERIAL_NUMBER is the most direct way to locate a specific serially controlled unit across all deliveries and containers.