Results for “unit_height”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The CLN_XML_CONTAINERS_V view is an APPS-owned database object within the Oracle E-Business Suite Release 12.1.1 and 12.2.2 environment. It belongs to the CLN — Supply Chain Trading Connector for RosettaNet product module, which provides the integration layer for B2B message exchange using the RosettaNet and OAG (Open Applications Group) standards. The view is documented with a VALID status, confirming that it compiles successfully against the referenced base objects.

The specific purpose of this view is to supply the SHIPUNIT containers section of the OAG SHOW_SHIPMENT_005 XML payload. In the OAGIS SHOW_SHIPMENT_005 document, container-level information — such as the physical shipping units, their serial numbers, seals, tracking numbers, and volumetric attributes — is reported alongside shipment and delivery header details. This view isolates and reshapes that container data from the WSH (Shipping) and MTL (Inventory) schemas so it can be marshalled directly into the outbound XML message.

Underlying Base Objects

Per the ETRM documentation, the view is defined over the following referenced base objects, all accessed through APPS synonyms:

• WSH_DELIVERY_DETAILS — aliased as WCI; supplies the container records, filtered by CONTAINER_FLAG = 'Y'. This is the primary driver table.
• WSH_DELIVERY_ASSIGNMENTS — aliased as WDA; links delivery details to their parent delivery, providing the DELIVERY_ID and PARENT_DELIVERY_DETAIL_ID used in the payload hierarchy.
• MTL_SYSTEM_ITEMS — aliased as MTI; joined outer (via the (+) operator) to supply container item dimensions (UNIT_HEIGHT, UNIT_LENGTH, UNIT_WIDTH).

The joins are: WDA.DELIVERY_DETAIL_ID = WCI.DELIVERY_DETAIL_ID (inner), plus outer joins on INVENTORY_ITEM_ID and ORGANIZATION_ID to MTL_SYSTEM_ITEMS, ensuring containers without a matching item definition are still returned. The WHERE clause restricts rows to container-flagged details (CONTAINER_FLAG = 'Y') and outbound line direction (LINE_DIRECTION IS NULL OR LINE_DIRECTION = 'O'). SELECT DISTINCT eliminates duplication introduced by the assignment join.

Key Columns

• CONTAINER_INSTANCE_ID — maps to WCI.DELIVERY_DETAIL_ID; the unique container instance identifier.
• CONTAINER_SERIAL_NUMBER — the container's serial number (WCI.SERIAL_NUMBER).
• CONTAINER_TYPE_INT — internal container type code (WCI.CONTAINER_TYPE_CODE).
• CONTAINER_VOLUME / CONTAINER_VOLUME_UOM_CODE_INT — volumetric measure and its unit of measure.
• CONTAINER_NET_WEIGHT — net weight of the container.
• CONTAINER_SEAL_CODE — security seal applied to the container.
• CONTAINER_TRACKING_NUMBER — carrier or internal tracking reference.
• DELIVERY_ID — parent delivery header identifier, from WDA.
• UNIT_HEIGHT / UNIT_LENGTH / UNIT_WIDTH — container item dimensions from MTL_SYSTEM_ITEMS.
• PARENT_DELIVERY_DETAIL_ID — supports container nesting/hierarchy.
• LPN_ID — the License Plate Number identifier associated with the container.

Common Use Cases and Queries

This view is typically consumed by the CLN RosettaNet/OAG integration programs when constructing SHOW_SHIPMENT_005 payloads, and by technical consultants troubleshooting container data in outbound shipment documents. A representative diagnostic query is:

• SELECT container_instance_id, container_serial_number, container_seal_code, container_tracking_number, delivery_id FROM cln_xml_containers_v WHERE delivery_id = :p_delivery_id;
• SELECT * FROM cln_xml_containers_v WHERE lpn_id IS NOT NULL; to inspect containers linked to license plates.
• SELECT container_type_int, container_volume, container_volume_uom_code_int, unit_height, unit_length, unit_width FROM cln_xml_containers_v; to verify dimensional and volumetric data mapped into the OAG payload.

Because the view is read-only and exposes APPS synonyms, it can be queried directly by integration developers and support analysts without additional grants beyond those already held on the underlying shipping tables.