Search Results ce_260_cf_reversal_v




Overview
Explore in AI Chat

Overview

CE_260_CF_REVERSAL_V is a Cash Management (CE) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is part of the ETRM (E-Business Tax and Treasury Reporting Model) family of interface views, identified in the documentation as a Cash Management object described as "AR receipts for reversing or unclearing." The numeric prefix "260" is a strong indicator of a programmatic interface convention, referencing the Cash Management reversal and unclear processing program. In practice, the view exposes cashflow records—principally receipts originating in Oracle Receivables—that are candidates for a reversal or unclearing operation.

The view returns a positional result set with roughly fifty columns, many of which are anonymous DECODE and NVL expressions aliased by their ordinal position. This structure is characteristic of an ETRM interface view designed to feed a concurrent program rather than to be queried ad hoc by end users. Its role is therefore primarily integration and batch processing: it assembles the header, bank account, payment, statement, and reconciliation attributes required to drive reversal or unclearing logic against cashflow and reconciliation data.

Underlying Base Objects

The view is defined over a broad set of Cash Management, Receivables-adjacent, and Financials common objects. The documented base objects for ETRM 12.2.2 include:

The joins bind each cashflow to its bank account, its payment instruction, its reconciliation record, and the relevant bank statement, producing a single flattened row per reversal-eligible cashflow.

Key Columns

The positional columns map to the following semantics:

  • Column 1 (ROWID) — row identifier of the underlying cashflow record.
  • Columns 3–4 (BANK_ACCOUNT_ID, CASHFLOW_ID) — the bank account and unique cashflow identifiers that anchor the operation.
  • Columns 5–6 (CASHFLOW_DIRECTION, MEANING) — the direction of the cashflow and its decoded lookup meaning.
  • Columns 7–11 — bank transaction number, currency code, cashflow amount, and cleared amount, with DECODE logic returning functional, bank, or foreign amount variants.
  • Column 12 — accounting date, coalesced from the accounting history or the cleared date.
  • Columns 13–17 (status, cashflow date, cleared date) — status meaning, the cashflow date, and cleared date values.
  • Columns 19–21 (counterparty bank, bank name) — payout and counterparty bank details.
  • Column 26 (PAYMENT_METHOD_CODE) — the payment method associated with the transaction.
  • Columns 39–44 — the constant 260, the remittance number, counterparty account number, and statement reconciliation identifiers (statement line ID, statement number, amount).
  • Columns 46–47 — a functional/bank/foreign currency classification and the base amount.

Common Use Cases and Queries

Typical usage is by the Cash Management reversal and unclear concurrent program, which consumes the view's rows to reverse or unclear AR receipts. A functional analyst may also query the view to inspect which cashflows are candidates for these operations.

  • Identify candidate cashflows for reversal: select CASHFLOW_ID, BANK_ACCOUNT_ID, and the cashflow amount and status columns, filtering on the cashflow direction and status codes returned by the view.
  • Audit reconciliation linkage: join the statement line ID and statement number columns back to CE_STATEMENT_HEADERS and CE_STATEMENT_LINES to confirm which receipts are already reconciled.
  • Reconcile amounts by currency: use the functional/bank/foreign classification column to compare cashflow amounts against the base amount and cleared amount for each cashflow.

Because positional column access is brittle, queries should select explicit ordinal positions with meaningful aliases, for example: SELECT cashflow_id, bank_account_id, cashflow_amount, cleared_amount FROM app.ce_260_cf_reversal_v WHERE cashflow_status_code = 'CLEARED'. The view should be treated as read-only, as it is intended to present cashflow state rather than to be updated directly.