Search Results ce_available_transactions_v




Overview
Explore in AI Chat

Overview

CE_AVAILABLE_TRANSACTIONS_V is an APPS-owned database view in Oracle E-Business Suite that consolidates bank transactions eligible for reconciliation in Oracle Cash Management (CE). It presents a harmonised, security-filtered result set drawn from multiple transaction-type-specific views, allowing bank statement reconciliation, cash positioning, and treasury reporting to operate against a single logical interface rather than querying each underlying source independently.

The view is central to the Cash Management reconciliation workbench. Records returned by the view represent transactions that have not yet been fully reconciled or cleared and are therefore "available" for matching against bank statement lines. Depending on the transaction category, these may be payments, receipts, miscellaneous journal entries, EFT transactions, or cash-flow transactions sourced from Payables, Receivables, General Ledger, and Treasury.

Because it is a view rather than a table, no storage is allocated to it directly; however, performance characteristics are inherited from the underlying views and their base tables, and it is subject to Oracle row-level security through the MO_GLOBAL and FND_ACCESS_CONTROL_UTIL packages referenced in its definition.

Underlying Base Objects

The view is not defined over base tables directly; it is assembled from a family of transaction-specific views, each of which targets a particular reconciliation context. The documented reference objects include:

Procedural components referenced by the definition include CE_AUTO_BANK_MATCH and CE_AUTO_BANK_CLEAR (rate determination), PAY_CE_RECONCILIATION_PKG, IBY_FD_EXTRACT_GEN_PVT, and the security/utility packages FND_GLOBAL, FND_PROFILE, FND_ACCESS_CONTROL_UTIL, MO_GLOBAL, and XTR_USER_ACCESS. The UNION of these sources yields a single row per available transaction, with a TRX_ID/TRX_TYPE discriminator identifying its origin.

Key Columns

The column list is extensive. Notable columns include:

Common Use Cases and Queries

Typical applications include reconciliation dashboards, un-reconciled item ageing reports, deposit_date-based cash forecasting, and integration extracts. A representative query filtering by deposit date is:

SELECT trx_number, trx_type, deposit_date, amount, currency_code, status_dsp, bank_account_id FROM ce_available_transactions_v WHERE deposit_date BETWEEN :start_date AND :end_date AND org_id = :org_id AND status = 'UNRECONCILED' ORDER BY deposit_date, trx_number;

Because the view enforces organisation and access control through MO_GLOBAL and XTR_USER_ACCESS, callers must initialise the multi-org context (MO_GLOBAL.SET_POLICY_CONTEXT) and, in payments-based flows, invoke the appropriate initialisation methods before executing queries; otherwise the result set may be empty or incomplete.