Search Results container_tare_weight




Overview
Explore in AI Chat

Overview

APPS.WSH_OPSM_ASN_CONTAINERS_V is a valid, seeded database view in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 releases, owned by the APPS schema and registered under the FND Design Data reference WSH.WSH_OPSM_ASN_CONTAINERS_V. It exposes container (License Plate Number, or LPN) information associated with Advance Shipment Notices (ASN) and outbound delivery records processed by Oracle Warehouse Management (WMS) and the Order Processing and Shipping Management (OPSM) module. The view is a reporting and integration construct: rather than storing data, it flattens the relationships between deliveries, delivery details, container instances, and inventory items into a single read-only projection that shipping, logistics, and integration developers can query directly.

Because the view surfaces attributes such as CONTAINER_FILL_PERCENT, CONTAINER_MAXIMUM_VOLUME, CONTAINER_MAXIMUM_LOAD_WEIGHT, and CONTAINER_MINIMUM_FILL_PERCENT, it is a primary source for users investigating container utilization thresholds. This accounts for its appearance in searches for "container_minimum_fill_percent," a column that stores the configured floor percentage below which a container is considered insufficiently filled for shipping rule evaluation. The view is consumed programmatically by WSH_OPSM_ASN_BE_PKG, the OPSM ASN business-event package, confirming its role as a supporting data source for ASN generation and container validation logic.

Underlying Base Objects

According to the documented dependency metadata, WSH_OPSM_ASN_CONTAINERS_V is defined over four base objects, all referenced through public synonyms resolved against the APPS schema:

  • MTL_PARAMETERS — the inventory organization parameters table, providing organization-level context such as master organization identifiers used to join container items to their definitions.
  • MTL_SYSTEM_ITEMS — the item master, supplying item descriptions (ITEM_DESCRIPTION) and item attribute validation for the container item and its contents.
  • WSH_DELIVERY_ASSIGNMENTS — the table that links delivery details to deliveries, enabling the view to correlate a container to a specific DELIVERY_ID.
  • WSH_DELIVERY_DETAILS — the shipping detail table that anchors container instance records to the outbound shipment line and inventory transactions.

The view depends on these tables in a read-only fashion; no materialization or trigger logic is documented. Because it is referenced by WSH_OPSM_ASN_BE_PKG, changes to container data propagate to ASN business events through normal query execution.

Key Columns

The view exposes 24 columns covering container identity, physical measurements, and delivery linkage:

Common Use Cases and Queries

The view is most frequently queried for container-level ASN reporting, fill-rate compliance, and integration extracts. A representative query listing containers below their minimum fill threshold is:

  • SELECT lpn, container_type, container_fill_percent, container_minimum_fill_percent, delivery_id FROM apps.wsh_opsm_asn_containers_v WHERE container_fill_percent < container_minimum_fill_percent;

Other common patterns include joining DELIVERY_ID to WSH_DELIVERIES for shipment manifests, aggregating CONTAINER_NET_WEIGHT and CONTAINER_VOLUME by delivery, and traversing the parent-child LPN hierarchy via PARENT_CONTAINER_INSTANCE_ID. Integration developers building ASN messages typically extract all columns for containers tied to a delivery, using WSH_OPSM_ASN_BE_PKG as the runtime partner. Because the view is read-only and joins a small number of tables, it is generally safe for high-frequency reporting, though large delivery volumes benefit from filtering on DELIVERY_ID.