Results for “statement_line_status”

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

Overview

The APPS.CEBV_BANK_STATEMENT_LINES view provides a denormalized, read-only presentation of bank statement line records held in Oracle E-Business Suite Cash Management. It joins each statement line to its parent statement header and resolves several coded columns into human-readable meanings drawn from the Cash Management lookups and transaction code tables. The view is defined with the WITH READ ONLY clause, so it is intended strictly for query and reporting purposes and cannot be used to perform DML against the underlying statement lines.

For users searching on statement_line_status, the view is directly relevant: it exposes the statement line status through the CE_LOOKUPS lookup type STATEMENT_LINE_STATUS. Rather than returning the raw status code stored on CE_STATEMENT_LINES, the view presents the corresponding lookup meaning, which simplifies interpretation in reports and integrations.

Underlying Base Objects

The view is owned by APPS and is defined over the following documented objects:

• CE_STATEMENT_LINES (synonym) — the primary source of individual bank statement line records, aliased as SL.
• CE_STATEMENT_HEADERS (synonym) — joined on statement_header_id to supply statement number and statement date, aliased as SH.
• CE_LOOKUPS (view) — joined twice, once as L1 on lookup type BANK_TRX_TYPE to resolve the transaction type, and once as L2 on lookup type STATEMENT_LINE_STATUS to resolve line status.
• CE_TRANSACTION_CODES (synonym) — outer-joined on transaction_code_id to provide the bank transaction code, aliased as TC.
• GL_DAILY_CONVERSION_TYPES (synonym) — outer-joined on conversion_type to resolve the exchange rate type, aliased as DC.

The joins to CE_TRANSACTION_CODES and GL_DAILY_CONVERSION_TYPES are outer joins, whereas the joins to the lookup tables and statement headers are inner joins. This means a statement line must have a valid trx_type and status lookup, plus a matching header, to appear in the result set.

Key Columns

• STATEMENT_LINE_ID, STATEMENT_HEADER_ID, LINE_NUMBER — primary identifiers and ordering within a statement.
• TRX_DATE, EFFECTIVE_DATE, EXCHANGE_RATE_DATE — key dates for the line and any associated currency conversion.
• L1.MEANING — meaning of the bank transaction type (BANK_TRX_TYPE lookup).
• L2.MEANING — meaning of the statement line status (STATEMENT_LINE_STATUS lookup), the resolved form of the searched field.
• TRX_CODE — bank transaction code from CE_TRANSACTION_CODES.
• AMOUNT, ORIGINAL_AMOUNT, CHARGES_AMOUNT, CURRENCY_CODE, EXCHANGE_RATE, USER_CONVERSION_TYPE — monetary and conversion details.
• BANK_TRX_NUMBER, TRX_TEXT, CUSTOMER_TEXT, BANK_ACCOUNT_TEXT, INVOICE_TEXT — descriptive references carried on the statement line.
• STATEMENT_NUMBER, STATEMENT_DATE — header-level context.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — audit columns.

Common Use Cases and Queries

Typical scenarios include reconciling statement lines by status, reporting unreconciled lines, and validating cash transactions imported through bank statement processing. Filtering on the resolved status meaning is straightforward because the view already performs the lookup join.

SELECT statement_line_id, statement_number, line_number,
       trx_date, meaning, amount, currency_code
FROM   apps.cebv_bank_statement_lines
WHERE  meaning = 'Unreconciled';

To summarize activity by status and transaction type:

SELECT meaning, trx_code, COUNT(*), SUM(amount)
FROM   apps.cebv_bank_statement_lines
GROUP  BY meaning, trx_code;

Because the view is read-only, it is well suited to ad hoc reporting, extracts, and integration queries where a reliable, decoded view of statement line data is required.