Results for “ar_batches_all”

50+ results




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

Overview

AR.AR_BATCHES_ALL is the core Receivables table that stores receipt batch information in Oracle E-Business Suite 12.1.1 and 12.2.2. It is the parent object for automatic and manual receipt batch processing, grouping individual cash receipts, interim cash receipts, adjustments, and related transactions under a single controlling batch record. The table is owned by the AR schema and carries the ORG_ID column, meaning it participates in multi-org (Operating Unit) security through the standard MOAC model. Each row represents one batch, defined by a name, a batch date, a source, a control count, and a control amount used to balance batch entry against actual entered receipts.

From a dimensional modeling perspective, the heuristic Data Vault classification mined from the foreign-key structure is satellite-leaning. This suggests modelling the table as a satellite attached to the receipt-batch hub rather than as an independent hub, since the majority of its attributes describe the descriptive context of a batch whose business identity is anchored by its primary and unique keys.

Key Information Stored

The table documents 62 columns. The following are the most operationally significant:

Standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and the fifteen ATTRIBUTE flex columns are also present for audit and descriptive flexibility.

Common Use Cases and Queries

Typical scenarios include batch reconciliation, lockbox transmission tracking, posting-status reporting, and audit of manual versus automatic batches. A common reconciliation query compares the control totals against the actual summed receipts joined through AR_CASH_RECEIPTS_ALL.BATCH_ID:

  • Find all open batches for an operating unit: SELECT batch_id, name, batch_date, status, control_amount FROM ar_batches_all WHERE status = 'OPEN' AND org_id = :p_org_id;
  • Compare control versus actual totals by joining AR_BATCHES_ALL to AR_CASH_RECEIPTS_ALL on BATCH_ID and aggregating AMOUNT.
  • Trace a lockbox batch to its transmission using TRANSMISSION_REQUEST_ID joined to AR_TRANSMISSIONS_ALL.
  • Report batches whose deposits are pending by filtering on DEPOSIT_DATE and STATUS.
  • Cross-reference remittance batches on customer transactions through RA_CUSTOMER_TRX_ALL.REMITTANCE_BATCH_ID.

Related Objects

  • AR_CASH_RECEIPTS_ALL — Child table via BATCH_ID; the confirmed cash receipts belonging to each batch.
  • AR_INTERIM_CASH_RECEIPTS_ALL and AR_INTERIM_CASH_RCPT_LINES_ALL — Child tables via BATCH_ID; unposted receipts pending processing.
  • AR_BATCH_SOURCES_ALL — Parent source definition referenced by BATCH_SOURCE_ID.
  • AR_TRANSMISSIONS_ALL — Remittance transmission referenced by TRANSMISSION_REQUEST_ID.
  • CE_BANK_ACCT_USES_ALL — Bank account use referenced by REMIT_BANK_ACCT_USE_ID.
  • AR_LOCKBOXES_ALL — Lockbox definition referenced by LOCKBOX_ID.
  • AR_ADJUSTMENTS_ALL and AR_AUTOREC_EXCEPTIONS — Child tables via BATCH_ID for adjustments and auto-receipt exceptions.
  • RA_CUSTOMER_TRX_ALL — References this table via REMITTANCE_BATCH_ID.
  • FV_AR_BATCHES_ALL — Federal financials extension table referencing BATCH_ID.
  • AR_MC_BATCHES — Multi-currency companion table referencing BATCH_ID.