Results for “iby_batches_all”

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

Overview

IBY_BATCHES_ALL is a core table in the Oracle E-Business Suite Payments (IBY) module. It stores records of settlement batch information created and updated by the system during execution of the "Create Settlement Batches" concurrent program. The table captures batch operations for both credit card transactions and bank account transfers, consolidating settlement activity into discrete, auditable batch units. Each row represents a single settlement batch associated with a specific payee and payment instrument.

In terms of data modeling, the relationship structure suggests this object behaves as a satellite-leaning entity. It holds descriptive attributes, statuses, and state-transition timestamps around batch processing, anchored by its own surrogate key while referencing hub-like entities such as payees, payment instruments, and legal entities. This classification is heuristic and reflects how the foreign key graph clusters, not a formally declared Data Vault construct.

Key Information Stored

The table contains 48 documented columns. The most significant are summarized below.

• MBATCHID — The surrogate primary key (IBY_BATCHES_ALL_PK). It uniquely identifies each settlement batch record and is the primary join key for downstream settlement and transaction summary tables.
• BATCHID and PAYEEID — Together these form the unique business key candidate IBY_BATCH_PREQ_BATCH_PAYEE_UK, enforcing one batch per batch identifier per payee. A second unique index, IBY_BATCHES_MBATCHID_U2, reinforces MBATCHID uniqueness.
• MPAYEEID — Foreign key to IBY_PAYEE, identifying the payee receiving settlement proceeds.
• BEPID and BEPCODE — Reference the payment system entry point (IBY_BEPINFO) and its code, describing the channel through which the batch was routed.
• BATCHSTATUS and BATCHSTATEID — Capture the lifecycle state of the batch (open, closed, transmitted), critical for reconciliation reporting.
• BATCHTOTAL, BATCHSALES, BATCHCREDIT — Monetary aggregates for the batch total, sales amount, and credit amount, expressed in CURRENCYNAMECODE.
• NUMTRXNS — Count of transactions contained in the batch, used for validation against IBY_TRXN_SUMMARIES_ALL.
• BATCHOPENDATE and BATCHCLOSEDATE — Timestamps defining the batch processing window.
• LEGAL_ENTITY_ID and ORG_ID — Identify the legal entity and operating unit context, supporting multi-org security and reporting.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, governing row-level access.
• PROCESS_PROFILE_CODE, SETTLEDATE, and INSTRUMENT_TYPE — Describe the processing profile applied, the settlement date, and the payment instrument category (credit card, bank account, and so forth).

Common Use Cases and Queries

Typical reporting scenarios include monitoring batch status, reconciling settlement totals, and investigating failed or disputed batches. A common query lists open or transmitted batches for a given org and period:

• SELECT mbatchid, batchid, payeeid, batchstatus, batchtotal, numtrxns FROM iby_batches_all WHERE org_id = :org_id AND batchopendate >= :start_date AND batchstatus IN ('OPEN','TRANSMITTED');
• Aggregate settlement volume by currency and legal entity: SELECT legal_entity_id, currencynamecode, SUM(batchtotal), SUM(numtrxns) FROM iby_batches_all GROUP BY legal_entity_id, currencynamecode;
• Lookup a specific batch by its business key: SELECT * FROM iby_batches_all WHERE batchid = :batchid AND payeeid = :payeeid;
• Join to IBY_TRXN_SUMMARIES_ALL via MBATCHID to reconcile the sum of transaction amounts against BATCHTOTAL.
• Filter using BR_DISPUTED_FLAG and BATCHSTATUS to surface disputed batches requiring operational follow-up.

Related Objects

IBY_BATCHES_ALL participates in several documented foreign key relationships:

• IBY_BEPINFO — Referenced via IBY_BATCHES_ALL.BEPID, supplying payment system entry point details.
• IBY_PAYEE — Referenced via IBY_BATCHES_ALL.MPAYEEID, providing payee identity.
• FND_SECURITY_GROUPS — Referenced via SECURITY_GROUP_ID, enforcing row-level security.
• FV_LEGAL_ENTITIES — Referenced via LEGAL_ENTITY_ID, tying batches to their legal entity.
• IBY_PAY_BATCHES_ALL — References IBY_BATCHES_ALL through IBY_BATCH_ID and PAYER_ID, linking payment batches to settlement batches.
• IBY_TRXN_SUMMARIES_ALL — References IBY_BATCHES_ALL via MBATCHID, holding transaction-level summaries that roll up into each batch.

These relationships position IBY_BATCHES_ALL as the central settlement anchor between payment instructions, transaction summaries, and payee master data within the IBY Payments architecture.