Search Results action_enabled_flag

Overview

The APPS.ALR_ALERT_ACTIONS_VIEW is an Oracle E-Business Suite internal database view owned by the APPS schema. It consolidates alert definition metadata with the action sets, action groups, and individual actions that are associated with each alert. In the context of Oracle EBS 12.1.1 and 12.2.2, this view serves as a denormalized read interface over the alerting subsystem managed by the Alert Manager (ALR) module, presenting a horizontally flattened picture of the alert-to-action hierarchy in a single result set.

Because the object carries the designation "Oracle Internal Use Only," it is not a supported integration surface. Oracle Corporation does not support direct access to its data except from standard Oracle Applications programs. It is nonetheless commonly encountered by technical consultants who query it for diagnostics, reporting extracts, and impact analysis of alert configurations.

Underlying Base Objects

The view is defined over six documented base objects, each referenced through a synonym:

• ALR_ALERTS — the parent alert definitions, supplying application, alert identity, and alert-level enablement.
• ALR_ACTION_SETS — action sets assigned to an alert, with their sequence and enabled status.
• ALR_ACTION_SET_MEMBERS — the membership rows tying an action set to an action or action group.
• ALR_ACTION_GROUPS — named groups of actions used as escalation or threshold containers.
• ALR_ACTION_GROUP_MEMBERS — membership rows linking actions into action groups.
• ALR_ACTIONS — the leaf-level actions executed when an alert fires.

The view joins these tables along the alert, action set, and action group foreign keys to produce one row per action set member, enriched with alert and action attributes. It is the semantic layer Oracle's own alert-processing programs rely on to resolve, order, and validate the actions that a given alert will execute.

Key Columns

The most frequently requested column, ACTION_ENABLED_FLAG, indicates whether a specific action is currently enabled. It is paired with ACTION_END_DATE_ACTIVE, which records the last date the action remains active, allowing date-bounded enablement to be evaluated at runtime. The equivalent alert-level controls are exposed as ALERT_ENABLED_FLAG and ALERT_END_DATE_ACTIVE, and the intermediate layer provides ACTION_SET_ENABLED_FLAG.

Ordering is governed by ACTION_SET_SEQUENCE (execution order of enabled action sets for an alert) and ACTION_SET_MEMBER_SEQUENCE (execution order of an action or action group during an action set check). Structural columns include APPLICATION_ID, ALERT_ID, ALERT_NAME, ACTION_SET_ID, ACTION_SET_NAME, ACTION_GROUP_ID, ACTION_GROUP_NAME, ACTION_GROUP_TYPE, ACTION_SET_MEMBER_TYPE, THRESHOLD_OR_ESCALATION_GROUP, ACTION_ID, ACTION_VERSION_NUMBER, ACTION_NAME, ACTION_TYPE, ACTION_LEVEL, and ACTION_LEVEL_TYPE.

Common Use Cases and Queries

Typical scenarios include auditing which alerts have disabled actions, tracing the full escalation path for a threshold group, and documenting alert configurations before an upgrade or clone.

• Locate alerts that contain at least one disabled action: filter on ACTION_ENABLED_FLAG = 'N' and group by ALERT_NAME.
• Report all enabled actions for a given alert, ordered by execution sequence, to verify timing behaviour.
• Reconcile action sets and action groups against their expected membership during configuration reviews.

A representative query:

SELECT alert_name, action_set_name, action_group_name, action_name,
  action_set_member_sequence, action_enabled_flag, action_end_date_active
FROM apps.alr_alert_actions_view
WHERE alert_enabled_flag = 'Y'
  AND action_enabled_flag = 'Y'
ORDER BY alert_name, action_set_sequence, action_set_member_sequence;

Because the view is internal and unsupported, any production dependency should be reviewed carefully and, where possible, replaced with supported Oracle APIs.