Search Results os_argument_string

Overview

APPS.ALR_ACTIONS_V is an Oracle E-Business Suite view that exposes alert action definitions maintained by the Alert Manager (ALR) module. In EBS 12.1.1 and 12.2.2, the Oracle Alert framework allows administrators to define an alert, its periodic frequency, and one or more actions to be performed when the alert's conditions evaluate true. Those actions can include sending an email, printing a message, running a concurrent program, invoking an operating system program, or executing a SQL statement. ALR_ACTIONS_V presents the rows of the base ALR_ACTIONS table together with decoded, human-readable values for the response set, distribution list, and the application that owns the concurrent, operating system, or SQL program referenced by the action.

The view is read-only and is used primarily for reporting, data extraction, and integration. Rather than storing its own data, it resolves foreign keys at query time so that consumers see application names and response set or list names in place of raw numeric identifiers. The presence of the OS_PROGRAM_APPLICATION column is directly relevant to users searching on that term: it identifies the application owning the operating system program associated with an action that executes at the operating system level.

Underlying Base Objects

ALR_ACTIONS_V is defined over four documented base objects, all accessed through APPS synonyms:

• ALR_ACTIONS — the primary table holding each alert action, including its type, level, message content, recipients, and program identifiers.
• ALR_DISTRIBUTION_LISTS — joined to resolve the distribution list name (LIST) for actions that distribute to a named list; the join is outer and restricted to enabled lists.
• ALR_RESPONSE_SETS — joined to resolve the response set name (RESPONSE_SET); the join is outer and restricted to enabled response sets.
• FND_APPLICATION_TL — joined to translate the application identifier (PROGRAM_APPLICATION_ID) into an application name. The join is outer and constrained to the session language via USERENV('LANG').

Because the application join uses PROGRAM_APPLICATION_ID, the resulting FA.APPLICATION_NAME is projected under several aliases—CNC_PROGRAM_APPLICATION_ID, OS_PROGRAM_APPLICATION, and SQL_PROGRAM_APPLICATION—each representing the same owning application name but surfaced for the concurrent, operating system, and SQL program contexts respectively.

Key Columns

• NAME, DESCRIPTION, ACTION_TYPE, ACTION_LEVEL_TYPE — identity and classification of the action and the level at which it operates (for example, summary versus detail).
• TO_RECIPIENTS, CC_RECIPIENTS, BCC_RECIPIENTS, PRINT_RECIPIENTS, PRINTER, REPLY_TO, SUBJECT — addressing and message header attributes for notification actions.
• RESPONSE_SET_ID, RESPONSE_SET, FOLLOW_UP_AFTER_DAYS — response handling configuration.
• MSG_FILE_NAME, MSG_BODY, COLUMN_WRAP_FLAG, MAXIMUM_SUMMARY_MESSAGE_WIDTH — message formatting attributes for the message action.
• CONCURRENT_PROGRAM_ID, CNC_PROGRAM_APPLICATION_ID, CNC_FILE_NAME, CNC_ARGUMENT_STRING — concurrent program action details.
• OS_PROGRAM_APPLICATION, OS_ARGUMENT_STRING, OS_FILE_NAME, OS_BODY — operating system program action details; OS_PROGRAM_APPLICATION names the owning application.
• SQL_PROGRAM_APPLICATION, SQL_ARGUMENT_STRING, SQL_FILE_NAME, SQL_BODY — SQL statement action details.
• ENABLED_FLAG, END_DATE_ACTIVE, DATE_LAST_EXECUTED, VERSION_NUMBER — lifecycle and audit attributes.
• APPLICATION_ID, ALERT_ID, ACTION_ID, ROWID ROW_ID — ownership and unique row identification.

Common Use Cases and Queries

Typical uses include auditing which alert actions invoke operating system programs, verifying recipients and response sets, and extracting alert action metadata for migration or documentation.

Listing operating system program actions with their owning application:

• SELECT name, os_program_application, os_file_name, os_argument_string, enabled_flag FROM apps.alr_actions_v WHERE action_type = 'OS' ORDER BY name;

Reviewing distribution and response configuration for notification actions:

• SELECT name, action_type, list, response_set, to_recipients, subject, enabled_flag FROM apps.alr_actions_v WHERE response_set IS NOT NULL OR list IS NOT NULL;

Identifying disabled or expired actions for cleanup:

• SELECT action_id, name, application_id, enabled_flag, end_date_active, date_last_executed FROM apps.alr_actions_v WHERE enabled_flag = 'N' OR end_date_active < SYSDATE;