Search Results eam_failure_set_associations




Overview
Explore in AI Chat

Overview

The EAM_FAILURE_SET_ASSOCIATIONS table, owned by the EAM schema, defines the linkage between an inventory item and an associated failure set within Oracle Enterprise Asset Management. In Oracle EBS 12.1.1 and 12.2.2, this table acts as a mapping construct that records which failure sets apply to which inventory items, enabling maintenance organizations to associate standardized failure coding hierarchies with specific assets, equipment, or spare parts. The table's status is VALID and it resides within the EAM product module.

From a heuristic Data Vault modeling perspective, the FK structure suggests this object is satellite-leaning. It carries descriptive attributes—such as whether a failure code is mandatory—layered over a composite business key formed by SET_ID and INVENTORY_ITEM_ID. Rather than acting as a pure hub or link, it behaves as a dependent descriptive object tied to the failure set and item relationship.

Key Information Stored

The table contains nine documented columns. The composite primary key, EAM_FAILURE_SET_ASSOCIATION_PK, is defined on the pair SET_ID and INVENTORY_ITEM_ID. A unique index, EAM_FAILURESET_ASSOCIATION_U1, enforces the same combination, confirming this pair as the business-key candidate and preventing duplicate associations.

  • SET_ID — Identifies the failure set being associated; part of the composite PK and FK.
  • INVENTORY_ITEM_ID — Identifies the inventory item to which the failure set applies; the second component of the composite PK.
  • FAILURE_CODE_REQUIRED — Flag indicating whether a failure code must be captured during failure recording for this association.
  • EFFECTIVE_END_DATE — The date on which the association ceases to be effective, supporting date-effective maintenance of item-to-failure-set mappings.
  • CREATED_BY — The user who created the association record.
  • CREATION_DATE — The timestamp when the record was created.
  • LAST_UPDATED_BY — The user who last modified the record.
  • LAST_UPDATE_DATE — The timestamp of the most recent modification.
  • LAST_UPDATE_LOGIN — The login session identifier associated with the last update.

The audit columns follow standard Oracle EBS patterns and support change tracking and concurrency control across the application.

Common Use Cases and Queries

This table is principally queried when determining which failure sets are available for a given item, or conversely, which items reference a particular failure set. Typical scenarios include failure coding configuration, maintenance reporting by failure set, and validation of failure code requirements during work order completion.

  • Retrieve all failure sets associated with a specific item:
    SELECT set_id, failure_code_required FROM eam_failure_set_associations WHERE inventory_item_id = :item_id;
  • List items governed by a specific failure set, filtered by effective end date:
    SELECT inventory_item_id FROM eam_failure_set_associations WHERE set_id = :set_id AND (effective_end_date IS NULL OR effective_end_date > SYSDATE);
  • Reporting on associations requiring failure codes using the FAILURE_CODE_REQUIRED flag.
  • Auditing configuration changes via CREATION_DATE, LAST_UPDATE_DATE, and the associated user columns.

Related Objects

The documented foreign key relationship links SET_ID in this table to the failure set definition table, forming the primary dependency. The most significant related objects include:

  • EAM_FAILURE_SETS (or equivalent failure set definition table) — joined on SET_ID to resolve the failure set name and description.
  • MTL_SYSTEM_ITEMS_B — joined on INVENTORY_ITEM_ID to resolve item identifiers, descriptions, and organization attributes.
  • EAM_FAILURE_CODES — referenced through the failure set hierarchy to obtain the actual failure code values governed by FAILURE_CODE_REQUIRED.
  • EAM_FAILURE_SET_ASSOCIATIONS itself, self-referenced through the shared SET_ID column in the documented relationship data.
  • EAM_WORK_ORDERS and failure reporting entities — indirectly dependent when failure code entry is governed by these associations.

Together these objects support the end-to-end configuration of failure analysis within Enterprise Asset Management, with EAM_FAILURE_SET_ASSOCIATIONS serving as the item-level binding that activates failure sets for maintenance execution.