Search Results threshold_or_escalation_group




Overview
Explore in AI Chat

Overview

APPS.ALR_ALERT_HISTORY_VIEW is a reporting view in the Oracle E-Business Suite Alert Manager (ALR) schema that consolidates alert definition metadata with the execution history of alert actions. It joins the alert action definition view to the check-action history view on a composite key covering application, alert, action set, action set member, action, and action version. The view is read-only and is intended for inquiry and reporting rather than transactional processing.

Its role is to expose, in a single denormalized result set, both what an alert action is configured to do and what actually happened when the alert was evaluated. Parameters such as action set sequence, action set member sequence, and alert check date are surfaced together with execution outcomes including exceptions raised, actions performed, and output values. This makes the view a convenient source for operational monitoring reports, alert performance analysis, and integration extracts. Because the user search term was "action_set_member_sequence," it is worth noting that this column is projected directly from the alert actions view and identifies the position of a member within its action set, which is essential for ordering actions as the alert engine executes them.

Underlying Base Objects

Per the documented ETRM metadata, the view is defined over exactly two base objects, both of which are themselves views in the APPS schema:

  • ALR_CHECK_ACTION_HISTORY_VIEW (aliased H) — supplies the historical and execution-oriented columns, such as alert check date, purge date, check success flag, oracle id, number of exceptions, number of actions performed, action level, action executed flag, exception sequence, and output attributes.
  • ALR_ALERT_ACTIONS_VIEW (aliased A) — supplies the alert and action definition columns, including alert name, action set name and sequence, action set member sequence and type, action group name, threshold or escalation group, action name, action version number, action level type, and action type.

The two views are correlated in the WHERE clause on six equality predicates: application_id, alert_id, action_set_id, action_set_member_id, action_id, and action_version_number. Consequently, history rows are only returned where a matching current action definition exists; alerts whose definitions have been removed may not appear.

Key Columns

Common Use Cases and Queries

Typical uses include auditing which alert actions executed, reviewing exceptions raised over a period, and validating the configured execution order of action set members.

  • Investigate a specific alert's action history, ordered by execution sequence:
SELECT alert_name, alert_check_date, action_set_name,
       action_set_member_sequence, action_name, action_executed_flag,
       number_of_exceptions, output_value
FROM   apps.alr_alert_history_view
WHERE  alert_name = :p_alert_name
ORDER  BY alert_check_date DESC, action_set_member_sequence;
  • Summarize failures by action to identify problematic definitions:
SELECT action_name, action_type,
       COUNT(*) AS executions,
       SUM(number_of_exceptions) AS total_exceptions
FROM   apps.alr_alert_history_view
WHERE  alert_check_success_flag = 'N'
GROUP  BY action_name, action_type;
  • Verify the sequence of members configured for an action set:
SELECT DISTINCT action_set_name, action_set_member_sequence,
       action_set_member_type, action_name
FROM   apps.alr_alert_history_view
WHERE  alert_name = :p_alert_name
ORDER  BY action_set_name, action_set_member_sequence;

Because all base objects are views, queries against ALR_ALERT_HISTORY_VIEW may involve significant join and aggregation cost on large history volumes; restricting by application, alert, or check date is advisable.