Search Results eam_failure_sets_u1

Overview

EAM.EAM_FAILURE_SETS is a foundational reference table within the Oracle Enterprise Asset Management (EAM) module, storing the definition of failure sets. A failure set functions as a reusable library of Failure, Cause, and Resolution (FCR) codes. Once defined, a failure set is associated with one or more Asset Groups so that failure information can be captured consistently at the work order level. The table resides in the EAM schema, holds the FND Design Data reference EAM.EAM_FAILURE_SETS, and is stored in the APPS_TS_TX_DATA tablespace with a PCT Free of 10. From a Data Vault modeling perspective, the mined FK structure classifies this object as standalone, which suggests it is best modeled as a hub or reference table rather than a link or satellite, since it maintains its own business keys without foreign key dependencies on other transactional entities. The object is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2.

Key Information Stored

The table is defined by nine documented columns. The most significant are:

• SET_ID (NUMBER) — The surrogate primary key and unique identifier for each failure set. It is enforced by the primary key constraint EAM_FAILURE_SETS_PK and by the unique index EAM_FAILURE_SETS_U1.
• SET_NAME (VARCHAR2(80)) — The failure set name and the principal business-key candidate, enforced by the unique index EAM_FAILURE_SETS_U2. This is the value the user searching for "eam_failure_sets_u2" is most likely targeting.
• DESCRIPTION (VARCHAR2(240)) — Descriptive text identifying the purpose or scope of the failure set.
• EFFECTIVE_END_DATE (DATE) — The date beyond which the failure set becomes inactive, supporting end-dating and versioning semantics.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Who columns providing auditing and concurrency tracking.

The distinction between the surrogate key (SET_ID) and the business-key candidate (SET_NAME) is important: applications should resolve a failure set by name for user-facing lookups while using SET_ID for stable internal joins.

Common Use Cases and Queries

Typical usage includes validating that a failure set exists, retrieving its defining attributes, and filtering active sets. A basic retrieval query follows the documented query text:

• SELECT SET_ID, SET_NAME, DESCRIPTION, EFFECTIVE_END_DATE FROM EAM.EAM_FAILURE_SETS;
• Resolving a set by business key: SELECT SET_ID, DESCRIPTION FROM EAM.EAM_FAILURE_SETS WHERE SET_NAME = :p_set_name;
• Identifying active sets: SELECT SET_ID, SET_NAME FROM EAM.EAM_FAILURE_SETS WHERE EFFECTIVE_END_DATE IS NULL OR EFFECTIVE_END_DATE > SYSDATE;
• Auditing recent changes: SELECT SET_NAME, LAST_UPDATED_BY, LAST_UPDATE_DATE FROM EAM.EAM_FAILURE_SETS ORDER BY LAST_UPDATE_DATE DESC;

Reporting scenarios include cataloging available failure libraries, confirming which sets remain assignable to Asset Groups, and supporting maintenance analytics where FCR codes captured on work orders are traced back to their originating failure set.

Related Objects

The documented dependencies show that EAM.EAM_FAILURE_SETS does not reference any database object directly, but it is referenced by the APPS synonym EAM_FAILURE_SETS. In practice, the failure set is consumed through the EAM failure, cause, and resolution code tables that carry SET_ID as a foreign key, and through the Asset Group association tables that bind a failure set to maintenance assets. Work order failure capture interfaces read SET_ID to resolve the permitted FCR codes. The most significant dependent and adjacent objects include the APPS.EAM_FAILURE_SETS synonym, the failure code detail tables linked by SET_ID, the Asset Group definition tables that reference the set, and the work order failure entry APIs that validate SET_NAME against the EAM_FAILURE_SETS_U2 unique index.