Search Results ce_cp_disc_open_v




Overview
Explore in AI Chat

Overview

CE_CP_DISC_OPEN_V is an APPS-owned view within the Oracle E-Business Suite Cash Management (CE) product. It is documented as the "Cash Positioning Discoverer View for Opening Balances," indicating that its principal purpose is to expose the opening balance position of a bank account for a given cash positioning worksheet, formatted for consumption by Oracle Discoverer reports. The view is marked VALID in both the 12.1.1 and 12.2.2 releases, and it belongs to the standard reporting layer that supports the Cash Positioning and Forecasting functionality of Cash Management.

The view consolidates two related data sources: the worksheet-to-bank-account association and the opening balance detail. It computes a single BALANCE measure by selecting an opening balance component based on the worksheet's balance type and then adjusting it by a float component determined by the worksheet's float type. In this way it presents, for each worksheet header and bank account combination, an opening balance figure that reflects the tolerance and float conventions configured on the worksheet. Because it is a Discoverer-facing view rather than a base transactional view, it is intended for read-only reporting and analytical queries rather than for data maintenance.

Underlying Base Objects

The documented base objects referenced by CE_CP_DISC_OPEN_V are two views and several packages. The primary data sources are CE_CP_WS_BA_DISC_V (the worksheet/bank-account Discoverer view) and CE_CP_OPEN_BAL_V (the opening balance view). The join between them is an outer join on BANK_ACCOUNT_ID, with additional outer-join predicates restricting the opening balance rows to those whose STATEMENT_DATE is before the current system date and whose NEXT_STMT_DATE is on or after the current system date. This date window selects the statement period that is currently open as of SYSDATE.

The remaining referenced objects—FND_ACCESS_CONTROL_UTIL, FND_GLOBAL, FND_PROFILE, MO_GLOBAL, and XTR_USER_ACCESS—are standard EBS security, profile, and multi-org utility packages. Their presence indicates that the underlying views apply access control and profile-based filtering, typically to restrict the rows returned to the bank accounts and operating units the querying user is authorized to see. This is consistent with the security model applied throughout Cash Management reporting views.

Key Columns

  • WORKSHEET_HEADER_ID — Identifier of the cash positioning worksheet header to which the bank account and balance belong. This links the row to the worksheet definition.
  • BANK_ACCOUNT_ID — Identifier of the bank account for which the opening balance is reported. It is the join key between the worksheet/bank-account view and the opening balance view.
  • BALANCE — The computed opening balance. It is derived by selecting, from the opening balance source, the internal calculated balance, cashflow balance, or ledger balance according to the worksheet's BALANCE_TYPE, then adding or subtracting float amounts based on the worksheet's FLOAT_TYPE (for example, one-day or two-day float additions or subtractions). Where no matching opening balance row exists, the components default to zero through NVL.

Common Use Cases and Queries

The view supports cash positioning and cash forecasting reports where an opening balance is required as the starting point for a worksheet. Typical consumers are Discoverer workbooks and custom operational reports that reconcile opening, activity, and closing balances per bank account. Administrators may also query it directly to verify that opening balances are being resolved correctly for a given worksheet.

A representative query retrieves the opening balance for a specific worksheet header:

  • SELECT worksheet_header_id, bank_account_id, balance FROM apps.ce_cp_disc_open_v WHERE worksheet_header_id = :p_worksheet_id;

To obtain opening balances across all accounts visible to the user for current worksheets, a report may simply aggregate the measure:

  • SELECT bank_account_id, SUM(balance) open_balance FROM apps.ce_cp_disc_open_v GROUP BY bank_account_id;

Because access control packages participate in the underlying views, results are automatically limited to the bank accounts the user is permitted to access. Queries should therefore be run as an application user with the appropriate Cash Management responsibilities rather than as a privileged database account, so that the security predicates are applied as designed.