Search Results ce_statement_headers_interface

Overview

The CE_STATEMENT_HEADERS_INTERFACE view is a security-enabled, organization-scoped reporting view within the Oracle Cash Management (CE) module of Oracle E-Business Suite. It exposes bank statement header data that resides in the interface and open-interface tables used by the Bank Statement Integration and Bank Statement Open Interface processes. Its principal role is to provide a controlled read interface over statement header records that have been loaded — or are pending load — into Cash Management, allowing concurrent programs, reconciliation logic, and custom reports to retrieve header-level information without accessing the underlying interface table directly.

The view is defined as a filtered projection of CE_STATEMENT_HEADERS_INT_ALL. Rather than presenting every row, it applies an ORG_ID predicate derived from the session's CLIENT_INFO value, effectively restricting the result set to the operating unit (organization) associated with the current session. The view is documented as not implemented in the source database at the time the metadata was captured, meaning the view text is supplied by ETRM for reference but the database object itself may not be deployed in every instance. This is significant for developers, because a query against the view will fail if the object has not been created.

Underlying Base Objects

The documented definition references a single base object: CE_STATEMENT_HEADERS_INT_ALL, the all-organizations interface table for bank statement headers. No other base objects are documented. The relationship is a direct column-by-column projection, with the interface table supplying all of the exposed columns. The only transformation applied is the organization filter in the WHERE clause, which resolves the current organization identifier from the USERENV('CLIENT_INFO') session setting and compares it against the ORG_ID column using NVL normalization so that null organization values are treated uniformly. Because CE_STATEMENT_HEADERS_INT_ALL is an _ALL table, it is multi-organization aware; the view therefore acts as the organization-specific slice of that table.

Key Columns

• STATEMENT_NUMBER, BANK_ACCOUNT_NUM, STATEMENT_DATE — Statement identity and the bank account it belongs to, plus the statement date used for reconciliation grouping.
• BANK_NAME, BANK_BRANCH_NAME — Descriptive bank and branch information carried from the source statement load.
• CONTROL_BEGIN_BALANCE, CONTROL_END_BALANCE, CONTROL_TOTAL_DR, CONTROL_TOTAL_CR — Control totals used to validate that the sum of statement lines reconciles to the header.
• CONTROL_DR_LINE_COUNT, CONTROL_CR_LINE_COUNT, CONTROL_LINE_COUNT — Expected line counts for debit, credit, and total lines, supporting completeness and integrity checks during import.
• RECORD_STATUS_FLAG — Indicates the processing state of the header record within the interface.
• CURRENCY_CODE — Statement currency.
• ORG_ID — Operating unit owning the statement; central to the view's security predicate.
• CHECK_DIGITS, CASHFLOW_BALANCE, INT_CALC_BALANCE — Bank account validation and interest/cashflow calculation attributes.
• INTRA_DAY_FLAG, ONE_DAY_FLOAT, TWO_DAY_FLOAT — Intra-day statement indicator and float amounts.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE15 — Descriptive flexfield segments.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — Standard audit columns.

Common Use Cases and Queries

Typical uses include diagnosing bank statement import loads, validating control totals before reconciliation, and building custom reconciliation dashboards. The following query lists pending statement headers for the session's organization:

SELECT statement_number, bank_account_num, statement_date, currency_code, control_begin_balance, control_end_balance, record_status_flag
FROM ce_statement_headers_interface
WHERE statement_date >= SYSDATE - 30
ORDER BY statement_date DESC;

To compare control line counts against actual loaded detail lines, developers join the view to the corresponding line interface view on statement number and bank account. Because the view enforces the ORG_ID predicate automatically, callers must ensure CLIENT_INFO is initialized (as it is within Oracle Applications concurrent managers and forms sessions). Where the view is not deployed, the equivalent query should target CE_STATEMENT_HEADERS_INT_ALL directly with an explicit ORG_ID restriction.