Results for “document_sequence_number”

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

Overview

CEFV_BANK_STATEMENTS is a Business View owned by the APPS schema within the Cash Management (CE) module of Oracle E-Business Suite, and it is documented as VALID in both the 12.1.1 and 12.2.2 releases. It exposes a denormalized, read-only projection of bank statement header information joined to bank account and organization attributes, presenting cash managers and reporting tools with a flattened record set describing each imported or manually entered bank statement.

The view is defined with a WITH READ ONLY clause, confirming it is intended strictly for query and reporting consumption rather than transactional update. Because it exposes a stable column list over the underlying Cash Management statement header structures, it serves as a convenient integration point for custom reports, extracts, Oracle Business Intelligence datasets, and downstream reconciliation utilities that need statement-level balances and counts without reconstructing joins themselves.

Underlying Base Objects

The view text selects from three base tables, all accessed through APPS synonyms in the ETRM metadata: CE_STATEMENT_HEADERS, aliased SH; CE_BANK_ACCOUNTS, aliased BA; and HR_ALL_ORGANIZATION_UNITS, aliased OG. The header table is the driving table, joined to bank accounts on BANK_ACCOUNT_ID and to organization units through an outer join on ORG_ID (OG.ORGANIZATION_ID(+) = SH.ORG_ID). The outer join preserves statements whose organization identifier does not resolve to a valid organization unit record.

The commented-out fragments referencing CE_BANK_ACCT_BALANCES show that an earlier revision of the view joined statement headers to bank account balance rows by BANK_ACCOUNT_ID and STATEMENT_DATE. That join is disabled in the current definition, so the visible view does not return balance table data; any reliance on balance columns must be sourced separately.

Key Columns

• STATEMENT_ID — maps to STATEMENT_HEADER_ID, the primary identifier of the statement header record.
• BANK_ACCOUNT_NUMBER, BANK_ACCOUNT_NAME, BANK_ACCOUNT_ID — identify the bank account the statement belongs to.
• STATEMENT_NUMBER and STATEMENT_DATE — the statement reference and its statement date.
• BEGINNING_BALANCE, ENDING_BALANCE, DEBIT_TOTAL, CREDIT_TOTAL — control balances and control totals recorded on the header.
• DEBIT_LINE_COUNT, CREDIT_LINE_COUNT — control counts of debit and credit lines expected on the statement.
• CURRENCY_CODE — the statement currency taken from the bank account.
• COMPLETION_STATUS — the STATEMENT_COMPLETE_FLAG indicating whether statement entry is complete.
• DOCUMENT_SEQUENCE_NUMBER — the document sequence value assigned to the statement.
• ORG_NAME and ORG_ID — the operating unit name and identifier associated with the statement.
• CREATED_DATE, CREATED_BY, LAST_UPDATED_DATE, LAST_UPDATED_BY — standard audit columns.
• CHECK_DIGITS — the bank account check digit component.

Common Use Cases and Queries

Typical scenarios include verifying that statement control totals agree with their line counts, listing incomplete statements for follow-up entry, and exporting statement headers for a given operating unit. A representative query follows.

SELECT statement_id, bank_account_number, statement_number, statement_date,
beginning_balance, debit_total, credit_total, ending_balance,
debit_line_count, credit_line_count, completion_status
FROM apps.cefv_bank_statements
WHERE org_id = :p_org_id
AND statement_date BETWEEN :p_from_date AND :p_to_date;

Reports can also filter on completion_status to isolate statements requiring reconciliation, or aggregate debit_line_count and credit_line_count by bank_account_id to assess statement activity volume.