Search Results ce_arch_headers




Overview
Explore in AI Chat

Overview

The CE_ARCH_HEADERS table is a core data repository within the Oracle E-Business Suite Cash Management (CE) module. Its primary function is to serve as the archival store for records from the CE_STATEMENT_HEADERS_ALL table. This archiving process is a critical data management operation, typically executed to maintain performance and manage data volume in the active transaction tables by moving historical or reconciled bank statement header information to a separate, dedicated storage location. The table's existence ensures that a complete audit trail of all bank statement processing is preserved for compliance, historical reporting, and reconciliation inquiries, while keeping the operational tables optimized for current transaction processing.

Key Information Stored

As an archive of statement headers, CE_ARCH_HEADERS holds a historical snapshot of the metadata for each bank statement that has been loaded and processed. While the specific column list is not detailed in the provided metadata, the table's description and foreign key relationship imply it contains a copy of the key columns from CE_STATEMENT_HEADERS_ALL at the time of archiving. This logically includes the statement header's unique identifier (likely a column such as STATEMENT_HEADER_ID), the associated BANK_ACCOUNT_ID linking to the specific bank account, statement number, statement date, opening and closing balances, currency code, and status indicators. The BANK_ACCOUNT_ID is a confirmed critical column, forming the documented link to the AP_BANK_ACCOUNTS_ALL table which defines the bank account within the system.

Common Use Cases and Queries

The primary use case for CE_ARCH_HEADERS is historical analysis and reporting on bank statements that are no longer active in the primary transaction table. Common operational scenarios include generating long-term reconciliation reports, investigating historical discrepancies, and fulfilling audit requests for statement data beyond a certain age. A typical query pattern involves joining to the bank accounts table to retrieve account details and potentially to the archived lines table (CE_ARCH_LINES) for a complete historical statement view.

  • Sample Query: Retrieving archived statements for a specific bank account:
    SELECT arch.statement_header_id, arch.statement_number, arch.statement_date,
    aba.bank_account_name, aba.bank_account_num
    FROM ce_arch_headers arch,
    ap_bank_accounts_all aba
    WHERE arch.bank_account_id = aba.bank_account_id
    AND aba.bank_account_id = 1001
    ORDER BY arch.statement_date DESC;

Related Objects

CE_ARCH_HEADERS is intrinsically linked to several key objects within the Cash Management data model. Its relationships are primarily defined by foreign key constraints that ensure referential integrity with master and transactional data.

  • CE_STATEMENT_HEADERS_ALL: This is the direct source table. Records are moved from this active table into CE_ARCH_HEADERS during the archiving process.
  • AP_BANK_ACCOUNTS_ALL: This is a documented foreign key relationship. The BANK_ACCOUNT_ID column in CE_ARCH_HEADERS references the BANK_ACCOUNT_ID in AP_BANK_ACCOUNTS_ALL, linking each archived statement to its specific bank account definition.
  • CE_ARCH_LINES: While not listed in the provided metadata, standard architecture dictates that a related CE_ARCH_LINES table almost certainly exists to store the corresponding detailed transaction lines for each archived header, linked via the statement header's primary key.