Search Results dimension_uom_code




Overview

The APPS.WSH_STND_CONTAINERS_V view is a Shipping Execution (WSH) reporting object that exposes standardized container and delivery detail information for packed shipments in Oracle E-Business Suite 12.1.1 and 12.2.2. It is defined as a database view owned by the APPS schema and carries a VALID status. The view consolidates container-level attributes—such as container name, seal code, container type, weights, volumes, and tracking numbers—with item and dimensional data sourced from inventory and shipping tables. Its primary role is to provide a denormalized, read-only projection that supports container manifesting, packing slip reporting, freight documentation, and integration extracts without requiring consumers to join the underlying transaction tables directly.

The view is particularly relevant when dimension and unit-of-measure attributes are required, since it exposes DIMENSION_UOM_CODE alongside UNIT_HEIGHT, UNIT_LENGTH, and UNIT_WIDTH. Users searching for dimension_uom_code can retrieve the unit of measure in which container dimensions are expressed directly from this view.

Underlying Base Objects

The documented base objects underlying WSH_STND_CONTAINERS_V span several EBS modules:

The ITEM_NUMBER column applies a DECODE against CLIENT_ID and uses SUBSTR/INSTR logic with the concatenated segment delimiter, reflecting the flexible key flexfield structure of the item identifier.

Key Columns

The view exposes container identity, physical, and logistics attributes:

Common Use Cases and Queries

Typical scenarios include container manifesting reports, packing slip generation, dimensional weight calculations, and shipping integration extracts. A representative query retrieving container dimensions and their UOM:

  • SELECT container_name, item_number, unit_height, unit_length, unit_width, dimension_uom_code, gross_weight, weight_uom_code FROM wsh_stnd_containers_v WHERE delivery_id = :p_delivery_id;
  • SELECT container_name, tracking_number, ship_from_location, hazard_class FROM wsh_stnd_containers_v WHERE track_number IS NOT NULL;
  • SELECT container_type_code, fill_percent, filled_volume, volume_uom_code FROM wsh_stnd_containers_v WHERE fill_percent < 100;

Because the view joins several module objects, queries should filter on indexed keys such as DELIVERY_ID or DELIVERY_DETAIL_ID to avoid full scans. All access is read-only, and the view is suitable for both concurrent program reporting and external integration interfaces.