Search Results eam_resolution_codes




Overview
Explore in AI Chat

Overview

EAM_RESOLUTION_CODES is a reference (lookup) table in the Oracle Enterprise Asset Management (EAM) module. It stores the resolution codes defined in the system — the standardized set of outcomes or remediation dispositions that can be recorded against a failure. In the EAM failure-analysis model, a maintenance activity typically proceeds from a failure code through a cause code to a resolution code, forming the diagnostic triad used in reliability-centered and corrective maintenance workflows. This table supplies the valid resolution-code values that feed that triad.

The table resides in the EAM schema and is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2. Its physical schema comprises 8 columns, of which one is the primary key and one is a unique business-key candidate. Based on the foreign-key relationships mined from the ETRM data, the heuristic Data Vault classification for this object is hub-leaning. As a modeling suggestion, this reflects its role as a code-identity hub: it holds the set of unique codes that other tables reference, rather than acting as a transactional satellite. Its only documented dependent is EAM_FAILURE_COMBINATIONS, which points at it via RESOLUTION_CODE.

Key Information Stored

The most significant columns in EAM_RESOLUTION_CODES, drawn from the documented metadata, are:

  • RESOLUTION_CODE — the primary business identifier and the backbone of the table. It is both the primary key column of EAM_RESOLUTION_CODES_PK and the unique index candidate in EAM_RESOLUTION_CODES_U1. Every dependent row in EAM_FAILURE_COMBINATIONS resolves against this column.
  • DESCRIPTION — the human-readable text associated with each resolution code, presented in EAM forms and reports wherever a resolution is selected or displayed.
  • EFFECTIVE_END_DATE — the date on which a resolution code ceases to be valid. This supports date-effective (temporal) lookups so that historical failure combinations retain their original resolution while the code is retired from new entry.
  • Creation and update audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN record who created and last modified each row and when, providing the standard EBS WHO-column audit trail.

Regarding keys: RESOLUTION_CODE is simultaneously the surrogate/PK column and the business-key candidate, since the unique index EAM_RESOLUTION_CODES_U1 is defined on the same column. There is therefore no separate hidden surrogate identifier; the code itself is the join key throughout the schema.

Common Use Cases and Queries

Resolution codes are surfaced during failure-entry and work-order closeout, when a technician records how a failure was resolved. The most frequent query pattern joins the resolution definition to the failure combination that uses it:

  • Listing all valid resolution codes for a value list or report: SELECT resolution_code, description FROM eam.eam_resolution_codes WHERE effective_end_date IS NULL OR effective_end_date > SYSDATE ORDER BY resolution_code;
  • Reporting failure combinations with resolution descriptions: SELECT fc.failure_code, fc.cause_code, fc.resolution_code, rc.description FROM eam.eam_failure_combinations fc JOIN eam.eam_resolution_codes rc ON fc.resolution_code = rc.resolution_code;
  • Reliability analysis that counts resolutions recorded across assets to identify recurring corrective actions.
  • Validation queries confirming that every resolution code referenced by EAM_FAILURE_COMBINATIONS still resolves to an active, non-expired definition.

Because the table is small and static, it is commonly cached in value lists and used as a driver in collection-style anti-joins to detect orphaned references.

Related Objects

The table participates in a narrow, well-defined set of relationships:

  • EAM_FAILURE_COMBINATIONS — the primary dependent. Its RESOLUTION_CODE column carries a foreign key to EAM_RESOLUTION_CODES.RESOLUTION_CODE, and this is the only documented foreign-key relationship in the ETRM metadata.
  • EAM_RESOLUTION_CODES_PK — the primary-key constraint enforcing RESOLUTION_CODE uniqueness and non-nullity.
  • EAM_RESOLUTION_CODES_U1 — the unique index on RESOLUTION_CODE that reinforces the business-key candidate.
  • EAM failure-code and cause-code tables — sibling lookup tables that, together with EAM_RESOLUTION_CODES, supply the three dimensions of EAM_FAILURE_COMBINATIONS.

These objects collectively form the EAM failure-diagnosis reference model, in which EAM_RESOLUTION_CODES serves as the resolution dimension referenced by the failure-combination intersection table.