Search Results eam_locations_u2

Overview

INV.MTL_EAM_LOCATIONS is a transactional table in the Oracle E-Business Suite Inventory (INV) schema that stores the master attributes of every Enterprise Asset Management (EAM) Area. In EAM terminology, an "area" is a logical subdivision of a maintenance organization — such as a production line, a building, a plant zone, or a work center cluster — used to group assets geographically or functionally so that maintenance activities can be planned, scheduled, and reported against a bounded location. Each row in the table represents one such area record, scoped to a specific inventory organization, with an effective dating window defined by START_DATE and END_DATE. The table is stored in the APPS_TS_TX_DATA tablespace with PCT Free 10, and its indexes reside in APPS_TS_TX_IDX.

Because the table holds descriptive and effective-dated attributes about an EAM Area rather than capturing transactional events or serving purely as a join between two external entities, a heuristic Data Vault classification suggests a satellite-leaning profile. The unique, business-meaningful pairing of LOCATION_CODES and ORGANIZATION_ID functions as the natural key, while the surrogate LOCATION_ID acts as the stable hub-style identifier. The presence of standard WHO columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN) and concurrent program request columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE) reinforces the satellite interpretation, since these track changes and provenance of the descriptive record over time. This classification is offered strictly as a modeling suggestion; the object is a conventional normalized EBS table, not a Data Vault construct.

Key Information Stored

The most significant columns, as documented in the ETRM metadata, are the following:

• LOCATION_ID — NUMBER. The surrogate primary key of the table, uniquely identified by the MTL_EAM_LOCATIONS_U1 unique index. This is the internal identifier used by foreign key relationships across EAM and maintenance tables.
• LOCATION_CODES — VARCHAR2(30). The human-readable location code of the area. Together with ORGANIZATION_ID it forms the EAM_LOCATIONS_U2 unique index, making it the business-key candidate that users actually recognize and quote in day-to-day operations.
• ORGANIZATION_ID — NUMBER. The inventory organization that owns the area; it is also the FK column referencing MTL_PARAMETERS. Every area is organization-scoped, and it participates in both the U2 and the non-unique MTL_EAM_LOCATIONS_N1 index.
• START_DATE / END_DATE — DATE. The effective dating window of the area, supporting point-in-time queries and enabling users to see historical versus currently active areas.
• DESCRIPTION — VARCHAR2(240). Free text describing the purpose or physical characteristics of the area.
• CREATION_ORGANIZATION_ID — NUMBER. Captures the organization in which the area record was originally created, which can differ from the operating ORGANIZATION_ID in multi-organization rollouts.
• Standard WHO columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — provide auditing and change tracking.
• Concurrent program columns — REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — identify the concurrent request and program responsible for the most recent change.

Common Use Cases and Queries

Typical scenarios include reporting on active EAM areas per organization, resolving an area code entered by a user into its internal LOCATION_ID, and auditing recently changed area definitions. A point-in-time query for currently effective areas in an organization looks like:

• SELECT location_id, location_codes, description FROM inv.mtl_eam_locations WHERE organization_id = :org_id AND SYSDATE BETWEEN start_date AND NVL(end_date, SYSDATE);
• To resolve a business key: SELECT location_id FROM inv.mtl_eam_locations WHERE location_codes = :code AND organization_id = :org_id;
• To audit recent changes: SELECT location_id, location_codes, last_update_date, last_updated_by, request_id FROM inv.mtl_eam_locations WHERE last_update_date > :since ORDER BY last_update_date DESC;
• Reporting use cases include area-to-organization coverage, validity-gap checks (START_DATE > END_DATE or overlapping effective ranges), and joins to asset tables to count assets per area.

Related Objects

The primary documented relationships are as follows:

• INV.MTL_PARAMETERS — Referenced by MTL_EAM_LOCATIONS.ORGANIZATION_ID; join on ORGANIZATION_ID to obtain the organization's parameters and validation context.
• INV.MTL_EAM_LOCATIONS index set — EAM_LOCATIONS_U2 (LOCATION_CODES, ORGANIZATION_ID), MTL_EAM_LOCATIONS_U1 (LOCATION_ID), and MTL_EAM_LOCATIONS_N1 (ORGANIZATION_ID) support key resolution and organization-based access paths.
• Asset and work order tables — EAM asset records and work orders that carry an area or location reference join to this table via LOCATION_ID.
• APPS synonyms and views — The APPS schema synonym MTL_EAM_LOCATIONS exposes the same structure for application and reporting layers.

Because INV.MTL_EAM_LOCATIONS references only MTL_PARAMETERS and is referenced by dependent EAM maintenance objects, it behaves as a stable master record for area definitions, suitable for both operational lookups and historical reporting.