Search Results ce_200_transactions_v




Overview
Explore in AI Chat

Overview

CE_200_TRANSACTIONS_V is a Cash Management (CE) view owned by the APPS schema in Oracle E-Business Suite. Its documented purpose is to expose available AP payments for reconciliation or clearing. In practical terms, the view presents a bank-centric, reconciliation-ready extract of Oracle Payables payment records — checks, electronic payments, and related disbursements — that have not yet been fully reconciled against a bank statement line. Cash Management's manual and automatic reconciliation programs, as well as the AutoBank Reconciliation engine, consume rows from this view as candidate payment transactions.

Because the object is a view rather than a table, it does not store data itself. Instead it derives a normalized, presentation-oriented result set that blends payment header data, bank account context, currency conversion logic, lookup meanings, and reconciliation audit columns. The result set has a consistent shape that the reconciliation user interface and the Cash Management reconciliation workbench expect, allowing AP payments to be displayed side by side with statement lines irrespective of the underlying Payables tables. The view carries Status VALID and is shipped with 12.1.1 and 12.2.2, where the underlying Payables data model (notably AP_CHECKS_ALL) is unchanged in the areas used here.

Underlying Base Objects

The view is defined over a documented set of base objects, which follow a consistent pattern of joining Payables payment data to Cash Management bank account, lookup, and system-parameter infrastructure:

The view therefore behaves as an integration layer: it flattens many-to-one joins across Payables and Cash Management into a single row per payment candidate, with currency-normalized amounts ready for display.

Key Columns

The documented view text exposes several important columns, often through DECODE and TO_CHAR expressions. Notable items include the row identifier (based on the AP_CHECKS rowid), a hard-coded indicator column, bank account identifiers and descriptive name/number, the bank and branch party names, CHECK_ID, a literal 'PAYMENT' transaction category, payment method or status meaning, check number in both character and numeric form, currency code, transaction amount, and a currency-normalized amount. The view also produces cleared amount and cleared base amount columns with DECODE logic that maps the status 'CLEARED BUT UNACCOUNTED' to 'CLEARED', accounting date, status lookup code, check date, cleared date, future pay due date, cleared exchange date, exchange rate type, and user conversion type. Timestamp columns and the session/security columns derived from FND_GLOBAL and CE_SECURITY_PROFILES_GT complete the reconciliation context.

Common Use Cases and Queries

Typical usage centers on reconciliation reporting and integration extract. A basic query lists unreconciled payments for a bank account:

  • List available payments for a bank account: SELECT check_id, check_number, amount, currency_code, status_lookup_code FROM ce_200_transactions_v WHERE bank_account_id = :p_bank_account_id;
  • Filter by status: add AND status_lookup_code = 'CLEARED' to isolate already-cleared items.
  • Currency-normalized totals: SELECT currency_code, SUM(amount) FROM ce_200_transactions_v GROUP BY currency_code;
  • Join to statement reconciliation: join on check_id to AP or CE reconciliation tables to trace which payments remain outstanding.

Because the view is secured by Cash Management security profiles, results returned to an end user are automatically restricted to the bank accounts and organizations the user is authorized to access. This makes the view suitable both for ad hoc reporting and for feeding downstream reconciliation processes.