Search Results ce_bank_accounts




Overview

The CE_BANK_ACCOUNTS table is the central repository for all bank account master data within Oracle E-Business Suite Cash Management (CE). It represents the physical bank account held at a financial institution, serving as the core entity for all treasury, payment, and cash management operations. Each record in this table must be affiliated with a single bank branch, establishing a critical hierarchical relationship within the bank account model. Its integrity is paramount, as it is referenced by numerous transactional and setup tables across the Financials, Payables, Receivables, and Payments modules to facilitate cash positioning, bank reconciliation, and electronic funds transfer.

Key Information Stored

The table's primary key is BANK_ACCOUNT_ID, a unique system-generated identifier. Essential foreign key columns define its relationships: BANK_ID and BANK_BRANCH_ID link to the HZ_PARTIES table to identify the financial institution and its specific branch. ACCOUNT_HOLDER_ID and ACCOUNT_OWNER_PARTY_ID also reference HZ_PARTIES to specify the legal account holder and owner, while ACCOUNT_OWNER_ORG_ID links to HR_ALL_ORGANIZATION_UNITS to assign internal organizational ownership. Other significant columns include the account number, currency, account type (e.g., checking, savings), and status. The INTEREST_SCHEDULE_ID foreign key links to CE_INTEREST_SCHEDULES, enabling interest calculation tracking for the account.

Common Use Cases and Queries

This table is fundamental for reporting on bank account structures, validating setups for payment processing, and troubleshooting integration issues. A common query retrieves all active accounts for a specific operating unit or legal entity by joining with CE_BANK_ACCT_USES_ALL. Technical consultants often query it to diagnose payment failures by verifying the internal bank account setup referenced in Payment Manager (IBY) tables. For cash positioning reports, the table is joined with CE_BANK_ACCT_BALANCES and CE_PROJECTED_BALANCES. A typical validation SQL pattern is:

  • SELECT ba.bank_account_name, ba.bank_account_num, ba.currency_code, bu.primary_flag FROM ce_bank_accounts ba, ce_bank_acct_uses_all bu WHERE ba.bank_account_id = bu.bank_account_id AND bu.org_id = &org_id AND ba.account_status = 'A';

Related Objects

CE_BANK_ACCOUNTS has extensive relationships across the application. It is the parent table for key subsidiary tables like CE_BANK_ACCT_USES_ALL (which assigns accounts to legal entities or operating units) and CE_BANK_ACCT_BALANCES. Crucially, it is referenced by the core Oracle Payments (IBY) tables—such as IBY_PAYMENTS_ALL, IBY_DOCS_PAYABLE_ALL, and IBY_PAY_INSTRUCTIONS_ALL—to designate both internal and external bank accounts for transactions. It also feeds data into Cash Management tables for balances (CE_PROJECTED_BALANCES) and reconciliations (CE_STATEMENT_HEADERS), and interfaces with Federal Financials (FV_AR_BATCHES_ALL, FV_INTERIM_CASH_RECEIPTS_ALL).