Results for “next_stmt_date”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

CE_CP_OPEN_BAL_V is a Cash Management (CE) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. As documented in the ETRM metadata, the view presents the opening balances for bank accounts. It consolidates balance snapshots captured at the bank account level and exposes them alongside a derived prior-balance-date indicator, allowing report developers and integrators to identify the transaction that preceded a given balance record for each account. The view is classified as VALID and is registered as a standard APPS-owned object, making it available for customer-built reports, Cash Management reconciliation queries, and downstream integration extracts without requiring custom schema access.

Underlying Base Objects

The view text is a UNION of two nearly identical SELECT statements, both joining the balance table to a bank account source:

• CE_BANK_ACCT_BALANCES (SYNONYM) — the primary fact source, holding dated balance rows per bank account.
• CE_BANK_ACCTS_GT_V (VIEW) — a global temporary bank account view joined in the first branch of the UNION.
• CE_BANK_ACCOUNTS (SYNONYM) — the internal bank account table, joined in the second branch with the predicate ACCOUNT_CLASSIFICATION = 'SUBSIDIARY'.

Both branches join on BAL.BANK_ACCOUNT_ID = CBA.BANK_ACCOUNT_ID and both compute a trailing LAG window expression over BAL.BALANCE_DATE DESC partitioned by BANK_ACCOUNT_ID, defaulting to SYSDATE+10000 when no prior row exists. The UNION structure effectively covers accounts available through the temporary/global view as well as subsidiary-classified internal accounts, giving a single access point for opening balance data across account classifications.

Key Columns

The documented column set exposed by the view includes:

• BANK_ACCOUNT_ID — identifier of the bank account; the partition key for balance history.
• CURRENCY_CODE — currency of the account, sourced from the joined bank account record.
• STATEMENT_DATE — the balance date carried from CE_BANK_ACCT_BALANCES (aliased as BALANCE_DATE in the view text).
• NEXT_STMT_DATE — the derived prior balance date produced by the LAG expression; used to bound an opening-to-closing balance interval.
• LEDGER_BALANCE — the accounting ledger balance for the account on that date.
• CASHFLOW_BALANCE / AVAILABLE_BALANCE — the available balance used in cash positioning and cashflow reporting.
• INT_CALC_BALANCE / VALUE_DATED_BALANCE — the value-dated balance used in interest and float calculations.
• ONE_DAY_FLOAT and TWO_DAY_FLOAT — float amounts representing funds not yet cleared at one and two day horizons.

Common Use Cases and Queries

Typical scenarios include opening balance determination for bank reconciliation, cash positioning reports, and float analysis. To retrieve the opening balance for a specific account and date:

• SELECT bank_account_id, statement_date, ledger_balance, available_balance FROM ce_cp_open_bal_v WHERE bank_account_id = :p_account AND statement_date = :p_date;
• To reconstruct balance intervals per account, order by statement_date and use next_stmt_date as the closing bound of the prior window.
• To aggregate float exposure, sum one_day_float and two_day_float grouped by currency_code and statement_date.

Because the view performs the LAG computation internally, callers avoid duplicating analytic logic and obtain consistent interval boundaries. Queries should filter by bank_account_id and date range to limit the volume of balance rows scanned from CE_BANK_ACCT_BALANCES.