Results for “alr_alert_checks”

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

Overview

ALR_ALERT_CHECKS is a transactional table in the Oracle E-Business Suite Alert (ALR) module, owned by the ALR schema. It stores the outcome of individual alert check executions. In Oracle Alert, a periodic or event-driven check evaluates a SQL statement or a system condition against the database; each execution of such a check produces a row in ALR_ALERT_CHECKS that records when the check ran, which concurrent request performed the evaluation, and whether the threshold or condition was satisfied. The table therefore acts as the historical audit trail behind alert firing decisions, distinct from ALR_ALERTS (which defines the alert itself) and ALR_ACTION_SET_CHECKS (which maps checks to action sets).

Mined from its foreign-key structure, the table is satellite-leaning in Data Vault terms: its natural grain is the combination of APPLICATION_ID and ALERT_CHECK_ID, and it carries descriptive, state-bearing attributes (SUCCESS_FLAG, CHECK_TIME, REQUEST_ID) that describe the check execution rather than define a new business entity. This classification is a modeling suggestion rather than a documented fact, and should be validated against the actual alert-check frequency and versioning behaviour in a given implementation.

Key Information Stored

ALR_ALERT_CHECKS contains ten documented columns. The composite primary key, enforced by ALR_ALERT_CHECKS_PK, is (APPLICATION_ID, ALERT_CHECK_ID). This is the surrogate key distinguishing each check execution, and it is also the unique business-key candidate documented as ALR_ALERT_CHECKS_U1 on the same two columns.

• APPLICATION_ID — the application owning the alert; part of the primary key and the join to ALR_ALERTS.
• ALERT_CHECK_ID — the check identifier; second component of the primary key and the column referenced by ALR_ACTION_SET_CHECKS.
• ALERT_ID — the parent alert definition in ALR_ALERTS.
• REQUEST_ID — the concurrent request (FND_CONCURRENT_REQUESTS) that executed the check.
• SUCCESS_FLAG — indicates whether the check returned a result that triggered the alert.
• CHECK_TIME — timestamp of the check execution.
• HISTORY_PURGE_DATE — date after which the row is eligible for purge by the Alerts purge program.
• SECURITY_GROUP_ID — the security group (FND_SECURITY_GROUPS) under which the check was run, supporting Multi-Org Access Control.
• LAST_UPDATE_DATE / LAST_UPDATED_BY — standard EBS audit columns recording the most recent modification.

Common Use Cases and Queries

The most frequent reporting need is to determine why an alert did or did not fire within a given period. A typical query joins ALR_ALERT_CHECKS to ALR_ALERTS to obtain the alert name and to FND_CONCURRENT_REQUESTS to confirm the executing program:

• Alert effectiveness: count checks per alert, grouped by SUCCESS_FLAG, to measure firing rates.
• Performance tuning: correlate CHECK_TIME with REQUEST_ID to identify slow or long-running checks.
• Purge management: select rows where HISTORY_PURGE_DATE is due for cleanup to control table growth.
• Multi-Org auditing: filter by SECURITY_GROUP_ID to scope results to an operating unit.
• Action-set diagnostics: join ALR_ACTION_SET_CHECKS on (APPLICATION_ID, ALERT_CHECK_ID) to confirm which action sets were associated with a fired check.

Because the table grows with every check execution, queries should always constrain on CHECK_TIME or ALERT_ID and avoid full scans on production volumes.

Related Objects

ALR_ALERT_CHECKS is central to the Alert definition model and is referenced by several core EBS objects:

• ALR_ALERTS — parent alert definition, joined on APPLICATION_ID and ALERT_ID.
• ALR_ACTION_SET_CHECKS — maps checks to action sets; references ALR_ALERT_CHECKS on (APPLICATION_ID, ALERT_CHECK_ID).
• FND_CONCURRENT_REQUESTS — the concurrent program execution that ran the check, via REQUEST_ID.
• FND_SECURITY_GROUPS — security group context, via SECURITY_GROUP_ID.
• ALR_ACTION_SETS and the Alert Purge concurrent program — consume check history and drive maintenance.