Search Results insert_alr_action_sets

Overview

QA_ALERT_PKG is an APPS-owned PL/SQL package body classified under Oracle EBS as an OTHER API. It belongs to the Oracle Alerts and Quality/Alert infrastructure that supports the definition and maintenance of alert actions and action sets within the E-Business Suite. In the context of Oracle EBS 12.1.1 and 12.2.2, the package provides the server-side persistence logic that application forms, concurrent programs, and internal framework code rely upon when alert-related records must be created in the underlying ALR_* tables.

The package is documented as VALID and carries no downstream dependencies; no other database object references APPS.QA_ALERT_PKG. Its dependencies are inbound only, spanning a set of Alerts tables and standard Oracle technology components such as FND_API, STANDARD, and SYS. Because the package manipulates action and action-set metadata rather than executing alert logic itself, it functions as a supporting repository-layer utility for the Oracle Alert model.

Key Procedures and Functions

The ETRM metadata documents six procedures and functions in this package body. Their names reflect a consistent insert-oriented persistence pattern for alert actions and the components that compose action sets:

• INSERT_ALR_ACTIONS — Inserts records into the ALR_ACTIONS table, creating the definition of an individual alert action.
• UPDATE_ALR_ACTIONS — Updates existing alert action definitions, modifying attributes of an action previously created through the insert routine.
• INSERT_ALR_ACTION_SETS — Creates action set header records, establishing a named grouping of alert actions.
• INSERT_ALR_ACTION_SET_MEMBERS — Populates the membership table that links individual actions into an action set.
• INSERT_ALR_ACTION_SET_OUTPUTS — Inserts the output definitions associated with an action set.
• INSERT_ALR_ACTION_SET_INPUTS — Inserts the input definitions associated with an action set.

Together these routines cover the lifecycle operations required to build and revise the action and action-set configuration used by Oracle Alert. No parameter signatures are documented in the ETRM extract, and none should be assumed.

Tables Accessed

The package references the following APPS synonyms, each serving a specific role in the alert action data model:

• ALR_ACTIONS and ALR_ACTIONS_S — The action definition table and its corresponding translation or shadow table, supporting insert and update of action records.
• ALR_ACTION_SETS and ALR_ACTION_SETS_S — The action set header table and its shadow/translation counterpart.
• ALR_ACTION_SET_INPUTS, ALR_ACTION_SET_OUTPUTS, and ALR_ACTION_SET_MEMBERS plus ALR_ACTION_SET_MEMBERS_S — The component tables that define the inputs, outputs, and membership of an action set.
• ALR_ALERT_INPUTS and ALR_ALERT_OUTPUTS — The alert-level input and output tables, read to validate or align action set definitions with the parent alert.

The _S suffixed tables are used for translated or secured copies of the base records, consistent with the multilingual and multi-organization conventions in EBS. The user search term alr_actions_s corresponds directly to one of the tables this package writes to.

Usage Notes

QA_ALERT_PKG is not invoked by any other database object, indicating that it is called from outside the PL/SQL dependency graph — most likely from Oracle Forms or concurrent processing that manages Alert definitions. Typical invocation paths include the Oracle Alerts setup forms, where a user defines or modifies actions and action sets, and concurrent programs that seed or migrate alert configuration. Custom extensions that need to create alert actions programmatically can call the insert routines directly, provided they respect the underlying table constraints and the translated _S records.

Because the package is documented only through its dependency list and procedure names, callers should inspect the live package specification for exact parameter signatures before invoking it. Administrators should also confirm that the package remains VALID after patching or upgrades, since invalid state here can break the Alerts configuration path in both 12.1.1 and 12.2.2 environments.