Search Results max_load_quantity

Overview

WSHBV_CONTAINER_ITEMS is a read-only view owned by the APPS schema in Oracle E-Business Suite, defined within the WSH (Shipping Execution) product family. It exposes the relationship between container items and their associated load items as recorded in the WSH_CONTAINER_ITEMS base table, while enriching each row with descriptive attributes resolved from the Master Item flexfield. The view is registered as VALID in both Oracle EBS 12.1.1 and 12.2.2 and is intended primarily for reporting and integration scenarios, rather than for transactional data entry.

The "BV" naming convention indicates a Business View whose primary purpose is to surface denormalized, human-readable item descriptions and flexible-field values. Analysts, report developers, and interface programs commonly query this view to determine the maximum quantity of a container item that may be loaded onto a given load item without navigating the item master directly.

Underlying Base Objects

The view is defined over three physical objects. The driving table is WSH_CONTAINER_ITEMS, which holds the authoritative container-to-load-item mapping. Two references to MTL_SYSTEM_ITEMS are joined to the base table — self-joined aliases MSI1 and MSI2 — to translate the internal inventory item identifiers into their Master Item flexfield (MSTK) key values and to resolve the PREFERRED_FLAG lookup meaning.

The core join predicates are:

• WCI.CONTAINER_ITEM_ID = MSI1.INVENTORY_ITEM_ID, restricted by WCI.MASTER_ORGANIZATION_ID = MSI1.ORGANIZATION_ID.
• WCI.LOAD_ITEM_ID = MSI2.INVENTORY_ITEM_ID, restricted by WCI.MASTER_ORGANIZATION_ID = MSI2.ORGANIZATION_ID.
• Organization security is enforced through the token '_SEC:WCI.MASTER_ORGANIZATION_ID', with the view defined WITH READ ONLY.

In the ETRM documented metadata both MTL_SYSTEM_ITEMS and WSH_CONTAINER_ITEMS are referenced through synonyms visible to APPS.

Key Columns

• MASTER_ORGANIZATION_ID — The inventory organization that owns the container/load item relationship and the security context for the row.
• CONTAINER_ITEM_ID — The inventory item identifier for the container, keyed into the item master flexfield as "_KF:INV:MSTK:MSI1".
• LOAD_ITEM_ID — The inventory item identifier for the load item, keyed into the flexfield as "_KF:INV:MSTK:MSI2".
• MAX_LOAD_QUANTITY — The maximum quantity of the container item that can be loaded against the related load item; this is the column most frequently retrieved by users.
• PREFERRED_FLAG — A lookup-driven Yes/No indicator resolved through FND_LOOKUPS ("_LA:PREFERRED_FLAG:FND_LOOKUPS:YES_NO:MEANING"), denoting whether this container/load combination is the preferred configuration.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns inherited from the base table.

Common Use Cases and Queries

A typical report requirement is to identify the maximum load quantity for a container item within a specific organization. The following query illustrates a parameterized retrieval:

• SELECT container_item_id, load_item_id, max_load_quantity FROM apps.wshbv_container_items WHERE master_organization_id = :org_id AND container_item_id = :item_id;

Other common patterns include validating load quantities during shipping integrations, listing all preferred container configurations, and joining the view back to WSH_CONTAINER_ITEMS for audit reporting. Because the view enforces organization security and returns only read-consistent rows, it is safe to expose to BI Publisher, OAF-based shipping pages, and outbound interface extracts. Developers should note that MAX_LOAD_QUANTITY is a per-relationship attribute and must always be interpreted together with the container item and load item context.