Search Results ce_cp_disc_prior_v




Overview
Explore in AI Chat

Overview

CE_CP_DISC_PRIOR_V is an APPS-owned database view in the Oracle E-Business Suite Cash Management (CE) module, classified as VALID in both release 12.1.1 and 12.2.2. Its documented purpose is to serve as the Cash Positioning Discoverer View for Prior-day Balances. It is one of the standard building blocks behind the Cash Positioning workbook in Oracle Discoverer, supplying the opening or prior-day balance figures that are consolidated into a cash position worksheet for a given bank account.

The view does not store data. It is a read-only aggregation over open-balance, payments, receipts, and payroll cash-flow views, and it is intended to be consumed by Discoverer end-user layers rather than by transactional forms. Its presence in the ETRM directory reflects its role as a documented, supported reporting interface for cash positioning analytics.

Underlying Base Objects

Per the documented view metadata, CE_CP_DISC_PRIOR_V is defined over the following objects: ARP_CASHBOOK (package), CE_AP_FC_PAYMENTS_V (view), CE_AR_FC_RECEIPTS_V (view), CE_CP_OPEN_BAL_V (view), CE_CP_WORKSHEET_HEADERS (synonym), CE_CP_WORKSHEET_LINES (synonym), CE_PAY_FC_PAYROLL_V (view), CE_XTR_CASHFLOWS_V (view), and FND_GLOBAL (package).

The published view text shows a UNION ALL of three aggregation branches. Each branch joins CE_CP_WORKSHEET_HEADERS to CE_CP_OPEN_BAL_V and pairs the open balance with one cash-flow source: payables payments (CE_AP_FC_PAYMENTS_V), receivables receipts (CE_AR_FC_RECEIPTS_V, pre-aggregated by bank account, cash activity date, and currency), and payroll payments (CE_PAY_FC_PAYROLL_V). Currency handling is performed with DECODE against the open-balance currency, converting foreign-currency amounts to the base amount where currencies differ. Date predicates restrict rows to the period between the prior statement date and the current statement date, narrowing the dataset to prior-day activity.

FND_GLOBAL supplies the runtime environment, notably the operating unit and user context used to secure the cash positioning worksheet data, while ARP_CASHBOOK provides cashbook attributes referenced through the underlying open-balance view.

Key Columns

  • WORKSHEET_HEADER_ID — Identifier of the Cash Positioning worksheet header (from CE_CP_WORKSHEET_HEADERS). It links the aggregated amount to a specific worksheet, and therefore to an operating unit and bank account context. Each UNION ALL branch selects this column.
  • BANK_ACCOUNT_ID — The internal identifier of the bank account (from CE_CP_OPEN_BAL_V). This is the principal join and grouping key across all three branches and defines the account whose prior-day position is being reported.
  • AMOUNT — The summed prior-day amount. This is computed, not stored: it is the SUM over each branch of either the transaction currency amount (when the cash-flow currency matches the open-balance currency) or the base amount (when it does not). The outer SELECT re-aggregates with SUM(AMOUNT) grouped by WORKSHEET_HEADER_ID and BANK_ACCOUNT_ID, so the reported value is the net prior-day movement for that worksheet and account.

Common Use Cases and Queries

The primary scenario is replicating the prior-day balance column of the Cash Positioning workbook, either inside Discoverer or via custom SQL when a Discoverer environment is not available. A typical query is:

  • SELECT worksheet_header_id, bank_account_id, SUM(amount) FROM ce_cp_disc_prior_v WHERE worksheet_header_id = :p_worksheet_id GROUP BY worksheet_header_id, bank_account_id;

Because the view already aggregates to worksheet and bank account, callers should apply their own GROUP BY if they intend to combine rows rather than rely on the view's internal grouping. Other practical uses include reconciling prior-day calculated balances against bank statement opening balances, feeding an external treasury or cash-concentration model, and validating that payments, receipts, and payroll cash flows captured through CE_CP_OPEN_BAL_V net to the expected position at the start of the current day. As the view references FND_GLOBAL-based context, results are ordinarily scoped by operating unit through the worksheet header, and it should be treated as an APPS-owned reporting object that is queried, not modified.