Search Results eam_asset_failure_codes_u2

Overview

EAM.EAM_ASSET_FAILURE_CODES is a transactional table in the Oracle Enterprise Asset Management (eAM) module of Oracle E-Business Suite, valid in both release 12.1.1 and 12.2.2. The table stores the detail rows captured for an asset failure event, specifically the failure code, cause code, resolution code, and free-text comments entered by the user in the context of a work order. It is a child table of EAM_ASSET_FAILURES, which supplies the parent failure record, and it holds a foreign key to EAM_FAILURE_COMBINATIONS to identify the coded combination that was applied. Per the documented design, a single failure reported against an asset may carry one failure-code combination (COMBINATION_ID); the eAM user interfaces currently restrict reporting to one set of codes per asset failure. The table resides in the APPS_TS_TX_DATA tablespace with a PCTFREE of 10.

The metadata classifies this object heuristically as standalone under a Data Vault lens. Because it carries a surrogate primary key and descriptive code/comment attributes tied to a parent event, a Data Vault modeler might alternatively treat it as a satellite hanging off the EAM_ASSET_FAILURES hub, with the failure-code combination treated as a link to the failure-combination dimension.

Key Information Stored

The table contains twelve documented columns. The most operationally significant are listed below, distinguishing the surrogate key from business-key candidates defined by unique indexes.

• FAILURE_ENTRY_ID (NUMBER) — The surrogate primary key, enforced by unique index EAM_ASSET_FAILURE_CODES_U1. It uniquely identifies each failure-code detail row.
• FAILURE_ID (NUMBER) — Foreign key to the parent EAM_ASSET_FAILURES record; identifies the failure event to which these codes belong.
• COMBINATION_ID (NUMBER) — Foreign key to EAM_FAILURE_COMBINATIONS; identifies the coded failure combination applied to the event.
• FAILURE_CODE (VARCHAR2(80)) — The failure code describing the observed failure condition.
• CAUSE_CODE (VARCHAR2(80)) — The cause code describing the underlying root cause of the failure.
• RESOLUTION_CODE (VARCHAR2(80)) — The resolution code describing the corrective action taken.
• COMMENTS (VARCHAR2(2000)) — Free-text remarks captured by the user for the failure event.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Who columns tracking row creation and audit lineage.

A second unique index, EAM_ASSET_FAILURE_CODES_U2, covers the composite of FAILURE_ID, FAILURE_CODE, CAUSE_CODE, and RESOLUTION_CODE, making this quartet the documented business-key candidate and preventing duplicate code triplets against the same failure event.

Common Use Cases and Queries

The table is queried primarily when reporting on asset failure history, failure-code frequency, and root-cause analysis. A common pattern joins the detail rows back to the parent failure header and to the work order that generated the failure:

• Failure analysis: extracting all failure events for a given asset, grouped by FAILURE_CODE, CAUSE_CODE, and RESOLUTION_CODE, to identify recurring failure patterns and their dominant causes.
• Maintenance reporting: joining to EAM_ASSET_FAILURES on FAILURE_ID to retrieve work-order context, asset identity, and failure dates for a chosen interval.
• Code-combination validation: looking up COMBINATION_ID against EAM_FAILURE_COMBINATIONS to confirm that the reported failure, cause, and resolution codes form a valid, configured combination.
• Comment mining: scanning the COMMENTS column for qualitative maintenance observations that complement the structured code data.

A representative query retrieves all coded details for a specific failure event:

• SELECT FAILURE_ENTRY_ID, FAILURE_CODE, CAUSE_CODE, RESOLUTION_CODE, COMMENTS FROM EAM.EAM_ASSET_FAILURE_CODES WHERE FAILURE_ID = :p_failure_id;
• SELECT FAILURE_ID, FAILURE_CODE, COUNT(*) FROM EAM.EAM_ASSET_FAILURE_CODES GROUP BY FAILURE_ID, FAILURE_CODE ORDER BY 3 DESC;

Related Objects

• EAM.EAM_ASSET_FAILURES — The parent table; joined on FAILURE_ID. Provides the failure header, asset, and work-order linkage.
• EAM.EAM_FAILURE_COMBINATIONS — Referenced through COMBINATION_ID; defines the valid failure/cause/resolution code sets.
• EAM.EAM_ASSET_FAILURE_CODES_PK — The primary key constraint on FAILURE_ENTRY_ID that guarantees row uniqueness.
• EAM_ASSET_FAILURE_CODES_U1 / U2 — Unique indexes enforcing the surrogate key and the composite business-key candidate respectively.
• Work Order tables (eAM/WIP) — Linked indirectly through the parent failure record, providing the maintenance context in which the codes were captured.
• Failure code validation sets (FND lookups / eAM code definitions) — Supply the allowable FAILURE_CODE, CAUSE_CODE, and RESOLUTION_CODE values referenced in this table.