Search Results reversal_category




Overview
Explore in AI Chat

Overview

APPS.CE_REVERSAL_TRANSACTIONS_V is a reporting and integration view in the Oracle E-Business Suite Cash Management (CE) module. It presents a consolidated, user-facing projection of payment and receipt reversal transactions, exposing transaction-level attributes alongside reversal-specific context such as the reversal category, reversal reason, and reversal comments. The view is defined as a UNION ALL over a family of version-specific reversal views — CE_200_REVERSAL_V, CE_222_REVERSAL_V, CE_260_CF_REVERSAL_V, and CE_999_REVERSAL_V — each corresponding to a distinct bank statement or reconciliation format supported by the Cash Management auto-reconciliation engine.

Because the underlying reversal views are gated by calls into the CE_AUTO_BANK_MATCH and CE_AUTO_BANK_CLEAR packages (through the CE_AUTO_BANK_MATCH.GET_200 = 1 predicate visible in the documented view text), the view effectively surfaces only the reversal population relevant to the currently active reconciliation format. This makes it a stable integration point for external reporting tools, custom concurrent programs, and reconciliation dashboards that must remain unaware of the versioned internals.

Underlying Base Objects

The view is defined over multiple objects rather than a single base table. The documented referenced objects are:

  • CE_200_REVERSAL_V, CE_222_REVERSAL_V, CE_260_CF_REVERSAL_V, CE_999_REVERSAL_V — the version-specific reversal views UNIONed to form the consolidated result set.
  • CE_AUTO_BANK_MATCH — supplies the GET_200 style format-selection predicates that filter which branch contributes rows.
  • CE_AUTO_BANK_CLEAR — participates in the reconciliation/clearing logic exposed through the reversal views.
  • ARP_CASHBOOK — provides receipt-related context (bank account and currency information).
  • FND_GLOBAL — supplies session context such as ORG_ID and user identity, enforcing multi-org and security filtering.
  • IBY_FD_EXTRACT_GEN_PVT — supports payment instruction extraction and payment-method attributes.

Functionally, the view therefore sits on top of CE payment/receipt reversal data, the bank account model, and the auto-reconciliation engine, rather than on a single physical table.

Key Columns

The projection exposes 48+ columns. The most significant include:

Common Use Cases and Queries

Typical scenarios include reconciliation exception reporting, audit of reversals by category or reason, and feeding reversal data into downstream accounting or treasury extracts. A representative query filtering on the searched attribute is:

  • SELECT trx_number, trx_type, currency_code, amount, reversal_category, reversal_reason, reversal_comments, status FROM apps.ce_reversal_transactions_v WHERE reversal_category = '&category' AND org_id = :org_id;
  • Reversal volume by bank account: SELECT bank_account_num, reversal_category, COUNT(*) FROM apps.ce_reversal_transactions_v GROUP BY bank_account_num, reversal_category;
  • Statement reconciliation review: SELECT statement_number, trx_number, statement_line_amount, cleared_date FROM apps.ce_reversal_transactions_v WHERE statement_line_id IS NOT NULL;

Queries should always constrain by ORG_ID to respect multi-org security, and results reflect only the reversal population enabled by the currently active reconciliation format through the auto-bank-match predicates.