Results for “alr_response_actions”

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

Overview

ALR_RESPONSE_ACTIONS is a core configuration table in the Oracle Alert (ALR) module of Oracle E-Business Suite, documented as valid in both release 12.1.1 and 12.2.2. The table stores the member actions that belong to a response set, defining which actions execute when an alert fires and in what order. It acts as the intersection between response sets, alerts, and the individual actions assigned to them, forming the actionable output layer of the Alert Manager architecture. Users searching for "alr_response_actions" are typically investigating how alert responses are assembled, sequenced, and executed.

Based on the foreign key topology provided in the ETRM metadata, the heuristic Data Vault classification for this object is a link table. It resolves the many-to-many relationships among alerts, response sets, and actions, and is modeled as a transactional association rather than a descriptive hub or satellite. This classification is a modeling suggestion derived from FK structure, not a declarative statement in the product documentation.

Key Information Stored

• APPLICATION_ID, ALERT_ID, RESPONSE_SET_ID, RESPONSE_ID, SEQUENCE — the composite primary key (ALR_RESPONSE_ACTIONS_PK) that uniquely identifies each member action within a response set and establishes execution order.
• ACTION_ID — the foreign key identifying the specific Oracle Alert action executed as part of the response set; references ALR_ACTIONS.
• ENABLED_FLAG — indicates whether the member action is currently active.
• END_DATE_ACTIVE — the date on which the member action ceases to be effective; also part of the FK to ALR_ACTIONS.
• SECURITY_GROUP_ID — supports multi-org / security group data segregation; references FND_SECURITY_GROUPS.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN capture the standard who-column audit trail.
• ZD_EDITION_NAME — supports Edition-Based Redefinition (EBR) in 12.2.x online patching.

The surrogate-like business-key candidate is the unique index ALR_RESPONSE_ACTIONS_U1 on (APPLICATION_ID, RESPONSE_ID, SEQUENCE, ZD_EDITION_NAME), which distinguishes records independently of the primary key path.

Common Use Cases and Queries

Typical scenarios include auditing which actions a response set will trigger, verifying sequence ordering, and reporting on disabled or expired member actions.

• List member actions for a given response set, in execution order: SELECT action_id, sequence, enabled_flag FROM alr_response_actions WHERE application_id = :app AND response_set_id = :rs ORDER BY sequence;
• Identify all response sets that reference a specific action: SELECT response_set_id FROM alr_response_actions WHERE action_id = :action;
• Detect inactive or expired member actions: SELECT * FROM alr_response_actions WHERE enabled_flag = 'N' OR end_date_active < SYSDATE;
• Verify security group partitioning across responsibility access: join SECURITY_GROUP_ID to FND_SECURITY_GROUPS.

Related Objects

• ALR_ALERTS — joined on APPLICATION_ID and ALERT_ID; defines the alert owning the response.
• ALR_ACTIONS — joined on APPLICATION_ID, ACTION_ID, and END_DATE_ACTIVE; supplies the action definition.
• ALR_RESPONSE_SETS — joined on APPLICATION_ID, ALERT_ID, RESPONSE_SET_ID; the parent response set.
• FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID for multi-org security.

As a link table in the alert response model, ALR_RESPONSE_ACTIONS is essential to understanding how Oracle Alert assembles and executes response actions.