Results for “eam_item_type”

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

Overview

MTL_EAM_ITEMS_V is a public Oracle E-Business Suite view owned by the APPS schema and registered under the Inventory (INV) product family. As its documented description states, it presents a consolidated listing of all Enterprise Asset Management (EAM) items — that is, inventory items that have been flagged with an EAM item type so they can participate in maintenance work orders, asset hierarchies, and preventive maintenance scheduling. The view has been a standard, valid object across both the 12.1.1 and 12.2.2 releases, and its presence in ETRM confirms it as a supported reporting interface rather than a private implementation detail.

Its primary role is to expose only those item/organization combinations that are genuinely configured as maintainable assets, joining item master attributes to the maintenance organization and translating the internal lookup code stored on the item into a user-facing meaning. This makes it the natural starting point for asset registers, EAM item validation lists, and downstream integrations that must distinguish asset-type items from ordinary purchased or manufactured inventory.

Underlying Base Objects

The view is defined over three documented base objects:

• MTL_SYSTEM_ITEMS_KFV (documented in the 12.2.2 metadata as MTL_SYSTEM_ITEMS_VL) — the key-flexfield item master view supplying concatenated segment values, the item identifier, organization, description, EAM item type, and serial control code.
• MTL_PARAMETERS — the inventory organization parameters table (exposed to APPS as a synonym), used to relate each item's organization to its associated maintenance organization.
• MFG_LOOKUPS — the manufacturing lookup view, restricted to lookup type MTL_EAM_ASSET_TYPE. This is precisely the object referenced by the search term the user entered: the EAM item type is not free text but a validated lookup value drawn from this lookup type.

The join is an inner join on all three sources, so rows appear only where the item belongs to an organization with matching parameters and where the item's EAM_ITEM_TYPE matches an enabled lookup code. The lookup is additionally date-filtered, requiring SYSDATE to fall between the lookup's start and end active dates (with NVL defaults that treat a null start as yesterday and a null end as tomorrow), and to be enabled.

Key Columns

• CONCATENATED_SEGMENTS — the concatenated key flexfield segment string, the human-readable item identifier typically displayed on forms and reports.
• INVENTORY_ITEM_ID — the surrogate primary key of the item; required for any join back to MTL_SYSTEM_ITEMS_B or EAM tables.
• ORGANIZATION_ID — the inventory organization in which the item is defined.
• MAINT_ORGANIZATION_ID — the maintenance organization associated with that inventory organization, used to scope EAM work orders and asset activities.
• DESCRIPTION — the item description.
• EAM_ITEM_TYPE — the stored lookup code for the asset type.
• MEANING — the translated, user-facing meaning of that lookup code, sourced from MFG_LOOKUPS.
• SERIAL_NUMBER_CONTROL_CODE — indicates whether the item is serial-controlled, which is fundamental to tracking individual assets.

Common Use Cases and Queries

Typical uses include building an EAM asset register, populating value sets or LOVs restricted to valid asset items, validating item/organization combinations before creating maintenance work orders, and feeding external asset management or integration layers.

Listing all EAM items in a given maintenance organization:

• SELECT concatenated_segments, inventory_item_id, description, meaning, serial_number_control_code
• FROM apps.mtl_eam_items_v
• WHERE maint_organization_id = :maint_org_id
• ORDER BY concatenated_segments;

Resolving the friendly asset type for a specific item:

• SELECT inventory_item_id, organization_id, eam_item_type, meaning
• FROM apps.mtl_eam_items_v
• WHERE inventory_item_id = :item_id AND organization_id = :org_id;

Because the view does not expose all item attributes, most production queries join it back to MTL_SYSTEM_ITEMS_B on INVENTORY_ITEM_ID and ORGANIZATION_ID for costing, category, or UOM detail.