Search Results alr_response_action_history




Overview
Explore in AI Chat

Overview

The ALR_RESPONSE_ACTION_HISTORY table is a core data object within the Oracle E-Business Suite Alert (ALR) module. It functions as an audit and execution log for the response processing engine. When a user responds to an alert notification, the system processes that response, which may involve executing SQL statements, running operating system scripts, or sending follow-up messages. This table stores a historical record of each discrete action taken during that processing, providing a critical audit trail for troubleshooting, compliance, and performance analysis of automated alert workflows in both EBS 12.1.1 and 12.2.2.

Key Information Stored

The table's primary purpose is to log the execution details of response actions. Its structure is defined by a composite primary key consisting of RESPONSE_MESSAGE_ID and SEQUENCE, allowing multiple history entries for a single response message. Key columns include RESPONSE_MESSAGE_ID, which links to the originating response in ALR_RESPONSE_MESSAGES, and SEQUENCE, which orders the actions performed. Other significant fields likely include NODE_HANDLE and MESSAGE_HANDLE for linking to the specific alert instance in ALR_ACTUAL_RESPONSES, APPLICATION_ID and ALERT_ID to identify the source alert definition, and ORACLE_ID to record the user (from FND_ORACLE_USERID) who triggered the response. Additional columns typically capture timestamps, action types, status codes (success/error), and output or error messages from the executed action.

Common Use Cases and Queries

The primary use case is diagnosing failed or unexpected alert response processing. Administrators query this table to verify action execution and pinpoint errors. Common reporting needs include reviewing all actions for a specific alert over a time period or identifying chronically failing response steps. A typical diagnostic query joins to ALR_RESPONSE_MESSAGES and ALR_ALERTS.

  • Sample Query for Response History:
    SELECT arh.sequence, arh.creation_date, arh.action_type, arh.status, arh.message_text, a.name alert_name
    FROM alr_response_action_history arh,
         alr_response_messages arm,
         alr_alerts a
    WHERE arh.response_message_id = arm.response_message_id
    AND arh.application_id = a.application_id
    AND arh.alert_id = a.alert_id
    AND arm.creation_date > SYSDATE - 1
    ORDER BY arh.response_message_id, arh.sequence;
  • Audit & Compliance: Generating reports to demonstrate the automated processing trail for financial or operational alerts.
  • Performance Analysis: Identifying long-running response actions by analyzing timestamps between sequential entries.

Related Objects

ALR_RESPONSE_ACTION_HISTORY is centrally connected to several key Alert tables via documented foreign key relationships, forming the core of the response processing data model.

  • ALR_RESPONSE_MESSAGES: The parent table for the initial response submission. Joined via ALR_RESPONSE_ACTION_HISTORY.RESPONSE_MESSAGE_ID.
  • ALR_ACTUAL_RESPONSES: Links to the specific instance of an alert that was responded to. Joined via the composite key: ALR_RESPONSE_ACTION_HISTORY.NODE_HANDLE and ALR_RESPONSE_ACTION_HISTORY.MESSAGE_HANDLE.
  • ALR_ALERTS: References the master alert definition. Joined via the composite key: ALR_RESPONSE_ACTION_HISTORY.APPLICATION_ID and ALR_RESPONSE_ACTION_HISTORY.ALERT_ID.
  • FND_ORACLE_USERID: Identifies the Oracle user account associated with the response action. Joined via ALR_RESPONSE_ACTION_HISTORY.ORACLE_ID.