Search Results container_volume_uom_code_int




Overview
Explore in AI Chat

Overview

APPS.CLN_XML_CONTAINERS_RN_V is a reporting and integration view in Oracle E-Business Suite (documented for 12.1.1 and 12.2.2) that exposes container (LPN) and delivery detail information in a flattened form suitable for XML message generation. The view is defined in the APPS schema and its name reflects its role: it feeds the containers section of outbound XML payloads, most notably those used by logistics and warehouse execution integrations on the Release 12 architecture.

The view presents one row per container-type delivery detail, joined to its parent delivery and to the container's item master attributes, so that a downstream consumer can emit a complete container record without additional lookups. A second UNION branch injects a "dummy container" placeholder row for deliveries that have no container-flagged details, guaranteeing that every delivery is represented in the result set at least once.

For users who search on "container_serial_number", this view is the primary documented source: the column is exposed as CONTAINER_SERIAL_NUMBER, derived from WSH_DELIVERY_DETAILS.SERIAL_NUMBER.

Underlying Base Objects

The documented base objects referenced by the view are:

  • WSH_DELIVERY_DETAILS — aliased WCI in the primary branch and WDD in the UNION branch. Provides the container-level attributes: serial number, container type code, volume and UOM, net weight, seal code, tracking number, LPN identifier, and the container flag.
  • WSH_DELIVERY_ASSIGNMENTS — aliased WDA. Supplies the DELIVERY_ID and PARENT_DELIVERY_DETAIL_ID linkage that ties a detail to its delivery and to its parent line.
  • MTL_SYSTEM_ITEMS — aliased MTI. Supplies unit dimension attributes (UNIT_HEIGHT, UNIT_LENGTH, UNIT_WIDTH) for the inventory item behind the container.

The primary branch filters on WCI.CONTAINER_FLAG = 'Y' and outer-joins MTL_SYSTEM_ITEMS on both INVENTORY_ITEM_ID and ORGANIZATION_ID, so containers whose item master record is missing still appear. The UNION branch selects from WSH_DELIVERY_ASSIGNMENTS and WSH_DELIVERY_DETAILS where NVL(WDD.CONTAINER_FLAG,'N')='N' and WDA.PARENT_DELIVERY_DETAIL_ID IS NULL, emitting a row tagged RN_DUMMY_CONTAINER='Y' with all container-specific columns set to NULL.

Key Columns

  • CONTAINER_INSTANCE_ID — the delivery detail identifier of the container record.
  • CONTAINER_SERIAL_NUMBER — the container's serial number, the column most commonly targeted by container_serial_number searches.
  • CONTAINER_TYPE_INT — the container type code from the container-flagged detail.
  • CONTAINER_VOLUME, CONTAINER_VOLUME_UOM_CODE_INT, CONTAINER_NET_WEIGHT — physical attributes of the container.
  • CONTAINER_SEAL_CODE, CONTAINER_TRACKING_NUMBER — seal and carrier tracking identifiers.
  • DELIVERY_ID — the parent delivery header identifier.
  • PARENT_DELIVERY_DETAIL_ID — the parent detail, used for nested container hierarchies.
  • LPN_ID — the license plate number surrogate identifier.
  • UNIT_HEIGHT, UNIT_LENGTH, UNIT_WIDTH — dimensional attributes from MTL_SYSTEM_ITEMS.
  • RN_DUMMY_CONTAINER — 'N' for real containers, 'Y' for the placeholder row.

Common Use Cases and Queries

Typical usage is to resolve the serial number of a container on a given delivery, or to enumerate all containers shipped against a delivery for XML or interface troubleshooting.

SELECT delivery_id,
       container_instance_id,
       container_serial_number,
       container_type_int,
       lpn_id
  FROM apps.cln_xml_containers_rn_v
 WHERE delivery_id = :p_delivery_id
   AND rn_dummy_container = 'N';

To locate a container from a known serial number:

SELECT delivery_id, container_instance_id, container_tracking_number
  FROM apps.cln_xml_containers_rn_v
 WHERE container_serial_number = :p_serial_number;

Because the view emits a dummy row per container-less delivery, consumers joining it to other delivery-level data should filter on RN_DUMMY_CONTAINER = 'N' when only true containers are required, or retain all rows when a complete delivery census is needed. Direct queries should account for the DISTINCT and UNION operations, which may cause the optimizer to scan WSH_DELIVERY_DETAILS and WSH_DELIVERY_ASSIGNMENTS in full for large delivery ranges.