Search Results iby_batch_preq_batch_payee_uk

Overview

The IBY_BATCHES_ALL table is a core data object within the Oracle Payments (IBY) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It serves as the central repository for settlement batch information, a critical component in the payment processing lifecycle. The table is populated and updated by the system during the execution of the 'Create Settlement Batches' program. Its primary role is to store and manage metadata for batch operations involving both credit card transactions and bank account transfers, facilitating the grouping of individual payment instructions for efficient and organized settlement with financial institutions.

Key Information Stored

The table's structure is designed to track the identity, status, and relationships of settlement batches. The primary key is the MBATCHID column, which uniquely identifies each batch record. Another significant column is BATCHID, which, in conjunction with PAYEEID, forms a unique key (IBY_BATCH_PREQ_BATCH_PAYEE_UK), ensuring batch identification per payee. Critical foreign key columns establish essential relationships: BEPID links the batch to a specific Business Event Processor (BEP) or payment system in the IBY_BEPINFO table, and MPAYEEID references the master payee in the IBY_PAYEE table. While the provided metadata does not list all columns, typical data stored includes batch creation date, status (e.g., 'CREATED', 'SUBMITTED', 'SETTLED'), batch total amounts, and the associated payment method.

Common Use Cases and Queries

This table is fundamental for payment operations reporting and reconciliation. Common use cases include tracking the status of all settlement batches for a given time period, identifying batches associated with a specific payee or payment system, and reconciling batch totals against transaction summaries. A typical reporting query might join IBY_BATCHES_ALL with related transaction tables. For example, to list recent batches with their status and system:

• SELECT batch.mbatchid, batch.batchid, batch.status, bep.bep_name FROM iby_batches_all batch, iby_bepinfo bep WHERE batch.bepid = bep.bepid AND batch.creation_date > SYSDATE - 30 ORDER BY batch.creation_date DESC;

Another critical use case is troubleshooting, where technical consultants query this table to verify if a batch was successfully created by the concurrent program before proceeding to the next payment step.

Related Objects

The IBY_BATCHES_ALL table is a central hub within the Payments schema, with several key dependencies as indicated by its foreign keys. It has a direct foreign key relationship to IBY_BEPINFO (via BEPID) and IBY_PAYEE (via MPAYEEID). Furthermore, it is referenced as a parent table by other critical payment objects. The IBY_PAY_BATCHES_ALL table links individual payment instructions to a settlement batch using IBY_BATCH_ID. The IBY_TRXN_SUMMARIES_ALL table, which holds summarized transaction data, references IBY_BATCHES_ALL via MBATCHID, enabling the roll-up of transaction details to the batch level for reporting and settlement.