Search Results reversal_category_type




Overview
Explore in AI Chat

Overview

APPS.CE_222_REVERSAL_V is a reporting view in the Oracle E-Business Suite Cash Management (CE) module. It exposes cash receipt reversal activity by combining receipt header, receipt history, bank account, statement reconciliation, and customer information into a single denormalized result set. The numeric suffix "222" identifies a standard Cash Management reversal report data source, and the leading literal column value 222 (position 39 in the SELECT list) is used by the Cash Management reporting framework to tag rows belonging to that report identifier.

The view is central to reconciling reversed receipts against bank statements and to tracing why a receipt was reversed. It is bound to the search term "ckajst_reason" through the CR.REVERSAL_REASON_CODE, REVERSAL_COMMENTS, and related lookup meaning columns (positions 32 through 35), which surface the reversal category and the free-text reason recorded by the user. As a read-only view, it plays no transactional role; its purpose is reporting and integration, typically feeding concurrent report programs, custom inquiries, and downstream extracts in EBS 12.1.1 and 12.2.2.

Underlying Base Objects

According to the documented ETRM 12.2.2 metadata, the view is defined over a mixture of synonyms and views owned by APPS. The principal AR objects are AR_CASH_RECEIPTS_ALL (the receipt header, aliased CR in the SQL), AR_CASH_RECEIPT_HISTORY_ALL (receipt history, aliased CRH), AR_PAYMENT_SCHEDULES_ALL (payment schedule, including the customer due date, aliased APS), AR_RECEIPT_METHODS (payment method lookup, aliased RM), and AR_BATCHES_ALL. Supporting AR and GL objects include AR_LOOKUPS, GL_LEDGERS (for the functional currency SOB), and the ARP_CASHBOOK package.

The Cash Management side contributes CE_BANK_ACCOUNTS and CE_BANK_ACCT_USES_ALL (bank account, account number, name, and currency), CE_STATEMENT_HEADERS, CE_STATEMENT_LINES, CE_STATEMENT_RECONCILS_ALL, and CE_SYSTEM_PARAMETERS, together with the CE_AUTO_BANK_CLEAR package, CE_LOOKUPS, CE_SECURITY_PROFILES_GT, and HZ_CUST_ACCOUNTS / HZ_PARTIES for the customer account and party name. The joins tie each history row to its receipt, its bank account, its payment schedule, and any reconciliation to a bank statement line, producing one row per receipt-history combination.

Key Columns

Common Use Cases and Queries

Typical uses include a reversal reason inquiry, a reconciliation reconciliation-by-reason extract, and a period-end audit of reversed receipts for a given operating unit and ledger. A representative query follows:

  • SELECT receipt_number, party_name, reversal_category, reversal_reason_code, reversal_comments, amount, gl_date FROM apps.ce_222_reversal_v WHERE org_id = :p_org_id AND status = 'CLEARED';
  • SELECT reversal_reason_code, COUNT(*) FROM apps.ce_222_reversal_v WHERE gl_date BETWEEN :p_start AND :p_end GROUP BY reversal_reason_code;
  • SELECT statement_number, receipt_number, amount FROM apps.ce_222_reversal_v WHERE statement_number IS NOT NULL;

Because the view references CE_SECURITY_PROFILES_GT and ORG_ID, callers should apply the standard Cash Management security and multi-org predicates to ensure each user sees only authorized bank accounts and operating units. Reports should treat it strictly as a read-only data source; reversal processing itself continues to occur through the Cash Management and Receivables forms and APIs.