Results for “mtl_locator_restrictions”

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

Overview

APPS.MTL_SYSTEM_ITEMS_ER1_V is a reporting view in Oracle E-Business Suite 12.1.1 and 12.2.2 that presents enriched item master information. The suffix "ER1" denotes an "Entity Relationship" style reporting view, designed to expose denormalized item attributes together with their decoded, user-facing meanings rather than raw coded values. It is built primarily over MTL_SYSTEM_ITEMS_B_KFV and MTL_SYSTEM_ITEMS_TL, joining organizational and category context so that a single query returns descriptive item data suitable for reports, integrations, and ad hoc analysis.

The view is especially relevant to users searching for mtl_locator_restrictions, because one of its columns exposes the RESTRICT_LOCATORS_CODE attribute decoded through the MTL_LOCATOR_RESTRICTIONS lookup. This allows report authors to display whether an item's placement in locators is unrestricted, restricted, or fixed, without manually joining to the lookup tables.

Underlying Base Objects

The documented metadata lists the following referenced base objects for this view:

• MTL_SYSTEM_ITEMS_B_KFV and MTL_SYSTEM_ITEMS_TL — the item master base (key flexfield) and translated description tables, providing core item attributes and language-dependent descriptions.
• MTL_SYSTEM_ITEMS_B_KFV supplies INVENTORY_ITEM_ID, ORGANIZATION_ID, coded item attributes, and concatenated segments.
• HR_ALL_ORGANIZATION_UNITS_TL, HR_ORGANIZATION_UNITS, HR_GENERAL, and HR_SECURITY — provide organization name and the security model governing which organizations a user may access.
• MTL_PARAMETERS — supplies inventory organization parameters referenced in the join logic.
• MTL_ITEM_CATALOG_GROUPS_KFV and FA_CATEGORIES_B_KFV — provide category concatenated segments and category structure.
• MTL_ITEM_LOCATIONS_KFV, MTL_ITEM_SUB_DEFAULTS, OKS_COVERAGE_TEMPLTS_V, and RCV_ROUTING_HEADERS — supporting objects used in assembling the view's full column set.
• INV_MEANING_SEL — a package supplying the decoding functions c_fndcommon, c_unitmeasure, c_fnd_lookup_vl, c_mfg_lookup, c_lot_lookup, and c_seria... that translate stored codes into display meanings.

Key Columns

The view exposes item identity columns INVENTORY_ITEM_ID and ORGANIZATION_ID, along with ORGANIZATION_CODE and organization NAME from the HR organization tables. Item identification is completed by the two CONCATENATED_SEGMENTS columns (item key flexfield and category), plus MSI.DESCRIPTION and MSTL.LONG_DESCRIPTION.

Status and control columns include INVENTORY_ITEM_STATUS_CODE, INVENTORY_ITEM_FLAG, STOCK_ENABLED_FLAG, and MTL_TRANSACTIONS_ENABLED_FLAG, decoded where appropriate through ITEM_TYPE. UOM-related columns include PRIMARY_UOM_CODE, SECONDARY_UOM_CODE, DUAL_UOM_DEVIATION_HIGH/LOW, and ALLOWED_UNITS_LOOKUP_CODE.

The control-related attributes most relevant to the locator question are LOCATION_CONTROL_CODE, RESTRICT_SUBINVENTORIES_CODE, and RESTRICT_LOCATORS_CODE — the last decoded via MTL_LOCATOR_RESTRICTIONS. Lot, serial, and shelf-life attributes are also present: LOT_CONTROL_CODE, SERIAL_NUMBER_CONTROL_CODE, SHELF_LIFE_CODE and SHELF_LIFE_DAYS, along with LOT_STATUS_ENABLED and SERIAL_STATUS_ENABLED. REVISION_QTY_CONTROL_CODE and RESERVABLE_TYPE round out the planning and reservation controls.

Common Use Cases and Queries

Typical uses include item master extracts, organization-level item reports, integration feeds, and validating item setup. Because it decodes coded values, it is well suited for reports that must present human-readable meanings.

The example below retrieves locator restriction information per item, which is the scenario implied by the search term mtl_locator_restrictions:

• SELECT inventory_item_id, organization_id, organization_code, name, description, restrict_locators_code, location_control_code FROM apps.mtl_system_items_er1_v WHERE organization_code = :p_org;

To isolate items whose locator placement is restricted, filter on the decoded value returned by the MTL_LOCATOR_RESTRICTIONS lookup, or add predicates such as restrict_subinventories_code to examine subinventory restrictions alongside locator restrictions. Joining the view to MTL_ITEM_LOCATIONS on organization and item context supports locator-level availability reporting, while the HR_SECURITY package already embedded in the view's definition naturally limits results to the organization set the user is authorized to see.