Search Results dimension_uom_code




Overview
Explore in AI Chat

Overview

MTL_ITEM_LOCATIONS_KFV is an Oracle E-Business Suite key flexfield view owned by the APPS schema and defined in the Inventory (INV) module. It presents the item location key flexfield information stored in the MTL_ITEM_LOCATIONS table in a form suitable for reporting, integration, and inquiry purposes. The suffix "KFV" denotes key flexfield view, indicating that this object is intended to expose the concatenated and descriptive flexfield segments associated with inventory locators alongside the core descriptive attributes of each location.

Within Oracle EBS 12.1.1 and 12.2.2, key flexfield views such as this one are commonly referenced by forms, concurrent programs, and custom reports that require a denormalized or presentation-oriented rendering of flexfield data. The view is documented as VALID in the ETRM repository, and its definition is a straightforward SELECT from the MTL_ITEM_LOCATIONS base object. Notably, in the documented view text the concatenated segment columns are hard-coded as the literal value 'X' rather than being derived from an underlying key flexfield segment table, which means that the view as shipped exposes the locator attributes rather than a true multi-segment concatenation. This is an important distinction for developers who expect KFV views to resolve segment values through the FND key flexfield structures.

Underlying Base Objects

The documented metadata lists a single referenced base object: MTL_ITEM_LOCATIONS, accessed through a SYNONYM. Every column exposed by the view is projected directly from that table, and no joins to FND key flexfield segment tables (such as FND_ID_FLEX_SEGMENTS or the segment value tables) are present in the documented view text. The view therefore functions as a column-level projection over MTL_ITEM_LOCATIONS rather than a join-based construct.

Because the definition selects from a synonym resolved to the APPS-owned base table, the view inherits the locator data for all organizations and subinventories recorded in MTL_ITEM_LOCATIONS. The ROWID of the base row is exposed as ROW_ID, preserving a direct handle to the underlying physical row for use in updates performed through the view where permitted by the application's integrity rules.

Key Columns

Common Use Cases and Queries

The view is frequently used to list locators for a given organization or subinventory, to filter active locators by status, and to inspect capacity and occupancy attributes for warehouse planning. A typical query ordering locators by their drop sequence is shown below.

  • SELECT inventory_location_id, organization_id, subinventory_code, description, picking_order, dropping_order FROM mtl_item_locations_kfv WHERE organization_id = :org_id AND subinventory_code = :subinventory ORDER BY dropping_order;
  • SELECT inventory_location_id, subinventory_code, enabled_flag FROM mtl_item_locations_kfv WHERE organization_id = :org_id AND enabled_flag = 'Y' AND locator_status IS NOT NULL;
  • SELECT inventory_location_id, empty_flag, mixed_items_flag, location_available_units FROM mtl_item_locations_kfv WHERE organization_id = :org_id AND empty_flag = 'Y';

Because the concatenated segment columns are represented as 'X' in the documented view text, custom code requiring true flexfield concatenation must query the base key flexfield structures directly rather than relying on MTL_ITEM_LOCATIONS_KFV. For standard locator attribute reporting, capacity analysis, and pick/drop sequencing, however, the view provides a convenient and stable projection of MTL_ITEM_LOCATIONS.