Search Results alr_output_history




Overview
Explore in AI Chat

Overview

The ALR_OUTPUT_HISTORY table is a core data object within the Oracle E-Business Suite Alert module (ALR). It serves as the historical repository for the output generated by exception alerts. When an alert's action set executes and produces a result, such as a list of exception records, that output is logged in this table. Its primary role is to provide an audit trail and historical record of what data was identified and potentially acted upon by the alert engine at a specific point in time, enabling users to review past alert runs and their findings.

Key Information Stored

The table's structure is designed to uniquely identify and store the detailed output from an alert check. As defined by its primary key (ALR_OUTPUT_HISTORY_PK), the critical columns are APPLICATION_ID, CHECK_ID, ROW_NUMBER, and NAME. APPLICATION_ID links the data to a specific EBS application. CHECK_ID is a foreign key to the ALR_ACTION_SET_CHECKS table, identifying the specific alert check that generated the output. ROW_NUMBER sequences the individual rows of output data from a single check execution. The NAME column typically stores the name of the output variable or column from the alert's SELECT statement, while a corresponding VALUE column (implied by standard practice, though not explicitly listed in the provided metadata) would hold the actual data value for that row and column.

Common Use Cases and Queries

The primary use case is auditing and troubleshooting past alert activity. Administrators can query this table to verify what data an alert detected during its last run, which is critical for diagnosing why an alert did or did not trigger expected actions. A common query pattern involves joining to the ALR_ACTION_SET_CHECKS table to filter by a specific alert. For example, to retrieve the latest historical output for a known CHECK_ID:

  • SELECT NAME, VALUE, ROW_NUMBER FROM ALR_OUTPUT_HISTORY WHERE APPLICATION_ID = :app_id AND CHECK_ID = :check_id ORDER BY ROW_NUMBER;

Reporting use cases include generating summaries of alert activity over time or extracting historical snapshots of exception data for analytical purposes.

Related Objects

ALR_OUTPUT_HISTORY has a direct and documented foreign key relationship to the ALR_ACTION_SET_CHECKS table. This relationship is defined on the composite key of APPLICATION_ID and CHECK_ID. Therefore, ALR_ACTION_SET_CHECKS is the primary parent table, containing the definition of the alert check that produced the historical output. To query meaningfully, one typically joins these tables:

  • ALR_ACTION_SET_CHECKS (Foreign Key): Joined via (ALR_OUTPUT_HISTORY.APPLICATION_ID = ALR_ACTION_SET_CHECKS.APPLICATION_ID) AND (ALR_OUTPUT_HISTORY.CHECK_ID = ALR_ACTION_SET_CHECKS.CHECK_ID).

This join allows queries to filter or report on historical output using descriptive information about the alert check from its parent table.