Results for “maint_organization_id”

50+ results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

EAM_ASSET_FAILURES is a table in the EAM (Enterprise Asset Management) schema of Oracle E-Business Suite, valid across releases 12.1.1 and 12.2.2. It stores information about failure events recorded against assets, forming the transactional backbone of maintenance failure analysis, reliability reporting, and root-cause tracking within the Oracle EAM module. Each row represents a discrete failure event tied to a maintained asset, with associations to the organization, department, and functional area responsible for the event. Typical database administrators and EAM implementers query this object through the synonym EAM.EAM_ASSET_FAILURES or the corresponding EAM data model views.

From a Data Vault modeling perspective, the heuristic classification for this table is standalone — that is, it does not cleanly resolve to a pure hub, link, or satellite. It carries its own surrogate key, business keys, and descriptive attributes, reflecting a self-contained record of failure history rather than a normalized dimensional construct.

Key Information Stored

The table contains 15 documented columns. The most significant columns and their roles are:

Common Use Cases and Queries

Reliability engineers and maintenance planners use this table to analyze failure trends by asset, organization, department, and area. Common queries include:

  • Failure counts grouped by asset: SELECT OBJECT_ID, COUNT(*) FROM EAM.EAM_ASSET_FAILURES GROUP BY OBJECT_ID;
  • Failures within a date range: SELECT FAILURE_ID, FAILURE_DATE FROM EAM.EAM_ASSET_FAILURES WHERE FAILURE_DATE BETWEEN :from_date AND :to_date;
  • Failures by maintenance organization: SELECT MAINT_ORGANIZATION_ID, COUNT(*) FROM EAM.EAM_ASSET_FAILURES GROUP BY MAINT_ORGANIZATION_ID;
  • Joining to departments: SELECT f.FAILURE_ID, d.DEPARTMENT_CODE FROM EAM.EAM_ASSET_FAILURES f, BOM.BOM_DEPARTMENTS d WHERE f.DEPARTMENT_ID = d.DEPARTMENT_ID;

These patterns support MTBF/MTTR reporting, maintenance cost analysis, and asset performance dashboards.

Related Objects

The following objects are most significant in relation to EAM_ASSET_FAILURES, based on the documented FK relationships:

  • EAM_ASSET_FAILURE_CODES — references EAM_ASSET_FAILURES via FAILURE_ID; stores failure code details.
  • BOM_DEPARTMENTS — referenced by DEPARTMENT_ID; provides department context.
  • PAY_FUNCTIONAL_AREAS — referenced by AREA_ID; provides functional area context.
  • EAM_ASSET_FAILURES_PK / _U1 / _U2 — primary and unique indexes enforcing uniqueness on FAILURE_ID and SOURCE_ID.

Together these objects enable comprehensive failure analysis across the Oracle EAM data model.