Search Results eam_suppression_relations_u1

Overview

EAM.EAM_SUPPRESSION_RELATIONS is a transactional table in the Oracle E-Business Suite Enterprise Asset Management (EAM) schema that stores preventive maintenance suppression rules and suppression templates. The core semantic of the table is a parent-child dependency: a parent activity suppresses a child activity, meaning the child maintenance activity should not be generated or executed when the parent activity applies within the tolerances defined on the row. This mechanism is used by maintenance planners to avoid redundant or duplicate work orders across functionally dependent assets.

The table distinguishes two record modes via the TMPL_FLAG column. When TMPL_FLAG equals 'Y', the row represents a suppression template, and the PARENT_ASSOCIATION_ID and CHILD_ASSOCIATION_ID values reference activity association templates in MTL_EAM_ASSET_ACTIVITIES. When TMPL_FLAG is 'N' or null, the row represents an operational suppression rule, and the same two columns reference concrete asset activity associations in MTL_EAM_ASSET_ACTIVITIES. This dual-purpose design allows templates to be defined once and instantiated into asset-specific rules.

From a Data Vault modeling perspective, the mined classification for this object is link. This is a reasonable modeling suggestion: the table primarily records a many-to-many relationship between parent and child activity associations, with the tolerances and descriptive attributes behaving as link-level or dependent attributes rather than hub or satellite payloads.

Key Information Stored

The table contains 27 documented columns. The most significant are:

• PARENT_ASSOCIATION_ID — identifier of the parent activity association; the suppressing activity.
• CHILD_ASSOCIATION_ID — identifier of the child activity association; the activity to be suppressed.
• DAY_TOLERANCE — numeric tolerance in days defining the window within which suppression applies.
• RUNTIME_TOLERANCE — numeric tolerance expressed in runtime units for suppression applicability.
• DESCRIPTION — VARCHAR2(240) free-text description of the suppression relationship.
• TMPL_FLAG — discriminator between suppression templates ('Y') and operational suppression rules ('N' or null).
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — descriptive flexfield columns for customer-extensible attributes.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns maintained by EBS.

Two index structures are documented. The primary key, EAM_SUPPRESSION_RELATIONS_PK, is composed of the composite columns (PARENT_ASSOCIATION_ID, CHILD_ASSOCIATION_ID). A separate unique index, EAM_SUPPRESSION_RELATIONS_U1, is documented on the same two columns (PARENT_ASSOCIATION_ID, CHILD_ASSOCIATION_ID) in tablespace APPS_TS_TX_IDX, making it the documented business-key candidate. Note that the two columns form a natural composite key without a single surrogate identifier; consumers should therefore treat the pair as the logical identity of each relationship row.

Common Use Cases and Queries

Typical scenarios include maintenance program setup, suppression rule validation, and reporting on which activities are suppressed by which parents. A basic query to list all suppression rules (non-template) with their tolerances is:

• SELECT parent_association_id, child_association_id, day_tolerance, runtime_tolerance, description FROM eam.eam_suppression_relations WHERE NVL(tmpl_flag,'N') = 'N' ORDER BY parent_association_id, child_association_id;
• Template inventory: SELECT parent_association_id, child_association_id, description FROM eam.eam_suppression_relations WHERE tmpl_flag = 'Y';
• Join to the activity associations to resolve descriptions: SELECT s.child_association_id, a.association_name FROM eam.eam_suppression_relations s, eam.mtl_eam_asset_activities a WHERE s.child_association_id = a.association_id AND s.tmpl_flag = 'Y';
• Flexfield-driven reporting by filtering on ATTRIBUTE_CATEGORY and a specific ATTRIBUTE column configured for customer metadata.

Because both association columns are keyed, DBA and integration scenarios frequently query this table by composite key for updates and existence checks during data loading or migration, which is precisely the pattern served by EAM_SUPPRESSION_RELATIONS_U1.

Related Objects

• MTL_EAM_ASSET_ACTIVITIES — referenced through both foreign keys: EAM_SUPPRESSION_RELATIONS.PARENT_ASSOCIATION_ID and CHILD_ASSOCIATION_ID both reference this table's association records.
• EAM_SUPPRESSION_RELATIONS_PK — the composite primary key constraint on (PARENT_ASSOCIATION_ID, CHILD_ASSOCIATION_ID).
• EAM_SUPPRESSION_RELATIONS_U1 — the unique composite index on the same column pair, defined in APPS_TS_TX_IDX.
• EAM schema objects describing asset activities and association templates — since the template and rule modes both resolve into MTL_EAM_ASSET_ACTIVITIES, the activity metadata maintained here is the primary dependency surface.
• Preventive maintenance program setup forms and concurrent processes — routine maintenance scheduling logic reads suppression relations to determine whether a child activity should be generated in a given window, using DAY_TOLERANCE and RUNTIME_TOLERANCE.

Consumers integrating with this table should preserve the WHO audit columns, honor the composite key during merges, and set TMPL_FLAG correctly to avoid conflating templates with operational rules.