Search Results ce_intra_stmt_headers_u1




Overview

CE.CE_INTRA_STMT_HEADERS (also referenced in some environments as CE_INTRA_STMT_HEADERS_ALL) is an Oracle Cash Management table that stores intra-day bank statement header information. Each row represents a single intra-day bank statement, capturing the statement date, statement number, owning bank account, control totals, and reconciliation-related attributes. Intra-day statements are used to process high-volume banking activity — particularly in treasury and cash concentration scenarios — before the formal end-of-day statement is received from the bank. The table resides in the APPS_TS_TX_DATA tablespace with PCT Free 10.

From a heuristic Data Vault modeling perspective, this object best fits the classification of a satellite attached to a bank account hub, since it stores descriptive and control attributes keyed by bank account and statement identity rather than representing an independent business concept or a pure many-to-many relationship. The standalone classification mined from the FK structure reinforces this interpretation.

Key Information Stored

The surrogate primary key of the table is STATEMENT_HEADER_ID, a NUMBER(15) column. Two unique indexes enforce business-key uniqueness: CE_INTRA_STMT_HEADERS_U1 on (STATEMENT_HEADER_ID, ORG_ID) and CE_INTRA_STMT_HEADERS_U2 on (BANK_ACCOUNT_ID, STATEMENT_NUMBER, ORG_ID). The second index defines the natural business key for a statement in a multi-org context.

  • STATEMENT_HEADER_ID — Surrogate identifier for the statement header row.
  • BANK_ACCOUNT_ID — Identifies the internal bank account the statement belongs to; part of the natural business key.
  • STATEMENT_NUMBER — The bank-assigned statement number; part of the natural business key.
  • STATEMENT_DATE — The date on which the statement was issued.
  • AUTO_LOADED_FLAG — Y/N indicator showing whether the statement arrived through the open interface rather than manual entry.
  • CURRENCY_CODE — Currency of the statement amounts.
  • GL_DATE — Accounting date used for GL entries generated during reconciliation.
  • CONTROL_BEGIN_BALANCE / CONTROL_END_BALANCE — Opening and closing control balances; the end balance is derived as begin minus debits plus credits.
  • CONTROL_TOTAL_DR / CONTROL_TOTAL_CR — Total payment and receipt amounts used to validate against entered transactions.
  • CONTROL_DR_LINE_COUNT / CONTROL_CR_LINE_COUNT — Line counts used for control reconciliation against actual entries.
  • STATEMENT_COMPLETE_FLAG — Indicates whether the statement has been fully processed.
  • ORG_ID — Operating unit identifier supporting multi-org access.
  • DOC_SEQUENCE_ID / DOC_SEQUENCE_VALUE — Document sequencing for the statement, with DOC_SEQUENCE_ID referencing FND_DOCUMENT_SEQUENCES.
  • ONE_DAY_FLOAT / TWO_DAY_FLOAT — Float amounts used in cash positioning calculations.

Common Use Cases and Queries

Typical use cases include reconciling intra-day activity, monitoring control totals against entered transactions, and reporting cash positions across bank accounts. A common query pattern joins header and line information keyed by statement header, filtered by org:

  • Retrieve recent statements for a bank account: SELECT statement_header_id, statement_number, statement_date, control_end_balance FROM ce_intra_stmt_headers WHERE bank_account_id = :p_account AND org_id = :p_org ORDER BY statement_date DESC;
  • Identify auto-loaded statements pending review: SELECT * FROM ce_intra_stmt_headers WHERE auto_loaded_flag = 'Y' AND statement_complete_flag = 'N';
  • Control total validation: compare CONTROL_TOTAL_DR and CONTROL_TOTAL_CR against summed line amounts to detect discrepancies before reconciliation.
  • Reporting GL impact by accounting date: group by GL_DATE and CURRENCY_CODE.

Related Objects

The most significant relationships are: