Search Results insert_alr_action_set_outputs

Overview

QA_ALERT_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified under the ETRM "OTHER" API category. Its business function is to provide a programmatic interface for creating and maintaining Oracle Alert definitions — specifically Alert Actions and Alert Action Sets — within the Oracle Alert (ALR) module. Oracle Alert actions are the executable responses that fire when an alert's SQL query returns matching rows; they can send email notifications, submit concurrent programs, run host scripts, execute SQL scripts, or invoke other Oracle EBS operations. Maintaining these definitions manually through the Oracle Alert forms can be slow and error-prone when large numbers of actions must be created, copied between instances, or generated programmatically. QA_ALERT_PKG exposes a set of PL/SQL procedures that encapsulate the underlying table inserts, unique key generation through the ALR_ACTIONS_S and ALR_ACTION_SETS_S sequences, and validation of reference data such as alert inputs and outputs. The package is declared with AUTHID CURRENT_USER, meaning its compiled code executes with the privileges of the invoking user rather than the definer. The source header indicates it is an original Oracle Alert schema package (qaalrs.pls) that has been shipped since the early EBS releases.

Key Procedures and Functions

• INSERT_ALR_ACTIONS — Creates a new Alert Action record and returns the generated action identifier through its output parameter. The caller supplies the alert identifier, application, action name, action type, and the many attribute fields required by the action (recipients, subject, body, printer, concurrent program details, response set, follow-up days, version and audit columns). Status is returned as success or error.
• UPDATE_ALR_ACTIONS — Updates an existing Alert Action. The procedure supports two update modes: when a ROWID is supplied it is used directly as the update key (as required by Oracle Forms), and when null, the application identifier, alert identifier, and action name are used to locate the record.
• INSERT_ALR_ACTION_SETS — Creates an Alert Action Set header record, which groups a collection of actions that can be executed together.
• INSERT_ALR_ACTION_SET_MEMBERS — Inserts membership rows that associate Alert Actions with a given Action Set.
• INSERT_ALR_ACTION_SET_OUTPUTS — Creates output definitions for an Action Set, linking the set to alert outputs defined on the underlying alert.
• INSERT_ALR_ACTION_SET_INPUTS — Creates input definitions for an Action Set, binding the set's actions to the alert inputs they consume. This is the procedure most commonly sought when users search for "insert_alr_action_set_inputs," since it is the supported entry point for programmatically wiring inputs to an action set.

Tables Accessed

The package reads and writes the core Oracle Alert action tables via APPS synonyms: ALR_ACTIONS and its sequence ALR_ACTIONS_S supply the action identifiers; ALR_ACTION_SETS and ALR_ACTION_SETS_S provide the action set headers; ALR_ACTION_SET_MEMBERS and ALR_ACTION_SET_MEMBERS_S capture set memberships; ALR_ACTION_SET_INPUTS and ALR_ACTION_SET_OUTPUTS hold the input and output bindings for each set; and ALR_ALERT_INPUTS and ALR_ALERT_OUTPUTS store the alert-level input and output definitions that the set records reference. These tables are read for validation (confirming the referenced alert, input, or output exists) and written to persist the new definitions.

Usage Notes

QA_ALERT_PKG is typically invoked from the Oracle Alert forms (particularly the Action and Action Set windows) as the server-side insert and update logic, from Oracle-supplied setup programs, and from custom PL/SQL migrations or data-load scripts that replicate alert definitions between EBS instances. Because it is an ETRM "OTHER"-classified package and is not referenced by other documented packages, it should be treated as a low-level internal API: callers should respect the documented validation contract, pass correct audit columns and version numbers, and check the returned x_return_status against fnd_api.g_ret_sts_success or g_ret_sts_error before committing. No functional dependencies from other packages are documented, so any concurrent program or extension that uses it must be maintained directly by the invoking application.