Search Results eam_suppression_relations




Overview

EAM_SUPPRESSION_RELATIONS is an Enterprise Asset Management (EAM) table in the Oracle E-Business Suite, owned by the EAM schema. Its documented purpose is to store Preventive Maintenance (PM) suppression relations. In Oracle EBS, PM suppression allows a maintenance program to suppress the generation of a work order when another qualifying maintenance activity has already occurred or is scheduled within an allowable tolerance window. EAM_SUPPRESSION_RELATIONS captures those parent-child relationships between asset activities, together with the tolerance parameters that govern whether suppression applies.

The table is recorded in the ETRM 12.2.2 physical schema with 27 columns and is classified as a link in a heuristic Data Vault model mined from the foreign key structure. As a modeling suggestion, this classification reflects the table's role as an associative construct: it resolves a many-to-many relationship between maintenance activities rather than storing descriptive attributes about a single business entity. The parent and child association identifiers, both foreign keys to MTL_EAM_ASSET_ACTIVITIES, define the endpoints of each suppression relationship.

Key Information Stored

The most significant columns are:

  • PARENT_ASSOCIATION_ID — foreign key to MTL_EAM_ASSET_ACTIVITIES; identifies the asset activity that acts as the suppressing or controlling maintenance activity. Part of both the primary key and the unique index.
  • CHILD_ASSOCIATION_ID — foreign key to MTL_EAM_ASSET_ACTIVITIES; identifies the asset activity that may be suppressed. Also part of the primary key and unique index.
  • DAY_TOLERANCE — the day-based tolerance window used when evaluating suppression across the related activities.
  • RUNTIME_TOLERANCE — the runtime or meter-based tolerance applied to suppression evaluation, typical for meter-driven PM programs.
  • DESCRIPTION — user-facing text describing the suppression relationship.
  • TMPL_FLAG — indicates whether the record is a template definition rather than an active instance relationship.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard Oracle EBS descriptive flexfield (DFF) columns, providing extensibility for customer-specific attributes.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard audit columns tracking who created and last modified each row.

The surrogate primary key is EAM_SUPPRESSION_RELATIONS_PK, defined over PARENT_ASSOCIATION_ID and CHILD_ASSOCIATION_ID. The unique index EAM_SUPPRESSION_RELATIONS_U1 covers the same two columns, which serve as the composite business-key candidate: no two rows may define the same suppression pairing. No standalone generated surrogate column is documented; the composite identifier is the key.

Common Use Cases and Queries

The principal use case is diagnosing why a PM work order was or was not generated. For example, listing all child activities suppressed by a given parent activity:

SELECT child_association_id, day_tolerance, runtime_tolerance, description FROM eam.eam_suppression_relations WHERE parent_association_id = :parent_id;

A common reporting pattern joins both sides back to MTL_EAM_ASSET_ACTIVITIES to resolve readable activity context:

SELECT p.association_id, c.association_id, s.day_tolerance, s.runtime_tolerance FROM eam.eam_suppression_relations s, mtl_eam_asset_activities p, mtl_eam_asset_activities c WHERE s.parent_association_id = p.association_id AND s.child_association_id = c.association_id;

Other scenarios include auditing tolerance configuration before a PM run, reporting suppression matrices for maintenance planning, and identifying reciprocal or circular relations during data cleanup. Queries filtering on TMPL_FLAG separate reusable templates from live suppression definitions.

Related Objects

  • MTL_EAM_ASSET_ACTIVITIES — referenced twice via PARENT_ASSOCIATION_ID and CHILD_ASSOCIATION_ID; the definitive parent of the suppression link and the source of activity identity and scheduling attributes.
  • EAM_SUPPRESSION_RELATIONS_PK — the primary key constraint over the two association columns.
  • EAM_SUPPRESSION_RELATIONS_U1 — the unique business-key index, enforcing one relationship per parent-child pairing.
  • EAM Work Order / PM scheduling logic — consumes these rows during PM work order generation to decide whether a child activity is suppressed.
  • Standard audit and DFF infrastructure — FND audit columns and the ATTRIBUTE columns integrate with EBS flexfield and audit facilities.

Together these objects form the suppression graph used by EAM maintenance scheduling, making EAM_SUPPRESSION_RELATIONS a compact but operationally important link table.