Results for “alert_id”

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

Overview

ALR_ACTION_SET_CHECKS is a table in the ALR (Alert) product schema of Oracle E-Business Suite, documented as valid in both 12.1.1 and 12.2.2. It stores action set check information, functioning as the associative structure that ties an action set definition to the individual alert checks that invoke it. Within the Oracle Alert architecture, an alert is composed of checks that evaluate database conditions; when a check succeeds or fails, one or more action sets may be executed, and those action sets may contain further checks. ALR_ACTION_SET_CHECKS records these check-level associations so that the Alert Manager can evaluate and dispatch the correct action set for a given alert check.

Because the table carries its own identity (APPLICATION_ID plus CHECK_ID) while also referencing parent entities such as ALR_ACTION_SETS, ALR_ALERTS, ALR_ALERT_CHECKS, and FND_ORACLE_USERID, a Data Vault modeling heuristic classifies it as satellite-leaning. This is a modeling suggestion rather than a physical schema statement: the table behaves primarily as a descriptive or contextual record attached to the alert/action-set hubs, with foreign key columns serving both as the primary key and as references to the surrounding model.

Key Information Stored

The primary key, ALR_ACTION_SET_CHECKS_PK, is defined on the composite of APPLICATION_ID and CHECK_ID. The same two columns are also documented as unique index ALR_ACTION_SET_CHECKS_U1, so no separate surrogate key exists — the business identity and the physical key coincide.

• APPLICATION_ID — the owning application identifier; part of the primary key and used in nearly every foreign key relationship.
• CHECK_ID — the unique check identifier within the application; the second component of the primary key and the value propagated to dependent tables such as ALR_ACTION_DATA and ALR_OUTPUT_HISTORY.
• ALERT_ID — identifies the alert to which the check belongs, joining back to ALR_ALERTS.
• ACTION_SET_ID — the action set associated with the check; joins to ALR_ACTION_SETS and PA_ACTION_SETS.
• ALERT_CHECK_ID — the alert check that triggers this action set association; joins to ALR_ALERT_CHECKS and referenced by ALR_ACTUAL_RESPONSES.
• ORACLE_ID — the Oracle user identifier under which the action set executes; joins to FND_ORACLE_USERID.
• ROW_COUNT and ACTION_COUNT — counters capturing the volume of rows processed and actions performed for the check.
• SUCCESS_FLAG — outcome indicator for the check action set.
• SECURITY_GROUP_ID — the security group controlling visibility, joining to FND_SECURITY_GROUPS.

Common Use Cases and Queries

Typical usage focuses on diagnosing why an alert action set did or did not fire, and on reporting the check-to-action-set mapping. A basic lookup by application and check follows:

• Verify action set associations for a specific alert: SELECT CHECK_ID, ALERT_ID, ACTION_SET_ID, ALERT_CHECK_ID, SUCCESS_FLAG FROM ALR_ACTION_SET_CHECKS WHERE APPLICATION_ID = :app AND ALERT_ID = :alert;
• Locate the Oracle user and security group assigned to a check: SELECT ORACLE_ID, SECURITY_GROUP_ID FROM ALR_ACTION_SET_CHECKS WHERE APPLICATION_ID = :app AND CHECK_ID = :check;
• Trace activity volumes by joining to history: SELECT c.CHECK_ID, c.ROW_COUNT, c.ACTION_COUNT, h.ACTION_DATE FROM ALR_ACTION_SET_CHECKS c, ALR_ACTION_HISTORY h WHERE c.APPLICATION_ID = h.APPLICATION_ID AND c.CHECK_ID = h.CHECK_ID;
• Confirm successful dispatch: filter on SUCCESS_FLAG to isolate checks whose action sets completed, useful in operational monitoring and alert tuning.

Related Objects

• ALR_ALERTS — parent alert definition; joined via APPLICATION_ID and ALERT_ID.
• ALR_ACTION_SETS — the action set assigned to the check, joined via APPLICATION_ID and ACTION_SET_ID.
• ALR_ALERT_CHECKS — the alert check definition driving the action set, joined via APPLICATION_ID and ALERT_CHECK_ID.
• FND_ORACLE_USERID — resolves the ORACLE_ID execution account.
• FND_SECURITY_GROUPS — resolves SECURITY_GROUP_ID visibility controls.
• FND_PRODUCT_INSTALLATIONS — application registration referenced through APPLICATION_ID.
• ALR_ACTION_DATA, ALR_ACTION_HISTORY, ALR_ACTUAL_RESPONSES, ALR_OUTPUT_HISTORY — child tables keyed by APPLICATION_ID and CHECK_ID (or ALERT_CHECK_ID for actual responses) that record action payloads, execution history, responses, and output.