Search Results wshfv_container_contents




Overview

WSHFV_CONTAINER_CONTENTS is a read-only BIS (Business Intelligence System) business view owned by the APPS schema in Oracle E-Business Suite. It is delivered as part of the WSH – Shipping Execution module and is documented with a status of VALID in both EBS 12.1.1 and 12.2.2. The view exposes the contents of shipping containers, where a container is modeled in the delivery data model as a parent delivery detail record and its contents are the child delivery details assigned beneath it. Each row returned by the view represents a single packed item residing inside a container, together with the container identity, the description of the container item, and the packed quantity and unit of measure.

Because it is a BIS business view, it is intended primarily for reporting, ad hoc query, and downstream integration rather than for transactional update. It is defined WITH READ ONLY, confirming that it cannot be used for DML. The user search term "source_line_number" corresponds directly to one of its exposed columns, SOURCE_LINE_NUMBER, which carries the originating order line reference for the packed content. This makes the view a convenient single source for answering questions about which sales order or transfer order lines have been packed into which containers.

Underlying Base Objects

The view is defined over three documented base objects:

  • WSH_DELIVERY_ASSIGNMENTS (SYNONYM) – alias WDA, provides the assignment link between child delivery details and their parent container delivery detail.
  • WSH_DELIVERY_DETAILS (SYNONYM) – aliased twice: WDD for the content (child) delivery detail, and DD1 for the parent record whose item description supplies the container description.
  • MTL_SYSTEM_ITEMS (SYNONYM) – alias MSI, outer-joined on INVENTORY_ITEM_ID and ORGANIZATION_ID to supply master item attributes.

The driving join enforces that WDA.PARENT_DELIVERY_DETAIL_ID is not null, so only records actually assigned into a container are returned. The NVL(WDD.LINE_DIRECTION, 'O') IN ('O', 'IO') predicate restricts results to outbound or internal outbound line directions, excluding inbound shipments. Outer joins to MTL_SYSTEM_ITEMS and to the parent delivery detail ensure contents are still reported even when the item master or container record is incomplete.

Key Columns

Common Use Cases and Queries

Typical uses include container manifest reporting, packing verification, and reconciliation of shipped quantities against order lines. Because SOURCE_LINE_NUMBER is exposed, the view supports traceability from a specific order line back to every container in which its items were packed.

A representative query to trace a line by its source line number:

  • SELECT container_id, container_description, delivery_id, source_header_number, source_line_number, item_description, packed_quantity, uom FROM apps.wshfv_container_contents WHERE source_line_number = :p_line_number;

A query to list all contents of a given container:

  • SELECT delivery_detail_id, source_header_number, source_line_number, item_description, packed_quantity, uom FROM apps.wshfv_container_contents WHERE container_id = :p_container_id;

Because the view is read-only and based on synonyms in the APPS schema, it should be queried with the APPS credentials or through a reporting user granted SELECT access. Performance is generally reliable for reporting, though queries filtering on DELIVERY_ID or CONTAINER_ID benefit most from the indexed delivery detail structure beneath it.