Search Results alr_action_set_checks




Overview
Explore in AI Chat

Overview

The ALR_ACTION_SET_CHECKS table is a core data object within the Oracle E-Business Suite (EBS) Alert module (ALR). It functions as a critical junction table, linking the definition of an alert check to the specific action sets that should be executed when that check's condition is met. This table is essential for the operational logic of Oracle Alerts, a component used to monitor database events and business conditions, and to automatically trigger responses. It stores the configuration that determines which sequence of actions (like sending a message or running a concurrent program) is associated with a particular alert check, thereby enabling complex, multi-step automated workflows.

Key Information Stored

The table's primary key is a composite of APPLICATION_ID and CHECK_ID, ensuring uniqueness within the context of an EBS application. While the provided metadata does not list all columns, the foreign key relationships define its critical data points. The key columns include APPLICATION_ID (identifying the owning application), CHECK_ID (the unique identifier for this action set check record), ALERT_ID, ALERT_CHECK_ID, and ACTION_SET_ID. These columns store the foreign key references that form the relationships between an alert, its specific check condition, and the set of actions to perform. The ORACLE_ID column links to the database user (FND_ORACLE_USERID) context for the alert.

Common Use Cases and Queries

This table is primarily accessed for diagnostic, auditing, and configuration review purposes. Common scenarios include troubleshooting why an action set did not fire for a specific alert check or analyzing the workflow dependencies of an alert. A typical query would join ALR_ACTION_SET_CHECKS to ALR_ALERTS and ALR_ACTION_SETS to list all configured action sets for a given alert.

  • Sample Query: To find all action sets linked to a specific alert name:
    SELECT a.alert_name, ac.check_id, aset.action_set_name
    FROM alr_alerts a,
    alr_action_set_checks ac,
    alr_action_sets aset
    WHERE a.application_id = ac.application_id
    AND a.alert_id = ac.alert_id
    AND ac.application_id = aset.application_id
    AND ac.action_set_id = aset.action_set_id
    AND a.alert_name = '&ALERT_NAME';
  • Reporting use cases involve generating documentation of alert workflows or validating configurations during system migrations.

Related Objects

As evidenced by its foreign key constraints, ALR_ACTION_SET_CHECKS is a central hub with documented relationships to several key Alert tables. The table references parent entities and is referenced by child history and data tables.

  • Parent/Foreign Key References: FND_PRODUCT_INSTALLATIONS (APPLICATION_ID), ALR_ALERTS (APPLICATION_ID, ALERT_ID), ALR_ACTION_SETS (APPLICATION_ID, ACTION_SET_ID), ALR_ALERT_CHECKS (APPLICATION_ID, ALERT_CHECK_ID), FND_ORACLE_USERID (ORACLE_ID).
  • Child/Referencing Tables: ALR_ACTION_DATA (APPLICATION_ID, CHECK_ID), ALR_ACTION_HISTORY (APPLICATION_ID, CHECK_ID), ALR_ACTUAL_RESPONSES (APPLICATION_ID, ALERT_CHECK_ID), ALR_OUTPUT_HISTORY (APPLICATION_ID, CHECK_ID). These relationships show that the CHECK_ID from this table is used to track runtime data, history, and outputs for alert executions.