Search Results sql_argument_string

Overview

APPS.ALR_ACTIONS_V is a reporting and integration view within the Oracle E-Business Suite Alert Manager (ALR) module. It exposes the definition of alert actions configured in the system, joining the core action repository with lookup and descriptive data drawn from distribution lists, response sets, and application name translations. The view is defined in the APPS schema and is documented for both EBS 12.1.1 and 12.2.2. Because it consolidates human-readable names (list name, response set name, application name) alongside the raw foreign key identifiers, it is well suited for diagnostic queries, custom reporting, and integration logic where an action's full configuration must be reconstructed without performing manual joins.

Underlying Base Objects

The view is defined over the following documented objects: ALR_ACTIONS, ALR_DISTRIBUTION_LISTS, ALR_RESPONSE_SETS, and FND_APPLICATION_TL. ALR_ACTIONS supplies the driving rows and virtually all business columns. The remaining three objects are outer-joined, meaning that actions without a linked distribution list, response set, or registered application still appear. Two join conditions are noteworthy. First, FND_APPLICATION_TL is filtered by LANGUAGE = USERENV('LANG'), so application names appear in the session language. Second, the outer joins to ALR_RESPONSE_SETS and ALR_DISTRIBUTION_LISTS each include an ENABLED_FLAG = 'Y' predicate, meaning disabled lists or response sets are effectively invisible and their name columns resolve to null.

Key Columns

• NAME, DESCRIPTION, ACTION_TYPE, ACTION_LEVEL_TYPE — Identity and classification of the alert action.
• LIST, LIST_ID, LIST_APPLICATION_ID — Distribution list name and identifiers (from the outer-joined ALR_DISTRIBUTION_LISTS).
• TO_RECIPIENTS, CC_RECIPIENTS, BCC_RECIPIENTS, PRINT_RECIPIENTS, PRINTER, REPLY_TO, SUBJECT — Message delivery attributes for the e-mail/print action type.
• RESPONSE_SET_ID, RESPONSE_SET, FOLLOW_UP_AFTER_DAYS — Response-processing configuration.
• CONCURRENT_PROGRAM_ID, CNC_PROGRAM_APPLICATION_ID, CNC_FILE_NAME, CNC_ARGUMENT_STRING — Concurrent program action attributes (CNC prefix).
• OS_PROGRAM_APPLICATION, OS_FILE_NAME, OS_BODY, OS_ARGUMENT_STRING — Operating system/host action attributes (OS prefix).
• SQL_PROGRAM_APPLICATION, SQL_FILE_NAME, SQL_BODY, SQL_ARGUMENT_STRING — SQL action attributes (SQL prefix). The column SQL_ARGUMENT_STRING is the SQL-script argument text surfaced for SQL-type actions.
• MSG_FILE_NAME, MSG_BODY, COLUMN_WRAP_FLAG, MAXIMUM_SUMMARY_MESSAGE_WIDTH — Message formatting attributes.
• ENABLED_FLAG, END_DATE_ACTIVE, DATE_LAST_EXECUTED, VERSION_NUMBER — Lifecycle and audit columns.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, ROW_ID — Standard WHO columns and the pseudo-column ROWID exposed as ROW_ID.

Common Use Cases and Queries

A frequent requirement is searching for actions that reference a particular argument string, for example the SQL_ARGUMENT_STRING column. The following query lists enabled SQL actions whose argument string is not null:

• SELECT name, sql_program_application, sql_file_name, sql_argument_string FROM apps.alr_actions_v WHERE action_type = 'SQL' AND sql_argument_string IS NOT NULL AND enabled_flag = 'Y';
• SELECT name, list, response_set, to_recipients, subject FROM apps.alr_actions_v WHERE enabled_flag = 'Y' ORDER BY name;

The view is also useful for auditing delivery configuration (recipients, printer, reply-to) and for confirming which concurrent program or host script an action invokes. Because it already resolves application names and list/response-set names, it is preferred over querying ALR_ACTIONS directly in ad hoc reporting and integration extracts.