Results for “alr_response_sets”

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

Overview

The ALR_RESPONSE_SETS table is a core configuration object within the Oracle Alert (ALR) product of Oracle E-Business Suite, holding the definition of response sets that determine the actions, messages, and variables Oracle Alert applies when a given alert fires. In EBS 12.1.1 and 12.2.2 the table resides in the ALR schema, is fully valid, and exposes 14 physical columns. Each row binds a logical grouping of responses to a single alert, allowing administrators to categorize and enable different response behaviors without editing the alert definition itself. Based on foreign-key structure, the table functions as a hub in a hub-and-spoke Data Vault model: it holds the durable identity of a response set and is referenced by multiple dependent satellites (actual responses, actions, messages, variables, and valid responses). This classification is a modeling suggestion derived from the FK topology rather than an Oracle-declared attribute.

Key Information Stored

The surrogate primary key is ALR_RESPONSE_SETS_PK, composed of APPLICATION_ID, ALERT_ID, and RESPONSE_SET_ID. The most significant columns for identification and control are:

• APPLICATION_ID — identifies the owning application context and is part of every key and foreign key.
• ALERT_ID — references the parent alert in ALR_ALERTS; a response set cannot exist without its alert.
• RESPONSE_SET_ID — surrogate identifier for the individual response set.
• NAME — user-visible business name; together with APPLICATION_ID and ALERT_ID it forms the unique business key ALR_RESPONSE_SETS_UK1.
• DESCRIPTION — free-text explanation of the response set's purpose.
• ENABLED_FLAG — indicates whether the response set is active.
• END_DATE_ACTIVE — effective end date for the response set's validity.
• SECURITY_GROUP_ID — references FND_SECURITY_GROUPS for data-level security.
• ZD_EDITION_NAME — editioning column; unique indexes U1 (APPLICATION_ID, RESPONSE_SET_ID, ZD_EDITION_NAME) and U2 (APPLICATION_ID, ALERT_ID, NAME, ZD_EDITION_NAME) include it to support online patching in 12.2.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN track the DML history of each row.

Common Use Cases and Queries

Typical usage centers on reporting which alerts expose which response sets, and tracing the dependent actions and messages. A basic listing joins ALR_ALERTS to retrieve the alert name alongside its response sets:

SELECT a.alert_name, r.name, r.enabled_flag
FROM   alr.alr_response_sets r,
       alr.alr_alerts a
WHERE  r.application_id = a.application_id
AND    r.alert_id = a.alert_id
AND    r.enabled_flag = 'Y';

Administrators auditing response configuration query ALR_RESPONSE_ACTIONS, ALR_RESPONSE_MESSAGES, and ALR_RESPONSE_VARIABLES using the same three-part key to verify what each response set actually does. Valid-response validation and history reporting rely on ALR_VALID_RESPONSES and ALR_ACTUAL_RESPONSES respectively. Security-focused queries join FND_SECURITY_GROUPS on SECURITY_GROUP_ID to confirm the response set is visible to the intended operating unit.

Related Objects

• ALR_ALERTS — parent alert; joined on APPLICATION_ID and ALERT_ID.
• ALR_RESPONSE_ACTIONS — response behavior definitions; joined on APPLICATION_ID, ALERT_ID, and RESPONSE_SET_ID.
• ALR_RESPONSE_MESSAGES — message templates delivered by the response set.
• ALR_RESPONSE_VARIABLES and ALR_RESPONSE_VARIABLE_VALUES — variable definitions and their value assignments for the response set.
• ALR_VALID_RESPONSES — enumerated valid responses associated with the alert and response set.
• ALR_ACTUAL_RESPONSES — runtime responses recorded against a response set.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID for data security partitioning.