Search Results alr_action_set_members




Overview
Explore in AI Chat

Overview

The ALR_ACTION_SET_MEMBERS table is a core data structure within the Oracle E-Business Suite Alert (ALR) module. It functions as the junction table that defines the composition of alert action sets. An action set is a reusable collection of actions or action groups that can be executed when an alert condition is met. This table establishes the many-to-many relationship between an action set (ALR_ACTION_SETS) and its constituent members, which can be either individual actions (ALR_ACTIONS) or predefined groups of actions (ALR_ACTION_GROUPS). Its role is critical for the runtime engine, as it provides the definitive list of operations to perform upon an alert trigger, enabling complex, multi-step automated responses.

Key Information Stored

The table's primary key is a composite of APPLICATION_ID and ACTION_SET_MEMBER_ID, ensuring uniqueness within the application context. Its most significant columns define the relationships it manages. The APPLICATION_ID, ACTION_SET_ID, and ALERT_ID columns link the member to its parent action set and the overarching alert. The table then specifies the member's type and identity through the ACTION_ID and ACTION_GROUP_ID columns; one will be populated while the other is null, indicating whether the member is a discrete action or a reference to an action group. The SEQUENCE column dictates the order of execution for members within the set. Administrative columns like CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and END_DATE_ACTIVE (for soft-deleting members) support standard EBS auditing and lifecycle management.

Common Use Cases and Queries

A primary use case is auditing and troubleshooting alert configurations. Developers and functional consultants query this table to understand the complete workflow defined for an alert. Common reporting needs include listing all members of a specific action set or identifying all action sets that utilize a particular action. Sample queries include retrieving the execution sequence for an action set or validating configurations during migrations.

  • To list all action members for a specific alert and action set, ordered by sequence:
    SELECT aasm.sequence, act.action_name, agr.action_group_name
    FROM alr_action_set_members aasm,
    alr_actions act,
    alr_action_groups agr
    WHERE aasm.alert_id = :p_alert_id
    AND aasm.action_set_id = :p_action_set_id
    AND aasm.application_id = act.application_id(+)
    AND aasm.action_id = act.action_id(+)
    AND aasm.application_id = agr.application_id(+)
    AND aasm.action_group_id = agr.action_group_id(+)
    ORDER BY aasm.sequence;
  • To find all action sets containing a specific action:
    SELECT DISTINCT aas.action_set_name
    FROM alr_action_set_members aasm,
    alr_action_sets aas
    WHERE aasm.action_id = :p_action_id
    AND aasm.application_id = aas.application_id
    AND aasm.action_set_id = aas.action_set_id;

Related Objects

As indicated by its foreign keys, ALR_ACTION_SET_MEMBERS is centrally connected to several key Alert tables. It is a child of ALR_ACTION_SETS, ALR_ALERTS, ALR_ACTIONS, and ALR_ACTION_GROUPS. This structure enforces referential integrity, ensuring a member cannot exist without a valid parent action set, alert, and corresponding action or action group. Crucially, it is a parent table to ALR_ACTION_HISTORY, which records the execution instance for each action set member when an alert runs. This relationship is vital for post-execution review and debugging, linking runtime results back to the static configuration defined in ALR_ACTION_SET_MEMBERS.