Search Results ce_101_transactions_v




Overview
Explore in AI Chat

Overview

CE_101_TRANSACTIONS_V is a Cash Management (CE) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to expose available GL journals for reconciliation — that is, the General Ledger journal lines posted to the cash and bank clearing accounts that Cash Management can present to a user for manual or automatic reconciliation against bank statement lines. The view functions as a bridge between Oracle General Ledger and the Cash Management reconciliation workbench, normalizing journal line data into the transaction-shaped record that reconciliation expects.

The literal 101 embedded in the view text and in its row structure identifies the source type as GL journal lines within Cash Management's unified transaction model. This view is therefore read by reconciliation inquiry forms, reconciliation APIs, and customer-built reports that need to see unreconciled GL activity attributable to a bank account.

Underlying Base Objects

The view is defined over a documented set of base objects. The central fact source is GL_JE_LINES, joined to GL_JE_HEADERS and GL_JE_BATCHES for header and batch context. GL_JE_CATEGORIES supplies the journal category name, while GL_DAILY_CONVERSION_TYPES, GL_LEDGERS, and GL_PERIOD_STATUSES provide conversion and accounting period context.

Bank account identification comes from CE_BANK_ACCOUNTS, CE_BANK_ACCT_USES_ALL, and CE_GL_ACCOUNTS_CCID, which map the bank account to its cash, clearing, and bank GL accounts. HZ_PARTIES supplies the bank and branch party names. Reconciliation state and security are handled through CE_STATEMENT_RECONCILS_ALL, CE_SECURITY_PROFILES_GT, and CE_SYSTEM_PARAMETERS. Decoded values are resolved via CE_LOOKUPS and GL_LOOKUPS.

Key Columns

Common Use Cases and Queries

Typical scenarios include reconciling GL cash activity to bank statements, auditing unreconciled journal lines per bank account, and feeding custom reconciliation dashboards. A representative query is:

SELECT bank_account_id, bank_account_name, je_header_id, je_line_num, currency_code, effective_date, period_name, status FROM apps.ce_101_transactions_v WHERE bank_account_id = :p_bank_account_id AND effective_date BETWEEN :p_from_date AND :p_to_date ORDER BY effective_date, je_line_num;

Reports frequently filter on STATUS to isolate unreconciled lines and join CODE_COMBINATION_ID to GL code combinations for account analysis. Because the view applies Cash Management security profiles, results are automatically restricted to the bank accounts the querying user is authorized to see, making it suitable for both inquiry and downstream integration use.