Search Results eam_failure_sets_pk

Overview

EAM_FAILURE_SETS is a base table within the Oracle Enterprise Asset Management (EAM) module, owned by the EAM schema. It functions as the master repository for failure set definitions used in maintenance and reliability programs. A failure set in Oracle EAM is a user-defined grouping of failure codes that categorizes the ways an asset can fail, enabling standardized data capture during work order completion, failure analysis, and reliability reporting. Every failure set definition created through the EAM setup forms is persisted in this table.

The object carries a VALID status and is documented across Oracle EBS 12.1.1 and 12.2.2. Based on the FK structure mined from the data dictionary, the heuristic Data Vault classification for this object is standalone, which suggests a modeling treatment closer to an independent reference or lookup structure rather than a hub, link, or satellite within a Data Vault architecture. This is consistent with its role as a configuration-level entity that does not participate in heavy transactional foreign key relationships.

Key Information Stored

The documented physical schema for 12.2.2 lists nine columns. The most significant are:

• SET_ID — The surrogate primary key of the table, enforced by the index EAM_FAILURE_SETS_PK and also by the unique index EAM_FAILURE_SETS_U1. It uniquely identifies each failure set definition.
• SET_NAME — The business-key candidate for the failure set, enforced by the unique index EAM_FAILURE_SETS_UK (and EAM_FAILURE_SETS_U2). This is the user-visible name of the failure set.
• DESCRIPTION — Free-form descriptive text explaining the purpose or scope of the failure set.
• EFFECTIVE_END_DATE — The date on which the failure set ceases to be active, supporting date-effective or end-dated configuration.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Oracle EBS WHO columns capturing audit and concurrency information for each row.

Common Use Cases and Queries

Typical scenarios center on EAM setup and reporting. Administrators query this table to validate or extract failure set definitions for migration, audit, or documentation. Reliability engineers join it to downstream failure code assignments when performing failure analysis.

A representative query to list active failure sets:

• SELECT set_id, set_name, description FROM eam.eam_failure_sets WHERE effective_end_date IS NULL OR effective_end_date > SYSDATE;

A query resolving the set name for a given surrogate key:

• SELECT set_name FROM eam.eam_failure_sets WHERE set_id = :p_set_id;

Reporting use cases include generating a catalog of failure sets for reliability dashboards and reconciling configuration between environments via the SET_NAME business key.

Related Objects

The metadata identifies EAM_FAILURE_SETS as standalone in terms of mined foreign key structure, meaning no child tables were detected referencing it directly through enforced FKs. Nevertheless, within the broader EAM data model the following objects are functionally significant:

• EAM_FAILURE_CODES — Failure codes are grouped into failure sets; assignment relationships reference the set identifier.
• EAM_FAILURE_SET_CODES — Association table linking individual failure codes to a parent failure set, typically joined on SET_ID.
• EAM_WORK_ORDER_FAILURES — Captures failure data recorded against work orders, resolving to a failure set during analysis.
• EAM_ASSET_FAILURES — Records historical asset failure events that reference failure set members.
• EAM_FAILURE_SET_APIS / EAM setup forms — PL/SQL APIs and concurrent programs that insert and maintain rows in this table.

Because the mined structure indicates a standalone classification, integration is achieved primarily through application-level joins on SET_ID and SET_NAME rather than enforced database foreign keys.