Search Results tracking_quantity




Overview
Explore in AI Chat

Overview

The APPS.MTL_SYSTEM_ITEMS_ER4_V view is a supplementary database view within the Oracle E-Business Suite inventory module. Its designated purpose is to simplify forms coding in Oracle Applications, providing a flattened, user-friendly projection of item-level attribute data. Oracle classifies this object as a "supplementary view," and the ETRM documentation explicitly warns that Oracle does not recommend querying or altering data using this view because it may change dramatically in subsequent minor or major releases. The view is registered under the FND Design Data namespace INV.MTL_SYSTEM_ITEMS_ER4_V with an owner of APPS and a status of VALID in both Oracle EBS 12.1.1 and 12.2.2.

The "ER" prefix in the view name indicates that this object was originally constructed as a forms support view for a specific form block, most likely the Master Item definition form or a similar inventory item maintenance screen. Its principal role today is as a denormalized read source in reporting and integration scenarios where organization context and unit-of-measure attributes (including the tracking quantity UOM) are needed alongside the inventory item identifier.

Underlying Base Objects

The ETRM dependency metadata documents that MTL_SYSTEM_ITEMS_ER4_V references the following base objects:

Notably, the documentation records that MTL_SYSTEM_ITEMS_ER4_V is not referenced by any other database object, confirming it is a terminal, leaf-level view intended purely for consumption rather than further dependency.

Key Columns

The view exposes twelve columns. The organization context is carried by ORGANIZATION_CODE, ORGANIZATION_NAME, ORGANIZATION_ID, and MASTER_ORGANIZATION_ID, while INVENTORY_ITEM_ID provides the primary item key. Unit-of-measure attributes dominate the remaining columns: PRIMARY_UNIT_OF_MEASURE, TRACKING_QUANTITY (labeled "Tracking UOM" in the metadata), ONT_PRICING_QTY_SOURCE (pricing UOM), SECONDARY_UOM, and SECONDARY_DEFAULT_IND (defaulting indicator). Two numeric deviation factors, DUAL_UOM_DEVIATION_HIGH and DUAL_UOM_DEVIATION_LOW, support dual unit of measure processing. Several character columns are defined as VARCHAR2(4000), reflecting the use of lookup-meaning resolution rather than stored scaled columns.

Common Use Cases and Queries

Because the user searched for tracking_quantity, the most direct practical use of this view is to retrieve the tracking unit of measure alongside the primary and secondary UOMs for an item in a given organization. Dual UOM configurations, lot and serial tracking, and pricing quantity sources are all available in a single query without joining the base tables manually.

A representative query follows:

SELECT organization_code,
       organization_name,
       inventory_item_id,
       primary_unit_of_measure,
       tracking_quantity,
       secondary_uom,
       secondary_default_ind,
       dual_uom_deviation_high,
       dual_uom_deviation_low
FROM   apps.mtl_system_items_er4_v
WHERE  organization_id = :p_org_id
AND    inventory_item_id = :p_item_id;

For reporting, the view is useful when organization code and name must be presented together with item UOM attributes without a manual join to HR_ALL_ORGANIZATION_UNITS_TL. For integration, it can serve as a lightweight extraction source, though Oracle's documented caution regarding stability should be observed and direct base-table queries considered for long-term interfaces.