Results for “message_xml_id”

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

Overview

IBY_G_T_MESSAGES is a Payments (IBY) module table in the Oracle E-Business Suite 12.1.1 / 12.2.2 schema, owned by the IBY schema and documented as VALID. It functions as a transient staging and interface table that captures payment processing messages generated during outbound payment instruction, transaction summarization, and credit application workflows. The "G_T" naming convention identifies the table as a global temporary-style or interface staging object used to persist message payloads and their XML representations before final consumption by Oracle Payments and downstream payment system integrations.

Based on the foreign key topology mined from the ETRM metadata, the table exhibits a satellite-leaning Data Vault classification. It is not a pure hub (its primary key, MESSAGE_ID, is a surrogate identifier rather than a natural business key), and it does not resolve many-to-many relationships, so a link classification is not indicated. The column pattern of REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, CREATED_BY, and the four standard WHO audit columns confirms it behaves as a descriptive satellite attached to transaction summary, document, and credit application entities. This classification is a modeling suggestion only, derived heuristically from the FK structure.

Key Information Stored

The table contains 18 documented columns in the 12.2.2 physical schema. The columns of greatest functional importance include:

• MESSAGE_ID — the surrogate primary key, enforced by IBY_G_T_MESSAGES_PK and reinforced by unique index IBY_G_T_MESSAGES_U1. This is the single documented business-key candidate.
• REQUEST_ID — links the message row to the concurrent program request that generated it, enabling traceability through the concurrent manager.
• PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — identify the concurrent program and application that produced the message.
• TRXN_SUMMARY_ID — foreign key referencing IBY_TRXN_SUMMARIES_ALL, tying the message to a payment transaction summary record.
• CREDIT_APP_ID — foreign key referencing IBY_F_T_CRDT_APPS_ALL_B, associating the message with a credit application header.
• MESSAGE_XML_ID — foreign key referencing IBY_TRXN_DOCUMENTS, the pointer to the XML document payload stored for the message.
• MESSAGE_CAT_CODE and MESSAGE_TYPE_CODE — categorize and type the message for processing and routing logic.
• MESSAGE_TIME — the timestamp at which the message was generated.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, supporting multi-org or security-group filtering.
• OBJECT_VERSION_NUMBER — the standard EBS optimistic locking column for concurrent update protection.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — WHO audit columns for user and timestamp attribution.

Common Use Cases and Queries

Typical use cases include diagnosing failed or stalled payment instructions, tracing message generation back to a specific concurrent request, auditing XML payloads emitted for transaction summaries, and reconciling credit application messages. A representative diagnostic query joins the table to its request log:

• SELECT m.MESSAGE_ID, m.MESSAGE_CAT_CODE, m.MESSAGE_TYPE_CODE, m.MESSAGE_TIME, l.REQUEST_ID FROM IBY.IBY_G_T_MESSAGES m, IBY.IBY_G_T_MSG_REQ_LOG l WHERE m.MESSAGE_ID = l.MESSAGE_ID AND m.TRXN_SUMMARY_ID = :summary_id;
• SELECT m.MESSAGE_ID, m.MESSAGE_XML_ID FROM IBY.IBY_G_T_MESSAGES m WHERE m.CREDIT_APP_ID = :credit_app_id;
• SELECT m.MESSAGE_ID, m.MESSAGE_TIME FROM IBY.IBY_G_T_MESSAGES m WHERE m.MESSAGE_TIME >= :from_date AND m.MESSAGE_TIME < :to_date;

Because the table is interface-oriented, reporting queries should generally constrain by MESSAGE_TIME, REQUEST_ID, or the relevant foreign key to avoid full scans on what can be a high-volume staging object.

Related Objects

• IBY_TRXN_SUMMARIES_ALL — joined on IBY_G_T_MESSAGES.TRXN_SUMMARY_ID = IBY_TRXN_SUMMARIES_ALL.TRXN_SUMMARY_ID.
• IBY_TRXN_DOCUMENTS — joined on IBY_G_T_MESSAGES.MESSAGE_XML_ID = IBY_TRXN_DOCUMENTS.MESSAGE_XML_ID.
• IBY_F_T_CRDT_APPS_ALL_B — joined on IBY_G_T_MESSAGES.CREDIT_APP_ID = IBY_F_T_CRDT_APPS_ALL_B.CREDIT_APP_ID.
• FND_SECURITY_GROUPS — joined on IBY_G_T_MESSAGES.SECURITY_GROUP_ID.
• IBY_G_T_MSG_REQ_LOG — the dependent child table referencing this table on MESSAGE_ID.

These relationships define the processing chain: a transaction summary or credit application triggers message generation, the message payload is stored as an XML document, and the request log records the processing request that consumed it.