Results for “iby_batch_id”

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

Overview

IBY.IBY_PAY_BATCHES_ALL is a Payments (IBY) module table in Oracle E-Business Suite 12.1.1 and 12.2.2. As documented in the ETRM metadata, it stores batch level payment information as submitted by payable programs. Each row represents a payment batch created by a payable process such as Payables Payment Process Requests, and it holds the aggregated totals, customer and bank detail, payment method, currency, and processing status for that batch. The table therefore acts as the parent or header record for the individual payment instructions recorded in IBY_PAY_PAYMENTS_ALL.

From a data-modeling perspective, the mined foreign-key structure suggests a satellite-leaning classification. The table is anchored on its own surrogate primary key BATCH_ID while carrying a foreign key to IBY_BATCHES_ALL via IBY_BATCH_ID, which indicates the table primarily stores descriptive and status-oriented batch attributes attached to the core batch entity. It also participates in a parent role, since IBY_PAY_PAYMENTS_ALL.BATCH_ID references this table.

Key Information Stored

The documented physical schema contains 55 columns. The most significant are:

• BATCH_ID — the surrogate primary key, enforced by the IBY_PAY_BATCHES_ALL_PK unique index, and the column referenced by child payment records.
• IBY_BATCH_ID and IBY_MBATCH_ID — foreign-key linkage to the core batch definition in IBY_BATCHES_ALL.
• PMT_BATCH_REQUEST_ID — identifier of the originating payment batch request, traceable back to the payable program submission.
• PAYER_ID and MPAYER_ID — the payer (payment party) responsible for the batch.
• PMT_METHOD, CURRENCY_CODE, and REF_CURRENCY_CODE — the payment instrument and currency context for the batch.
• BATCH_TOTAL and NUM_OF_TRXNS — aggregate value and count of transactions in the batch, the primary financial control figures.
• BATCH_STATUS — processing state of the batch.
• REQUEST_DATE — submission date of the batch request.
• PMT_BATCH_NAME and PMT_BATCH_SET_ID — user-facing batch identity and grouping.
• Customer and originator bank attributes such as CUST_NAME, CUST_ADDR_CITY, ORIG_BANK_NAME, ORIG_BANK_ACCT_NUMBER, and ORIG_EFT_SWIFT_CODE — remittance and bank-routing detail carried at batch level.
• BEPID, BEP_CODE, and BEP_MESSAGE — payment system connectivity and error information.
• Standard audit columns including CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, and OBJECT_VERSION_NUMBER, plus ORG_ID for multi-organization security.

The only documented unique index is IBY_PAY_BATCHES_ALL_PK on BATCH_ID; no separate business-key unique index is documented.

Common Use Cases and Queries

Typical uses include reconciliation of payment batch totals against payment process request output, monitoring batch statuses, and reporting on originator bank and customer profiles. A common join pattern retrieves batch headers with their child payments:

• SELECT b.BATCH_ID, b.PMT_BATCH_NAME, b.BATCH_TOTAL, b.NUM_OF_TRXNS, p.PAYMENT_ID FROM IBY_PAY_BATCHES_ALL b, IBY_PAY_PAYMENTS_ALL p WHERE b.BATCH_ID = p.BATCH_ID;
• Trace a batch to its originating core batch: join IBY_BATCHES_ALL on IBY_BATCH_ID.
• Filter by ORG_ID and BATCH_STATUS for operational dashboards listing in-flight or failed batches.
• Aggregate BATCH_TOTAL by PMT_METHOD and CURRENCY_CODE for treasury reporting.

Related Objects

• IBY_BATCHES_ALL — parent core batch table, joined via IBY_BATCH_ID.
• IBY_PAY_PAYMENTS_ALL — child table; its BATCH_ID references IBY_PAY_BATCHES_ALL.BATCH_ID.
• IBY_PAY_BATCHES_ALL_PK — primary key index on BATCH_ID.
• Payables Payment Process Request objects (referenced through PMT_BATCH_REQUEST_ID) and IBY payment APIs that create and update batch rows, along with the payer and bank entities identified by PAYER_ID, CUST_ID, and the originator bank columns.