Search Results ce_bank_upgrade_errors_pk

Overview

CE_BANK_UPGRADE_ERRORS is a Cash Management (CE) module table in the Oracle E-Business Suite that stores errors encountered during the upgrade of banking entities — banks, bank branches, and bank accounts. When legacy or prior-release bank data is migrated forward into the current EBS data model, the upgrade process validates each record and records any failure conditions in this table. The table therefore functions as the diagnostic log for the bank data conversion, allowing DBAs and functional consultants to identify which banking records could not be upgraded, for what reason, and under which upgrade run.

From a data modeling perspective, the heuristically mined Data Vault classification for this object is standalone. It carries no foreign key dependencies in the documented relationship data, so it does not behave as a hub, link, or satellite in a strict Data Vault sense. Where a modeling exercise requires mapping it, it is best treated as an isolated error/event table keyed by the upgrade run rather than as part of a conformed dimensional structure.

Key Information Stored

The documented physical schema exposes ten columns. The most significant are:

• CE_UPGRADE_ID — Identifier of the specific bank upgrade run that produced the error. This is the primary grouping attribute for diagnostics and reporting.
• BANK_ENTITY_TYPE — Indicates whether the failing record is a bank, a bank branch, or a bank account, distinguishing the three entity classes handled by the upgrade.
• MESSAGE_NAME — The name of the error or warning message raised for the failing record, providing the reason the entity could not be upgraded.
• KEY_ERROR_FLAG — Flag denoting whether the error is key-level (for example, a duplicate or missing business key), which typically blocks the upgrade outright versus a non-key warning.
• APPLICATION_ID — The application owning the message or the affected record, used to resolve message text and to scope reporting.
• CREATION_DATE, CREATED_BY — Standard WHO audit columns recording when and by whom the error row was written.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns capturing the last modification of the row and the login session associated with it.

The primary key, CE_BANK_UPGRADE_ERRORS_PK, is a composite of CE_UPGRADE_ID, BANK_ENTITY_TYPE, and MESSAGE_NAME. A unique index, CE_BANK_UPGRADE_ERRORS_U1, covers those same three columns, confirming them as the business-key candidate for this table. Note that no surrogate single-column key is documented; the composite triple serves both roles.

Common Use Cases and Queries

The primary use case is post-upgrade validation: confirming whether all banks, branches, and accounts converted cleanly, and isolating the failures for remediation. A typical query groups errors by upgrade run and entity type:

• SELECT ce_upgrade_id, bank_entity_type, COUNT(*) FROM ce.ce_bank_upgrade_errors GROUP BY ce_upgrade_id, bank_entity_type;
• Filtering only hard failures: SELECT * FROM ce.ce_bank_upgrade_errors WHERE key_error_flag = 'Y' AND ce_upgrade_id = :upgrade_id;
• Join to FND messages to render readable text: SELECT e.ce_upgrade_id, e.bank_entity_type, m.message_text FROM ce.ce_bank_upgrade_errors e, applsys.fnd_new_messages m WHERE e.message_name = m.message_name AND e.application_id = m.application_id;

These patterns support conversion status dashboards, remediation tracking, and audit evidence that the upgrade was reviewed before sign-off.

Related Objects

Because the documented relationship data classifies this table as standalone, no foreign keys are defined against it. Logical relationships nonetheless exist and are the ones most useful in practice:

• CE_BANKS — The bank records whose upgrade is being validated.
• CE_BANK_BRANCHES — Branch-level records, corresponding to BANK_ENTITY_TYPE values for branches.
• CE_BANK_ACCOUNTS — Account-level records, corresponding to the account entity type.
• FND_NEW_MESSAGES (joined on APPLICATION_ID and MESSAGE_NAME) — Supplies the readable message text for reporting.
• CE_UPGRADE / the bank upgrade driver — The process that populates CE_UPGRADE_ID and writes the error rows.

Together these objects form the diagnostic chain: the upgrade driver processes banking entities, and any entity it cannot convert is recorded here with its CE_UPGRADE_ID, entity type, and message for follow-up.