Search Results container_volume_uom_code_int

Overview

ECE_DSNO_CONTAINERS_V is a database view historically shipped with the Oracle e-Commerce Gateway (EC) module, the EDI and business-document exchange framework embedded in Oracle E-Business Suite. Its name derives from the legacy "DSNO" (Delivery Shipping Notice / Advance Ship Notice) extraction layer that the e-Commerce Gateway used to build outbound ASN (856) and related shipping documents from Oracle Shipping Execution data. In Oracle EBS 12.1.1 and 12.2.2, however, the object carries the documented status "No longer used." The ETRM metadata explicitly records that it is not implemented in the current database, meaning the view should not be relied upon for new development, and it may not even exist in a freshly provisioned 12.x environment.

Despite its deprecated status, the view remains relevant as a reference artifact. It exposes the container hierarchy used by Oracle Shipping Execution — containers, their serial numbers, weights, volumes, and parent/master relationships — in a flattened, denormalized form suited to EDI payload generation. Because the user search term "container_serial_number" maps directly to a column in this view, ECE_DSNO_CONTAINERS_V is frequently encountered when developers attempt to trace how container serial numbers were historically surfaced to e-Commerce Gateway output.

Underlying Base Objects

The documented view text joins five base objects:

• WSH_PACKED_CONTAINERS WPC — the primary container record, supplying the delivery, item, serial, lot, weight, volume, and DFF attribute columns.
• WSH_PACKED_CONTAINERS WPCP — self-joined to resolve the parent container sequence number.
• WSH_PACKED_CONTAINERS WPCM — self-joined to resolve the master container serial number via NVL fallback.
• MTL_SYSTEM_ITEMS MSI — joins on CONTAINER_INVENTORY_ITEM_ID = INVENTORY_ITEM_ID to supply container type, maximum volume, maximum load weight, and minimum fill percent.
• WSH_DELIVERIES DLV — supplies the actual departure identifier associated with the delivery.

All containers therefore derive from the Oracle Shipping Execution (WSH) schema, with item-level definitions sourced from Oracle Inventory (MTL). The ETRM metadata documents no additional referenced base objects for 12.2.2.

Key Columns

The most significant exposed columns include:

• CONTAINER_SERIAL_NUMBER — sourced from WPC.SERIAL_NUMBER; this is the column matched by the user's search and represents the unique serial assigned to a packed container.
• MASTER_SERIAL_NUMBER — resolves either the container's own master serial or its parent's via NVL.
• DELIVERY_ID / DEPARTURE_ID — link the container to its parent delivery and actual departure.
• CONTAINER_ID, PARENT_CONTAINER_ID, MASTER_CONTAINER_ID, PARENT_SEQUENCE_NUMBER, SEQUENCE_NUMBER — define the container hierarchy and nesting order.
• CONTAINER_QUANTITY, LOT_NUMBER, CONTAINER_ITEM_ID — inventory context for the contents.
• CONTAINER_TYPE_INT, CONTAINER_MAXIMUM_VOLUME, CONTAINER_MAXIMUM_LOAD_WEIGHT, CONTAINER_MINIMUM_FILL_PERCENT — item-level container specifications.
• CONTAINER_GROSS_WEIGHT, CONTAINER_NET_WEIGHT, CONTAINER_TARE_WEIGHT, CONTAINER_VOLUME, CONTAINER_FILL_PERCENT and their UOM columns — physical measurements; tare weight is computed as GROSS_WEIGHT − NET_WEIGHT.
• CONTAINER_ATTRIBUTE1 through CONTAINER_ATTRIBUTE15 and CONTAINER_CATEGORY — DESCRIPTIVE flexfield attributes.

Common Use Cases and Queries

Given its deprecated status, ECE_DSNO_CONTAINERS_V should be treated as a reference model rather than a production source. Typical exploration scenarios include reconciling historical ASN container data, tracing serial-number lineage, or rebuilding equivalent logic against current WSH tables. A representative query is:

• SELECT delivery_id, container_id, container_serial_number, master_serial_number, container_gross_weight FROM ece_dsno_containers_v WHERE container_serial_number = :serial;

For modern implementations, query WSH_PACKED_CONTAINERS directly, joined to MTL_SYSTEM_ITEMS and WSH_DELIVERIES, replicating the view's join logic. This avoids dependency on an object the metadata explicitly states is not implemented.