Search Results iby_pay_payments_all




Overview
Explore in AI Chat

Overview

The IBY_PAY_PAYMENTS_ALL table is a core transaction table within the Oracle Payments (IBY) module of Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. Its primary role is to serve as the central repository for payment transaction information as submitted by source payable programs, such as Payables. Each record represents a single payment instruction generated by the system, which may correspond to a check, electronic funds transfer (EFT), or other payment method. The table is designed to store data at the transaction level, making it the definitive source for payment details after they are formatted and before they are transmitted or printed. As a multi-org table (indicated by the "_ALL" suffix), it contains data for all operating units, with access controlled by the MOAC (Multi-Org Access Control) security profile.

Key Information Stored

The table stores comprehensive attributes for each payment transaction. Based on the provided metadata, the primary key is the PMT_TRXN_ID column, which uniquely identifies each payment transaction record. This identifier is critical for linking payment data across the Payments schema. Another key column is BATCH_ID, which is a foreign key to the IBY_PAY_BATCHES_ALL table, grouping individual payments into the batches created during the payment process. While the full column list is not provided, typical data stored includes payment amount, currency, payment method (e.g., CHECK, ELECTRONIC), payment status, payee details, bank account information, and dates for creation, issuance, and clearing. The table essentially holds the payment instruction as it moves through the payment lifecycle.

Common Use Cases and Queries

This table is fundamental for payment inquiry, reconciliation, audit reporting, and troubleshooting. A frequent use case is tracing a specific payment from its source invoice to its final issuance. Given the user's search for "pmt_trxn_id," a common query pattern involves joining to the invoice payments table to retrieve the full payment-invoice relationship. For example, to find details for a specific payment transaction and its associated invoices:

  • SELECT ipmt.invoice_id, pay.* FROM iby_pay_payments_all pay, iby_pay_invoicepmts ipmt WHERE pay.pmt_trxn_id = ipmt.pmt_trxn_id AND pay.pmt_trxn_id = :your_trxn_id;

Another standard reporting use case is listing all payments within a specific batch for reconciliation purposes:

  • SELECT pmt_trxn_id, payment_amount, payment_currency FROM iby_pay_payments_all WHERE batch_id = :your_batch_id ORDER BY pmt_trxn_id;

Related Objects

The IBY_PAY_PAYMENTS_ALL table has integral relationships with several other key Payments objects, as indicated by the foreign keys. The primary foreign key relationship is with IBY_PAY_BATCHES_ALL via the BATCH_ID column, linking each payment to its parent batch. Crucially, the PMT_TRXN_ID column is referenced by the IBY_PAY_INVOICEPMTS table, which serves as the intersection table mapping payments to the specific invoices they are settling. This relationship is essential for understanding the application of payments. Other related tables not listed in the excerpt but commonly joined include IBY_PAY_SERVICE_REQUESTS (for the payment process request) and IBY_DOCS_PAYABLE_ALL (for the original payment instruction documents).