Results for “iby_g_t_msg_req_log”

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

Overview

The IBY.IBY_G_T_MSG_REQ_LOG table is a Payments module data object within the Oracle E-Business Suite (EBS) IBY schema. It functions as a logging and audit trail for message request activity processed through the Oracle Payments messaging framework. Each row captures one message request event, recording when a message was requested, how many times, and the response returned by an external system. This makes it a critical diagnostic and reconciliation artifact for integrations that exchange payment instructions and status messages with external financial institutions, clearing houses, or payment gateways.

Under a heuristic Data Vault classification, the documented foreign key structure — a reference to IBY_G_T_MESSAGES plus a SECURITY_GROUP_ID link to FND_SECURITY_GROUPS — suggests a satellite-leaning model. In practice this means the table behaves primarily as a descriptive, event-context record attached to a parent message entity rather than as an independent hub or associative link. The MSG_REQ_LOG_ID surrogate key provides row-level identity, while MESSAGE_ID ties each log entry back to the message definition it describes.

Key Information Stored

The table is documented with 16 columns in the 12.2.2 physical schema. The most significant are:

• MSG_REQ_LOG_ID — surrogate primary key, enforced by the IBY_G_T_MSG_REQ_LOG_PK constraint and mirrored by the unique index IBY_G_T_MSG_REQ_LOG_U1. This is the business-key candidate for row identity.
• MESSAGE_ID — foreign key to IBY_G_T_MESSAGES, identifying the parent message definition being logged.
• MSG_REQ_COUNT — the number of times the message request was issued, useful for retry and throttling analysis.
• MSG_REQ_TIME — the timestamp at which the message request was executed.
• EXT_SYSTEM_RESP_CODE — the response code returned by the external system, enabling success/failure classification.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program context identifying the batch job that generated the request.
• OBJECT_VERSION_NUMBER — optimistic locking column for concurrent update control.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS WHO columns for audit lineage.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, supporting multi-tenant or operating-unit data segregation.

Common Use Cases and Queries

Typical scenarios include troubleshooting failed payment message transmissions, measuring message request frequency, and reconciling external system responses against internal payment records.

To review recent message activity for a specific message:

• SELECT l.MSG_REQ_LOG_ID, l.MESSAGE_ID, l.MSG_REQ_COUNT, l.MSG_REQ_TIME, l.EXT_SYSTEM_RESP_CODE FROM IBY.IBY_G_T_MSG_REQ_LOG l WHERE l.MESSAGE_ID = :p_message_id ORDER BY l.MSG_REQ_TIME DESC;

To trace requests back to the originating concurrent program:

• SELECT l.REQUEST_ID, l.PROGRAM_ID, l.MSG_REQ_TIME, l.EXT_SYSTEM_RESP_CODE FROM IBY.IBY_G_T_MSG_REQ_LOG l WHERE l.REQUEST_ID = :p_request_id;

To identify messages exceeding a retry threshold:

• SELECT MESSAGE_ID, SUM(MSG_REQ_COUNT) total_requests FROM IBY.IBY_G_T_MSG_REQ_LOG GROUP BY MESSAGE_ID HAVING SUM(MSG_REQ_COUNT) > 5;

These queries support operational monitoring and are frequently used in BI Publisher reports or custom OAF pages built for payment operations teams.

Related Objects

The most significant objects related to this table, based on the documented FK relationships, are:

• IBY_G_T_MESSAGES — joined via IBY_G_T_MSG_REQ_LOG.MESSAGE_ID, the parent message definition table.
• FND_SECURITY_GROUPS — joined via SECURITY_GROUP_ID, providing security-group context.
• FND_CONCURRENT_REQUESTS — related through REQUEST_ID, supplying concurrent program execution details.
• FND_CONCURRENT_PROGRAMS — related through PROGRAM_ID and PROGRAM_APPLICATION_ID.
• IBY_G_T_MSG_REQ_LOG_PK / IBY_G_T_MSG_REQ_LOG_U1 — the primary key constraint and unique index defining row identity.

These relationships make the table a dependable anchor for joining message definitions to their runtime request evidence within the Oracle Payments integration layer.