Results for “ce_stat_lines_inf_v”

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

Overview

CE_STAT_LINES_INF_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Cash Management (CE) product family and is documented in the ETRM repository with the terse description "Retrofitted," indicating that the object was carried forward from an earlier release lineage rather than newly designed for the R12 architecture. Functionally, the view exposes the row-level content of the bank statement lines interface table, CE_STATEMENT_LINES_INTERFACE, in a denormalized, read-oriented form that downstream processes, concurrent programs, and custom extensions can query without referencing the base table directly. It is the canonical surface through which statement line data passes on its way into the Cash Management statement reconciliation workflow. Because the statement lines interface holds the staging records produced by bank statement loaders and statement file parsers, this view effectively represents the inbound side of bank statement processing, including transaction amounts, charge amounts, currency and exchange rate information, and the descriptive flexfield attribute columns.

Underlying Base Objects

The view is defined over a single base object, documented in the ETRM metadata as the synonym CE_STATEMENT_LINES_INTERFACE, which resolves to the underlying Cash Management interface table in the APPS schema. The projection is a straightforward SELECT of the table's columns, with one notable transformation: the view substitutes SLI.ROWID as a column aliased ROW_ID in place of the table's native primary key or surrogate identifier. This use of ROWID is characteristic of interface-style views and reflects the transient nature of the staging table, where rows are inserted, validated, and purged rather than retained as durable business records. No joins, unions, or aggregations are present in the view text. Consequently, the view carries no independent data of its own and inherits entirely the transactional lifecycle, indexing, and concurrency behavior of the base interface table.

Key Columns

The column list is dominated by bank statement line attributes. BANK_ACCOUNT_NUM, STATEMENT_NUMBER, and LINE_NUMBER form the natural identification triplet for a statement line. TRX_DATE, TRX_CODE, and EFFECTIVE_DATE capture the transaction date, the bank transaction code used during reconciliation matching, and the accounting-effective date respectively. AMOUNT, CHARGES_AMOUNT, ORIGINAL_AMOUNT, and EXCHANGE_RATE constitute the monetary core: AMOUNT is the statement line value, CHARGES_AMOUNT carries bank fees or service charges associated with the line, ORIGINAL_AMOUNT preserves the foreign-currency value, and EXCHANGE_RATE supports conversion. Currency context is supplied by CURRENCY_CODE, USER_EXCHANGE_RATE_TYPE, and EXCHANGE_RATE_DATE. Descriptive fields include TRX_TEXT, INVOICE_TEXT, BANK_ACCOUNT_TEXT, CUSTOMER_TEXT, and BANK_TRX_NUMBER. Standard audit columns CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, and LAST_UPDATE_DATE are exposed, along with the full ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 descriptive flexfield segments. The user's search term, CHARGES_AMOUNT, maps directly to the bank charge component of a statement line.

Common Use Cases and Queries

Typical uses include verifying statement load results, diagnosing reconciliation failures, and building custom reports over charges. A representative query listing lines with bank charges above a threshold is:

• SELECT statement_number, line_number, trx_date, amount, charges_amount, currency_code FROM ce_stat_lines_inf_v WHERE charges_amount > 0 ORDER BY trx_date, statement_number, line_number;
• SELECT bank_account_num, SUM(charges_amount) total_charges FROM ce_stat_lines_inf_v GROUP BY bank_account_num;
• SELECT line_number, trx_text, invoice_text, bank_trx_number FROM ce_stat_lines_inf_v WHERE statement_number = :p_statement AND bank_account_num = :p_account;

Because the view is a thin wrapper over a staging table, rows are expected to appear and disappear as the statement load and reconciliation cycle runs; queries should therefore be scoped tightly by statement number or account to avoid scanning large transient volumes.