Results for “ce_statement_numbers_v”

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

Overview

The APPS.CE_STATEMENT_NUMBERS_V view is a lightweight reference object within the Oracle Cash Management (CE) module. Its sole function is to expose the distinct set of bank statement numbers known to the application, drawn from both the permanent statement header table and the open interface table used during statement import. Unlike most Cash Management views that return transaction or balance detail, this view is deliberately narrow: it returns a single column, STATEMENT_NUMBER, and is intended to support validation, lookup, and list-of-values style requirements.

Because the view returns a de-duplicated union of statement identifiers, it provides a consolidated catalogue of every statement number that exists either as a completed, stored statement or as a pending record staged for import. This makes it useful wherever an administrator, concurrent program, or integration component needs to confirm the range of valid statement numbers without querying the two source tables independently. In the EBS 12.1.1 and 12.2.2 releases, the object is owned by the APPS schema, has a VALID status, and is defined strictly as a view rather than a materialized object, so it always reflects the current contents of its base tables.

Underlying Base Objects

The view is defined over two synonyms: CE_STATEMENT_HEADERS and CE_STATEMENT_HEADERS_INT. CE_STATEMENT_HEADERS is the primary transactional table that stores fully loaded bank statements, including their headers, balances, and associated lines. CE_STATEMENT_HEADERS_INT is the Cash Management statement interface table, which holds statement header records staged by the Bank Statement Import process before validation and transfer into the permanent tables.

The view text is a simple UNION (not UNION ALL) of the STATEMENT_NUMBER column from each source. The UNION operator removes duplicate statement numbers, so any number that appears simultaneously in the interface table and the permanent table is listed only once. No filtering, join conditions, or additional predicates are applied. As a result, the view inherits the access and volume characteristics of both underlying objects and depends on the caller's privileges on the two CE tables.

Key Columns

The view exposes a single column:

• STATEMENT_NUMBER — the bank statement identifier. It carries the same meaning as the corresponding columns in CE_STATEMENT_HEADERS and CE_STATEMENT_HEADERS_INT, and it is the field most commonly used to reference a statement during reconciliation, inquiry, or import troubleshooting.

Because no other columns are projected, the view cannot be used to determine whether a given number resides in the permanent table or the interface table, nor to retrieve statement dates, bank account information, or status. Callers requiring that context must query the base tables directly.

Common Use Cases and Queries

Typical scenarios include validating user-entered statement numbers, populating selection lists, and reconciling the interface and permanent stores during import.

Listing all known statement numbers:

• SELECT statement_number FROM ce_statement_numbers_v ORDER BY statement_number;

Checking whether a specific statement number exists:

• SELECT statement_number FROM ce_statement_numbers_v WHERE statement_number = :p_statement_number;

Counting the distinct statements visible across both sources:

• SELECT COUNT(*) FROM ce_statement_numbers_v;

Identifying numbers staged in the interface but not yet transferred to the permanent table requires a direct comparison with the base tables, since the view itself does not disclose origin. In all cases the view is read-only and requires no special initialization; it can be used safely in reports, validation logic, and PL/SQL that must confirm the existence of a statement number across the Cash Management statement lifecycle.