Search Results invbv_inventory_locators

Overview

INVBV_INVENTORY_LOCATORS is an APPS-owned read-only view in the Oracle E-Business Suite Inventory (INV) module. It presents inventory locator (storage location) definitions stored in the MTL_ITEM_LOCATIONS table, exposing descriptive attributes, physical capacity constraints, and standard audit columns. In ETRM documentation for release 12.2.2 the object is marked VALID and described as "Retrofitted," indicating that the view was carried forward or recreated to preserve compatibility with earlier customizations, reports, or integrations that depended on this interface across the 12.1.1 and 12.2.2 releases.

Because the view enforces a WITH READ ONLY clause, it cannot be used for inserts, updates, or deletes. Its primary role is as a reporting and integration interface: external systems, custom concurrent programs, and BI Publisher reports can query locator master data without touching the underlying transactional table directly. The presence of a bind-style security predicate ('_SEC:MIL.ORGANIZATION_ID' IS NOT NULL) further indicates that the view participates in Oracle's organization-level security framework, transparently restricting rows based on the operating unit or organization context of the session.

This view is particularly relevant to searches involving maximum_volume, since it exposes MAXIMUM_VOLUME (sourced from MAX_CUBIC_AREA), allowing users to report on the volumetric capacity of each locator alongside its weight and unit capacity limits.

Underlying Base Objects

The view is defined exclusively over MTL_ITEM_LOCATIONS, referenced through the APPS synonym MTL_ITEM_LOCATIONS. There are no joins to subinventory, organization, or UOM tables in the view definition; instead, related codes and identifiers are returned as raw column values. This single-table construction keeps the view lightweight and predictable, which is advantageous for high-volume reporting.

MTL_ITEM_LOCATIONS is the master table for inventory locators within a subinventory. Each row represents a physical storage position and carries capacity metadata used by putaway, picking, and warehouse management processes. The view selects a defined subset of columns from this table, renaming several of them in the output (for example, LOCATION_MAXIMUM_UNITS is exposed as MAXIMUM_CAPACITY, MAX_CUBIC_AREA as MAXIMUM_VOLUME, DISABLE_DATE as INACTIVE_DATE, and SUBINVENTORY_CODE as SUBINVENTORY_NAME).

Key Columns

• INVENTORY_LOCATOR_ID — Maps to INVENTORY_LOCATION_ID, the unique surrogate key for the locator.
• ORGANIZATION_ID — The inventory organization that owns the locator; also the column referenced by the security predicate.
• DESCRIPTION — The locator's descriptive name or code as displayed to users.
• INACTIVE_DATE — Sourced from DISABLE_DATE; a non-null value indicates the locator is disabled for new transactions.
• PICKING_ORDER — Sequence used to prioritize locators during picking.
• MAXIMUM_CAPACITY — Sourced from LOCATION_MAXIMUM_UNITS; the locator's maximum unit capacity.
• SUBINVENTORY_NAME — Sourced from SUBINVENTORY_CODE; identifies the parent subinventory.
• WEIGHT_UOM_CODE and MAXIMUM_WEIGHT — The unit of measure and maximum weight the locator can hold.
• VOLUME_UOM_CODE and MAXIMUM_VOLUME — The unit of measure and maximum volume (from MAX_CUBIC_AREA) the locator can hold; these are the columns of interest for maximum-volume analysis.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — Standard audit columns.

Common Use Cases and Queries

Typical uses include capacity reporting, locator master-data extracts, and validation of volumetric or weight constraints during warehouse configuration. A simple listing of active locators with their volume limits is shown below:

SELECT organization_id, subinventory_name, inventory_locator_id, description, maximum_volume, volume_uom_code, maximum_weight, maximum_capacity FROM apps.invbv_inventory_locators WHERE inactive_date IS NULL ORDER BY organization_id, subinventory_name, picking_order;

To identify locators exceeding a volume threshold within a specific organization:

SELECT inventory_locator_id, description, maximum_volume, volume_uom_code FROM apps.invbv_inventory_locators WHERE organization_id = :org_id AND maximum_volume IS NOT NULL AND maximum_volume > :threshold_volume ORDER BY maximum_volume DESC;

Because the view is read-only and security-filtered by organization, it is well suited to ad-hoc queries and downstream extracts, but should not be used as a target for DML. For transactional operations, the base table MTL_ITEM_LOCATIONS must be accessed through the supported Inventory APIs.