Results for “alr_actions”

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

Overview

The ALR_ACTIONS table resides in the ALR schema and belongs to the Oracle Alert (ALR) product family within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the definitions of the actions that an Oracle Alert executes when its triggering condition is satisfied — for example, sending an email, running a concurrent program, submitting an operating system script, or invoking a response action that a recipient can act upon. Each row represents a discrete, versioned action definition associated with a parent alert.

From a dimensional-modeling perspective, the mined foreign-key structure classifies this table as hub-leaning in a Data Vault heuristic. This suggests modeling APPLICATION_ID plus ACTION_ID as a business hub key, with descriptive and configuration attributes (message body, recipients, printer settings, review thresholds) treated as satellite data. This classification is a modeling suggestion derived from the FK topology, not a prescribed Oracle design.

Key Information Stored

The table contains 36 documented columns. The most significant are:

• APPLICATION_ID and ACTION_ID — the composite business identifier for an action. Together with END_DATE_ACTIVE they form the primary key ALR_ACTIONS_PK and the unique index ALR_ACTIONS_U1 (adding ZD_EDITION_NAME in 12.2.2 for editioning).
• ALERT_ID — the parent alert this action belongs to; combined with APPLICATION_ID, NAME, and END_DATE_ACTIVE it forms unique key ALR_ACTIONS_UK1.
• NAME — the user-visible action name, unique within the parent alert.
• ACTION_TYPE and ACTION_LEVEL_TYPE — determine the action mechanism (message, concurrent program, script, response) and its scope (detail versus summary).
• ENABLED_FLAG — indicates whether the action is active.
• FILE_NAME, ARGUMENT_STRING — used for script and program-based actions.
• PROGRAM_APPLICATION_ID, CONCURRENT_PROGRAM_ID — identify the concurrent program invoked by the action, referencing FND_CONCURRENT_PROGRAMS.
• LIST_APPLICATION_ID, LIST_ID — reference an ALR_DISTRIBUTION_LISTS distribution list for recipient resolution.
• TO_RECIPIENTS, CC_RECIPIENTS, BCC_RECIPIENTS, PRINT_RECIPIENTS, PRINTER, SUBJECT, REPLY_TO — control email and print delivery of the action output.
• BODY, COLUMN_WRAP_FLAG, MAXIMUM_SUMMARY_MESSAGE_WIDTH — define message formatting content.
• RESPONSE_SET_ID, FOLLOW_UP_AFTER_DAYS — support response-driven actions where recipients reply within a configured window.
• VERSION_NUMBER — versions the action; combined with APPLICATION_ID, ACTION_ID, and END_DATE_ACTIVE it forms ALR_ACTIONS_UK2.
• SECURITY_GROUP_ID — links the row to FND_SECURITY_GROUPS for multi-organization security.
• ZD_EDITION_NAME — the editioning column introduced in the 12.2 online-patching architecture.

Common Use Cases and Queries

ALR_ACTIONS is queried primarily when auditing, cloning, or troubleshooting Oracle Alert configurations. Typical reporting scenarios include identifying all enabled email actions for a given alert, listing actions that invoke concurrent programs, and tracing which distribution lists feed which actions. A representative query follows:

SELECT a.action_id, a.name, a.action_type,
       a.enabled_flag, a.subject
FROM   alr.alr_actions a
WHERE  a.application_id = :app_id
AND    a.alert_id       = :alert_id
AND    (a.end_date_active IS NULL
        OR a.end_date_active > SYSDATE);

To find actions that invoke concurrent programs:

SELECT ac.name, ac.concurrent_program_id
FROM   alr.alr_actions ac
WHERE  ac.program_application_id IS NOT NULL;

Because the table is editioned in 12.2.2, queries should generally filter on the edition view rather than the base table. Data-Vault-style staging often lands this hub on (APPLICATION_ID, ACTION_ID) as the natural key, with message and recipient attributes staged into a satellite.

Related Objects

The following objects are the most significant references to ALR_ACTIONS:

• ALR_ALERTS — parent alert; joined via APPLICATION_ID and ALERT_ID.
• ALR_DISTRIBUTION_LISTS — recipient source; joined via LIST_APPLICATION_ID and LIST_ID.
• FND_CONCURRENT_PROGRAMS — program invoked by the action; joined via PROGRAM_APPLICATION_ID and CONCURRENT_PROGRAM_ID.
• FND_SECURITY_GROUPS — security grouping; joined via SECURITY_GROUP_ID.
• ALR_ACTION_GROUP_MEMBERS — group membership; joins on APPLICATION_ID and ACTION_ID.
• ALR_ACTION_SET_MEMBERS — action-set membership; joins on APPLICATION_ID and ACTION_ID.
• ALR_ACTION_OUTPUTS — formatted output definitions linked to the action.
• ALR_RESPONSE_ACTIONS — response actions tied to the parent definition.

Together these relationships establish ALR_ACTIONS as the central definitional hub of the Oracle Alert action subsystem.