Search Results pick_uom_code

Overview

WMS_ITEM_LOCATIONS_KFV is a view in the APPS schema owned by the Warehouse Management (WMS) product family. The ETRM metadata describes it plainly as a "Dummy view for Mobile Locator KFF." This description is central to understanding its purpose: the view exists to satisfy the key flexfield (KFF) interface conventions used by the Mobile Locator functionality, not to deliver an independently meaningful business dataset. It presents a column set that mirrors the structure expected by the locator key flexfield, but the descriptive flexfield segments themselves are not resolved from a genuine compiled segment string.

This is confirmed by the view text, which hard-codes the concatenated segment output. Both CONCATENATED_SEGMENTS and LOCATOR_SEGMENTS are returned as the literal string 'X' rather than being derived from the locator flexfield segments. In Oracle EBS 12.1.1 and 12.2.2, this pattern is common for placeholder views used during flexfield validation or mobile processing where a real segment concatenation is not required at the database-object level. Any reporting built directly against this view must therefore treat the segment columns as non-informative.

Underlying Base Objects

The documented base object is MTL_ITEM_LOCATIONS, referenced through a synonym. The view is defined as a straightforward projection over this table:

• MTL_ITEM_LOCATIONS — the inventory location master table that stores subinventory locations, coordinates, capacity attributes, and flexfield context columns.

Every column exposed by WMS_ITEM_LOCATIONS_KFV originates from MTL_ITEM_LOCATIONS, including ROWID aliased as ROW_ID. No joins, unions, or aggregations are present. Because it is a simple projection, the view inherits the row granularity of MTL_ITEM_LOCATIONS: one row per inventory location per organization. There is no filtering logic, so disabled, expired, or empty locations remain visible unless the caller adds predicates.

Key Columns

The view exposes a broad column list. The following are the most relevant in practice:

• ROW_ID — the underlying ROWID of the MTL_ITEM_LOCATIONS row, useful for row identification.
• INVENTORY_LOCATION_ID / ORGANIZATION_ID — the primary identifiers of a location and its owning inventory organization.
• CONCATENATED_SEGMENTS / LOCATOR_SEGMENTS — dummy values ('X') and must not be used as real segment strings.
• SUBINVENTORY_CODE — the subinventory to which the location belongs.
• MAX_CUBIC_AREA, CURRENT_CUBIC_AREA, AVAILABLE_CUBIC_AREA, SUGGESTED_CUBIC_AREA — cubic capacity metrics for the locator, central to warehouse space planning. The user's search term max_cubic_area maps directly to this column.
• MAX_WEIGHT, CURRENT_WEIGHT, AVAILABLE_WEIGHT, LOCATION_MAXIMUM_UNITS, LOCATION_CURRENT_UNITS, LOCATION_AVAILABLE_UNITS — weight and unit capacity controls.
• LENGTH, WIDTH, HEIGHT, VOLUME_UOM_CODE, DIMENSION_UOM_CODE — physical dimension attributes.
• ENABLED_FLAG, DISABLE_DATE, START_DATE_ACTIVE, END_DATE_ACTIVE, LOCATOR_STATUS — lifecycle and status indicators.
• X_COORDINATE, Y_COORDINATE, Z_COORDINATE, PICKING_ORDER, DROPPING_ORDER — physical placement and pick-path sequencing.

Common Use Cases and Queries

The view is typically queried when mobile or locator processing requires an MTL_ITEM_LOCATIONS-shaped result set, or when reporting on location capacity such as maximum cubic area. A representative query retrieving capacity attributes by organization and subinventory follows:

• Capacity review: SELECT inventory_location_id, organization_id, subinventory_code, max_cubic_area, current_cubic_area, available_cubic_area FROM apps.wms_item_locations_kfv WHERE organization_id = :org_id AND subinventory_code = :sub;
• Active locations only: add AND enabled_flag = 'Y' and filter out rows where disable_date IS NULL OR disable_date > SYSDATE.
• Pick-path ordering: select picking_order, x_coordinate, y_coordinate, z_coordinate ordered by picking_order for put-away and picking configuration.

Because the segment columns are dummies, applications requiring a true locator flexfield concatenation should query the underlying flexfield views or MTL_ITEM_LOCATIONS directly. WMS_ITEM_LOCATIONS_KFV should be regarded as a compatibility and interface artifact rather than a reporting source of record.