Search Results eam_asset_failure_codes_pk

Overview

EAM_ASSET_FAILURE_CODES is a transactional table owned by the EAM schema within the Oracle Enterprise Asset Management (EAM) module. It stores the detailed coding information captured for a failure event. In the EAM data model, a failure event recorded in EAM_ASSET_FAILURES may be decomposed into one or more failure entries, each of which attributes the event to a specific failure code, cause code, and resolution code. This table holds that attribution detail, and it serves as the primary source for failure analysis, reliability reporting, and corrective action tracking.

The Data Vault classification for this table is a standalone classification, mined heuristically from its foreign key structure. Under a Data Vault modeling approach, this suggests the table behaves as a satellite-like detail structure anchored to an event parent, rather than as a pure hub or link. It is not a business key registry in its own right; its identity is derived from the parent failure record it qualifies.

Key Information Stored

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

• FAILURE_ENTRY_ID — the surrogate primary key, enforced by EAM_ASSET_FAILURE_CODES_PK and also indexed by EAM_ASSET_FAILURE_CODES_U1. It uniquely identifies each failure coding entry.
• FAILURE_ID — foreign key to EAM_ASSET_FAILURES, identifying the parent failure event to which this coding row belongs.
• COMBINATION_ID — foreign key to EAM_FAILURE_COMBINATIONS, linking the entry to a predefined valid combination of failure, cause, and resolution codes.
• FAILURE_CODE — the specific failure mode or fault classification observed.
• CAUSE_CODE — the assigned root cause of the failure.
• RESOLUTION_CODE — the corrective action or resolution applied.
• COMMENTS — free-form text describing the failure, diagnosis, or corrective work.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS audit columns providing creation and change attribution.

Beyond the primary key, the business-key candidate is captured by the unique index EAM_ASSET_FAILURE_CODES_U2 on the composite of FAILURE_ID, FAILURE_CODE, CAUSE_CODE, and RESOLUTION_CODE. This enforces that a given failure event cannot carry duplicate coding combinations.

Common Use Cases and Queries

Typical scenarios include failure code distribution analysis, root cause trending, reliability-centered maintenance reporting, and linking coding detail back to work orders and asset history. A representative query joining the detail table to its parent event is:

• SELECT f.FAILURE_ID, c.FAILURE_CODE, c.CAUSE_CODE, c.RESOLUTION_CODE, c.COMMENTS FROM EAM.EAM_ASSET_FAILURE_CODES c JOIN EAM.EAM_ASSET_FAILURES f ON f.FAILURE_ID = c.FAILURE_ID;
• SELECT FAILURE_CODE, COUNT(*) FROM EAM.EAM_ASSET_FAILURE_CODES GROUP BY FAILURE_CODE ORDER BY 2 DESC; — top failure modes.
• SELECT c.FAILURE_CODE, c.CAUSE_CODE, c.RESOLUTION_CODE FROM EAM.EAM_ASSET_FAILURE_CODES c WHERE c.COMBINATION_ID = :p_combination_id; — resolving code combinations.

These patterns support Pareto analysis on failure modes, mean-time-between-failure studies, and audit of the coding validity against configured combinations.

Related Objects

• EAM_ASSET_FAILURES — parent table referenced via FAILURE_ID; the primary join path for event-level context.
• EAM_FAILURE_COMBINATIONS — reference table referenced via COMBINATION_ID; defines valid failure/cause/resolution combinations.
• Failure code lookup and setup tables in the EAM module that populate FAILURE_CODE, CAUSE_CODE, and RESOLUTION_CODE values.
• Work order and asset history objects in EAM that consume failure coding for reliability reporting.

The two documented foreign keys — FAILURE_ID to EAM_ASSET_FAILURES and COMBINATION_ID to EAM_FAILURE_COMBINATIONS — are the essential relationships for navigating this table.