Results for “ce_ce_statement_headers”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

CE_CE_STATEMENT_HEADERS is a Cash Management (CE) schema table within the Oracle E-Business Suite. The ETRM metadata documents this object as a backup of the CE_STATEMENT_HEADERS table created prior to the bank_account_id foreign key upgrade. Its presence in a production or cloned environment therefore indicates that a structural migration touched the parent STATEMENT_HEADERS entity—typically a patch or upgrade step that re-sequenced or re-keyed the BANK_ACCOUNT_ID relationship—and that the pre-upgrade copy was retained rather than dropped. The table is owned by the CE schema and holds the same eight columns recorded for the primary structure: STATEMENT_HEADER_ID, BANK_ACCOUNT_ID, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, and OBJECT_VERSION_NUMBER, along with a primary key constraint named CE_CE_STATEMENT_HEADERS_U1.

From a Data Vault modeling perspective, the heuristic classification is standalone. The metadata records no foreign key dependencies, so the table can be modeled as an isolated structure rather than as a hub or a link. In practice, the surrogate key STATEMENT_HEADER_ID behaves as a hub-style business key, while the audit columns (creation and update attributes) form satellite-style descriptive metadata. Implementers adopting a Data Vault design against EBS staging layers may choose to treat the table as a single hub with one attached satellite.

Key Information Stored

The documented columns fall into three functional groups. The identity and business-key group centers on STATEMENT_HEADER_ID (the surrogate primary key, backed by CE_CE_STATEMENT_HEADERS_U1) and BANK_ACCOUNT_ID, which links the header to a bank account in Cash Management. Because the table exists specifically because of a BANK_ACCOUNT_ID upgrade, this column's values in the backup are likely to reference the pre-upgrade representation.

• STATEMENT_HEADER_ID — surrogate primary key; the unique identifier of the statement header.
• BANK_ACCOUNT_ID — identifies the bank account to which the statement header belongs; the subject of the upgrade that produced this backup.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the EBS framework to detect concurrent updates.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard who-column triplet recording the last modification.
• CREATION_DATE, CREATED_BY — the standard who-column pair recording initial insert.

No secondary unique index is documented beyond the primary key, so STATEMENT_HEADER_ID is the sole documented unique key; BANK_ACCOUNT_ID should not be assumed unique across rows.

Common Use Cases and Queries

Because the table is a pre-upgrade backup, its primary uses are reconciliation and audit of the bank_account_id migration. A typical verification compares population counts and orphaned references between the backup and the live table:

• Count comparison: SELECT COUNT(*) FROM ce.ce_ce_statement_headers; against the live CE_STATEMENT_HEADERS.
• Row-level difference: a MINUS query on STATEMENT_HEADER_ID joined to the live table to find statements present before the upgrade but absent afterward.
• Orphan detection: LEFT JOIN CE_BANK_ACCOUNTS on BANK_ACCOUNT_ID to find pre-upgrade references that no longer resolve.
• Audit reporting: selecting CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, and LAST_UPDATE_DATE to attribute when each statement was originally captured.
• Post-upgrade cleanup validation: confirming the backup can be safely dropped once reconciliation is signed off.

Related Objects

• CE_STATEMENT_HEADERS — the live parent table this backup mirrors; join on STATEMENT_HEADER_ID.
• CE_BANK_ACCOUNTS — join on BANK_ACCOUNT_ID to resolve bank account details.
• CE_STATEMENT_LINES — statement lines belonging to a header; join on STATEMENT_HEADER_ID.
• CE_BANK_ACCT_USES_ALL — bank account use assignments referenced via BANK_ACCOUNT_ID.
• FND_USER — join CREATED_BY and LAST_UPDATED_BY to resolve application user names.

These relationships are inferred from Cash Management's logical model and the documented BANK_ACCOUNT_ID upgrade context; the ETRM metadata records the backup as standalone with no declared foreign keys.