Search Results ce_cp_disc_trx_v




Overview
Explore in AI Chat

Overview

CE_CP_DISC_TRX_V is a Cash Management (CE) reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It functions as the Cash Positioning Discoverer View for All Transaction Sources, consolidating bank account transaction activity from multiple cash positioning sub-views into a single, horizontally unified result set. The view is designed primarily to support Oracle Discoverer-based cash positioning worksheets, allowing treasury users and reporting analysts to query all transaction source types through one object rather than joining the individual source-specific views.

The view is implemented as a UNION ALL of eight subordinate extraction views (ARR, APP, XTI, XTO, PAY, CEI, CEO) plus a direct selection from CE_CP_WORKSHEET_LINES for user-defined inflow and outflow transactions (UDI and UDO). A final NOT EXISTS predicate removes transactions recorded in CE_CP_TRX_EXCLUDED for the current system date, preventing excluded items from inflating reported cash positions. The object is marked VALID and is referenced in ETRM 12.2.2 documentation.

Underlying Base Objects

The view is defined over the following documented objects:

Supporting packages include FND_GLOBAL, FND_PROFILE, FND_ACCESS_CONTROL_UTIL, MO_GLOBAL, XTR_USER_ACCESS, and ARP_CASHBOOK, which supply security context, org access, and profile option resolution used indirectly by the underlying extraction views.

Key Columns

  • WORKSHEET_HEADER_ID — Identifies the cash positioning worksheet header to which the line belongs.
  • BANK_ACCOUNT_ID — The internal bank account identifier associated with the transaction.
  • WORKSHEET_LINE_ID — The unique line identifier within the worksheet; also used as REFERENCE_ID for UDI/UDO rows and for exclusion matching.
  • TRX_DESC / DESCRIPTION — Descriptive text for the transaction; the outer query aliases DESCRIPTION to TRX_DESC.
  • SOURCE_TYPE — Literal discriminant ('ARR', 'APP', 'XTI', 'XTO', 'PAY', 'CEI', 'CEO', 'UDI', 'UDO') identifying the originating transaction stream.
  • DETAIL — Additional qualifying detail for each line.
  • BALANCE — Signed monetary amount; for UDO rows the sign is inverted via DECODE(SOURCE_TYPE,'UDO',-AMOUNT,AMOUNT).

Common Use Cases and Queries

The most frequent use is driving a Discoverer workbook or ad hoc query to present a complete reconciled cash position for a bank account. A typical listing filtered by bank account and worksheet header resembles:

  • SELECT worksheet_header_id, bank_account_id, worksheet_line_id, trx_desc, source_type, detail, balance FROM apps.ce_cp_disc_trx_v WHERE bank_account_id = :p_bank_account_id AND worksheet_header_id = :p_header_id ORDER BY source_type, worksheet_line_id;

Analysts also aggregate balances by source type to reconcile the worksheet total against underlying subledger activity:

  • SELECT source_type, SUM(balance) FROM apps.ce_cp_disc_trx_v WHERE worksheet_header_id = :p_header_id GROUP BY source_type;

A third pattern isolates user-defined entries, using the WORKSHEET_LINE_ID column as REFERENCE_ID, by querying with SOURCE_TYPE IN ('UDI','UDO'). Because the view filters CE_CP_TRX_EXCLUDED for SYSDATE, results reflect only transactions not manually excluded as of the current date, which is essential for accurate intraday cash positioning reports.