Search Results iby_trxn_summaries_all

Overview

The IBY_TRXN_SUMMARIES_ALL table is a core data repository within the Oracle E-Business Suite Payments (IBY) module, serving as the primary transactional record for payment requests. It functions as a central summary table, capturing high-level information for every payment transaction initiated across the application, regardless of whether the transaction is processed online (real-time) or offline (batch). Its generic design accommodates the various payment instruments and methods supported by Oracle Payments, including checks, electronic funds transfers (EFT), and credit cards. As a multi-org table (indicated by the _ALL suffix), it stores data for all operating units, making it essential for consolidated enterprise reporting and transaction auditing.

Key Information Stored

The table's primary key is the TRXNMID column, a unique identifier for each payment request summary. Its extensive foreign key relationships reveal the breadth of data it consolidates. Key columns link to critical master and transactional data, including: MPAYEEID (payee), MBATCHID (payment batch), BEPID (Billing and Payment System process), and PAYER_INSTR_ASSIGNMENT_ID (payer's payment instrument). It also holds references to external system identifiers, such as CUST_ACCOUNT_ID from Receivables, AR_RECEIPT_METHOD_ID, and SALES_REP_PARTY_ID. While specific descriptive column names are not detailed in the provided metadata, the foreign keys indicate the table stores core attributes like the payment amount, currency, status, request date, and the associated tangible (MTANGIBLEID) which represents the physical payment medium.

Common Use Cases and Queries

This table is fundamental for payment lifecycle tracking, reconciliation, and troubleshooting. Common operational and reporting queries involve joining to its related master tables. For example, to generate a payment register report for a specific batch, one would join IBY_TRXN_SUMMARIES_ALL to IBY_BATCHES_ALL and IBY_PAYEE. Troubleshooting a specific payment request often starts by querying this table using a known internal identifier. A typical query pattern for auditing purposes would be:

• SELECT trx.trxnmid, trx.payment_amount, trx.payment_currency_code, batch.batch_name, payee.payee_name FROM iby_trxn_summaries_all trx, iby_batches_all batch, iby_payee payee WHERE trx.mbatchid = batch.mbatchid AND trx.mpayeeid = payee.mpayeeid AND batch.batch_status = 'PAID';

The table is also critical for integration points, as downstream processes, such as credit card authorization (referenced by IBY_F_T_CRDT_APPS_ALL_B) and payment messaging (IBY_G_T_MESSAGES), depend on its transaction summary ID.

Related Objects

IBY_TRXN_SUMMARIES_ALL has a wide network of dependencies, as shown by its numerous foreign keys. Key related objects include:

• Master Data Tables: IBY_PAYEE, IBY_TANGIBLE, IBY_BEPINFO, IBY_BATCHES_ALL, HZ_PARTIES, HZ_CUST_ACCOUNTS.
• Instrument & Method Tables: IBY_PMT_INSTR_USES_ALL, IBY_CC_ISSUER_RANGES, AR_RECEIPT_METHODS.
• Extension Tables: IBY_FNDCPT_TX_EXTENSIONS (for initiator data).
• Dependent Transaction Tables: IBY_F_T_CRDT_APPS_ALL_B (credit card applications) and IBY_G_T_MESSAGES, which use TRXN_SUMMARY_ID as a foreign key to link detailed processing records back to the summary.