Search Results ce_stmt_int_tmp_u1

Overview

The CE.CE_STMT_INT_TMP table is a transient interface (staging) object within the Cash Management (CE) module of Oracle E-Business Suite, documented as VALID in both 12.1.1 and 12.2.2. It exists solely to hold bank statement data extracted from an external bank flat file via SQL*Loader before that data is validated and transferred into the permanent bank statement tables. The table is populated and deleted each time the statement loading program executes, meaning it functions as an ephemeral workspace rather than a persistent repository. Because the column set is deliberately generic — a small set of identifier columns followed by thirty-five positional COLUMNn fields plus standard Who columns — the table accommodates the widely varying formats of external bank statement files without schema changes. In heuristic Data Vault terms, this object is best modeled as a standalone raw staging landing zone rather than a hub, link, or satellite; it carries no foreign key relationships, and its classification as standalone reflects that it is a load buffer, not a component of a conformed dimensional model.

Key Information Stored

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

• REC_NO (NUMBER) — the surrogate sequential record number and the sole documented primary key (CE_STMT_INT_TMP_PK). It is also the column of the unique index CE_STMT_INT_TMP_U1, the object the user searched for, which enforces uniqueness at the APPS_TS_INTERFACE tablespace level and serves as the business-key candidate.
• REC_ID_NO (VARCHAR2(30)) — a record identifier value parsed from the source file, typically the bank-assigned statement or sequence reference.
• COLUMN1 (VARCHAR2(2000)) — the widest staging column, generally holding the full raw input line.
• COLUMN2 through COLUMN35 (VARCHAR2(255) each) — positional fields into which the loader places parsed statement attributes (statement number, date, amount, currency, transaction code, and similar).
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — standard Who columns capturing load audit information.

Common Use Cases and Queries

The primary practical use of this table is diagnostic. When a bank statement load terminates with an error, the offending records remain in CE_STMT_INT_TMP long enough to be inspected and corrected before the load is re-run. Useful access patterns include:

• Verifying whether a load has already been consumed: SELECT COUNT(*) FROM ce.ce_stmt_int_tmp; — a return of zero confirms the program cleared the buffer.
• Inspecting the raw parsed content of a specific row: SELECT rec_no, rec_id_no, column1, column2, column3 FROM ce.ce_stmt_int_tmp WHERE rec_no = :rec_no;
• Locating records tied to a particular bank reference: SELECT rec_no, rec_id_no FROM ce.ce_stmt_int_tmp WHERE rec_id_no = :ref;
• Identifying the loading session via Who columns: SELECT created_by, creation_date FROM ce.ce_stmt_int_tmp ORDER BY rec_no;

Because the data is transient, this table is not a reliable source for historical reporting; reconciliation and bank statement reporting should target the permanent CE statement tables instead.

Related Objects

The documented metadata records no foreign key relationships, consistent with the standalone Data Vault classification. The following objects are the most significant in the surrounding load and reconciliation flow:

• CE_STMT_INT_TMP_PK — primary key constraint on REC_NO.
• CE_STMT_INT_TMP_U1 — unique index on REC_NO in APPS_TS_INTERFACE.
• CE_STATEMENT_HEADERS — permanent header table receiving validated records.
• CE_STATEMENT_LINES — permanent line table holding individual transactions.
• CE_BANK_ACCOUNTS — identifies the bank account to which the loaded statement belongs.
• CE_BANK_BRANCHES — supporting bank branch reference used during validation.
• CE_STMT_LOAD_ERRORS — captures validation failures originating from staged rows.
• CE_STMT_LOADER / the Bank Statement Loader concurrent program — the process that populates and purges this table.

Together these objects form the bank statement ingestion pipeline in which CE_STMT_INT_TMP is the short-lived first hop.