Search Results mtl_eam_network_assets




Overview
Explore in AI Chat

Overview

MTL_EAM_NETWORK_ASSETS is an Enterprise Asset Management (EAM) table owned by the INV (Inventory) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to store the association of assets to an asset route — that is, the network relationship that links a maintainable asset (or network object) to the asset or serialized item it belongs to or traverses. Asset routes, sometimes called linear assets or network assets, are used in EAM to model infrastructure such as pipelines, transmission lines, and roadways, where the relationship between a network parent and its associated assets must be tracked across an organization.

The table is documented with 37 columns and is registered in the ETRM repository as VALID. Based on the mined foreign key structure, the heuristic Data Vault classification for this object is a link table. This classification is a modeling suggestion only: the table serves as an associative entity that resolves many-to-many relationships between serialized network objects and maintenance assets, rather than acting as a standalone hub or a descriptive satellite.

Key Information Stored

The primary key is NETWORK_ASSOCIATION_ID, defined by the constraint MTL_EAM_NETWORK_ASSETS_PK and reinforced by the unique index MTL_EAM_NETWORK_ASSETS_U1, which makes it the principal business-key candidate for the row identity.

Common Use Cases and Queries

Typical reporting needs include listing all assets associated with a given network object, auditing associations created by a specific concurrent program, and checking which associations are currently active. A representative query is:

SELECT network_association_id, organization_id,
       network_item_id, network_serial_number,
       inventory_item_id, serial_number,
       start_date_active, end_date_active
FROM   mtl_eam_network_assets
WHERE  organization_id = :org_id
AND    TRUNC(SYSDATE) BETWEEN NVL(start_date_active, SYSDATE)
                          AND NVL(end_date_active, SYSDATE);

Because the table references MTL_SERIAL_NUMBERS twice, joins must alias the serial number table distinctly for network and maintenance sides to avoid ambiguous column resolution. The ATTRIBUTE columns support customer-specific reporting where standard columns are insufficient, and the program audit columns assist in data correction and reconciliation tasks.

Related Objects

  • MTL_PARAMETERS — joined on ORGANIZATION_ID to resolve organization context.
  • MTL_SERIAL_NUMBERS — joined twice: on (NETWORK_ITEM_ID, NETWORK_SERIAL_NUMBER) for the network object and on (INVENTORY_ITEM_ID, SERIAL_NUMBER) for the maintenance asset, both qualified by ORGANIZATION_ID.
  • MTL_SYSTEM_ITEMS_B — referenced indirectly via the item identifiers for descriptive item information.
  • EAM asset route and network API/forms — the application layer that maintains these associations.
  • MTL_EAM_NETWORK_ASSETS_PK / U1 — the constraints and unique index enforcing row identity.