Search Results output_value

Overview

ALR_ALERT_HISTORY_VIEW is an APPS-owned, VALID database view within the Oracle E-Business Suite Alert (ALR) product module. It exposes the complete combined history of alert check executions and alert action executions, providing a single reporting surface for both the periodic evaluation of alert conditions and the actions that those evaluations subsequently triggered. Because it consolidates check-level and action-level history into one denormalized structure, the view is the primary reference object for administrators and developers who need to audit how alerts behaved over time across Oracle EBS 12.1.1 and 12.2.2.

The view is read-only by design. It supports reporting, reconciliation, and diagnostic integration rather than transactional processing, and it is typically consumed through Oracle Reports, BI Publisher, SQL*Plus, or custom concurrent programs.

Underlying Base Objects

The documented view metadata identifies two referenced base objects, both themselves views:

• ALR_CHECK_ACTION_HISTORY_VIEW — supplies execution history rows, including check dates, success flags, purge dates, exception counts, action counts, and output values.
• ALR_ALERT_ACTIONS_VIEW — supplies alert and action definition attributes, including names, sequences, types, and levels.

ALR_ALERT_HISTORY_VIEW joins these on six key columns: APPLICATION_ID, ALERT_ID, ACTION_SET_ID, ACTION_SET_MEMBER_ID, ACTION_ID, and ACTION_VERSION_NUMBER. This six-part join correlates each historical execution record with the precise alert action definition (and version) that produced it, preserving version-specific history when action definitions are revised.

Key Columns

• APPLICATION_ID — identifies the Oracle application owning the alert.
• ALERT_NAME, ACTION_SET_NAME, ACTION_GROUP_NAME, ACTION_NAME — descriptive identifiers for the alert and its constituent action components.
• ALERT_CHECK_DATE — timestamp of the alert check execution.
• ALERT_CHECK_SUCCESS_FLAG — indicates whether the alert check completed successfully. This is the column most commonly searched for as alert_check_success_flag.
• ACTION_SET_CHECK_SUCCESS_FLAG — success indicator at the action set level, distinct from the top-level check flag.
• HISTORY_PURGE_DATE — date on which the record becomes eligible for purge.
• NUMBER_OF_EXCEPTIONS, NUMBER_OF_ACTIONS_PERFORMED — quantitative outcome metrics for the check run.
• ACTION_EXECUTED_FLAG, ACTION_LEVEL, ACTION_TYPE — describe whether and how each action fired.
• ORACLE_ID, EXCEPTION_SEQUENCE — correlation identifiers linking history to underlying alert processing internal records.
• OUTPUT_NAME, OUTPUT_DATA_TYPE, OUTPUT_VALUE — captured output from the alert/action execution.

Common Use Cases and Queries

Typical scenarios include auditing failed alert checks, measuring action throughput, and investigating why an alert fired but no action was taken. The following query lists recent unsuccessful checks:

• SELECT alert_name, alert_check_date, number_of_exceptions, number_of_actions_performed FROM apps.alr_alert_history_view WHERE alert_check_success_flag = 'N' AND alert_check_date > SYSDATE - 7 ORDER BY alert_check_date DESC;

To summarize action execution by alert:

• SELECT alert_name, action_name, COUNT(*) executions FROM apps.alr_alert_history_view WHERE action_executed_flag = 'Y' GROUP BY alert_name, action_name;

To review captured output for a specific alert:

• SELECT alert_check_date, output_name, output_data_type, output_value FROM apps.alr_alert_history_view WHERE alert_name = :alert_name ORDER BY alert_check_date DESC;

Queries should filter on ALERT_CHECK_DATE to avoid scanning purge-eligible history, and access should be granted carefully since the view spans all applications in the EBS instance.