Search Results cln_xml_containers_rn_v




Overview
Explore in AI Chat

Overview

The APPS.CLN_XML_CONTAINERS_RN_V view is a RosettaNet integration construct delivered as part of the CLN – Supply Chain Trading Connector for RosettaNet module in Oracle E-Business Suite 12.1.1 and 12.2.2. Its purpose is to expose shipping container (logistics unit) information originating in Oracle Warehouse Management and Shipping Execution in a flattened, integration-friendly shape that the RosettaNet outbound message generation layer can consume. The view supports RosettaNet PIP messages that carry packing, container, and shipment structure data — most notably the packing list and shipment notification flows (such as PIP 3B2 / 3B18 style container hierarchies), where each physical handling unit must be described with its serial number, type, volume, weight, seal, and dimensional attributes.

The view is read-only and defined entirely on shipping and inventory master data; it carries no transactional persistence of its own. Because it normalizes container versus non-container delivery detail lines into a single row shape, it shields the integration layer from the physical structure of the underlying delivery-detail tables.

Underlying Base Objects

ETRM documentation for 12.2.2 identifies the referenced base objects as WSH_DELIVERY_ASSIGNMENTS, WSH_DELIVERY_DETAILS (both accessed through APPS synonyms), and MTL_SYSTEM_ITEMS. The view joins these as follows:

  • WSH_DELIVERY_ASSIGNMENTS (alias WDA) supplies the delivery-to-detail assignment link, the owning DELIVERY_ID, and the PARENT_DELIVERY_DETAIL_ID used to reconstruct the container hierarchy.
  • WSH_DELIVERY_DETAILS (alias WCI for container rows, WDD for the non-container branch) supplies the container attributes and the CONTAINER_FLAG used to segregate physical containers from loose items.
  • MTL_SYSTEM_ITEMS (alias MTI) is outer-joined on INVENTORY_ITEM_ID and ORGANIZATION_ID to supply unit height, length, and width for the container item.

The view is the UNION of two branches: the first returns actual container records (where CONTAINER_FLAG = 'Y') with RN_DUMMY_CONTAINER = 'N'; the second returns a synthetic placeholder row for delivery details that are not containers (NVL(WDD.CONTAINER_FLAG,'N') = 'N' and WDA.PARENT_DELIVERY_DETAIL_ID IS NULL) with all container columns nulled and RN_DUMMY_CONTAINER = 'Y'. This guarantees the RosettaNet mapping always receives at least one container node per delivery.

Key Columns

Common Use Cases and Queries

Typical usage is inside the CLN RosettaNet outbound document generation logic, which selects container data for a delivery and maps it to the packing or shipment XML structure. Ad hoc queries are common for troubleshooting outbound messages and verifying container hierarchy.

Retrieve all real containers for a delivery:

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

Inspect the complete container set including the synthetic placeholder row:

SELECT container_instance_id, parent_delivery_detail_id,
       rn_dummy_container, unit_height, unit_length, unit_width
FROM   apps.cln_xml_containers_rn_v
WHERE  delivery_id = :p_delivery_id
ORDER  BY rn_dummy_container;

Because the placeholder branch returns a null container instance, integrations should always test RN_DUMMY_CONTAINER before emitting container-level XML elements to avoid generating empty container nodes.