CE Bank Branches – Oracle EBS SQL Report
Oracle E-Business Suite SQL report from the Enginatics Library powered by Blitz Report™.
Overview
This Report is the repository of all bank branches covering both internal and external bank accounts and will list the bank branches along with an indication of usage: -Internal -Supplier -Customer
Report Parameters
Bank Name, Bank Branch Name, Show Internal Usage, Show Supplier Usage, Show Customer Usage
Oracle EBS Tables Used
ce_bank_accounts, iby_ext_bank_accounts, iby_pmt_instr_uses_all, iby_external_payees_all, ap_suppliers, iby_external_payers_all, ce_bank_branches_v, ce_banks_v, fnd_territories_vl
Report Categories
Related Reports
AP Supplier Upload, AP Suppliers, AR Customer Upload, AR Customers and Sites
Running This SQL Without Blitz Report
Some Oracle EBS SQL reports in this library require functions from the utility package xxen_util. Install it before running the SQL directly against your Oracle EBS database.
Download & Import Options
| Resource | Link |
|---|---|
| Excel Example Output | CE Bank Branches 02-Aug-2024 090909.xlsx |
| Blitz Report™ XML Import | CE_Bank_Branches.xml |
| Full SQL on Enginatics | www.enginatics.com/reports/ce-bank-branches/ |
Executive Summary
The CE Bank Branches report serves as a master directory of all bank branches defined in the system, covering both internal (company-owned) and external (supplier/customer) banks. It provides a clear view of the banking network relationships, indicating whether a branch is used for internal treasury operations, supplier payments, or customer receipts. This report is vital for Master Data Management (MDM) teams to maintain a clean and accurate banking hierarchy.
Business Challenge
As organizations grow, the number of bank branches in the system can proliferate, leading to:
- Duplicate Records: Multiple entries for the same physical branch (e.g., “Citibank NY” vs. “Citi New York”).
- Obsolete Data: Branches that are no longer in use but remain active in the system.
- Routing Errors: Payments failing because they are routed to an incorrect or inactive branch code (SWIFT/BIC).
Maintaining a clean “Golden Source” of bank branch data is critical for payment processing efficiency.
Solution
This report lists every bank branch along with its parent Bank and its usage flags.
Key Features:
- Usage Indicators: Clearly marks if a branch is used for:
- Internal: Linked to the company’s own bank accounts.
- Supplier: Linked to supplier payment details.
- Customer: Linked to customer remittance details.
- Global Coverage: Includes branches from all territories and countries.
- Integration: Links to the underlying party tables (
HZ_PARTIES) to show the full relationship structure.
Architecture
The report queries CE_BANK_BRANCHES_V and CE_BANKS_V for the core branch data. It joins to IBY (Payments) tables to determine usage.
Key Tables:
CE_BANK_BRANCHES_V: The primary view for bank branch definitions.CE_BANK_ACCOUNTS: To identify internal usage.IBY_EXT_BANK_ACCOUNTS: To identify external (supplier/customer) usage.AP_SUPPLIERS: To link branches to specific suppliers.
Impact
- Data Hygiene: Enables the identification and cleanup of duplicate or unused branch records.
- Payment Success: Reduces payment rejections caused by invalid branch routing codes.
- Compliance: Helps ensure that the banking master data matches official bank records.
Useful Links
- Blitz Report™ – World’s Fastest Oracle EBS Reporting Tool
- Oracle Discoverer Replacement – Import Worksheets into Blitz Report™
- Oracle EBS Reporting Toolkits by Blitz Report™
- Blitz Report™ FAQ & Community Q&A
- Supply Chain Hub by Blitz Report™
- Blitz Report™ Customer Case Studies
- Oracle EBS Reporting Blog
- Oracle EBS Reporting Resource Centre
© 2026 Enginatics