Search Results ce_bank_upgrade_modes




Overview
Explore in AI Chat

Overview

CE_BANK_UPGRADE_MODES is a Cash Management (CE) table in the Oracle E-Business Suite database, owned by the CE schema. Its documented purpose is to store the bank upgrade mode of each bank entity for source products in which the current bank tables reside. It therefore acts as a control and reference table consulted during the bank data upgrade and migration process, recording how bank, branch, account, and account-use records originating from a given source product are to be handled.

The table is documented in ETRM for both Oracle EBS 12.1.1 and 12.2.2, with the 12.2.2 physical schema exposing twelve columns. The primary key is defined by the CE_BANK_UPGRADE_MODES_PK constraint on the SOURCE_PRODUCT_NAME column. From a heuristic Data Vault perspective, the FK/PK relationship metadata classifies this object as standalone, with no dependent or parent foreign key relationships. This suggests a modeling approach in which the table can be treated as a small reference or control satellite keyed by its source product identifier, rather than as a transactional hub or a link table interconnecting multiple business entities.

Key Information Stored

The documented columns capture both the identity of the source product and the upgrade behavior to be applied to the associated banking entities, together with standard Oracle EBS audit columns.

  • SOURCE_PRODUCT_NAME — the business key and the single column of the primary key CE_BANK_UPGRADE_MODES_PK; identifies the source product whose bank tables are being upgraded.
  • BANK_UPGRADE_MODE — the upgrade mode governing treatment of bank records for the identified source product.
  • BRANCH_UPGRADE_MODE — the upgrade mode governing treatment of branch records.
  • ACCOUNT_UPGRADE_MODE — the upgrade mode governing treatment of bank account records.
  • LAST_BANK_UPG_ID — the identifier of the last bank upgrade processed for this source product.
  • LAST_ACCOUNT_UPG_ID — the identifier of the last account upgrade processed.
  • LAST_ACCT_USE_UPG_ID — the identifier of the last account use upgrade processed.
  • CREATION_DATE, CREATED_BY — standard audit columns recording when and by whom the row was created.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns recording the most recent modification and its originating session.

Because SOURCE_PRODUCT_NAME is both the primary key and the only documented business-key candidate, it uniquely identifies one row per source product. The LAST_*_UPG_ID columns support checkpointing so that upgrades may resume from the last successfully processed bank, account, or account use record.

Common Use Cases and Queries

Typical uses center on monitoring and validating the bank upgrade process during or after an EBS release upgrade. A direct lookup of the configured modes for a source product is a common starting point:

  • SELECT source_product_name, bank_upgrade_mode, branch_upgrade_mode, account_upgrade_mode FROM ce.ce_bank_upgrade_modes;
  • SELECT * FROM ce.ce_bank_upgrade_modes WHERE source_product_name = :p_source_product;
  • SELECT source_product_name, last_bank_upg_id, last_account_upg_id, last_acct_use_upg_id FROM ce.ce_bank_upgrade_modes ORDER BY last_update_date DESC;
  • SELECT source_product_name, last_update_date, last_updated_by FROM ce.ce_bank_upgrade_modes WHERE last_update_date >= :p_since;

Reporting scenarios include confirming that upgrade modes are populated for every source product prior to beginning a migration, tracking progress through the LAST_*_UPG_ID checkpoints, and auditing who last modified a given row through the standard audit columns.

Related Objects

The ETRM metadata classifies this table as standalone, so no foreign key relationships to parent or child tables are documented. Its most significant associations are therefore logical rather than enforced:

  • CE_BANK_UPGRADE_MODES_PK — the primary key constraint on SOURCE_PRODUCT_NAME, providing unique access and driving index-based lookups.
  • CE_BANKS, CE_BANK_BRANCHES, CE_BANK_ACCOUNTS, CE_BANK_ACCT_USES_ALL — the Cash Management bank entities whose upgrade behavior is governed by the modes recorded here; joins are made logically on the source product rather than through a declared foreign key.
  • Other Cash Management setup and upgrade control tables in the CE schema that participate in the same migration and validation activity.

Because the table is a standalone reference object, queries generally treat it as a lookup keyed by SOURCE_PRODUCT_NAME rather than as a participant in relational joins.