Results for “ce_upga_ba_uses_all”

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

Overview

CE_UPGA_BA_USES_ALL is a Cash Management (CE) audit table that resides in the CE schema and holds the VALID status in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented function is to serve as an audit table for CE_UPG_BA_USES_ALL, the working table used during the bank account upgrade process. In practice, this means CE_UPGA_BA_USES_ALL captures a trailing record of the bank account usage rows that were processed during an upgrade of bank account data, allowing the outcome of the upgrade to be reviewed, reconciled, or retained for troubleshooting after the working records in CE_UPG_BA_USES_ALL have been consumed or purged.

The object is recorded as a standalone table. Using a heuristic Data Vault classification mined from its foreign key structure, it is modeled as a standalone entity rather than a hub, link, or satellite. Its distinguishable grain is driven by a single-column primary key, CE_UPGA_BA_USES_PK, defined on CE_UPGRADE_ID. The documented physical schema in ETRM 12.2.2 lists 46 columns.

Key Information Stored

The most significant columns fall into three groups: upgrade identity, bank account usage attributes, and standard audit columns.

• CE_UPGRADE_ID — primary key and the surrogate identifier for the audit record (CE_UPGA_BA_USES_PK).
• CE_BANK_ACCT_USE_ID — business-key candidate linking the audit record to the original bank account use being upgraded.
• PARENT_UPGRADE_ID — reference to a parent upgrade, useful for tracing chained upgrade operations.
• UPGRADE_STATUS — status of the upgrade for that usage record.
• PRIMARY_ACCT_USE_FLAG / SECONDARY_ACCT_USE_FLAG — indicate whether the usage is primary or secondary.
• PRIMARY_FLAG, POOLED_FLAG, END_DATE — usage role, pooling indicator, and effective end date.
• AP_USE_ENABLE_FLAG, AR_USE_ENABLE_FLAG, XTR_USE_ENABLE_FLAG, PAY_USE_ENABLE_FLAG — per-product enablement flags for Payables, Receivables, Treasury, and Payments.
• EDISC_RECEIVABLES_TRX_ID, UNEDISC_RECEIVABLES_TRX_ID, BR_STD_RECEIVABLES_TRX_ID — Receivables transaction references for earned discount, unearned discount, and standard.
• DIRECT_DEBIT_AUTH_FLAG — direct debit authorization indicator.
• ORG_ID / ORG_PARTY_ID — operating unit and party context.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID — standard audit and concurrent program columns that identify who ran the upgrade and when.

Common Use Cases and Queries

The primary use case is post-upgrade reconciliation: confirming that every bank account usage processed during an upgrade reached an expected UPGRADE_STATUS and that enablement flags were preserved. A representative query joins the audit table to the concurrent program request:

• SELECT ce_upgrade_id, ce_bank_acct_use_id, upgrade_status, request_id FROM ce.ce_upga_ba_uses_all WHERE request_id = :p_request_id;
• SELECT ce_bank_acct_use_id, ap_use_enable_flag, ar_use_enable_flag, pay_use_enable_flag, xtr_use_enable_flag FROM ce.ce_upga_ba_uses_all WHERE org_id = :p_org_id AND end_date IS NULL;
• SELECT parent_upgrade_id, COUNT(*) FROM ce.ce_upga_ba_uses_all GROUP BY parent_upgrade_id;

Reporting typically targets failed or unresolved upgrade statuses, flag mismatches between the legacy and upgraded usage records, and audit trails for compliance reviews of bank account configuration changes.

Related Objects

• CE_UPG_BA_USES_ALL — the source working table this object audits; join on CE_UPGRADE_ID.
• CE_BANK_ACCT_USES_ALL — the live bank account usage table; join on CE_BANK_ACCT_USE_ID.
• CE_BANK_ACCOUNTS — bank account master; reached through CE_BANK_ACCT_USE_ID.
• FND_CONCURRENT_REQUESTS — join on REQUEST_ID for program and request context.
• FND_APPLICATION — join on PROGRAM_APPLICATION_ID.
• FND_USER — join on CREATED_BY and LAST_UPDATED_BY for user attribution.
• AR_RECEIVABLES_TRX_ALL — join on the three receivables transaction ID columns.
• HR_ALL_ORGANIZATION_UNITS — join on ORG_ID or ORG_PARTY_ID for operating unit context.