Results for “mtl_item_locations”

50+ results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

MTL_ITEM_LOCATIONS is the Inventory (INV) master table that stores the definitions for stock locators within Oracle E-Business Suite Release 12.1.1 and 12.2.2. A stock locator represents a physical storage position inside a subinventory — a bin, aisle, rack, shelf, or staging position — and is the finest level of inventory granularity tracked by the application. The table is owned by the INV schema and holds 94 documented columns. Each row defines one locator for one organization, and is uniquely identified by the combination of INVENTORY_LOCATION_ID and ORGANIZATION_ID.

From a dimensional modeling standpoint, the ETRM heuristic classifies MTL_ITEM_LOCATIONS as hub-leaning. In Data Vault terms, it behaves as a hub: it carries a stable surrogate key (INVENTORY_LOCATION_ID) that is referenced by a very large number of dependent tables throughout Inventory, WIP, Receiving, Warehouse Management, and Process Manufacturing, while its own foreign keys point outward to a small set of reference masters. This makes it a candidate for a hub design in a Data Vault model, with attributes such as capacity, status, and flags distributed to satellites.

Key Information Stored

The primary key MTL_ITEM_LOCATIONS_PK is composed of INVENTORY_LOCATION_ID and ORGANIZATION_ID, where INVENTORY_LOCATION_ID is the surrogate locator identifier. A second unique index, MTL_ITEM_LOCATIONS_U1, also covers (INVENTORY_LOCATION_ID, ORGANIZATION_ID), reinforcing that this pair is the business-key candidate for the locator record.

Common Use Cases and Queries

The most common use case is resolving a locator ID from a transaction record back to its descriptive name and subinventory. Transaction tables such as MTL_MATERIAL_TRANSACTIONS, MTL_ONHAND_QUANTITIES, MTL_RESERVATIONS, and RCV_TRANSACTIONS all carry LOCATOR_ID, and virtually every locator-level inventory report joins back to MTL_ITEM_LOCATIONS.

  • Locator lookup for on-hand reporting — join MTL_ONHAND_QUANTITIES.LOCATOR_ID to INVENTORY_LOCATION_ID and ORGANIZATION_ID to list quantities by bin.
  • Listing active stock locators in a subinventory — filter on ORGANIZATION_ID, SUBINVENTORY_CODE, and ENABLED_FLAG = 'Y'.
  • Capacity and utilization reporting — query LOCATION_CURRENT_UNITS versus LOCATION_MAXIMUM_UNITS, or CURRENT_WEIGHT versus MAX_WEIGHT, to identify overfull or empty bins using EMPTY_FLAG.
  • Material status enforcement — join STATUS_ID to MTL_MATERIAL_STATUSES_B to identify locators restricted to quarantined or rejected stock.
  • Audit and receiving analysis — join MTL_MATERIAL_TRANSACTIONS or RCV_TRANSACTIONS on LOCATOR_ID to trace put-away and movement activity per locator.
  • Attribute and flexfield reporting — use ATTRIBUTE_CATEGORY/ATTRIBUTE1–15 and SEGMENT1–20 for site-specific locator classifications.

Related Objects

MTL_ITEM_LOCATIONS is referenced by an extensive set of dependent tables, confirming its hub role. The most significant relationships include: