Search Results alr_action_sets_uk1

Overview

The ALR_ACTION_SETS table is a core repository within the Oracle E-Business Suite Alert (ALR) module, serving as the master definition table for alert action sets. An action set is a logical grouping of one or more executable actions that are performed when an alert's periodic or event-driven condition is met. This table is fundamental to the alerting engine's workflow, defining what specific operations—such as sending a message, executing a concurrent program, or running a script—are to be triggered in response to a database event or scheduled check. Its integrity is critical for the correct execution and auditing of automated business notifications and processes across both EBS 12.1.1 and 12.2.2 versions.

Key Information Stored

The table's structure centers on uniquely identifying an action set within the context of a specific alert and application. The primary key (ALR_ACTION_SETS_PK) is a composite of APPLICATION_ID and ACTION_SET_ID, ensuring uniqueness across the entire EBS instance. A separate unique key (ALR_ACTION_SETS_UK1) enforces that within a single alert (APPLICATION_ID, ALERT_ID), each action set NAME must be distinct. While the provided metadata does not list all columns, the essential relational columns include APPLICATION_ID (linking to the product), ALERT_ID (linking to the parent alert in ALR_ALERTS), ACTION_SET_ID (the unique sequence identifier), and NAME (the user-defined identifier for the action set). Other typical columns would define execution order, enabled status, and summary descriptions.

Common Use Cases and Queries

Primary use cases involve troubleshooting alert execution, auditing configured actions, and performing data fixes. Administrators often query this table to understand the action sets tied to a malfunctioning alert or to verify configurations during migrations. A common diagnostic query joins to the ALR_ALERTS table to list all action sets for a specific alert:

• SELECT aas.name, aas.action_set_id FROM alr_action_sets aas, alr_alerts aa WHERE aas.application_id = aa.application_id AND aas.alert_id = aa.alert_id AND aa.name = '&ALERT_NAME';

Another frequent pattern is reviewing the hierarchical structure of an alert by joining to related detail tables like ALR_ACTION_SET_MEMBERS to see the individual actions within each set. Reporting on the volume and assignment of action sets across different application modules is also a standard administrative task.

Related Objects

The ALR_ACTION_SETS table sits at the center of a key relational schema, with several child tables storing detailed components of an action set, as documented by its foreign key relationships:

• Parent Table: ALR_ALERTS (via APPLICATION_ID, ALERT_ID)
• Child Tables (referencing ALR_ACTION_SETS.APPLICATION_ID and .ACTION_SET_ID):
  • ALR_ACTION_HISTORY: Logs execution history for the action set.
  • ALR_ACTION_SET_CHECKS: Stores suppression and recurrence check criteria.
  • ALR_ACTION_SET_INPUTS: Defines inputs required for the actions.
  • ALR_ACTION_SET_MEMBERS: Contains the specific actions (e.g., message, concurrent request) within the set.
  • ALR_ACTION_SET_OUTPUTS: Manages outputs from the executed actions.

These relationships form a complete data model for defining, executing, and tracking alert-based workflows.