Search Results parent_instance_number

Overview

MTL_EAM_ASSET_NUMBERS_ALL_V is an APPS-owned database view in the Oracle E-Business Suite Inventory (INV) module. It consolidates asset number, serial number, and Enterprise Asset Management (EAM) attribute information for maintained inventory items into a single queryable structure. The view is defined in the APPS schema and is documented as VALID in the ETRM repository for both 12.1.1 and 12.2.2.

Its primary role is to expose asset-instance metadata for reporting, integration, and inquiry forms where a flattened, read-only projection of EAM asset attributes is required. It joins item instance, serial number, item master, and maintenance organization data, abstracting complex base-table relationships behind a single view. The presence of user-defined attribute columns (ATTRIBUTE1 through ATTRIBUTE30) and the CONTEXT column indicates support for descriptive flexfield values, making the view suitable for extensible reporting on customer-specific asset attributes.

Underlying Base Objects

The view is constructed over a broad set of EAM, Inventory, and shared reference objects. Core dependencies include CSI_ITEM_INSTANCES, which supplies the instance-level row identity (via ROWID), subinventory, locator, category, and asset criticality information; MTL_SERIAL_NUMBERS, which contributes the serial number and current organization; and MTL_SYSTEM_ITEMS and its key flexfield view MTL_SYSTEM_ITEMS_B_KFV, which supply concatenated segments, EAM item type, and item description.

Additional joins bring in maintenance defaults through EAM_ORG_MAINT_DEFAULTS and EAM_ASSET_SAFETY_TYPES, maintenance organization codes through MTL_PARAMETERS, and department and location reference data through BOM_DEPARTMENTS, MTL_EAM_LOCATIONS, and PN_LOCATIONS_ALL. Hierarchical and geographic data is retrieved via MTL_OBJECT_GENEALOGY, CSI_II_GEOLOCATIONS, and CSI_GIS_INSTANCE_LOC_UTL_PKG. Fixed asset linkage is provided by FA_ADDITIONS_B and CSI_I_ASSETS. Lookup meanings are resolved through MFG_LOOKUPS, party and site reference through HZ_PARTY_SITES and HZ_LOCATIONS, and supplier association through PO_VENDOR_SITES_ALL. This dependency set confirms the view's role as a cross-functional integration point between Inventory, EAM, and Fixed Assets.

Key Columns

• INVENTORY_ITEM_ID, SERIAL_NUMBER, ROW_ID: Identity columns linking each asset record to its item instance and serial number.
• DESCRIPTIVE_TEXT: Derived from INSTANCE_DESCRIPTION or the serial number's descriptive text, providing the asset's human-readable name.
• CURRENT_SUBINVENTORY_CODE, CURRENT_LOCATOR_ID, CURRENT_ORGANIZATION_ID: Physical and organizational placement of the asset.
• FA_ASSET_ID, ASSET_NUMBER (FA_ASSET_NUMBER), ASSET_CATEGORY_ID: Fixed asset synchronization identifiers, relevant to the fa_sync_flag search context — these columns tie EAM assets to Oracle Assets records.
• MAINTAINABLE_FLAG, ASSET_CRITICALITY_CODE, ASSET_CRITICALITY: Maintenance eligibility and criticality indicators.
• EAM_ITEM_TYPE, ASSET_GROUP_DESCRIPTION, CONCATENATED_SEGMENTS: Item-definition attributes describing the asset group.
• NETWORK_ASSET_FLAG, CATEGORY_NAME, PN_LOCATION_NAME: Network classification and physical position details.
• ATTRIBUTE1–ATTRIBUTE30, CONTEXT: Descriptive flexfield segments for customer extensions.

Common Use Cases and Queries

The view is typically used to report asset inventories, verify Fixed Asset linkage, and populate custom asset dashboards. A representative query to inspect assets and their Fixed Asset correspondence is:

SELECT inventory_item_id,
       serial_number,
       descriptive_text,
       current_subinventory_code,
       fa_asset_id,
       fa_asset_number,
       maintainable_flag
FROM   apps.mtl_eam_asset_numbers_all_v
WHERE  fa_asset_id IS NOT NULL;

Because the view includes EAM item type and asset group columns, it also supports filtering by equipment classification, for example restricting results to a specific EAM_ITEM_TYPE. Integration scripts frequently use the view to reconcile EAM-maintained instances against FA_ADDITIONS_B when validating the fa_sync_flag condition. Organizations should note that, as a view, it inherits no independent storage and performance depends on the underlying base tables and indexing; restricting queries by organization or serial number is advisable for large datasets.