Search Results alr_action_data




Overview
Explore in AI Chat

Overview

The ALR_ACTION_DATA table is a core data object within the Oracle E-Business Suite Alert (ALR) module. It functions as the repository for detailed exception information generated during the execution of an alert's action set. When a periodic alert runs its defined checks and identifies rows that meet its exception criteria, the specific data from those rows is captured and stored in this table. Its primary role is to provide a persistent, auditable record of the exact data that triggered an alert action, enabling review and analysis of the exceptions raised by the system.

Key Information Stored

The table's structure is designed to link exception data to a specific alert execution instance and its originating check. The primary key uniquely identifies each exception record through a combination of APPLICATION_ID, ACTION_HISTORY_ID, and ROW_NUMBER. The APPLICATION_ID ties the data to a specific EBS application. The ACTION_HISTORY_ID is a foreign key linking to the ALR_ACTION_HISTORY table, which logs the overall execution of an action set. The CHECK_ID column references the specific check within the action set that generated the exception. The table also contains columns for storing the actual exception data values, typically holding information such as the column names and values from the source table that violated the alert condition.

Common Use Cases and Queries

The primary use case is troubleshooting and auditing alert performance. Administrators query this table to verify what specific data triggered an alert, especially when the output is unexpected. A common reporting need is to list all exceptions generated by a particular alert run. A sample query pattern joins ALR_ACTION_DATA to ALR_ACTION_HISTORY and ALR_ALERTS for context:

  • SELECT aad.ROW_NUMBER, aad.exception_data_columns, ah.ALERT_NAME FROM ALR_ACTION_DATA aad, ALR_ACTION_HISTORY ah WHERE aad.ACTION_HISTORY_ID = ah.ACTION_HISTORY_ID AND aad.APPLICATION_ID = ah.APPLICATION_ID AND ah.ALERT_ID = :p_alert_id ORDER BY ah.RUN_DATE DESC;

This data is also critical for custom integrations that consume alert exceptions programmatically, where the raw exception data is extracted from ALR_ACTION_DATA for further processing.

Related Objects

ALR_ACTION_DATA maintains documented foreign key relationships with two key Alert tables, forming the core of the alert execution data model.

  • ALR_ACTION_SET_CHECKS: The relationship is defined on columns (APPLICATION_ID, CHECK_ID). This links each row of exception data back to the specific check definition that identified it.
  • ALR_ACTION_HISTORY: The relationship is defined on columns (APPLICATION_ID, ACTION_HISTORY_ID). This is the most critical link, tethering the detailed exception data to a specific execution instance of an alert's action set.

These relationships ensure data integrity and enable comprehensive joins to retrieve a complete picture of an alert's execution history and its resulting exceptions.