Results for “wsh_container_contents_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

WSH_CONTAINER_CONTENTS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It belongs to the Order Entry (OE) product family and, as its name and ETRM description ("Container contents") indicate, exposes the line-level contents of packing containers used during the warehouse shipping and packing process. The view answers the operational and reporting question: "What items, in what quantities, from which order lines, are packed inside a given container?"

Because packing information is scattered across shipping container tables, picking tables, and order tables, this view pre-joins them into a single denormalized result set. That makes it suitable for container manifests, packing verification reports, shipping documentation, and integration extracts that require container-to-order traceability without reconstructing the underlying join graph each time.

Underlying Base Objects

The view is defined over six base objects, all referenced through APPS synonyms:

• WSH_PACKED_CONTAINERS (aliased PC) — the driving container record, supplying CONTAINER_ID, DELIVERY_ID, and ORGANIZATION_ID.
• SO_PICKING_LINE_DETAILS (SPLD) — the packing detail that links a container to a picking line; supplies SHIPPED_QUANTITY, exposed as PACKED_QUANTITY.
• SO_PICKING_LINES_ALL (SPLA) — the picking line, providing INVENTORY_ITEM_ID, ORDER_LINE_ID, and PICKING_HEADER_ID.
• SO_LINES_ALL (SOLA) — the order line, supplying LINE_NUMBER.
• SO_HEADERS_ALL (SOHA) — the order header, supplying ORDER_NUMBER.
• MTL_SYSTEM_ITEMS (MSI) — the item master, supplying DESCRIPTION and PRIMARY_UOM_CODE.

All joins are inner joins on the natural keys (CONTAINER_ID, PICKING_LINE_ID, INVENTORY_ITEM_ID, ORDER_LINE_ID, HEADER_ID). The item join is additionally constrained by ORGANIZATION_ID (MSI.ORGANIZATION_ID = PC.ORGANIZATION_ID), so item attributes are resolved for the warehouse organization holding the container. A residual predicate SPLA.PICKING_HEADER_ID + 0 > 0 filters out picking lines not tied to a picking header.

Key Columns

• CONTAINER_ID — identifier of the packing container; primary grouping key for manifest output.
• DELIVERY_ID — the delivery to which the container belongs, enabling linkage to delivery and trip planning data.
• INVENTORY_ITEM_ID — the packed item.
• DESCRIPTION — item description from MTL_SYSTEM_ITEMS.
• PICKING_LINE_DETAIL_ID — the specific packing detail row.
• ORDER_LINE_ID — the sales order line fulfilled.
• PACKED_QUANTITY — the shipped quantity packed into the container, sourced from SO_PICKING_LINE_DETAILS.SHIPPED_QUANTITY.
• UOM_CODE — the item's primary unit of measure.
• ORDER_LINE_NUMBER and ORDER_NUMBER — human-readable order references.

Common Use Cases and Queries

Typical uses include printing container manifests, auditing packed versus ordered quantities, and feeding shipping confirmations to external systems. A simple manifest query by container:

• SELECT container_id, order_number, order_line_number, inventory_item_id, description, packed_quantity, uom_code FROM apps.wsh_container_contents_v WHERE container_id = :p_container_id;

Contents of all containers on a delivery:

• SELECT container_id, order_number, order_line_number, description, packed_quantity FROM apps.wsh_container_contents_v WHERE delivery_id = :p_delivery_id ORDER BY container_id, order_line_number;

Aggregated packed quantity per order line for reconciliation:

• SELECT order_number, order_line_number, inventory_item_id, SUM(packed_quantity) total_packed FROM apps.wsh_container_contents_v WHERE order_number = :p_order GROUP BY order_number, order_line_number, inventory_item_id;

Because the view performs multi-table joins with no bind-friendly filtering of its own, queries should always constrain on container_id, delivery_id, or order_number to keep execution efficient on large shipping volumes.