Search Results eam_failure_codes




Overview
Explore in AI Chat

Overview

EAM_FAILURE_CODES is a reference (setup) table in the Oracle E-Business Suite Enterprise Asset Management (EAM) module, owned by the EAM schema. It stores the failure codes defined in the system — the standardized, user-defined reason codes that describe why an asset, component, or maintenance activity failed. In Oracle EBS 12.1.1 and 12.2.2, these codes form part of the reliability and maintenance-quality foundation of the product: they allow organizations to classify failure events consistently so that breakdown history, downtime analysis, and root-cause reporting can be aggregated and trended across assets and work orders.

The table is intentionally narrow, containing only eight documented columns in the 12.2.2 physical schema. This reflects its role as a lookup of valid code values rather than a transactional or historical record. From a heuristic Data Vault modeling perspective, EAM_FAILURE_CODES is best classified as a satellite-like reference set — effectively a hub of the business key (FAILURE_CODE) combined with its descriptive attributes (DESCRIPTION, effective dating, and audit columns). It is characterized in the mined relationship data as standalone, meaning it does not itself carry foreign keys to other EAM tables; it is referenced by other objects.

Key Information Stored

The most significant columns documented for this object are:

  • FAILURE_CODE — The business identifier for the failure code. This column is both the primary key column (via constraint EAM_FAILURE_CODES_PK) and the business-key candidate (via unique index EAM_FAILURE_CODES_U1). Because it is the single unique business key, it serves as the surrogate-and-business identifier for each row.
  • DESCRIPTION — The human-readable name or explanation of the failure code, presented to users on EAM work order and failure-analysis forms and reports.
  • EFFECTIVE_END_DATE — Supports date-effective (end-dating) behavior, allowing a failure code to be retired from active selection without deleting its historical usage.
  • CREATED_BY, CREATION_DATE — Standard WHO audit columns recording the creating user and timestamp.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns capturing the most recent modification user, timestamp, and login session.

Note that the table does not include a separate hidden surrogate numeric key in the documented metadata; the FAILURE_CODE itself is the primary key and the unique business key.

Common Use Cases and Queries

The most frequent use of this table is to populate and validate failure-code selection lists and to join failure code descriptions onto transactional failure and work-order data for reporting. A basic validation query retrieves the active, effective codes:

SELECT failure_code, description
FROM   eam.eam_failure_codes
WHERE  effective_end_date IS NULL
   OR  effective_end_date >= SYSDATE
ORDER BY failure_code;

For reliability reporting, the code list is joined to failure-combination data to attach descriptive text to historical failures. This supports Pareto analysis of failure causes, mean-time-between-failure (MTBF) trending, and downtime categorization by asset or location. Because the table is a reference set, it is also commonly extracted into data warehouses and reconciled against the EAM_FAILURE_COMBINATIONS mapping table to ensure every combination references a currently defined code.

Related Objects

The principal dependent object documented in the metadata is:

  • EAM_FAILURE_COMBINATIONS — References EAM_FAILURE_CODES through the join column EAM_FAILURE_COMBINATIONS.FAILURE_CODE. This table holds valid failure-code combinations (for example, failure code paired with cause and resolution codes), making EAM_FAILURE_CODES a parent lookup for those combination definitions.

Beyond the documented foreign-key relationship, failure codes are consumed by EAM work-order and failure-analysis functionality, where FAILURE_CODE values are captured on transactional records and reported against the DESCRIPTION held in this table. Administrators maintain the code list directly through the EAM setup (Failure Codes) forms, which write to this table.