Search Results ce_stmt_lines_interface_pk

Overview

CE_STATEMENT_LINES_INTERFACE is the Cash Management open interface table that stages individual bank statement lines prior to import into the Oracle E-Business Suite bank statement data model. It resides in the CE schema and is classified as VALID in both release 12.1.1 and 12.2.2. Its documented description is simply "Open interface for bank statement lines," which reflects its primary function: to serve as the inbound staging area for external statement loaders, reconciliation utilities, and third-party integrations that must feed line-level detail into Cash Management.

Each row in the table represents one statement line, identified by the composite business key of STATEMENT_NUMBER, BANK_ACCOUNT_NUM, and LINE_NUMBER. The metadata heuristic classifies this object as satellite-leaning. In Data Vault terms, this suggests modeling it as a satellite attached to a hub or link representing the bank account/statement relationship, since the table carries descriptive transaction attributes keyed to a parent statement header rather than acting as an independent business entity hub.

Key Information Stored

The primary key is enforced by the unique index CE_STATEMENT_LNS_INTERFACE_U1, which covers the three business-key candidate columns STATEMENT_NUMBER, BANK_ACCOUNT_NUM, and LINE_NUMBER. The Oracle-named constraint is CE_STMT_LINES_INTERFACE_PK. These three columns establish the identity of the line and link it to its parent statement header.

The most significant descriptive columns include:

• TRX_DATE, EFFECTIVE_DATE — the transaction and value dates of the bank line.
• TRX_CODE — the bank transaction code classification.
• AMOUNT, ORIGINAL_AMOUNT, CHARGES_AMOUNT — monetary values for the line, its original amount, and any associated bank charges.
• CURRENCY_CODE — the currency of the line, with a documented foreign key to FND_CURRENCIES.
• USER_EXCHANGE_RATE_TYPE, EXCHANGE_RATE_DATE, EXCHANGE_RATE — rate information used to convert the line to functional currency.
• BANK_TRX_NUMBER — the bank's own reference number for the transaction.
• TRX_TEXT, INVOICE_TEXT, CUSTOMER_TEXT — free-form narrative fields carrying bank and customer descriptions.
• The standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE) and the fifteen ATTRIBUTE columns plus ATTRIBUTE_CATEGORY for extensibility.

Common Use Cases and Queries

The principal use case is loading external bank statements. Typical processing involves inserting rows for a given statement, then invoking the Cash Management statement import program, which validates and transfers the lines into the bank statement tables. Errored rows are written to CE_LINE_INTERFACE_ERRORS keyed on the same three columns.

A common reconciliation query retrieves all lines staged for a specific statement and account:

• SELECT line_number, trx_date, trx_code, amount, currency_code FROM ce_statement_lines_interface WHERE statement_number = :stmt AND bank_account_num = :acct ORDER BY line_number;
• Joining to CE_LINE_INTERFACE_ERRORS on STATEMENT_NUMBER, BANK_ACCOUNT_NUM, and LINE_NUMBER isolates rejected lines for correction.
• Aggregating AMOUNT by CURRENCY_CODE and TRX_CODE supports cash position reporting before formal import.

Related Objects

The table participates in the following documented relationships:

• CE_STATEMENT_HEADERS_INT_ALL — parent header table; joined on STATEMENT_NUMBER and BANK_ACCOUNT_NUM.
• CE_LINE_INTERFACE_ERRORS — child error table referencing STATEMENT_NUMBER, BANK_ACCOUNT_NUM, and LINE_NUMBER for validation failures.
• FND_CURRENCIES — currency validation via CURRENCY_CODE.
• Cash Management statement import concurrent programs consume these rows to populate the permanent bank statement and reconciliation tables.