Search Results lockbox_batch_name




Overview
Explore in AI Chat

Overview

AR_BATCHES_ALL_MRC_V is a multi-reporting-currency (MRC) view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It exposes automatic receipt batch information from the Receivables (AR) module across multiple sets of books, joining the transactional batch header in AR_BATCHES_ALL with its reporting-currency counterpart in AR_MC_BATCHES. The view is defined as a join between AR_BATCHES_ALL (aliased B) and AR_MC_BATCHES (aliased MC) on BATCH_ID, with a WHERE clause that restricts rows to the set of books identified by the CLIENT_INFO session context. This design allows a single query to return the same batch expressed in the functional and reporting currencies, which is essential for organizations operating multiple sets of books under a single ledger architecture.

Because the view exposes the LOCKBOX_BATCH_NAME column, it is directly relevant to users searching for "lockbox_batch_name". That column carries the bank-side batch identifier used when receipts arrive through lockbox remittance files, making this view a primary access point for lockbox reconciliation reporting.

Underlying Base Objects

The documented base objects underlying the view are:

The join predicate MC.BATCH_ID = B.BATCH_ID pairs each batch header with its reporting-currency row, while the SET_OF_BOOKS_ID filter on AR_MC_BATCHES is dynamically resolved from the client environment. The NVL fallback of -99 returns no matching reporting-currency rows when the client context is not initialized.

Key Columns

Prominent columns exposed by the view include:

  • BATCH_ID — unique batch identifier, used to join beneath the batch to receipts and distributions.
  • SET_OF_BOOKS_ID — the reporting set of books for which the row is returned.
  • NAME / BATCH_DATE / GL_DATE — the batch name, the accounting batch date, and the general ledger date.
  • STATUS / BATCH_APPLIED_STATUS — the batch processing status and its applied status.
  • LOCKBOX_ID / LOCKBOX_BATCH_NAME — the lockbox reference and the bank-provided lockbox batch name.
  • CURRENCY_CODE / EXCHANGE_RATE_TYPE / EXCHANGE_DATE / EXCHANGE_RATE — the currency and conversion information, with the exchange columns sourced from AR_MC_BATCHES.
  • RECEIPT_METHOD_ID / RECEIPT_CLASS_ID / REMITTANCE_BANK_ACCOUNT_ID — payment method and remittance bank identifiers.
  • TYPE / BATCH_SOURCE_ID / CONTROL_COUNT / CONTROL_AMOUNT — batch source, type, and control totals.
  • ORG_ID — the operating unit that owns the batch.

Attribute columns ATTRIBUTE1 through ATTRIBUTE15 and the standard WHO audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) are also exposed.

Common Use Cases and Queries

Typical uses include lockbox batch reconciliation, multicurrency batch reporting, and integration extracts that require both functional and reporting-currency values. A representative query isolating lockbox batches follows:

  • SELECT batch_id, name, lockbox_id, lockbox_batch_name, batch_date, status, control_count, control_amount, currency_code FROM ar_batches_all_mrc_v WHERE lockbox_batch_name IS NOT NULL AND batch_date >= :p_from_date;

To reconcile lockbox batch totals against bank activity:

  • SELECT lockbox_batch_name, currency_code, control_count, control_amount, exchange_rate, gl_date FROM ar_batches_all_mrc_v WHERE org_id = :p_org_id ORDER BY lockbox_batch_name;

Because the SET_OF_BOOKS_ID filter derives from CLIENT_INFO, callers must initialize the session context before querying; otherwise the -99 fallback yields an empty result set. In Release 12, the view is most reliable when invoked from within an application session or when the client context is explicitly set using the standard FND client-info APIs. For single-set-of-books reporting, AR_BATCHES_ALL alone is sufficient; this MRC view is appropriate only where reporting-currency values are required.