Results for “ce_260_reconciled_v”

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

Overview

CE_260_RECONCILED_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite. It belongs to the Cash Management (CE) product family and is classified as valid. As its description states, the view exposes reconciled statement lines intended for the unreconciling process. Within the Bank Statement Reconciliation workflow, this object provides the data set from which previously reconciled bank statement lines can be identified and reversed, allowing a reconciliation to be undone without manually rebuilding the underlying statement records.

Functionally, the view is a curated projection over the Cash Management reconciliation tables. It normalizes currency handling, translates transactional codes and statuses through the CE_LOOKUPS view, and supplies constant marker columns that identify the record context. The literal value 260 and the constant 1 appearing in the select list, together with the 'N' and 'STATEMENT' string literals, are signature fields used by the reconciliation engine to recognize rows drawn from this specific source. Because it is a view rather than a table, it stores no data and inherits the security and DML restrictions of the tables beneath it.

Underlying Base Objects

Per the documented ETRM metadata, CE_260_RECONCILED_V is defined over the following base objects:

• CE_BANK_ACCTS_GT_V — a view supplying bank account attributes, including account name, account number, currency code, and bank branch.
• CE_LOOKUPS — a view used to resolve transaction type and status codes into descriptive meanings.
• CE_STATEMENT_HEADERS — a synonym for the statement header table, providing header-level data such as statement number, statement date, GL date, control end balance, and statement complete flag.
• CE_STATEMENT_LINES — a synonym for the statement line table, the primary source of individual cashflow lines subject to reconciliation.
• CE_STATEMENT_RECONCILS_ALL — a synonym for the reconciliation detail table, linking statement lines to the transactions against which they were matched.
• CE_SYSTEM_PARAMETERS — a synonym for Cash Management system parameters, notably supplying the set of books used to determine functional currency.
• CE_TRANSACTION_CODES — a synonym for transaction code definitions.
• GL_DAILY_CONVERSION_TYPES — a synonym for General Ledger conversion type definitions used for exchange rate handling.
• GL_SETS_OF_BOOKS — a view supplying the functional currency of the operating set of books.

Key Columns

The select list exposes several categories of columns. Identification columns include ROWID of the statement line and the statement line identifier. Financial columns include AMOUNT, ORIGINAL_AMOUNT, CHARGES_AMOUNT, EXCHANGE_RATE, and EXCHANGE_RATE_DATE. Currency handling is prominent: the CURRENCY_CODE column is derived through nested NVL logic across the line, header, and bank account, while a separate DECODE expression classifies the transaction as FUNCTIONAL, BANK, or FOREIGN by comparing the line currency to the functional and bank currencies. The view also carries GL_DATE, TRX_DATE, EFFECTIVE_DATE, and header dates. Descriptive columns include lookup-derived MEANING values for transaction type and status, the bank account name and number, statement number, statement date, and the transaction code description. It also exposes STATUS, LINE_NUMBER, DOC_SEQUENCE_VALUE, CONTROL_END_BALANCE, STATEMENT_COMPLETE_FLAG, and audit columns such as CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, and LAST_UPDATED_BY, plus REQUEST_ID. Multiple placeholder columns are cast to NULL or TO_NUMBER(NULL), preserving a fixed column layout expected by the calling program.

Common Use Cases and Queries

The principal use case is populating the candidate list presented during the unreconcile operation in Cash Management. A typical query retrieves reconciled lines for a bank account and date range:

• SELECT statement_line_id, bank_trx_number, trx_date, amount, currency_code, status FROM ce_260_reconciled_v WHERE bank_account_id = :p_account_id AND trx_date BETWEEN :p_from AND :p_to;
• Filtering by statement to isolate all reconcilable lines on a given statement: SELECT * FROM ce_260_reconciled_v WHERE statement_number = :p_statement_number AND statement_complete_flag = 'Y';
• Reporting on currency classification for reconciliation audit purposes: SELECT statement_line_id, currency_code, amount FROM ce_260_reconciled_v WHERE currency_code = 'FUNCTIONAL';

Because the view is read-only and joins several large tables, queries should always be constrained by bank account, statement, or date to avoid full scans. It is also commonly used in custom reconciliation reports and in data extracts feeding downstream matching engines, since it already resolves lookup meanings and currency classification that would otherwise require manual joins.