Search Results ce_222_reversal_v




Overview

CE_222_REVERSAL_V is a read-only Oracle EBS view owned by the APPS schema and registered under the Cash Management (CE) product family. Its documented purpose is to expose AR receipts that are candidates for reversing or unclearing. The numeric suffix "222" identifies the internal functional window or program that consumes this view — in this case the Receipt Reversal and Unclearing path within Cash Management. The view is marked VALID in ETRM 12.2.2 and presents each qualifying receipt history row in a flattened, denormalized layout suitable for Oracle Forms blocks, concurrent programs, and reporting.

Conceptually the view answers a single business question: which receipt history rows are presently eligible for reversal or for having their cleared status undone? It joins cash receipt headers and history, bank account context, payment schedules, lookups, and statement reconciliation data so callers do not need to reconstruct this logic themselves. The constant literal 222 emitted at column position 39 acts as a function code so that downstream callers can identify the source of the row.

Underlying Base Objects

The view draws from six functional clusters of base objects:

Key Columns

Common Use Cases and Queries

Typical usage includes driving the Receipt Reversal form, populating unclearing candidates for cash management operators, and feeding reconciliation reporting. A minimal diagnostic query:

SELECT receipt_number,
       currency_code,
       status,
       amount,
       gl_date,
       party_name,
       reversal_category
FROM   apps.ce_222_reversal_v
WHERE  status = 'CLEARED'
ORDER  BY gl_date DESC;

To isolate receipts sitting on an unreconciled bank account:

SELECT receipt_number, bank_account_num,
       statement_number, amount
FROM   apps.ce_222_reversal_v
WHERE  statement_line_id IS NULL
AND    currency_type = 'FUNCTIONAL';

Because the view joins a large matrix of tables, queries should filter aggressively on CASH_RECEIPT_ID, CASH_RECEIPT_HISTORY_ID or RECEIPT_NUMBER to avoid full scans. Do not perform DML against this view; reversal and unclearing must be executed through the supported Cash Management APIs or forms, which apply the required reversal category and reason codes and update AR_CASH_RECEIPT_HISTORY_ALL and the associated accounting events.