Search Results document_sequence_number

Overview

The CEBV_BANK_STATEMENTS view is a Cash Management (CE) business view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents bank statement header information in a denormalized, reporting-friendly format. The view abstracts the underlying statement header table and exposes descriptive aliases for columns that end users and integrators rely on when building inquiries, reports, and interfaces. Because it is defined with a WITH READ ONLY clause, the view is intended strictly for query and reporting purposes and cannot be used to insert, update, or delete statement records directly.

The view carries the "_BV" suffix in its name, which is a conventional Oracle EBS naming pattern indicating a "business view." Such views are commonly referenced by Oracle Reports, Oracle Discoverer workbooks, XML Publisher templates, and custom SQL that needs a stable, human-readable projection of cash management data.

Underlying Base Objects

Per the ETRM metadata, CEBV_BANK_STATEMENTS is defined over a single referenced base object: the CE_STATEMENT_HEADERS table (accessed through its APPS synonym). The view text selects statement header columns and maps several of them to friendlier column aliases. There is a commented-out join to CE_BANK_ACCT_BALANCES in the view definition, but it is disabled, meaning the balances relationship is not active in the delivered view. The definition also includes a security predicate, '_SEC:SH.ORG_ID' IS NOT NULL, which enforces organizational (multi-org) security filtering based on ORG_ID. The trailing WITH READ ONLY clause confirms the view is query-only.

Key Columns

The view exposes the following columns, which map back to CE_STATEMENT_HEADERS attributes:

• STATEMENT_ID — Surrogate identifier derived from STATEMENT_HEADER_ID, uniquely identifying each statement header.
• STATEMENT_NUMBER — The bank-assigned or system statement number.
• STATEMENT_DATE — The effective date of the statement.
• BEGINNING_BALANCE / ENDING_BALANCE — Control opening and closing balances (from CONTROL_BEGIN_BALANCE and CONTROL_END_BALANCE).
• DEBIT_TOTAL / CREDIT_TOTAL — Control totals for debits and credits (CONTROL_TOTAL_DR / CONTROL_TOTAL_CR).
• DEBIT_LINE_COUNT / CREDIT_LINE_COUNT — Control counts of debit and credit lines.
• CURRENCY_CODE — Currency of the statement.
• COMPLETION_STATUS — The statement complete flag (STATEMENT_COMPLETE_FLAG).
• DOCUMENT_SEQUENCE_NUMBER — The document sequence value (DOC_SEQUENCE_VALUE), relevant to sequence auditing for the user searching "document_sequence_number."
• BANK_ACCOUNT_ID and ORG_ID — The owning bank account and operating unit.
• CREATED_DATE, CREATED_BY, LAST_UPDATED_DATE, LAST_UPDATED_BY — Standard audit columns.
• CHECK_DIGITS — Bank account check digits for validation.

Common Use Cases and Queries

Typical use cases include reconciling statement control totals against transaction lines, reporting on statement completion status, and validating document sequencing. A representative query targeting the searched term follows:

SELECT statement_number, statement_date, document_sequence_number, currency_code, completion_status
FROM apps.cebv_bank_statements
WHERE org_id = :p_org_id
ORDER BY statement_date DESC;

Because the view honors ORG_ID security, callers operating in a multi-org context must supply or inherit a valid operating unit. The view is read-only, so any adjustment to statement data must be performed against the base CE_STATEMENT_HEADERS table through the standard Cash Management application flows rather than through this business view.