Search Results iby_pay_batches_all_pk

Overview

The IBY_PAY_BATCHES_ALL table is a core data repository within the Oracle E-Business Suite Payments (IBY) module. It serves as the primary table for storing batch-level payment information generated when payable programs, such as Oracle Payables, submit payment instructions for processing. Its role is to maintain a master record of each payment batch, linking high-level batch attributes to the individual payment instructions stored in related tables. As a multi-org table (indicated by the "_ALL" suffix), it contains data for all operating units, with access typically controlled by a security profile or the MO_GLOBAL.ORG_ID column.

Key Information Stored

The table's structure is centered on the unique batch identifier. The primary key is the BATCH_ID column, which uniquely identifies each payment batch record. According to the provided metadata, two critical foreign key relationships define its integration. The IBY_BATCH_ID column links to the IBY_BATCHES_ALL table, which holds more general batch control information. The PAYER_ID column is a foreign key to the IBY_PAY_PAYMENTS_ALL table, establishing the connection between a batch and the specific payment instructions it contains. While the full column list is not detailed in the excerpt, typical columns in this table would include batch name, creation date, status, total batch amount, payment currency, and the identifier of the submitting program (e.g., Payables Payment Process).

Common Use Cases and Queries

This table is central to payment batch inquiry, reconciliation, and audit reporting. A common use case is tracking the status and composition of batches submitted from Payables. For example, to list all payment batches created within a specific date range for a given operating unit, a query would join on IBY_BATCHES_ALL for descriptive information. Troubleshooting often involves identifying batches associated with failed payments by joining IBY_PAY_BATCHES_ALL to IBY_PAY_PAYMENTS_ALL and filtering on payment status. A typical reporting pattern is aggregating the total payment amount per batch, which involves summing amounts from the payment lines table grouped by BATCH_ID.

Related Objects

• IBY_BATCHES_ALL: Linked via the foreign key IBY_PAY_BATCHES_ALL.IBY_BATCH_ID. This table stores broader administrative batch details.
• IBY_PAY_PAYMENTS_ALL: Linked via the foreign key IBY_PAY_BATCHES_ALL.PAYER_ID. This is the core payments table where individual payment instructions reside; the relationship defines which payments belong to a specific batch.
• IBY_PAY_BATCHES_ALL_PK: The primary key constraint on the BATCH_ID column, ensuring uniqueness.
• AP_INVOICE_PAYMENTS_ALL / AP_CHECKS_ALL: While not directly referenced in the metadata, in a standard Payables-to-Payments flow, batches and payments in IBY tables ultimately relate back to these Payables tables for accounting and check issuance details.