Search Results ce_upg_ba_uses_pk

Overview

CE_UPG_BA_USES_ALL is a Cash Management (CE) staging table that stores bank account uses information specifically for bank upgrade purposes. It resides in the CE schema and is classified as VALID in Oracle E-Business Suite 12.1.1 and 12.2.2. The table functions as an intermediate repository that holds the target or "new" bank account use records generated during the bank data migration and upgrade process, allowing the upgrade utilities to transform legacy bank account data into the current CE bank account model before final validation and post-upgrade conversion.

From a heuristic Data Vault modeling perspective, the table exhibits characteristics most consistent with a satellite structure: it carries descriptive attributes, flags, and an end date keyed to an upgrade identifier, and it references a parent legal entity. The literal "_UPG_" and "_ALL" naming convention combined with the CE_UPGRADE_ID column confirms its short-lived, batch-oriented nature rather than a persistent operational entity.

Key Information Stored

The table's 53 documented columns capture bank account usage, which is the association between a bank account and the entity or application that uses it (Accounts Payable, Accounts Receivable, Payroll, Treasury, and so on). The most significant columns are:

• CE_UPGRADE_ID — the surrogate primary key (via CE_UPG_BA_USES_PK) and the business-key candidate defined by unique index CE_UPG_BA_USES_U1; it identifies the upgrade batch row.
• CE_BANK_ACCT_USE_ID — the identifier of the bank account use being staged or generated.
• SOURCE_APPLICATION_ID and SOURCE_PK_ID — trace the originating application and the source record's primary key, enabling reconciliation back to pre-upgrade data.
• PARENT_UPGRADE_ID — links the row to a parent upgrade context, supporting hierarchical processing.
• PARTY_CODE, ACCOUNT_NUMBER, and UPGRADE_STATUS — describe the owning party, the bank account number, and the row's progress through the upgrade workflow.
• PRIMARY_FLAG, PRIMARY_ACCT_USE_FLAG, and SECONDARY_ACCT_USE_FLAG — indicate whether the use is primary or secondary.
• LEGAL_ENTITY_ID — the documented foreign key to FV_LEGAL_ENTITIES, tying the use to a legal entity.
• Application enablement flags — AP_USE_ENABLE_FLAG, AR_USE_ENABLE_FLAG, XTR_USE_ENABLE_FLAG, PAY_USE_ENABLE_FLAG, and CE_USE_ENABLE_FLAG — determine which applications may use the account.
• POOLED_FLAG, END_DATE, and DIRECT_DEBIT_AUTH_FLAG — govern pooling, effective dating, and debit authorization characteristics.
• Standard audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and the ATTRIBUTE1–ATTRIBUTE15 flexfields plus ORG_ID for multi-org context.

Common Use Cases and Queries

This table is primarily used during bank upgrade projects, and queries typically focus on monitoring progress and validating converted uses. A representative progress query grouping by upgrade status is:

SELECT CE_UPGRADE_ID, UPGRADE_STATUS, COUNT(*) FROM CE.CE_UPG_BA_USES_ALL GROUP BY CE_UPGRADE_ID, UPGRADE_STATUS;

To trace a staged use back to its source, join on SOURCE_APPLICATION_ID and SOURCE_PK_ID. To resolve the owning legal entity, join LEGAL_ENTITY_ID to FV_LEGAL_ENTITIES. Reporting scenarios include reconciling enablement flags against the target CE_BANK_ACCT_USES_ALL table after upgrade, auditing rows still pending conversion, and confirming primary/secondary designation consistency. Because the table is transient, it should not be queried for ongoing operational reporting.

Related Objects

• FV_LEGAL_ENTITIES — referenced via the LEGAL_ENTITY_ID foreign key, resolving the legal entity owner.
• CE_BANK_ACCT_USES_ALL — the production destination table to which staged uses are ultimately converted; the primary comparison target for post-upgrade reconciliation.
• CE_BANK_ACCOUNTS — the account master referenced through ACCOUNT_NUMBER.
• CE_UPG_BANK_ACCOUNTS_ALL and related CE_UPG_* upgrade staging tables — sibling objects sharing the CE_UPGRADE_ID context.
• AP_BANK_ACCOUNTS_ALL, AR_BANK_ACCOUNTS, and PAY_BANK_ACCOUNTS — legacy application-specific account tables that the enabled-use flags reconcile against.
• CLIENT_INFO / multi-org APIs — used to scope queries by ORG_ID.