Search Results date_last_executed

Overview

ALR_ACTIONS_V is a seeded, read-only database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the ALR (Alert) product. Its documented description is simply "Alert Actions View." In the Oracle Alert architecture, an alert consists of an event or periodic check that evaluates a SELECT statement and, when conditions are met, fires one or more actions. Each action defines what the system does in response — send an email or printed message, run a concurrent program, execute a host or SQL script, or trigger a response set — and how recipients, content, scheduling, and follow-up behavior are configured. ALR_ACTIONS_V presents that action definition metadata in a denormalized, report-friendly form.

The view is significant for reporting and integration because it resolves several foreign-key relationships that would otherwise require manual joins. Distribution list names, response set names, and application names for concurrent, operating system, and SQL actions are exposed as readable values rather than raw IDs. This makes the view suitable for alert administration audits, migration assessments, and custom reporting on notification configuration without relying on the underlying transactional tables directly. Because it is a view, it should be queried, not updated; DML must be directed to the base tables through the supported Alert forms.

Underlying Base Objects

The documented referenced base objects are ALR_ACTIONS, ALR_DISTRIBUTION_LISTS, ALR_RESPONSE_SETS, and FND_APPLICATION_TL, all accessed through APPS synonyms. ALR_ACTIONS is the driving table and supplies the action definition, including recipient, message, program, and audit columns. ALR_DISTRIBUTION_LISTS is outer-joined on LIST_ID to resolve the list name into the LIST column, with an additional predicate restricting rows to enabled lists (ENABLED_FLAG = 'Y'). ALR_RESPONSE_SETS is outer-joined on RESPONSE_SET_ID to supply the RESPONSE_SET name, likewise filtered to enabled response sets. FND_APPLICATION_TL is outer-joined on PROGRAM_APPLICATION_ID and filtered by USERENV('LANG') to return the application name in the session language. All joins are outer (+) joins, so an action is never dropped from the result set simply because its list, response set, or application lookup is missing or disabled.

Key Columns

• TO_RECIPIENTS, CC_RECIPIENTS, BCC_RECIPIENTS, PRINT_RECIPIENTS — the address fields controlling who receives the action output by mail or print; the column to_recipients is the primary "To" distribution target.
• ACTION_TYPE, ACTION_LEVEL_TYPE — the kind of action performed (for example, message, concurrent program, OS script, or SQL script) and the level at which it applies (summary versus detail).
• LIST, LIST_ID, LIST_APPLICATION_ID — the distribution list name, its internal ID, and owning application, resolved from ALR_DISTRIBUTION_LISTS.
• SUBJECT, MSG_BODY, MSG_FILE_NAME, REPLY_TO, PRINTER — message content and delivery attributes for notification-style actions.
• RESPONSE_SET_ID, RESPONSE_SET, FOLLOW_UP_AFTER_DAYS — the response set triggered by the action and the follow-up interval.
• CNC_PROGRAM_APPLICATION, CNC_FILE_NAME, CNC_ARGUMENT_STRING; OS_PROGRAM_APPLICATION, OS_FILE_NAME, OS_BODY, OS_ARGUMENT_STRING; SQL_PROGRAM_APPLICATION, SQL_FILE_NAME, SQL_BODY, SQL_ARGUMENT_STRING — action-specific execution parameters for concurrent, OS, and SQL actions.
• ENABLED_FLAG, END_DATE_ACTIVE, DATE_LAST_EXECUTED, VERSION_NUMBER — lifecycle and audit attributes.
• ALERT_ID, ACTION_ID, APPLICATION_ID, ROW_ID — identifiers linking the action to its parent alert and enabling row-level addressing.

Common Use Cases and Queries

Typical uses include auditing recipient configuration, identifying alerts that send mail to specific addresses, and checking which actions remain enabled.

To find actions by recipient:

• SELECT action_id, name, to_recipients, cc_recipients, enabled_flag FROM apps.alr_actions_v WHERE to_recipients LIKE '%@example.com%';
• SELECT name, action_type, list, response_set, subject FROM apps.alr_actions_v WHERE action_type = 'MESSAGE';
• SELECT alert_id, action_id, name, cnc_program_application, date_last_executed FROM apps.alr_actions_v WHERE enabled_flag = 'Y' AND end_date_active IS NULL;

Because the view filters to enabled distribution lists and response sets, administrators should query the base tables directly when disabled lookups must also be inspected.