Results for “alr_response_messages”

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

Overview

The ALR.ALR_RESPONSE_MESSAGES table is a core data object within the Oracle EBS Alert (ALR) module. Its documented purpose is to store the actual messages received in reply to alert messages that Oracle Alert has dispatched to recipients. In the Oracle Alert workflow, an alert can be defined with response processing, allowing recipients to reply with acknowledgment or action-oriented responses. This table captures the inbound side of that dialogue, persisting the content, routing metadata, and processing state of each reply.

From a dimensional modeling perspective, the ETRM metadata classifies this object heuristically as satellite-leaning. This suggests it is best modeled as a satellite table attached to a business hub or link, holding descriptive and transactional attributes about each response message. Its primary key, RESPONSE_MESSAGE_ID, is a surrogate identifier, and the table is heavily involved in foreign key relationships with response-definition and response-history tables, reinforcing its role as a transactional detail store within the Alert response subsystem.

Key Information Stored

The ALR_RESPONSE_MESSAGES table contains 18 documented columns. The most operationally significant are described below.

• RESPONSE_MESSAGE_ID — The surrogate primary key defined by the ALR_RESPONSE_MESSAGES_PK constraint. It uniquely identifies each received response message.
• MESSAGE_HANDLE and NODE_HANDLE — Handles tying the response to the actual response record and originating node; these participate in a foreign key to ALR_ACTUAL_RESPONSES.
• APPLICATION_ID, ALERT_ID, RESPONSE_SET_ID, RESPONSE_ID, RESPONSE_TYPE — Collectively identify the alert, response set, and response definition the inbound message corresponds to. These columns support foreign keys to ALR_VALID_RESPONSES and ALR_RESPONSE_SETS.
• SUBJECT and BODY — The human-readable subject line and full text content of the received reply.
• SENT_FROM, TO_RECIPIENTS, CC_RECIPIENTS, BCC_RECIPIENTS, REPLY_TO — Email routing metadata capturing the sender, distribution list, carbon-copy and blind-copy recipients, and the reply-to address.
• RECEIVED and DATE_PROCESSED — Timestamps recording when the reply was received and when Oracle Alert finished processing it.
• SECURITY_GROUP_ID — The multi-org security group applied to the record, referencing FND_SECURITY_GROUPS.

The unique index ALR_RESPONSE_MESSAGES_U1 on RESPONSE_MESSAGE_ID confirms the surrogate key as the sole documented business-key candidate.

Common Use Cases and Queries

Typical reporting scenarios include auditing alert acknowledgement rates, tracing the lifecycle of a response from receipt through processing, and identifying unprocessed replies. A representative query joining the parent response definition follows.

• Listing replies awaiting processing: SELECT RESPONSE_MESSAGE_ID, SUBJECT, RECEIVED FROM ALR.ALR_RESPONSE_MESSAGES WHERE DATE_PROCESSED IS NULL ORDER BY RECEIVED;
• Correlating replies to a specific alert: SELECT m.SUBJECT, m.SENT_FROM, m.RECEIVED FROM ALR.ALR_RESPONSE_MESSAGES m WHERE m.APPLICATION_ID = :app AND m.ALERT_ID = :alert;
• Auditing response actions: join to ALR_RESPONSE_ACTION_HISTORY on RESPONSE_MESSAGE_ID to reconstruct actions taken after receipt.

Related Objects

The table participates in several documented foreign key relationships.

• ALR_ACTUAL_RESPONSES — referenced via NODE_HANDLE and MESSAGE_HANDLE.
• ALR_VALID_RESPONSES — referenced via APPLICATION_ID, ALERT_ID, RESPONSE_SET_ID, and RESPONSE_ID.
• ALR_RESPONSE_SETS — referenced via APPLICATION_ID, ALERT_ID, and RESPONSE_SET_ID.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID.
• ALR_RESPONSE_ACTION_HISTORY — a child table referencing this table through RESPONSE_MESSAGE_ID.