Results for “instance_number”

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

Overview

The MTL_EAM_ASSET_REBUILDS_V view is an APPS-owned database view in the Oracle E-Business Suite Inventory (INV) module that consolidates asset, rebuild, and object genealogy information for Enterprise Asset Management (EAM) items. It is defined as a VALID object within the ETRM documentation for releases 12.1.1 and 12.2.2. The view presents a read-only projection that joins item instance data with serial number records, object genealogy relationships, category assignments, and system item attributes, allowing reporting and integration consumers to identify assets alongside their rebuild parents and child counts without writing complex multi-table joins directly against the base tables.

Its primary role is to expose hierarchical asset relationships — specifically the linkage between a rebuilt asset and the parent object from which it originated — while filtering to EAM item types and active, serial-controlled instances. The view is commonly accessed in asset tracking dashboards, rebuild reporting, and integration extracts where consumers need a single-row-per-asset representation enriched with parent asset metadata.

Underlying Base Objects

The view is constructed over six documented base objects, all referenced through APPS synonyms except one view:

• CSI_ITEM_INSTANCES (SYNONYM) — source of the item instance, serial number, instance description, criticality, maintainability flag, and active date ranges.
• MTL_SYSTEM_ITEMS_B_KFV (VIEW) — provides concatenated item segments, EAM item type, and asset group description.
• MTL_SERIAL_NUMBERS (SYNONYM) — supplies serial number and genealogy object identifiers for both the asset and its parent.
• MTL_OBJECT_GENEALOGY (SYNONYM) — defines the parent-child object relationship used to derive PARENT_ITEM_ID, PARENT_SERIAL_NUMBER, and PARENT_OBJECT_ID.
• MTL_CATEGORIES_KFV (SYNONYM) — resolves the category name via an outer join on CATEGORY_ID.
• MTL_PARAMETERS (SYNONYM) — anchors the current maintenance organization identifier.

The join conditions restrict results to EAM item types 1 and 3, serial-controlled items, and instances whose active date range encompasses the current system date. Genealogy rows are further filtered to genealogy type 5 with active date validation.

Key Columns

• INVENTORY_ITEM_ID and SERIAL_NUMBER — primary asset identifiers from CSI_ITEM_INSTANCES.
• PARENT_ITEM_ID, PARENT_SERIAL_NUMBER, and PARENT_OBJECT_ID — the rebuild parent linkage derived from MTL_SERIAL_NUMBERS and MTL_OBJECT_GENEALOGY; these are the columns most frequently queried, including by the search term "parent_item_id".
• GEN_OBJECT_ID — the genealogy object identifier for the current asset.
• NO_OF_CHILDREN — a scalar subquery count of active MTL_OBJECT_GENEALOGY records where the current object acts as parent.
• CURRENT_ORGANIZATION_ID — the maintenance organization from MTL_PARAMETERS.
• CONCATENATED_SEGMENTS, EAM_ITEM_TYPE, and ASSET_GROUP_DESCRIPTION — item-level attributes.
• CATEGORY_NAME — resolved via the outer join to MTL_CATEGORIES_KFV.
• CURRENT_STATUS, INSTANCE_NUMBER, INSTANCE_ID, and DESCRIPTIVE_TEXT — instance-level detail.
• ASSET_CRITICALITY and MAINTAINABLE_FLAG — asset management flags, with maintainable defaulting to 'Y' via NVL.

Common Use Cases and Queries

Typical usage includes locating all assets that share a given rebuild parent, auditing rebuild trees, and counting descendant objects. A representative query retrieving parent linkage is:

• SELECT INVENTORY_ITEM_ID, SERIAL_NUMBER, PARENT_ITEM_ID, PARENT_SERIAL_NUMBER, NO_OF_CHILDREN FROM APPS.MTL_EAM_ASSET_REBUILDS_V WHERE PARENT_ITEM_ID = :item_id;
• SELECT CONCATENATED_SEGMENTS, INSTANCE_NUMBER, CURRENT_STATUS FROM APPS.MTL_EAM_ASSET_REBUILDS_V WHERE CURRENT_ORGANIZATION_ID = :org_id AND MAINTAINABLE_FLAG = 'Y';
• SELECT PARENT_ITEM_ID, COUNT(*) FROM APPS.MTL_EAM_ASSET_REBUILDS_V GROUP BY PARENT_ITEM_ID HAVING COUNT(*) > 1;

Because the view already filters for active, serial-controlled EAM assets, consumers avoid re-implementing those predicates. For performance, queries filtering on PARENT_ITEM_ID, INVENTORY_ITEM_ID, or CURRENT_ORGANIZATION_ID benefit from the indexed base tables beneath the view.