Search Results container_attribute1




Overview
Explore in AI Chat

Overview

WSH_DSNO_CONTAINERS_V is a Shipping Execution (WSH) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is a denormalized container (LPN) reporting view that presents logistics container instances alongside their parent-child hierarchy, weights, volumes, descriptive flexfield context, and key inventory identifiers. The view is defined with a SELECT DISTINCT clause, which de-duplicates rows produced by the multi-table join used to resolve parent container relationships.

The view is most commonly surfaced in Distributed Order (DSNO) and shipping-related reporting, integration extracts, and custom concurrent programs. Because a container's gross weight is a frequently queried attribute — particularly for freight rating, manifesting, carrier label generation, and load planning — the column CONTAINER_GROSS_WEIGHT (sourced from WCI.GROSS_WEIGHT) is a primary reason users search for this object. The companion UOM column CONTAINER_GROSS_WEIGHT_UOM_INT (from WCI.WEIGHT_UOM_CODE) should always be selected together with the weight value to preserve unit-of-measure context.

Underlying Base Objects

The documented base objects referenced by WSH_DSNO_CONTAINERS_V are:

  • WSH_DELIVERY_DETAILS (synonym) — the primary shipping detail table supplying delivery detail records, parent delivery detail linkage, and container instance attributes.
  • WSH_DELIVERY_ASSIGNMENTS_V (view) — used to resolve delivery-to-detail assignments and support the parent container hierarchy.
  • MTL_SYSTEM_ITEMS (synonym) — the item master, referenced for container item definition data.
  • WMS_EPC (synonym) — the EPC (Electronic Product Code) table used in serialized container handling.

The view text also aliases WCI (container instance, derived from WSH_DELIVERY_DETAILS), WDA (delivery assignment), and WCIP (parent container instance), joining container rows to their parent via PARENT_DELIVERY_DETAIL_ID. This self-referencing join is what produces the PARENT_CONTAINER_INSTANCE_ID and PARENT_LPN columns.

Key Columns

Common Use Cases and Queries

Typical scenarios include freight weight roll-ups, carrier label and manifest extracts, and LPN hierarchy reporting. A representative query for container weights is:

SELECT container_instance_id, lpn, container_gross_weight, container_gross_weight_uom_int, container_volume FROM apps.wsh_dsno_containers_v WHERE container_gross_weight IS NOT NULL;

To report nested container hierarchies, query PARENT_LPN and LPN together. When aggregating weights for rating, join CONTAINER_ITEM_ID to MTL_SYSTEM_ITEMS for item descriptions. Because the view is DISTINCT-based and joins multiple tables, filter on the container instance or LPN wherever possible to limit row volume.