Search Results next_stmt_date




Overview

The view APPS.CE_CP_OPEN_BAL_V is a cash management reporting object that exposes opening bank statement balances and associated float amounts for bank accounts. "CP" denotes the Cash Positioning modules in Oracle Cash Management, and the view name indicates that it presents the opening balance position of each bank account as of a given statement date. It is owned by the APPS schema and is registered in FND Design Data as CE.CE_CP_OPEN_BAL_V.

The view is classified as an Oracle Internal Use Only object. Oracle Corporation does not support direct access to its data except from standard Oracle Applications programs. It exists primarily to service the Cash Positioning, cash forecasting, and bank reconciliation processes rather than to be queried directly by end users. The NEXT_STMT_DATE column, which users frequently identify when searching for this object, is the field used by these processes to classify a balance snapshot according to the subsequent statement date and to reason about balances that pertain to the following statement cycle.

Underlying Base Objects

The view is defined over three documented objects in the APPS schema. CE_BANK_ACCOUNTS (a synonym) supplies the bank account master data, including the account identifier and currency. CE_BANK_ACCT_BALANCES (a synonym) supplies the actual statement balance records, including ledger, cashflow, interest-calculated, and float balances. CE_BANK_ACCTS_GT_V (a view) is a global temporary–style view that participates in the join, typically representing the effective/current set of bank accounts for the balancing context of the query.

The view is itself a dependency for several other objects, confirming its role as a low-level building block: CE_CP_DISC_OPEN_V, CE_CP_DISC_OVERDUE_V, CE_CP_DISC_PRIOR_V, CE_CP_PRIORDAY, and CE_CSH_FCST_POP. This dependency chain shows that CE_CP_OPEN_BAL_V feeds the Cash Positioning prior-day and open-balance logic, cash forecasting population, and related reporting views.

Key Columns

  • BANK_ACCOUNT_ID (NUMBER(15)) — identifies the bank account to which the balance row belongs.
  • CURRENCY_CODE (VARCHAR2(15)) — the currency of the bank account and its balances.
  • STATEMENT_DATE (DATE) — the bank statement date for the balance snapshot.
  • NEXT_STMT_DATE (DATE) — the next bank statement date associated with the balance record.
  • LEDGER_BALANCE (NUMBER) — the bank statement ledger balance.
  • CASHFLOW_BALANCE (NUMBER) — the bank statement cashflow balance.
  • INT_CALC_BALANCE (NUMBER) — the bank statement interest calculated balance.
  • ONE_DAY_FLOAT (NUMBER) — the one-day float balance.
  • TWO_DAY_FLOAT (NUMBER) — the two-day float balance.

Common Use Cases and Queries

The view supports cash positioning prior-day logic, cash forecasting population, and internal reconciliation reporting. A direct query such as the following retrieves all columns, and is typical when diagnosing float or open-balance discrepancies for a specific account or statement date:

SELECT BANK_ACCOUNT_ID, CURRENCY_CODE, STATEMENT_DATE, NEXT_STMT_DATE, LEDGER_BALANCE, CASHFLOW_BALANCE, INT_CALC_BALANCE, ONE_DAY_FLOAT, TWO_DAY_FLOAT FROM APPS.CE_CP_OPEN_BAL_V WHERE NEXT_STMT_DATE = :p_stmt_date;

Because the object carries the Oracle Internal Use Only warning, practical deployment should avoid building custom integrations directly on it. Where its data is required, the supported approach is to rely on the standard Cash Management programs and the dependent views and concurrent processes that Oracle already maintains against this object. Users searching for NEXT_STMT_DATE should understand that this column is the linkage between an opening balance row and the subsequent statement cycle, and is most meaningfully interpreted within those supported Cash Management flows.