Results for “ce_260_cf_reconciled_v”

50+ results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

CE_260_CF_RECONCILED_V is an APPS-owned database view in the Oracle E-Business Suite Cash Management (CE) module. Its documented purpose is to expose reconciled cashflow receipts and payments for unreconciling. In practical terms, the view surfaces bank statement lines and their associated cashflows that have already been matched and reconciled, so that downstream processes, reports, and integrations can identify, review, or reverse those reconciliations.

The view is registered in ETRM as VALID in the APPS schema and is present in both Oracle EBS 12.1.1 and 12.2.2 environments. It belongs to the family of CE_260_* reconciliation views that Cash Management uses during the bank reconciliation workflow. The 260-series naming convention reflects the standard Oracle Cash Management reconciliation program/report numbering, and the "CF" designation indicates that the rowset is cashflow-centric. Because it is a view rather than a table, it holds no persistent data; it projects and joins the underlying reconciliation, statement, and cashflow entities at query time.

The view is therefore best understood as a reporting and reconciliation-support construct. It supplies already-reconciled receipt and payment records together with the identifiers needed to unreconcile them, making it useful for reconciliation audits, correction of erroneous matches, and controlled reversal of prior reconciliation activity.

Underlying Base Objects

According to the documented 12.2.2 metadata, CE_260_CF_RECONCILED_V is defined over the following referenced base objects:

The view text confirms these relationships: it joins cashflows (CC) to statement lines (CLL), bank accounts (ABA), the ledger (SOB), currencies (FC), and lookups (LK, L2), and correlates reconciliation records from CE_STATEMENT_RECONCILS_ALL. The ROWID of the cashflow is retained as the first column, which is significant for update/reversal operations.

Key Columns

The view exposes a positional column list, many annotated in the view text. Notable columns include:

  • ROWID — the cashflow ROWID, distinguishing each cashflow record for unreconciling.
  • Flag ('N') — a literal indicator column.
  • STATEMENT_LINE_ID / BANK_ACCOUNT_ID / CASHFLOW_ID — keys linking the row to its statement line, bank account, and cashflow.
  • CASHFLOW_DIRECTION — receipt or payment direction.
  • TRX_TYPE (LK.MEANING) — transaction type meaning from lookups.
  • BANK_TRXN_NUMBER and TRX_NUMBER — bank-assigned and system transaction references.
  • CASHFLOW_CURRENCY_CODE and currency type — a DECODE classified as 'FUNCTIONAL', 'BANK', or 'FOREIGN'.
  • CASHFLOW_AMOUNT and BANK_ACCOUNT_AMOUNT — the transaction amount and its bank-account-currency equivalent, computed with exchange-rate and minimum-accountable-unit rounding logic.
  • AMOUNT (CRE.AMOUNT) — the reconciled amount.
  • Accounting/clearing dates — NVL(CCH.ACCOUNTING_DATE, CC.CLEARED_DATE), CLEARED_DATE, and CLEARED_EXCHANGE_DATE.
  • CASHFLOW_STATUS_CODE and status meaning (L2.MEANING) — reconciliation status.
  • Clearing charges and clearing error amounts — converted to bank account currency using the same rounding rules.

Common Use Cases and Queries

The primary use case is identifying reconciled cashflows eligible for unreconciliation. A typical query filters by bank account and reconciliation status:

SELECT cashflow_id, bank_trxn_number, cashflow_amount,
       bank_account_amount, cleared_date, cashflow_status_code
FROM   apps.ce_260_cf_reconciled_v
WHERE  bank_account_id = :p_bank_account_id
AND    cleared_date >= :p_from_date;

Analysts also use the view to reconcile statement lines against cashflows in audit reporting, and to confirm that the accounting date, cleared date, and exchange rate attributes are correctly stamped before reversal. Because security-profile enforcement is embedded through CE_SECURITY_PROFILES_GT, queries automatically respect the accessing user's bank account access. The view should be treated as read-oriented reference data; unreconciliation is performed through the supported Cash Management APIs and concurrent programs rather than direct DML against the view.