Search Results mtl_eam_locations




Overview
Explore in AI Chat

Overview

MTL_EAM_LOCATIONS is an Inventory (INV) module table that stores the EAM (Enterprise Asset Management) location definitions used by Oracle eAM to identify where assets, work orders, and maintenance activities are performed. In Oracle EBS 12.1.1 and 12.2.2, the table resides in the INV schema and holds the master list of asset locations per inventory organization. Each row represents a discrete EAM location — such as a physical area, building, line, or functional work center — and is scoped to a single inventory organization through ORGANIZATION_ID. The table is central to the eAM data model because eAM assets, work orders, and meter readings are frequently associated with an EAM location rather than a standard subinventory or stock locator.

From a Data Vault modeling perspective, the mined classification of this table is satellite-leaning. This is a heuristic suggestion: because the table carries descriptive attributes (LOCATION_CODES, DESCRIPTION, START_DATE, END_DATE) and is tied to a single parent (MTL_PARAMETERS via ORGANIZATION_ID), it behaves like a descriptive satellite rather than a hub or a link. Treating it as a satellite of the organization context is a reasonable modeling choice, though LOCATION_ID itself functions as the stable surrogate key.

Key Information Stored

The table contains 16 documented columns. The most significant are:

  • LOCATION_ID — Surrogate primary key (MTL_EAM_LOCATIONS_PK). Uniquely identifies each EAM location. Also surfaced as unique index MTL_EAM_LOCATIONS_U1.
  • LOCATION_CODES — The business identifier for the location, such as a short code or name. Combined with ORGANIZATION_ID, this forms unique index EAM_LOCATIONS_U2, making it the primary business-key candidate.
  • ORGANIZATION_ID — Foreign key to MTL_PARAMETERS. Scopes the location to a specific inventory organization and anchors the tenant/operating-unit context.
  • DESCRIPTION — Free-text description of the location, used in reporting and on work order documents.
  • START_DATE / END_DATE — Effective-dating attributes indicating when the location is valid for use. Inactive or retired locations are typically represented by an END_DATE in the past.
  • CREATION_ORGANIZATION_ID — The organization in which the location record was originally created, useful for multi-org audit and reconciliation.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns capturing who created and last modified the record.
  • REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program context columns recording which request and program inserted or updated the row.

Common Use Cases and Queries

Typical use cases include reporting on active EAM locations, validating location references on work orders, and generating asset-location listings for maintenance planning.

  • List active EAM locations for an organization:
    SELECT LOCATION_ID, LOCATION_CODES, DESCRIPTION
    FROM MTL_EAM_LOCATIONS
    WHERE ORGANIZATION_ID = :org_id
    AND (END_DATE IS NULL OR END_DATE > SYSDATE);
  • Resolve a location code to its surrogate key for join logic:
    SELECT LOCATION_ID FROM MTL_EAM_LOCATIONS
    WHERE LOCATION_CODES = :code AND ORGANIZATION_ID = :org_id;
  • Audit recently created locations using CREATION_DATE and CREATED_BY.
  • Join to MTL_PARAMETERS to obtain the organization name alongside location rows for cross-org reporting.

Related Objects

  • MTL_PARAMETERS — Referenced by MTL_EAM_LOCATIONS.ORGANIZATION_ID; provides inventory organization definition.
  • EAM_WORK_ORDERS / EAM_ASSETS — eAM work order and asset tables that commonly reference LOCATION_ID to indicate where maintenance occurs.
  • MTL_EAM_LOCATIONS_PK / MTL_EAM_LOCATIONS_U1 / EAM_LOCATIONS_U2 — Primary and unique indexes enforcing LOCATION_ID uniqueness and the LOCATION_CODES + ORGANIZATION_ID business key.
  • MTL_ITEM_LOCATIONS / MTL_SYSTEM_ITEMS — Related INV tables frequently joined for asset and item context surrounding EAM locations.
  • EAM Location APIs/concurrent programs — Standard eAM maintenance forms and import programs that read and write location rows, governed by the audit columns listed above.