Search Results eam_failure_combinations_u1

Overview

EAM.EAM_FAILURE_COMBINATIONS is a transactional configuration table within the Oracle Enterprise Asset Management (EAM) module of Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the library of unique combinations of a failure code, a cause code, and a resolution code, each combination belonging to a defined failure set. In operational terms, this table constitutes the curated catalogue that maintenance planners and reliability engineers assemble so that failure reporting against assets of a specific type remains consistent, standardized, and analytically usable.

Each row represents one logically valid triplet — a specific failure paired with its permissible cause and the resolution applied — scoped to a failure set (SET_ID). The table is therefore the transactional intersection of three independent code libraries, and it is the object that governs which failure narratives are available when users record asset failure events.

From a Data Vault modeling perspective (heuristic, mined from the foreign-key structure), this object is best classified as a link table. It resolves a many-to-many relationship among failure sets, failure codes, cause codes, and resolution codes, and it carries descriptive, time-bounded attributes such as EFFECTIVE_END_DATE, which is characteristic of a link with a lightweight satellite or effectivity extension. This classification is a modeling suggestion rather than a physical design constraint.

Key Information Stored

The most significant columns in this table are:

• COMBINATION_ID — Sequence-generated surrogate primary key (defined by EAM_FAILURE_COMBINATIONS_PK). It uniquely identifies each failure-cause-resolution combination and is the column referenced by downstream transactional tables.
• SET_ID — Identifier of the failure set to which the combination belongs; the primary scoping and grouping attribute.
• FAILURE_CODE — The failure code (VARCHAR2(80)) describing the observed failure mode.
• CAUSE_CODE — The cause code (VARCHAR2(80)) identifying the root cause associated with the failure.
• RESOLUTION_CODE — The resolution code (VARCHAR2(80)) identifying the corrective action applied.
• EFFECTIVE_END_DATE — The date beyond which the combination is considered inactive, enabling soft retirement of combinations without deletion.
• Standard Who columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN, which provide the audit trail required for all EBS transactional data.

Two unique indexes define the business-key candidates. EAM_FAILURE_COMBINATIONS_U1 enforces uniqueness on the surrogate COMBINATION_ID. EAM_FAILURE_COMBINATIONS_U2 — the index referenced in the user's search — enforces uniqueness on the natural composite key of SET_ID, FAILURE_CODE, CAUSE_CODE, and RESOLUTION_CODE. This composite constraint guarantees that no duplicate combination can exist within a single failure set, which is precisely the integrity rule that makes the library reliable for reporting. The table is stored in the APPS_TS_TX_DATA tablespace with PCTFREE 10, and its indexes reside in APPS_TS_TX_IDX.

Common Use Cases and Queries

The principal use case is failure reporting on assets: when a maintenance technician records a failure against an asset, the valid failure-cause-resolution triplets are drawn from this table, filtered by the failure set associated with the asset's type. Reliability engineers also query the table to audit which combinations are still active, and to validate that a proposed combination does not already exist within a set.

A representative query retrieves all active combinations for a given failure set:

• SELECT combination_id, failure_code, cause_code, resolution_code FROM eam.eam_failure_combinations WHERE set_id = :p_set_id AND (effective_end_date IS NULL OR effective_end_date > SYSDATE);

A duplicate-detection query against the unique business key is equally common before inserting new combinations:

• SELECT combination_id FROM eam.eam_failure_combinations WHERE set_id = :set_id AND failure_code = :f AND cause_code = :c AND resolution_code = :r;

Reporting scenarios include frequency analysis of failures by cause within a set, resolution effectiveness analysis, and extraction of the complete combination catalogue for use in third-party reliability tools or the HR hierarchy/EDW extracts.

Related Objects

The following objects have the most significant documented relationships with EAM_FAILURE_COMBINATIONS:

• EAM_ASSET_FAILURE_CODES — References this table through COMBINATION_ID; records actual failure events logged against assets.
• HRI_EDW_EVENT_HRCHY_CMBNS — References COMBINATION_ID for HR/EDW hierarchy and event reporting.
• EAM_CAUSE_CODES — Referenced by the CAUSE_CODE foreign key; the lookup library of valid causes.
• EAM_RESOLUTION_CODES — Referenced by the RESOLUTION_CODE foreign key; the lookup library of valid resolutions.
• EAM_FAILURE_COMBINATIONS# — The underlying base table object referenced by this table in the dependency chain.

The SET_ID and FAILURE_CODE relationships are also documented as foreign-key dependencies; their parent lookup tables should be identified during implementation before building joins.