Search Results max_load_quantity

Overview

The WSHBV_CONTAINER_LOAD view is a reporting and integration artifact within the Oracle E-Business Suite Order Entry (OE) module. It is owned by the APPS schema and is documented with a status of VALID in the ETRM repository for release 12.2.2, with equivalent behavior in 12.1.1. Functionally, the view is a thin projection over the WSH_CONTAINER_LOAD base object in the Warehouse Management (WSH) product family, exposing container-to-item loading relationships together with the maximum quantity that a given container item is permitted to hold. Rather than computing values or joining multiple sources, the view presents the stored load configuration in a denormalized, single-row-per-relationship form, which makes it convenient for concurrent programs, Form personalizations, BI Publisher data templates, and third-party integration extracts that need to read container load limits without navigating the full WSH data model. Because the view is defined directly over a synonym rather than over a set of joined tables, its performance profile mirrors that of the underlying WSH_CONTAINER_LOAD table, and all DML restrictions of the base object apply. No row-level security or organization access filtering is layered inside the view itself, so consumers are responsible for restricting results by MASTER_ORGANIZATION_ID or by whatever operating unit context their report requires.

Underlying Base Objects

Per the documented ETRM metadata, the view references a single base object: the synonym WSH_CONTAINER_LOAD, which resolves to the physical container load table in the WSH schema. The view definition is a straightforward SELECT from that synonym aliased as WCL, projecting thirteen columns. The relationship is therefore one-to-one at the structural level: for every row in WSH_CONTAINER_LOAD, the view returns exactly one row with an identical column list. This design means no aggregation, filtering, or transformation occurs inside the view. Any change to the underlying table — such as a new load relationship being defined during shipping or container configuration — is immediately visible through the view. Conversely, the view cannot be used to insert, update, or delete rows unless the base table is updatable through the synonym, which is generally not supported for this type of configuration data in a supported customization context.

Key Columns

The columns exposed fall into three functional groups. The first group identifies the master and load relationship: MASTER_ORGANIZATION_ID identifies the inventory organization that owns the container configuration; CONTAINER_ITEM_ID is the inventory item identifier for the container itself; and LOAD_ITEM_ID is the item identifier for the contents that may be loaded into that container. Together these three columns form the natural business key of a container load rule. The second group centers on the quantity attribute that users most frequently search for — MAX_LOAD_QUANTITY — which stores the maximum number of units of the load item that the container item can hold. This is the principal business value of the view and the column most often surfaced in reports, alerts, and validation logic. The third group consists of standard Oracle who-columns and concurrent program audit fields: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, and REQUEST_ID. These columns support audit reporting, change tracking, and identification of the concurrent request that last modified a given load rule.

Common Use Cases and Queries

Typical use cases include validating pick-and-pack capacity during shipping execution, generating container capacity reports for warehouse planning, and building integration extracts that push load limits to external warehouse management or transportation systems. Because the view is a direct projection, queries are simple and index-friendly. A representative query retrieving load limits for a specific container item is shown below.

• SELECT container_item_id, load_item_id, max_load_quantity FROM apps.wshbv_container_load WHERE master_organization_id = :org_id AND container_item_id = :container_id;
• SELECT l.max_load_quantity, msi.segment1 container_item FROM apps.wshbv_container_load l, apps.mtl_system_items_b msi WHERE l.container_item_id = msi.inventory_item_id AND l.master_organization_id = msi.organization_id AND l.master_organization_id = :org_id;
• SELECT max_load_quantity, last_update_date, last_updated_by FROM apps.wshbv_container_load WHERE request_id = :request_id;

Consumers should always qualify queries on MASTER_ORGANIZATION_ID and the container or load item identifiers to avoid full scans, and should treat the view as read-only reference data rather than as an interface for maintaining container load configuration.