Search Results manual_regular

Overview

APPS.AR_BATCHES_V is a supplementary view in the Oracle E-Business Suite Receivables module, owned by the APPS schema and registered under FND Design Data as AR.AR_BATCHES_V. Its documented status is VALID in both EBS 12.1.1 and 12.2.2. The view is classified as a supplementary view used to simplify Oracle Forms coding, which means it exists primarily to flatten lookups and joins that would otherwise have to be performed by the Receivables batch-entry and remittance screens. Oracle explicitly warns that this view should not be queried or altered for data maintenance purposes, and that its definition may change dramatically in subsequent minor or major releases. Despite this caveat, it remains one of the most frequently referenced objects by technical consultants and reporting developers because it consolidates descriptive "meaning" columns — most notably BATCH_STATUS_MEANING, the column users search for when they need to translate a batch status code into a readable value.

Underlying Base Objects

Per the documented ETRM 12.2.2 metadata, APPS.AR_BATCHES_V is defined over a broad set of base objects. The central table is AR_BATCHES (accessed via a synonym), which stores one row per automatic receipt batch and holds the batch identifier, batch date, GL date, deposit date, control count, control amount, exchange rate information, and status codes. AR_BATCH_SOURCES_ALL supplies BATCH_SOURCE_NAME and AUTO_BATCH_NUMBERING. AR_LOCKBOXES contributes LOCKBOX_NUMBER, LOCKBOX_BATCH_NAME, and the lockbox identifier for lockbox-originated batches. AR_TRANSMISSIONS_ALL provides TRANSMISSION_NAME and the transmission request identifier. AR_RECEIPT_CLASSES and AR_RECEIPT_METHODS supply the receipt class and receipt method names, while AR_RECEIPT_METHOD_ACCOUNTS_ALL, CE_BANK_ACCOUNTS, and CE_BANK_ACCT_USES resolve the remittance bank account, bank branch, and bank name attributes. AR_LOOKUPS (a view) and HZ_CODE_ASSIGNMENTS / HZ_PARTIES / HZ_RELATIONSHIPS supply the decoded meaning columns such as BATCH_STATUS_MEANING, BATCH_APPLIED_STATUS_MEANING, and RECEIPT_METHOD_CODE_MEANING. GL_DAILY_CONVERSION_TYPES provides the exchange rate type description. Security and context are enforced through FND_ACCESS_CONTROL_UTIL, FND_GLOBAL, FND_PROFILE, MO_GLOBAL, and XTR_USER_ACCESS.

Key Columns

The most consulted columns include BATCH_ID and NAME (the batch identifier and user-visible batch name), SET_OF_BOOKS_ID, TYPE (the batch type, such as automatic receipts or lockbox), BATCH_SOURCE_NAME, CURRENCY_CODE, BATCH_DATE, GL_DATE, DEPOSIT_DATE, CLOSED_DATE, and EXCHANGE_DATE. Financial control columns include CONTROL_COUNT, CONTROL_AMOUNT, and EXCHANGE_RATE. The STATUS and BATCH_APPLIED_STATUS columns store the internal lookup codes, while BATCH_STATUS_MEANING and BATCH_APPLIED_STATUS_MEANING expose their translated descriptions — these are the columns most often requested when users ask what a batch's current state actually means. Bank and remittance attributes include RECEIPT_CLASS_NAME, RECEIPT_METHOD_NAME, RECEIPT_METHOD_CODE_MEANING, BANK_NAME, BANK_BRANCH_NAME, BANK_ACCOUNT_NUMBER, and BANK_DEPOSIT_NUMBER. Traceability columns include CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, REQUEST_ID, OPERATION_REQUEST_ID, and TRANSMISSION_REQUEST_ID.

Common Use Cases and Queries

Typical scenarios include batch status reconciliation, lockbox transmission auditing, and reconciliation of control amounts against applied receipts. Because the view already resolves the status meaning, reporting queries need not join AR_LOOKUPS directly. A representative query is:

• SELECT batch_id, name, batch_status_meaning, batch_applied_status_meaning, batch_date, control_count, control_amount FROM apps.ar_batches_v WHERE batch_date >= :p_from_date AND batch_date < :p_to_date ORDER BY batch_date;
• SELECT b.batch_id, b.name, b.batch_status_meaning, t.transmission_name FROM apps.ar_batches_v b WHERE b.transmission_id IS NOT NULL;
• SELECT batch_source_name, currency_code, SUM(control_amount) FROM apps.ar_batches_v WHERE status = :p_status GROUP BY batch_source_name, currency_code;

Because the view is designated supplementary and subject to change across releases, permanent customizations should reference the underlying base tables (AR_BATCHES, AR_LOOKUPS, AR_BATCH_SOURCES_ALL) rather than depending on AR_BATCHES_V column stability.