Results for “statement_number”

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

Overview

CE_STATEMENT_BANKS_V is a Cash Management (CE) reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its purpose is narrow and precise: it presents a unified list of bank statement numbers paired with the bank account number to which each statement belongs. The view accomplishes this by unioning two distinct sources of statement data — external statements staged in the open interface table CE_STATEMENT_HEADERS_INT, and reconciled statements already resident in the CE_STATEMENT_HEADERS base table. Because the CE_STATEMENT_HEADERS_INT staging table stores a bank account number directly, while CE_STATEMENT_HEADERS stores only a BANK_ACCOUNT_ID foreign key, the view resolves the latter by joining to CE_BANK_ACCOUNTS. This makes the view a convenient reconciliation-ready bridge between two storage models and a stable, low-cost source for lookups, LOVs, and lightweight reporting on statement-to-account relationships.

Underlying Base Objects

The view is defined over three documented base objects, all referenced through APPS synonyms:

• CE_STATEMENT_HEADERS_INT — the bank statement open interface (staging) table. The union's first branch selects STATEMENT_NUMBER and BANK_ACCOUNT_NUM directly from this table, so staged, not-yet-imported statements appear here with the account number supplied by the external source.
• CE_STATEMENT_HEADERS — the permanent bank statement header table holding imported statements. It provides STATEMENT_NUMBER and BANK_ACCOUNT_ID.
• CE_BANK_ACCOUNTS — the bank account definition table, joined to CE_STATEMENT_HEADERS on BANK_ACCOUNT_ID to retrieve BANK_ACCOUNT_NUM for the reconciled branch.

Both branches are combined with UNION (not UNION ALL), so duplicate statement-number/account-number combinations appearing in both the interface and the permanent table collapse into a single row.

Key Columns

• STATEMENT_NUMBER — the bank statement identifier, sourced from CE_STATEMENT_HEADERS_INT.STATEMENT_NUMBER in the first branch and CE_STATEMENT_HEADERS.STATEMENT_NUMBER in the second.
• BANK_ACCOUNT_NUM — the user-visible bank account number. In the interface branch it is taken directly from CE_STATEMENT_HEADERS_INT; in the header branch it is derived via CE_BANK_ACCOUNTS.BANK_ACCOUNT_NUM through the BANK_ACCOUNT_ID join. This is the column surfaced when users search on "bank_account_num".

No other columns are exposed; the view is deliberately minimal.

Common Use Cases and Queries

The view is typically used to locate the account associated with a statement, to confirm that a staged statement has loaded, or as an LOV source. Representative queries:

• Find the account for a given statement: SELECT bank_account_num FROM ce_statement_banks_v WHERE statement_number = :stmt;
• List all statements for an account: SELECT statement_number FROM ce_statement_banks_v WHERE bank_account_num = :acct;
• Validate load status by comparing the interface and headers population: SELECT statement_number, bank_account_num FROM ce_statement_banks_v ORDER BY bank_account_num, statement_number;
• Feed downstream reconciliations or custom reports needing a simple statement-to-account map, joined back to CE_STATEMENT_HEADERS on STATEMENT_NUMBER where additional header detail is required.

Because it is a simple two-branch union with no aggregation, the view performs efficiently and is safe for ad hoc querying, though result sets depend on statement data being present in either the interface or the permanent header table.