Search Results maximum_weight




Overview
Explore in AI Chat

Overview

APPS.INVBV_INVENTORY_LOCATORS is a Business Intelligence System (BIS) view in the Oracle E-Business Suite Inventory module, registered under FND Design Data INV.INVBV_INVENTORY_LOCATORS. It presents a specific physical location within a subinventory — typically a row, rack, or bin — together with the capacity, weight, and volume constraints defined for that locator. The object resides in the APPS schema with a status of VALID and is classified as a view rather than a base table, meaning it is a read-only presentation layer intended for reporting, extraction, and integration rather than transactional data entry. In Oracle EBS 12.1.1 and 12.2.2, such BIS views are commonly exposed through the Business Intelligence System and the corresponding Oracle Business Intelligence applications, allowing warehouse and inventory data to be queried without direct dependency on the full column set or internal join logic of the underlying tables. Because it is defined in the APPS schema and carries a stable column list, it is frequently used as a source for custom reports, data warehousing loads, and interface programs that need locator-level attribute data across organizations.

Underlying Base Objects

The documented dependency for APPS.INVBV_INVENTORY_LOCATORS is a single base object: MTL_ITEM_LOCATIONS, referenced through the APPS synonym. MTL_ITEM_LOCATIONS is the transactional master table that stores every inventory locator defined within an organization, including descriptive attributes, capacity and dimensional limits, picking order, and audit columns. The view projects a selected subset of that table's columns and, consistent with the BIS design pattern, does not join additional tables for its core definition. The metadata notes that the view is not referenced by any other database object, confirming it is a terminal consumer object in the dependency chain. Consequently, any change to the structure or data of MTL_ITEM_LOCATIONS for a given organization is immediately reflected in query results from this view. The view does not expose all columns of MTL_ITEM_LOCATIONS, so consumers requiring attributes outside the published list must query the base table directly.

Key Columns

The view exposes the following columns, which correspond to locator attributes in MTL_ITEM_LOCATIONS:

  • INVENTORY_LOCATOR_ID — Primary identifier for the locator; the join key to inventory transaction tables.
  • ORGANIZATION_ID — Identifies the inventory organization to which the locator belongs.
  • DESCRIPTION — User-defined description of the physical location, up to 50 characters.
  • INACTIVE_DATE — Date on which the locator is no longer available for use.
  • PICKING_ORDER — Numeric sequence used to prioritize picking activities within the subinventory.
  • MAXIMUM_CAPACITY — Maximum unit capacity permitted for the locator.
  • SUBINVENTORY_NAME — Name of the subinventory containing the locator, up to 10 characters.
  • WEIGHT_UOM_CODE — Unit of measure associated with the maximum weight value.
  • MAXIMUM_WEIGHT — Maximum weight permitted for the locator, expressed in the associated weight UOM. This is the column most relevant to the search term "maximum_weight".
  • VOLUME_UOM_CODE — Unit of measure associated with the maximum volume value.
  • MAXIMUM_VOLUME — Maximum volume permitted for the locator.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — Standard audit columns recording record creation and last modification.

Common Use Cases and Queries

Typical use cases include warehouse capacity analysis, weight and volume utilization reporting, locator master data extracts, and validation of picking sequences. The following query lists all active locators in a given organization with their weight and volume limits:

  • SELECT inventory_locator_id, subinventory_name, description, maximum_weight, weight_uom_code, maximum_volume, volume_uom_code FROM apps.invbv_inventory_locators WHERE organization_id = :org_id AND (inactive_date IS NULL OR inactive_date > SYSDATE);

To find locators whose maximum weight exceeds a threshold, filter directly on MAXIMUM_WEIGHT:

  • SELECT description, maximum_weight, weight_uom_code FROM apps.invbv_inventory_locators WHERE maximum_weight > :threshold ORDER BY maximum_weight DESC;

Because the view is not referenced by other database objects, it can be queried or extracted without concern for downstream dependency impact. Consumers should note that the view exposes only the documented columns and that unit-of-measure codes must be interpreted against the weight and volume UOM defined for the maximum values.