Results for “resolution_code”

50+ results




Overview
Explore in AI Chat

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

Overview

EAM.EAM_FAILURE_COMBINATIONS is a reference and transactional-link table within the Oracle E-Business Suite Enterprise Asset Management (EAM) module. It stores the unique Failure / Cause / Resolution (FCR) code combinations that are available to maintenance personnel when recording an asset failure event. In Oracle EAM terminology, a "combination" represents one valid permutation of a failure code, its associated cause code, and the corrective resolution code. By validating combinations in this table, EAM enforces code consistency — users cannot arbitrarily pair a resolution with an unrelated failure, which preserves the analytical integrity of maintenance history.

The table carries the combination identifier COMBINATION_ID as its surrogate primary key, defined by the constraint EAM_FAILURE_COMBINATIONS_PK. In line with the ETRM Data Vault classification included in the metadata, this object is best modeled as a link — a relationship table that connects three independent reference domains (failure codes, cause codes, resolution codes) within a given set. It is not a hub because it does not hold a standalone business entity, and it is not a satellite because it performs the joining role between the referenced code tables.

Key Information Stored

The table exposes eleven documented columns. The most significant are the following:

  • COMBINATION_ID — the numeric surrogate primary key assigned by the EAM sequence. This is the value referenced by downstream transactional tables, and it is the first column most users search for by name.
  • SET_ID — the reference data set (usually the operating unit or organization set) that scopes which combinations are valid for a given installation.
  • FAILURE_CODE — the failure mode or symptom, drawn from the EAM failure code list.
  • CAUSE_CODE — the underlying cause attributed to the failure, drawn from EAM_CAUSE_CODES.
  • RESOLUTION_CODE — the corrective action taken, drawn from EAM_RESOLUTION_CODES.
  • EFFECTIVE_END_DATE — the date on which the combination becomes inactive; a null value indicates an active combination.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard EBS audit columns used for change tracking and concurrency management.

Two unique indexes document the business-key candidates. EAM_FAILURE_COMBINATIONS_U1 enforces uniqueness of COMBINATION_ID (redundant with the primary key constraint but maintained separately), while EAM_FAILURE_COMBINATIONS_U2 enforces uniqueness across the deterministic business key of (SET_ID, FAILURE_CODE, CAUSE_CODE, RESOLUTION_CODE). The _U2 index is the meaningful business rule: within a set, no two rows may represent the same failure/cause/resolution triple.

Common Use Cases and Queries

A frequent scenario is to resolve a failure-code description to its surrogate key before inserting into EAM_ASSET_FAILURE_CODES. For example: 

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

Reporting users often need the full descriptive combination for analysis. Joining this table to its three reference domains produces a readable FCR listing: 

SELECT fc.combination_id, fc.failure_code, f.description failure_desc,
       fc.cause_code, c.description cause_desc,
       fc.resolution_code, r.description resolution_desc
FROM   eam.eam_failure_combinations fc
       LEFT JOIN eam.eam_cause_codes      c ON fc.cause_code = c.cause_code
       LEFT JOIN eam.eam_resolution_codes r ON fc.resolution_code = r.resolution_code
WHERE  fc.set_id = :p_set_id
AND    fc.effective_end_date IS NULL;

Typical uses include building maintenance-analytics dashboards (failure Pareto charts, MTTR analysis by resolution), restricting the LOVs shown on the EAM failure entry form, and auditing which combinations are active for a given operating unit.

Related Objects

  • EAM_CAUSE_CODES — referenced via CAUSE_CODE; provides the cause description and its own set context.
  • EAM_RESOLUTION_CODES — referenced via RESOLUTION_CODE; provides the resolution description.
  • EAM_FAILURE_CODES — referenced via FAILURE_CODE; provides the failure mode description.
  • EAM_ASSET_FAILURE_CODES — the key downstream table; its COMBINATION_ID column points back to this table, so every recorded asset failure resolves to one FCR combination.
  • HRI_EDW_EVENT_HRCHY_CMBNS — an HR/EDW hierarchy table that references COMBINATION_ID, exposing FCR combinations to the enterprise data warehouse.

In addition, the EAM Failure Code setup form and its underlying PL/SQL validation routines read this table when assembling the failure/cause/resolution LOV. Any change to an active combination should therefore be coordinated with those setup transactions to avoid orphaning existing asset failure records.