Search Results container_maximum_load_weight

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

Overview

The WSH_OPSM_ASN_CONTAINERS_V view is a shipping execution object owned by the APPS schema within the WSH (Shipping Execution) product module. It exposes container, or License Plate Number (LPN), information associated with Advance Shipment Notices and delivery details. The view flattens hierarchical container relationships — including parent-child LPN structures — into a single queryable result set, making it well suited for reporting, outbound integration, and label-generation scenarios where a caller must retrieve the full attribute set of each container on a delivery.

Because it is a view rather than a table, it holds no data of its own; it consistently re-derives container information from the underlying shipping and inventory structures at query time. In Oracle EBS 12.1.1 and 12.2.2, this view is commonly referenced by ASN-related processes and by custom reports that need to reconstruct the packing hierarchy of an outbound shipment.

Underlying Base Objects

The view text joins several base objects, all exposed through APPS synonyms:

• WSH_DELIVERY_DETAILS — The primary source. It appears twice, effectively aliased as WCI (the container itself) and WCIP (the parent container), joined on PARENT_DELIVERY_DETAIL_ID. The predicate WCI.CONTAINER_FLAG = 'Y' restricts the result set to container rows.
• WSH_DELIVERY_ASSIGNMENTS — Provides the container-to-delivery association and the parent-child linkage via PARENT_DELIVERY_DETAIL_ID and DELIVERY_DETAIL_ID.
• MTL_SYSTEM_ITEMS — Supplies item context for the container inventory item. It is outer-joined on both INVENTORY_ITEM_ID and ORGANIZATION_ID.
• MTL_PARAMETERS — Used in a scalar subquery to determine whether the organization is configured for SSCC-18 LPN numbering based on TOTAL_LPN_LENGTH and UCC_128_SUFFIX_FLAG.

The outer joins to WSH_DELIVERY_DETAILS (WCIP) and MTL_SYSTEM_ITEMS allow containers without a defined parent or without a resolvable item to remain in the result set.

Key Columns

• CONTAINER_INSTANCE_ID — Aliased from DELIVERY_DETAIL_ID; the unique container identifier.
• LPN — The container name (CONTAINER_NAME).
• PARENT_CONTAINER_INSTANCE_ID and PARENT_LPN — The parent container identifier and name, enabling nesting reconstruction.
• CONTAINER_ITEM_ID — The inventory item defining the container type.
• MASTER_SERIAL_NUMBER, CONTAINER_SERIAL_NUMBER, LOT_NUMBER — Serial and lot tracking attributes.
• CONTAINER_GROSS_WEIGHT, CONTAINER_NET_WEIGHT, CONTAINER_TARE_WEIGHT — Weight measures; tare is derived as gross minus net.
• CONTAINER_VOLUME, CONTAINER_MAXIMUM_VOLUME, CONTAINER_MAXIMUM_LOAD_WEIGHT — Capacity attributes.
• CONTAINER_FILL_PERCENT, CONTAINER_MINIMUM_FILL_PERCENT — Fill-level metrics.
• CONTAINER_SEAL_CODE, CONTAINER_TRACKING_NUMBER — Security and query tracking references.
• DELIVERY_ID — Links the container to its parent delivery.
• LPN_TYPE — Emits 'SSCC-18' when the organization parameters indicate SSCC-18 numbering; otherwise null.

Common Use Cases and Queries

Typical scenarios include generating ASN container listings, printing LPN labels, and validating packing hierarchies. A representative query retrieving all containers for a delivery follows:

• SELECT lpn, parent_lpn, container_item_id, container_gross_weight, container_volume, lpn_type FROM wsh_opsm_asn_containers_v WHERE delivery_id = :p_delivery_id;
• Identifying root (top-level) containers: filter WHERE parent_container_instance_id IS NULL.
• Reconstructing the hierarchy: order or group by PARENT_CONTAINER_INSTANCE_ID to walk the container tree.
• Detecting SSCC-18 registered LPNs: filter WHERE lpn_type = 'SSCC-18'.

Because the view resolves parent relationships and organization-level LPN numbering dynamically, it is preferable to querying WSH_DELIVERY_DETAILS directly when complete container context is required.