Results for “ce_ce_cp_pd_balances”

24 results




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

Overview

CE_CE_CP_PD_BALANCES is a Cash Management (CE) schema table in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is narrowly scoped: it is a backup of the CE_CP_PRIORDAY_BALANCES table captured before the bank account foreign key upgrade was applied. It is therefore an upgrade artifact rather than a table used in day-to-day Cash Management processing. The table is marked VALID in the data dictionary and is owned by the CE schema, with a documented physical schema of twelve columns.

Because the table exists to preserve the pre-upgrade state of prior-day bank account balances, it is not referenced by standard application flows, concurrent programs, or online pages. Its principal value is forensic and diagnostic: it permits administrators and support analysts to compare the state of prior-day balance data before and after the bank account foreign key migration, particularly where a discrepancy in bank account identification is suspected.

Applying a heuristic Data Vault classification based on the documented foreign key structure, this table is satellite-leaning. It records descriptive, time-stamped balance attributes attached to a bank account parent rather than acting as a hub of business entities or a link between entities. This classification is a modeling suggestion derived from the FK pattern and should not be treated as a physical design statement about the delivered table.

Key Information Stored

The documented column list contains twelve columns. The most significant are:

  • BANK_ACCOUNT_ID and CE_BANK_ACCOUNT_ID — the original and upgraded bank account identifiers. The documented foreign key is CE_CE_CP_PD_BALANCES.CE_BANK_ACCOUNT_ID referencing CE_BANK_ACCOUNTS. The coexistence of both columns reflects the nature of the upgrade: the pre-upgrade value is retained alongside the post-upgrade key.
  • AS_OF_DATE — the business date to which the prior-day balance applies, the principal temporal qualifier for any balance row.
  • WORKSHEET_HEADER_ID — the identifier of the associated worksheet header, tying the balance record to a reconciliation worksheet context.
  • SOURCE_TYPE — a discriminator describing the origin or category of the balance record.
  • ROWID_VAR — a row identifier variable used during the upgrade to correlate backup rows with their source rows.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — standard EBS audit columns.
  • LAST_UPDATE_LOGIN and OBJECT_VERSION_NUMBER — the login audit column and the standard optimistic locking version number used by the EBS framework.

The ETRM metadata does not document a primary key or unique index for this table. The closest candidates for a business key are the combination of BANK_ACCOUNT_ID, AS_OF_DATE, and WORKSHEET_HEADER_ID, since a prior-day balance is naturally scoped to an account, a date, and a worksheet. This should be confirmed against the database rather than assumed, as the table is a backup copy and may not carry the constraints of its source.

Common Use Cases and Queries

Typical use is verification during or after the bank account foreign key upgrade. A simple approach is to compare row counts and key values between the backup and the live table for a given account and date range:

  • Count comparison: select BANK_ACCOUNT_ID, AS_OF_DATE, count(*) from CE_CE_CP_PD_BALANCES group by BANK_ACCOUNT_ID, AS_OF_DATE and compare against the equivalent aggregation on CE_CP_PRIORDAY_BALANCES.
  • Orphan detection: identify backup rows whose CE_BANK_ACCOUNT_ID does not resolve to CE_BANK_ACCOUNTS, using a left outer join on CE_BANK_ACCOUNTS and a null filter.
  • Key mapping audit: list rows where BANK_ACCOUNT_ID and CE_BANK_ACCOUNT_ID differ, to document how the migration remapped account keys.
  • Worksheet reconciliation: join WORKSHEET_HEADER_ID to the worksheet header table to confirm the balances belong to the expected worksheet.

Because the table is a static backup, it should not be used as a reporting source for operational Cash Management reporting. Any query against it should be qualified by AS_OF_DATE and account to avoid full scans of a table with no documented indexing.

Related Objects

  • CE_BANK_ACCOUNTS — the referenced parent of the documented foreign key CE_CE_CP_PD_BALANCES.CE_BANK_ACCOUNT_ID.
  • CE_CP_PRIORDAY_BALANCES — the source table of which this object is the pre-upgrade backup; the primary comparison target.
  • CE_BANK_ACCOUNT_HEADERS and CE_BANK_ACCOUNT_USES — related bank account configuration tables commonly joined when interpreting account identifiers.
  • CE_STMT_HDRS and CE_STMT_LINES — bank statement objects that consume prior-day balance information in reconciliation.
  • CE_WORKSHEET_HEADERS — the worksheet context referenced by WORKSHEET_HEADER_ID.

The definitive reference for this object remains the ETRM data dictionary entry, which documents the twelve columns and the single foreign key relationship described above.