Search Results ce_statement_lns_interface_u1

Overview

The CE.CE_STATEMENT_LINES_INTERFACE table is the open interface staging area for bank statement line data in Oracle E-Business Suite Releases 12.1.1 and 12.2.2. It is owned by the Cash Management (CE) product and resides in the APPS_TS_INTERFACE tablespace with a PCT Free of 10, which is characteristic of high-volume, transient interface data. Each row represents a single bank statement line awaiting validation and transfer into the permanent CE_STATEMENT_LINES table.

The table serves as the inbound landing zone for external bank statement files, whether sourced from bank feeds, flat-file loads, or custom integrations. Once populated, the Bank Statement Import program is executed to validate each row and migrate statement line information into the production CE_STATEMENT_LINES table. When errors occur, the Bank Statement Interface form allows users to inspect, correct, or delete rejected rows before re-running the import. The table's lifecycle is classified as active with public scope, indicating it is a supported and directly queryable object within the CE product family.

From a dimensional modeling perspective, the ETRM metadata classifies this table heuristically as satellite-leaning. This suggests that practitioners modeling the data warehouse layer may treat CE_STATEMENT_LINES_INTERFACE as a satellite around a bank statement hub, carrying descriptive attributes keyed by the statement identity rather than acting as an independent hub or a pure intersection link.

Key Information Stored

The table contains 38 documented columns, of which the most operationally significant are the following:

• STATEMENT_NUMBER (VARCHAR2, 50) — Identifies the bank statement to which the line belongs.
• BANK_ACCOUNT_NUM (VARCHAR2, 30) — The bank account number associated with the statement line.
• LINE_NUMBER (NUMBER, 15) — The sequential line number within the statement.
• TRX_DATE (DATE) — Transaction date of the line, used to update the cleared date on AP checks and AR receipts when EFFECTIVE_DATE is null.
• TRX_CODE (VARCHAR2, 30) — Bank transaction code describing the nature of the line.
• EFFECTIVE_DATE (DATE) — Effective date used primarily to update AR receipt clearing dates.
• TRX_TEXT (VARCHAR2, 255) — Free-text description of the statement line.
• INVOICE_TEXT (VARCHAR2, 70) — Invoice number text used to match available transactions by invoice.
• AMOUNT (NUMBER) — The statement line amount.
• CURRENCY_CODE (VARCHAR2, 15) — Currency of the statement line, validated against FND_CURRENCIES.
• EXCHANGE_RATE, USER_EXCHANGE_RATE_TYPE, and EXCHANGE_RATE_DATE — Currency conversion attributes applied when the line currency differs from the ledger currency.
• ORIGINAL_AMOUNT and CHARGES_AMOUNT — Supporting amount components used during reconciliation.
• BANK_TRX_NUMBER — The bank's own transaction reference for the line.

The documented physical primary key is CE_STMT_LINES_INTERFACE_PK, comprising STATEMENT_NUMBER, BANK_ACCOUNT_NUM, and LINE_NUMBER. A separate unique index, CE_STATEMENT_LNS_INTERFACE_U1, enforces uniqueness on the same three columns (STATEMENT_NUMBER, BANK_ACCOUNT_NUM, LINE_NUMBER) in the APPS_TS_INTERFACE tablespace. The user's search term "ce_statement_lns_interface_u1" therefore maps directly to this unique business-key index rather than to a surrogate key. Standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE) and fifteen ATTRIBUTE columns provide audit and extensibility support, while ATTRIBUTE_CATEGORY controls descriptive flexfield context.

Common Use Cases and Queries

Typical operational scenarios include monitoring the backlog of unimported statement lines, diagnosing validation failures, and reconciling loaded lines against source bank feeds.

• Counting pending interface rows prior to running Bank Statement Import: SELECT STATEMENT_NUMBER, BANK_ACCOUNT_NUM, COUNT(*) FROM CE.CE_STATEMENT_LINES_INTERFACE GROUP BY STATEMENT_NUMBER, BANK_ACCOUNT_NUM;
• Reviewing rows with a specific currency requiring rate application: SELECT STATEMENT_NUMBER, LINE_NUMBER, AMOUNT, CURRENCY_CODE, EXCHANGE_RATE FROM CE.CE_STATEMENT_LINES_INTERFACE WHERE CURRENCY_CODE <> 'USD';
• Correlating interface lines with recorded errors via CE_LINE_INTERFACE_ERRORS on STATEMENT_NUMBER and LINE_NUMBER to isolate rows that failed validation.
• Extracting inbound amounts and dates for daily bank reconciliation reporting prior to import completion.

Because the table is an interface object, queries should generally be limited to staging, validation, and reconciliation reporting rather than serving as a permanent transactional source.

Related Objects

• CE.CE_STATEMENT_HEADERS_INT_ALL — Parent statement header interface; joined on STATEMENT_NUMBER and BANK_ACCOUNT_NUM.
• CE.CE_STATEMENT_LINES — The destination table populated by Bank Statement Import.
• CE.CE_LINE_INTERFACE_ERRORS — Child error table keyed by STATEMENT_NUMBER, providing validation failure detail.
• FND_CURRENCIES — Lookup validating CURRENCY_CODE.
• Bank Statement Import Program — Concurrent program that processes rows from this interface.
• Bank Statement Interface Form — Application form used to inspect and correct staged rows.