Search Results ar_lockboxes

Overview

AR_BATCHES_V is a declarative view owned by the APPS schema and exposed as part of the Oracle Receivables (AR) module. It presents a denormalized, reporting-friendly projection of receipt and remittance batch information held in the AR_BATCHES base table, enriched with descriptive attributes drawn from batch sources, receipt classes, receipt methods, transmissions, lockboxes, bank branches, and daily conversion types. In Oracle EBS 12.1.1 and 12.2.2 the view is marked VALID and is intended primarily for inquiry, reporting, and integration consumers that require batch context without joining the full set of transactional tables manually.

The view resolves foreign keys into human-readable names — batch source name, receipt class name, receipt method name, transmission name, lockbox number, and exchange rate type display — and derives a normalized TYPE value through a DECODE expression over BT.TYPE and BT.BATCH_APPLIED_STATUS. It also exposes multi-org and access-control awareness through references to FND_GLOBAL, FND_PROFILE, FND_ACCESS_CONTROL_UTIL, MO_GLOBAL, and XTR_USER_ACCESS, so query results respect the operating unit and security context of the session.

Underlying Base Objects

The documented base objects underlying AR_BATCHES_V include AR_BATCHES (the primary driving table), AR_BATCH_SOURCES_ALL, AR_LOCKBOXES, AR_RECEIPT_CLASSES, AR_RECEIPT_METHODS, AR_RECEIPT_METHOD_ACCOUNTS_ALL, AR_TRANSMISSIONS_ALL, GL_DAILY_CONVERSION_TYPES, AR_LOOKUPS (itself a view), CE_BANK_ACCOUNTS, CE_BANK_ACCT_USES (a view), HZ_PARTIES, HZ_RELATIONSHIPS, and HZ_CODE_ASSIGNMENTS. Several of these are referenced as synonyms in the APPS schema, while security and context are supplied by the FND and MO packages.

Because it is a view rather than a table, AR_BATCHES_V stores no data of its own. All values are derived at query time from the joins above. This has two practical consequences: the view always reflects current base-table state, and query performance depends heavily on the selectivity of predicates passed through to AR_BATCHES.

Key Columns

• BATCH_ID, NAME, TYPE — primary batch identifier, user-visible batch name, and the normalized batch type produced by the DECODE over BT.TYPE and BT.BATCH_APPLIED_STATUS (for example MANUAL_REGULAR, MANUAL_QUICK, or POSTBATCH_WAITING).
• BATCH_SOURCE_ID, BATCH_SOURCE_NAME, AUTO_BATCH_NUMBERING — the batch source and whether numbering is automatic.
• SET_OF_BOOKS_ID, CURRENCY_CODE, BATCH_DATE, GL_DATE, DEPOSIT_DATE, CLOSED_DATE — accounting and dating attributes.
• EXCHANGE_RATE, EXCHANGE_RATE_TYPE, EXCHANGE_RATE_TYPE_DSP — conversion rate and its descriptive type from GL_DAILY_CONVERSION_TYPES.
• RECEIPT_CLASS_ID/NAME, RECEIPT_METHOD_ID/NAME, REMIT_METHOD_CODE and its meaning — receipt classification and remittance method, including a lookup-derived meaning.
• CONTROL_COUNT, CONTROL_AMOUNT — expected batch totals used for reconciliation.
• TRANSMISSION_ID/NAME, LOCKBOX_ID/NUMBER, LOCKBOX_BATCH_NAME, MEDIA_REFERENCE — transmission and lockbox identifiers.
• REMIT_BANK_ACCT_USE_ID, REMITTANCE_BANK_BRANCH_ID, BANK_BRANCH_ID, BANK_NAME — bank account and branch attribution derived through HZ_PARTIES and bank tables.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, and the PROGRAM_* concurrency columns.

Common Use Cases and Queries

Typical uses include batch status inquiries, reconciliation of control amounts against applied receipts, and integration extracts for treasury or lockbox processing. A representative query lists open batches for the current operating unit:

• SELECT batch_id, name, type, batch_source_name, control_count, control_amount FROM ar_batches_v WHERE closed_date IS NULL ORDER BY batch_date DESC;
• SELECT batch_id, name, receipt_method_name, receipt_class_name, currency_code, exchange_rate FROM ar_batches_v WHERE batch_id = :p_batch_id;
• SELECT name, lockbox_number, transmission_name, media_reference FROM ar_batches_v WHERE lockbox_id IS NOT NULL;

When filtering, always constrain on indexed base columns such as BATCH_ID, SET_OF_BOOKS_ID, or BATCH_DATE to ensure the optimizer pushes predicates to AR_BATCHES. The view should be treated as read-only; all maintenance is performed against the underlying AR_BATCHES table through the Receivables forms or APIs.