Results for “action_set_member_id”

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

Overview

ALR_ACTION_HISTORY is a transaction-history table in the Oracle Alert (ALR) product within Oracle E-Business Suite 12.1.1 and 12.2.2. It records the actual execution history of alert actions — that is, each instance in which an alert's action (or a member of an action set) was run against a triggered alert condition. While the alert definition tables describe what should happen, ALR_ACTION_HISTORY captures what did happen: which action executed, at what action level, whether it succeeded, and the message and node context in which it was processed.

The table is owned by the ALR schema and is documented as VALID, with 17 columns in the ETRM 12.2.2 physical schema. Its primary key is ALR_ACTION_HISTORY_PK, defined on the composite (APPLICATION_ID, ACTION_HISTORY_ID). A second unique index, ALR_ACTION_HISTORY_U1, mirrors the same (APPLICATION_ID, ACTION_HISTORY_ID) pair and therefore serves as the business-key candidate. The presence of ALERT_ID, ACTION_SET_ID, ACTION_ID, CHECK_ID, and ACTION_SET_MEMBER_ID as descriptive context around that key supports a satellite-leaning classification under a heuristic Data Vault model: the table primarily stores descriptive state about an action-execution event, keyed by that event identifier. A full historical record would typically pair this satellite with the hub/link structures of the alert, alert set, and action-definition tables it references.

Key Information Stored

The most significant columns, as documented in the ETRM metadata, are:

• APPLICATION_ID / ACTION_HISTORY_ID — the composite primary key. APPLICATION_ID ties the record to the owning alert application, while ACTION_HISTORY_ID is the surrogate/unique identifier of the execution-history row.
• ALERT_ID — the alert whose action was executed; a foreign-key reference to ALR_ALERTS.
• ACTION_SET_ID — the action set that contained the executed action; references ALR_ACTION_SETS (and PA_ACTION_SETS for the action-set definition).
• ACTION_ID — the specific action definition executed.
• CHECK_ID — the action set check that governed the execution, referenced via ALR_ACTION_SET_CHECKS.
• ACTION_SET_MEMBER_ID — the action-set member row that produced the execution; references ALR_ACTION_SET_MEMBERS.
• ACTION_LEVEL — the level or scope at which the action was executed.
• ACTION_EXECUTED_FLAG / SUCCESS_FLAG — flags indicating whether the action was executed and whether it completed successfully. These two columns support the primary operational reporting on this table.
• MESSAGE_HANDLE / NODE_HANDLE — identifiers linking the action execution to the actual response context; NODE_HANDLE references ALR_ACTUAL_RESPONSES.
• MAXIMUM_SUMMARY_MESSAGE_WIDTH and COLUMN_WRAP_FLAG — formatting parameters captured at execution time.
• SECURITY_GROUP_ID — the security group context, referencing FND_SECURITY_GROUPS.
• VERSION_NUMBER / LAST_UPDATE_DATE — row-version and audit metadata.

Common Use Cases and Queries

The principal use is operational and historical reporting on alert action execution — for example, identifying failed actions, understanding execution patterns over time, and diagnosing why an alert produced no response. A typical query groups executions by alert and success status:

• Failure analysis: SELECT ALERT_ID, ACTION_ID, ACTION_LEVEL, MAXIMUM_SUMMARY_MESSAGE_WIDTH FROM ALR.ALR_ACTION_HISTORY WHERE SUCCESS_FLAG = 'N' AND ACTION_EXECUTED_FLAG = 'Y';
• Execution counts per alert: SELECT ALERT_ID, COUNT(*) FROM ALR.ALR_ACTION_HISTORY GROUP BY ALERT_ID ORDER BY 2 DESC;
• Drill-down to responses: join NODE_HANDLE and MESSAGE_HANDLE to ALR_ACTUAL_RESPONSES (both columns are FK-shared there) to correlate an executed action with its generated response message.
• Action-set diagnostics: join ACTION_SET_ID and CHECK_ID to confirm which set member and check triggered each execution.

Because the table is a history store, it grows with alert activity and is a prime candidate for purge or archival reporting in mature environments.

Related Objects

ALR_ACTION_HISTORY is heavily relational, with parent references and one child table:

• ALR_ALERTS — joined on APPLICATION_ID (and ALERT_ID) to retrieve the alert definition.
• ALR_ACTION_SETS and PA_ACTION_SETS — joined on APPLICATION_ID / ACTION_SET_ID for action-set context.
• ALR_ACTION_SET_MEMBERS — joined on ACTION_SET_MEMBER_ID to identify the member that executed.
• ALR_ACTION_SET_CHECKS — joined on CHECK_ID to identify the governing action-set check.
• ALR_ACTUAL_RESPONSES — joined on NODE_HANDLE and MESSAGE_HANDLE for response-level detail.
• ALR_ACTION_DATA — the child table referencing this table via APPLICATION_ID and ACTION_HISTORY_ID; holds the detailed action data for each history row.
• FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID for security-group context.