Search Results ce_222_txn_for_batch_v




Overview
Explore in AI Chat

Overview

CE_222_TXN_FOR_BATCH_V is an Oracle E-Business Suite view owned by the APPS schema and validated in the Cash Management (CE) product. Its documented purpose is to present Available Remittance Batches for Reconciliation or Clearing. Functionally, the view exposes cash receipt history rows that are eligible to be grouped into a remittance batch and subsequently processed through bank reconciliation or clearing workflows.

The view is a critical component of the CE remittance batch processing architecture. It surfaces the transactional detail required to assemble a batch of receipts, including receipt amounts, accounted amounts, currency conversion attributes, exchange rate information, and the bank account context. Users searching for the identifier column prv_stat_cash_receipt_hist_id — the prior statement cash receipt history reference — will find that this view returns the current CASH_RECEIPT_HISTORY_ID alongside related receipt history and batch identifiers, enabling reconciliation logic to correlate the current history row with the preceding statement line.

Underlying Base Objects

The view is defined over a substantial join across the Receivables and Cash Management schemas. Documented referenced objects include the synonyms AR_BATCHES_ALL, AR_CASH_RECEIPTS_ALL, AR_CASH_RECEIPT_HISTORY_ALL, AR_PAYMENT_SCHEDULES_ALL, AR_RECEIPT_CLASSES, AR_RECEIPT_METHODS, CE_BANK_ACCOUNTS, CE_BANK_ACCT_USES_ALL, CE_SECURITY_PROFILES_GT, CE_STATEMENT_RECONCILS_ALL, CE_SYSTEM_PARAMETERS, and GL_DAILY_CONVERSION_TYPES, together with the views AR_LOOKUPS, CE_LOOKUPS, CE_BANK_ACCT_USES_OU_V, and GL_SETS_OF_BOOKS, plus the package CE_AUTO_BANK_CLEAR.

Central to the definition are the receipt tables AR_CASH_RECEIPTS_ALL and AR_CASH_RECEIPT_HISTORY_ALL, joined twice (aliased CRH and CRH2) to link the current receipt history row to the batch history row. AR_BATCHES_ALL supplies the remittance batch context, while CE_STATEMENT_RECONCILS_ALL supports reconciliation status. CE_SECURITY_PROFILES_GT and CE_BANK_ACCT_USES_OU_V enforce operating unit and bank account security filtering, and GL_SETS_OF_BOOKS provides the set of books (SOB) currency used in the DECODE expressions.

Key Columns

  • CASH_RECEIPT_HISTORY_ID — Unique identifier of the receipt history row, the primary record exposed for batch association.
  • CASH_RECEIPT_ID — Foreign key to the parent receipt in AR_CASH_RECEIPTS_ALL.
  • BATCH_ID — The remittance batch to which the receipt history row belongs, sourced from the second history alias (CRH2).
  • TYPE and STATUS — Receipt type and current history status (for example, CLEARED), which drive amount and clearing logic.
  • CURRENCY_CODE, EXCHANGE_RATE, EXCHANGE_DATE, EXCHANGE_RATE_TYPE — Currency and conversion attributes used to distinguish entered versus accounted values.
  • AMOUNT-type expressions — Entered and accounted receipt amounts, each adjusted by NVL on FACTOR_DISCOUNT_AMOUNT, with DECODE logic selecting the correct value based on whether the receipt currency matches the SOB or bank account currency.
  • Cleared amounts — DECODE expressions returning AMOUNT or ACCTD_AMOUNT only when CRH.STATUS is 'CLEARED'.
  • GL_DATE, RECEIPT_DATE — Accounting and receipt dates used for period and reconciliation matching.
  • BANK_ACCT_USE_ID and ORG_ID — Bank account usage and operating unit context for security and filtering.

Common Use Cases and Queries

Typical use cases include identifying receipts eligible for remittance batching, reconciling cleared versus uncleared amounts, and populating bank reconciliation screens. The prior statement history identifier lookup usually arises when tracing a reconciliation entry back to its predecessor history record; the view supplies the current history and batch identifiers required for that linkage.

A representative query selecting available transactions for a batch:

  • SELECT CASH_RECEIPT_HISTORY_ID, CASH_RECEIPT_ID, BATCH_ID, STATUS, CURRENCY_CODE, GL_DATE, BANK_ACCT_USE_ID, ORG_ID FROM CE_222_TXN_FOR_BATCH_V WHERE STATUS = 'CLEARED' AND ORG_ID = :p_org_id;
  • SELECT CASH_RECEIPT_HISTORY_ID, BATCH_ID, EXCHANGE_RATE, RECEIPT_DATE FROM CE_222_TXN_FOR_BATCH_V WHERE CASH_RECEIPT_ID = :p_receipt_id;

Because the view enforces bank account and operating unit security through CE_SECURITY_PROFILES_GT and CE_BANK_ACCT_USES_OU_V, queries should always supply the ORG_ID and bank account context to return the correct data set.