Results for “action_group_type”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The ALR_ACTION_GROUPS table resides in the ALR schema and belongs to the Oracle Alert (ALR) product module. It stores the definitions of alert action, threshold, and escalation groups, providing the organizing construct through which Oracle Alert associates a defined response set with a specific alert. Each row represents a named group that governs how an alert responds when its conditions are satisfied, whether by executing a set of actions, applying a threshold, or triggering an escalation path.

In Oracle EBS 12.1.1 and 12.2.2, the table sits at the center of the Alert response framework. The ALR_ACTION_GROUP_MEMBERS and ALR_ACTION_SET_MEMBERS tables both reference it, meaning individual action or action-set entries are resolved through the parent group record. Based on the foreign key topology, the metadata suggests a hub-leaning Data Vault classification: the table anchors identity and descriptive attributes for action groups while dependent member and set tables act as link or satellite structures. This classification is a heuristic modeling suggestion rather than a prescribed design.

Key Information Stored

The physical schema documents 16 columns. The most significant are:

• APPLICATION_ID — Identifies the owning application; part of both the primary key and the foreign key to ALR_ALERTS.
• ACTION_GROUP_ID — The surrogate group identifier; the second component of the composite primary key ALR_ACTION_GROUPS_PK.
• ALERT_ID — The parent alert to which the group belongs; participates in unique index ALR_ACTION_GROUPS_U2.
• NAME — The user-defined group name; also part of ALR_ACTION_GROUPS_U2, making (APPLICATION_ID, ALERT_ID, NAME, GROUP_TYPE) a business-key candidate.
• GROUP_TYPE and ACTION_GROUP_TYPE — Classify the group as an action, threshold, or escalation grouping.
• ENABLED_FLAG — Indicates whether the group is active for processing.
• END_DATE_ACTIVE — Effective end date controlling group lifespan.
• DESCRIPTION — Free-text purpose description.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS for access control.
• ZD_EDITION_NAME — Editioning column supporting EBR in 12.2.2; present in both unique indexes U1 and U2.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns.

Common Use Cases and Queries

Typical reporting queries retrieve the action groups attached to a specific alert:

SELECT ag.action_group_id, ag.name, ag.group_type, ag.enabled_flag
FROM   alr.alr_action_groups ag
WHERE  ag.application_id = :app_id
AND    ag.alert_id = :alert_id;

Administrators frequently enumerate enabled groups for a period:

SELECT name, description
FROM   alr.alr_action_groups
WHERE  enabled_flag = 'Y'
AND    (end_date_active IS NULL OR end_date_active > SYSDATE);

Reconciliation queries join to members to audit which actions belong to each group, and validation queries check the business key (APPLICATION_ID, ALERT_ID, NAME, GROUP_TYPE) before inserting new definitions.

Related Objects

• ALR_ALERTS — Parent table joined on APPLICATION_ID and ALERT_ID.
• ALR_ACTION_GROUP_MEMBERS — Child table joined on APPLICATION_ID and ACTION_GROUP_ID.
• ALR_ACTION_SET_MEMBERS — Child table joined on APPLICATION_ID and ACTION_GROUP_ID.
• FND_SECURITY_GROUPS — Referenced through SECURITY_GROUP_ID.