Results for “cebv_bank_statement_lines”

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

Overview

CEBV_BANK_STATEMENT_LINES is a business view owned by the APPS schema within the Cash Management (CE) module of Oracle E-Business Suite. It presents a denormalized, read-only representation of bank statement line data by joining the core statement line table to several lookup and reference tables. Because statement records in the base tables store transaction types, reconciliation statuses, and currency conversion types as coded values, the view resolves these codes into human-readable meanings and exposes them alongside descriptive attributes such as bank transaction numbers, remittance text, and statement header context. This makes the view particularly well suited to reporting, ad hoc queries, and downstream integration where a flat, interpretable result set is preferred over querying the transactional tables directly. The view is defined WITH READ ONLY, so it is intended strictly for query access and cannot be used as a DML target.

Underlying Base Objects

The view is defined over five referenced base objects as documented in the ETRM metadata: CE_STATEMENT_LINES (SYNONYM), CE_STATEMENT_HEADERS (SYNONYM), CE_TRANSACTION_CODES (SYNONYM), CE_LOOKUPS (VIEW), and GL_DAILY_CONVERSION_TYPES (SYNONYM). CE_STATEMENT_LINES is the driving table, supplying the individual statement line records. It is joined to CE_STATEMENT_HEADERS on STATEMENT_HEADER_ID to bring in statement-level information. CE_TRANSACTION_CODES is an outer-joined source of transaction code definitions, with an additional join condition confirming the bank account against the header. CE_LOOKUPS is referenced twice — once for the BANK_TRX_TYPE lookup to resolve transaction types, and once for the STATEMENT_LINE_STATUS lookup to resolve reconciliation statuses. GL_DAILY_CONVERSION_TYPES is outer-joined to translate the exchange rate type into a conversion type name.

Key Columns

• STATEMENT_LINE_ID / LINE_NUMBER — Primary identifier and sequence position of the line within its statement.
• TRANSACTION_DATE / EFFECTIVE_DATE — The transaction date and the effective date carried on the statement line.
• TRANSACTION_TYPE — Derived from the BANK_TRX_TYPE lookup; the descriptive meaning of the line's transaction type.
• TRANSACTION_CODE — The transaction code value from CE_TRANSACTION_CODES.
• AMOUNT / TRANSACTION_AMOUNT — The line amount and its original/transaction amount equivalent.
• RECONCILIATION_STATUS — Derived from the STATEMENT_LINE_STATUS lookup; indicates whether the line is reconciled, unreconciled, or in another state.
• CURRENCY_CODE, EXCHANGE_RATE, EXCHANGE_RATE_TYPE, EXCHANGE_DATE — Currency and conversion attributes, with the rate type resolved via GL_DAILY_CONVERSION_TYPES.
• STATEMENT_NUMBER / STATEMENT_DATE / STATEMENT_ID — Header-level context identifying the parent statement.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE for traceability.

Common Use Cases and Queries

Typical uses include bank reconciliation reporting, statement line extracts, and integration feeds that require readable transaction and status descriptions. A basic query follows.

• Statement line listing: SELECT statement_number, line_number, transaction_date, transaction_type, amount, reconciliation_status FROM ce bv_bank_statement_lines WHERE statement_number = :p_number ORDER BY line_number;
• Unreconciled items: SELECT * FROM cebv_bank_statement_lines WHERE reconciliation_status = 'Unreconciled';
• Currency exposure: SELECT currency_code, exchange_rate_type, SUM(amount) FROM cebv_bank_statement_lines GROUP BY currency_code, exchange_rate_type;

Because the view already resolves code meanings, it reduces the join complexity required in custom reports and is a convenient starting point for analysis of bank statement activity.