Results for “alr_groups_and_actions_view”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The ALR_GROUPS_AND_ACTIONS_VIEW is a consolidated reporting view within the Oracle E-Business Suite Alert (ALR) module. It presents a unified listing of alert actions and action groups associated with a given alert, resolving the descriptive meaning of each action or group directly from the ALR_LOOKUPS reference table. The view is significant because it allows developers and administrators to query alert definitions without navigating the separate ALR_ACTIONS and ALR_ACTION_GROUPS tables, and without performing manual joins to decode lookup values. Its primary role is to support reporting, integration, and diagnostic queries that need to enumerate the configured actions for an alert, including both individually defined actions and grouped actions, together with exit actions registered at the alert level. The view is owned by the APPS schema and is documented as VALID. Given the user's search term "action_type," the view exposes an ACTION_TYPE column that classifies each action or group according to Oracle's ACTION_TYPE lookup codes, making it a natural starting point for queries that filter or categorize alert behavior.

Underlying Base Objects

The view is defined over several base objects, each referenced in ETRM metadata as synonyms owned by APPS:

• ALR_ACTIONS — stores individual alert actions, including the ACTION_TYPE value used to filter enabled actions.
• ALR_ACTION_GROUPS — stores grouping definitions that bundle multiple actions into a single logical unit.
• ALR_ALERTS — the alert header table, joined to provide context for exit actions.
• ALR_LOOKUPS — the reference lookup table, joined twice (aliased AORG and T) to resolve group type and action type meanings.

The view text is constructed as a three-part UNION ALL. The first branch selects from ALR_ACTIONS joined to two ALR_LOOKUPS instances, restricting to enabled actions (ENABLED_FLAG = 'Y') and tagging rows with TYPE = 'A'. The second branch selects from ALR_ACTION_GROUPS with equivalent lookup joins, tagging rows with TYPE = GROUP_TYPE. The third branch derives exit-action rows from ALR_ALERTS and ALR_LOOKUPS where LOOKUP_TYPE = 'ALR_EXIT_ACTION', assigning a synthetic ACTION_ID of -5 and TYPE = 'A'. This union design ensures that individual actions, action groups, and exit actions appear in a single, cohesive result set.

Key Columns

• APPLICATION_ID — identifies the application that owns the alert or action.
• ALERT_ID — the parent alert to which the action or group belongs.
• ACTION_ID — the primary identifier of the action or action group; synthetic value -5 marks exit actions.
• NAME — the descriptive name of the action, group, or exit-action meaning.
• ACTION_TYPE — the lookup code categorizing the action or group (for example, an action category), the primary filter attribute users search on.
• DESCRIPTION — a concatenation of the group type meaning and the action type meaning, formatted as "MEANING: MEANING" for readability.
• TYPE — indicates the row origin, where 'A' denotes a direct action (or exit action) and other values reflect the group type.

Common Use Cases and Queries

Typical scenarios include auditing which actions are configured for a specific alert, listing all actions of a given ACTION_TYPE, and surfacing exit actions in alert diagnostics. A representative query filtering by action type and alert follows:

• List all actions for an alert: SELECT ACTION_ID, NAME, ACTION_TYPE, DESCRIPTION, TYPE FROM APPS.ALR_GROUPS_AND_ACTIONS_VIEW WHERE ALERT_ID = :alert_id ORDER BY TYPE, ACTION_ID;
• Filter by action type: SELECT ALERT_ID, ACTION_ID, NAME, DESCRIPTION FROM APPS.ALR_GROUPS_AND_ACTIONS_VIEW WHERE ACTION_TYPE = 'EMAIL';
• Identify exit actions: SELECT ALERT_ID, NAME, DESCRIPTION FROM APPS.ALR_GROUPS_AND_ACTIONS_VIEW WHERE ACTION_ID = -5;
• Count actions per type: SELECT ACTION_TYPE, COUNT(*) FROM APPS.ALR_GROUPS_AND_ACTIONS_VIEW GROUP BY ACTION_TYPE;

Because the view consolidates decoded lookup meanings and unions multiple object types, it is suited to ad hoc reporting, migration validation, and integration extracts that require a complete picture of an alert's configured actions in Oracle EBS 12.1.1 and 12.2.2.