Search Results alr_alert_actions_view




Overview
Explore in AI Chat

Overview

ALR_ALERT_ACTIONS_VIEW is a denormalized reporting view owned by the APPS schema in Oracle E-Business Suite, belonging to the ALR (Alert) product family. It presents a flattened, hierarchically resolved picture of the alert action configuration: the actions that are attached to an action set, including actions reachable through action groups. In the Oracle Alert data model, actions are not attached directly to an alert in a single flat structure. Instead, an alert owns one or more action sets, each action set owns sequence-numbered members, and each member is either a single action or an action group, which in turn contains individual actions. This view collapses that multi-level structure into one row per resolved action per action set member, making it suitable for reporting, integration, and ad hoc inquiry without requiring callers to reproduce the outer-join logic themselves.

Because the view exposes the flag column as ALERT_ENABLED_FLAG (the enabled flag of the alert itself), it is frequently consulted when a user searches for the "alert_enabled_flag" attribute. The action-level and action-set-level enabled flags are also surfaced under distinct aliases, so the view is a convenient single source for determining whether an alert, its action sets, and its individual actions are currently active.

Underlying Base Objects

The view is defined over six documented base objects, all referenced through APPS synonyms:

The join path establishes the parent-child relationships from alert to action set to set member, then optionally outward to action groups and their members. Outer joins are used throughout the action and group branches so that set members referencing an action directly are preserved even when no matching group membership exists, and vice versa. The DECODE on GA.ACTION_ID derives ACTION_SET_MEMBER_TYPE as 'G' when the member resolves through a group and 'A' when it is a direct action.

Key Columns

Common Use Cases and Queries

Typical uses include auditing which actions an alert will actually execute, verifying enabled state across the alert/action-set/action hierarchy, and feeding alert configuration into integrations or custom reports. A representative query lists active actions for a specific alert:

  • SELECT alert_name, action_set_name, action_name, action_type, action_enabled_flag FROM alr_alert_actions_view WHERE application_id = :app_id AND alert_id = :alert_id AND alert_enabled_flag = 'Y' ORDER BY action_set_sequence, action_set_member_sequence;
  • SELECT alert_name, COUNT(*) FROM alr_alert_actions_view WHERE action_enabled_flag = 'Y' GROUP BY alert_name;
  • SELECT alert_name, action_name, action_group_name FROM alr_alert_actions_view WHERE action_set_member_type = 'G' ORDER BY alert_name, action_set_member_sequence;

Note that because outer joins can yield rows where the resolved action columns are null (for example, a set member pointing to an empty group), filters on ACTION_ID or ACTION_ENABLED_FLAG should be applied with that possibility in mind.