Results for “alr_action_data”

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

Overview

The ALR_ACTION_DATA table resides in the ALR (Alert) product schema of Oracle E-Business Suite and is documented as VALID in both release 12.1.1 and 12.2.2. Its ETRM description — "Exceptions found during an action set check" — identifies it as the detail-level repository that captures the individual exception rows produced when the Alert Manager evaluates an action set check against a database query. Where an action set defines the generic rules that drive alerting, ALR_ACTION_DATA materialises the concrete outcome: one row per exception encountered during a single evaluation pass of a given action history record.

Under the heuristic Data Vault classification mined from its foreign-key structure, this object is best modelled as a link table. It does not hold descriptive reference attributes of its own domain but instead resolves the many-to-many intersection between a run of the alerting process (ALR_ACTION_HISTORY) and the check definition that fired (ALR_ACTION_SET_CHECKS). Treating it as a link aligns with the composite primary key and the FK topology documented below.

Key Information Stored

ALR_ACTION_DATA contains six documented columns. The composite primary key, enforced through ALR_ACTION_DATA_PK and mirrored by the unique index ALR_ACTION_DATA_U1 on (APPLICATION_ID, ACTION_HISTORY_ID, ROW_NUMBER), uniquely identifies each exception row. The business-key candidate is therefore the same three-column combination, with ROW_NUMBER acting as an ordinal discriminator within each action history run.

• APPLICATION_ID — the application owning the alert definition; part of the PK and the leading column of both foreign keys.
• ACTION_HISTORY_ID — identifies the specific execution record in ALR_ACTION_HISTORY that generated the exceptions; part of the PK.
• ROW_NUMBER — sequence number distinguishing each exception line within the same action history; the third PK column.
• CHECK_ID — identifies the action set check that produced the exception, joining back to ALR_ACTION_SET_CHECKS.
• DUPLICATE_FLAG — marks whether the exception was detected as a repeat of a previously logged occurrence.
• SECURITY_GROUP_ID — the Multi-Org / data-security partitioning column, referencing FND_SECURITY_GROUPS.

Common Use Cases and Queries

The principal use case is operational troubleshooting: when an alert action set reports unexpected exception output, administrators query ALR_ACTION_DATA filtered by ACTION_HISTORY_ID to enumerate each offending row. A representative pattern joining the history header is:

• SELECT h.ACTION_HISTORY_ID, d.ROW_NUMBER, d.CHECK_ID, d.DUPLICATE_FLAG FROM ALR_ACTION_HISTORY h, ALR_ACTION_DATA d WHERE h.APPLICATION_ID = d.APPLICATION_ID AND h.ACTION_HISTORY_ID = d.ACTION_HISTORY_ID AND d.ACTION_HISTORY_ID = :history_id;
• Aggregate counts of exceptions per CHECK_ID to identify noisy checks: SELECT CHECK_ID, COUNT(*) FROM ALR_ACTION_DATA WHERE APPLICATION_ID = :app GROUP BY CHECK_ID;
• Filter on DUPLICATE_FLAG to isolate genuinely new exceptions from recurring ones for alert-fatigue reporting.

Reporting use cases include auditing the effectiveness of action set definitions over time and tracking exception volume trends per application or per check.

Related Objects

The documented foreign keys establish the core relationships; these are the most significant dependent and referenced objects:

• ALR_ACTION_HISTORY — the parent execution record; joined on APPLICATION_ID and ACTION_HISTORY_ID.
• ALR_ACTION_SET_CHECKS — the check definition that fired; joined on APPLICATION_ID and CHECK_ID.
• FND_SECURITY_GROUPS — provides the data-security partition referenced by SECURITY_GROUP_ID.
• ALR_ACTION_SETS and ALR_ACTIONS — the definitional parents reached transitively through the check and history records.
• ALR_ACTION_HISTORY_PKG and the Alert Manager concurrent program — PL/SQL and runtime consumers that populate this table during action set evaluation.