Search Results mtl_eam_network_assets_n2

Overview

INV.MTL_EAM_NETWORK_ASSETS is a transactional table in the Oracle E-Business Suite Inventory (INV) schema that stores information about assets associated with asset routes in the Enterprise Asset Management (EAM) module. Specifically, it records the effective start and end dates of associations between network objects and maintenance objects, allowing the system to maintain a time-phased history of how assets participate in linear or network-based asset structures.

The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, is owned by the INV schema, and is designated VALID in ETRM 12.2.2. Its primary key, MTL_EAM_NETWORK_ASSETS_PK, is defined on the surrogate column NETWORK_ASSOCIATION_ID. From a modeling perspective, the mined Data Vault classification for this object is link, since it resolves many-to-many style associations between network objects and maintenance objects with attribute-bearing effective dates.

Key Information Stored

The 37 documented columns support identity, effective dating, audit, and descriptive flexfield attributes. The most significant are:

• NETWORK_ASSOCIATION_ID — Surrogate primary key of the association. It is also the single column of the unique index MTL_EAM_NETWORK_ASSETS_U1, making it the documented business-key candidate.
• ORGANIZATION_ID — Organization identifier of the route asset; foreign key to MTL_PARAMETERS.
• START_DATE_ACTIVE / END_DATE_ACTIVE — Effective dating pairs that define the validity window of each association.
• NETWORK_ITEM_ID and NETWORK_SERIAL_NUMBER — Identify the network-side item and (where applicable) its serial number, the latter referencing MTL_SERIAL_NUMBERS.
• INVENTORY_ITEM_ID and SERIAL_NUMBER — Identify the maintenance-side item and serial number, with SERIAL_NUMBER also referencing MTL_SERIAL_NUMBERS.
• NETWORK_OBJECT_TYPE / NETWORK_OBJECT_ID — Polymorphic classification and identifier of the network object. NETWORK_OBJECT_ID is indexed by MTL_EAM_NETWORK_ASSETS_N1.
• MAINTENANCE_OBJECT_TYPE / MAINTENANCE_OBJECT_ID — Polymorphic classification and identifier of the maintenance object. MAINTENANCE_OBJECT_ID is indexed by MTL_EAM_NETWORK_ASSETS_N2.
• Standard who columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN.
• Concurrent program columns — REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — Descriptive flexfield columns.

Common Use Cases and Queries

Typical uses include reporting on assets currently associated with routes, resolving whether an association is active as of a given date, and tracing the maintenance/network pairing for a specific serial-numbered asset.

• Active associations for an organization on a given date:

  SELECT network_association_id, network_object_id,
         maintenance_object_id, start_date_active, end_date_active
    FROM inv.mtl_eam_network_assets
   WHERE organization_id = :org_id
     AND TRUNC(:as_of) BETWEEN start_date_active
                           AND NVL(end_date_active, :as_of);
  

• Finding associations by serial number: join SERIAL_NUMBER or NETWORK_SERIAL_NUMBER to MTL_SERIAL_NUMBERS.
• Retrieving all associations tied to a specific network object using the N1 index:

  SELECT * FROM inv.mtl_eam_network_assets
   WHERE network_object_id = :network_object_id;
  

• Auditing subsequent changes by querying LAST_UPDATE_DATE and LAST_UPDATED_BY.

Related Objects

The documented foreign keys and indexes reveal the primary related objects:

• INV.MTL_PARAMETERS — joined via ORGANIZATION_ID to obtain organization context.
• INV.MTL_SERIAL_NUMBERS — joined via SERIAL_NUMBER and NETWORK_SERIAL_NUMBER to resolve serialized asset identities.
• MTL_EAM_NETWORK_ASSETS_PK / _U1 — primary key and unique index on NETWORK_ASSOCIATION_ID.
• MTL_EAM_NETWORK_ASSETS_N1 — nonunique index supporting NETWORK_OBJECT_ID lookups.
• MTL_EAM_NETWORK_ASSETS_N2 — nonunique index supporting MAINTENANCE_OBJECT_ID lookups.
• The EAM network and maintenance object type columns reference the polymorphic parents implied by NETWORK_OBJECT_TYPE and MAINTENANCE_OBJECT_TYPE.