Search Results ce_upg_ba_uses_u1

Overview

CE.CE_UPG_BA_USES_ALL is a transient staging table in the Oracle E-Business Suite Cash Management (CE) module. It stores new bank account uses information generated during the bank upgrade process, serving as an intermediate repository between legacy or external source systems and the final CE_BANK_ACCT_USES_ALL destination tables. The table exists specifically to support data migration and conversion activities, capturing the mapping between source application bank account uses and their target Cash Management representation.

Under the heuristic Data Vault classification mined from its foreign key structure, this object models as a standalone table. It does not function as a conformed hub, link, or satellite within a formal Data Vault warehouse, but rather as an operational staging artifact whose lifecycle is tied to the upgrade execution. Records are populated during the upgrade, processed through status transitions, and eventually consumed to create or update production bank account uses. The "ALL" suffix indicates the table is not org-striped at the object level, relying instead on the ORG_ID column for multi-organization partitioning.

Key Information Stored

The table contains 53 documented columns, of which the following are most significant for understanding and querying the data:

• CE_UPGRADE_ID — The surrogate primary key (PK CE_UPG_BA_USES_PK) and sole column of the unique index CE_UPG_BA_USES_U1. This is the business-key candidate that uniquely identifies each upgrade row and is the column the user references when searching "ce_upg_ba_uses_u1".
• CE_BANK_ACCT_USE_ID — The identifier for the bank account use being staged.
• SOURCE_APPLICATION_ID and SOURCE_PK_ID — Together they identify the originating application and the source row's primary key, enabling traceability back to legacy data.
• PARENT_UPGRADE_ID — Links child records to a parent upgrade grouping.
• UPGRADE_STATUS — Tracks processing state; documented values are SUCCESS, PROCESSED, UNPROCESSED, and INVALID.
• GROUP_ID, PRIMARY_ACCT_USE_FLAG, and SECONDARY_ACCT_USE_FLAG — Manage account use grouping and identify primary versus secondary records.
• PARTY_CODE and ACCOUNT_NUMBER — External Trading (XTR) party and account identifiers used for reconciliation.
• LEGAL_ENTITY_ID — Foreign key to FV_LEGAL_ENTITIES, anchoring the account use to a legal entity.
• ORG_ID and ORG_PARTY_ID — Multi-organization context for the record.
• Use-enable flags (AP_USE_ENABLE_FLAG, AR_USE_ENABLE_FLAG, XTR_USE_ENABLE_FLAG, PAY_USE_ENABLE_FLAG, CE_USE_ENABLE_FLAG) — Indicate which subledgers may use the account.
• Standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and the sixteen ATTRIBUTE descriptive flexfield columns.

Common Use Cases and Queries

Primary use cases revolve around monitoring and validating upgrade progress. A common query checks processing status across a given upgrade run:

• Status summary: SELECT UPGRADE_STATUS, COUNT(*) FROM CE.CE_UPG_BA_USES_ALL GROUP BY UPGRADE_STATUS;
• Error triage: SELECT CE_UPGRADE_ID, SOURCE_APPLICATION_ID, SOURCE_PK_ID, ACCOUNT_NUMBER FROM CE.CE_UPG_BA_USES_ALL WHERE UPGRADE_STATUS = 'INVALID';
• Legal entity reconciliation: Joining CE_UPG_BA_USES_ALL to FV_LEGAL_ENTITIES on LEGAL_ENTITY_ID to verify account uses are attributed to the correct legal entity.
• Source traceability: Using the CE_UPG_BA_USES_N1 index path on SOURCE_APPLICATION_ID and SOURCE_PK_ID to locate a specific legacy record.
• Group inspection: Querying by GROUP_ID with PRIMARY_ACCT_USE_FLAG = 'Y' to validate that each account use group has exactly one primary record.

Related Objects

• FV_LEGAL_ENTITIES — Referenced via the foreign key on LEGAL_ENTITY_ID, establishing legal entity ownership.
• CE_BANK_ACCT_USES_ALL — The production destination table populated from staged rows once processing completes.
• CE_UPG_BANK_ACCOUNTS_ALL — Companion upgrade staging table for bank account headers associated with the same upgrade run.
• CE_BANK_ACCOUNTS — The master bank account definition against which staged uses are ultimately created.
• CE_SECURITY_PROFILES and related access control objects — Govern which users may use the resulting account uses.
• AP_BANK_ACCOUNTS_ALL / AR_BANK_ACCOUNTS — Subledger-facing views reflecting the enabled use flags once the upgrade commits.

Because CE_UPG_BA_USES_ALL is a staging object, it is typically truncated or purged after a successful upgrade cycle and should not be treated as a persistent reporting source in a steady-state production environment.