Search Results ap_bank_branches




Overview
Explore in AI Chat

Overview

The AP_BANK_BRANCHES table is a core master data table within the Oracle E-Business Suite Payables module (AP). It serves as the central repository for storing detailed information about the banking institutions and their specific branches used by an organization for its financial transactions. This table is fundamental to the setup and execution of payment processes, including electronic funds transfers (EFT), check printing, and bank reconciliations. Each record defines a unique bank branch, which can then be associated with one or more internal bank accounts defined in the AP_BANK_ACCOUNTS_ALL table. Its integrity is critical for ensuring accurate payment routing and financial reporting.

Key Information Stored

The table stores comprehensive branch details, with key identifiers enforced by primary and unique keys. The primary key is BANK_BRANCH_ID, a unique internal identifier. Critical business keys include BANK_NUM (the bank identifier number, like a routing number) and the combination of BANK_NAME and BANK_BRANCH_NAME, both enforced by unique constraints (UK1 and UK2) to prevent duplicate entries. Other significant columns link to configuration and processing logic, such as CLEARING_HOUSE_ID (for interbank settlements), TRANSMISSION_PROGRAM_ID and PRINTING_PROGRAM_ID (linking to payment formatting programs in AP_PAYMENT_PROGRAMS), TP_HEADER_ID (for Electronic Commerce Gateway transmissions), and PAYROLL_BANK_ACCOUNT_ID for integration with HRMS.

Common Use Cases and Queries

This table is primarily queried for bank setup maintenance, payment processing support, and integration reporting. Common scenarios include validating bank branch details before creating new internal accounts, generating reports of all configured banking partners, and troubleshooting payment transmission issues. A typical query to list all bank branches with their associated internal account count would be:

  • SELECT abb.bank_name, abb.bank_branch_name, abb.bank_num, COUNT(aba.bank_account_id) AS account_count FROM ap_bank_branches abb LEFT JOIN ap_bank_accounts_all aba ON abb.bank_branch_id = aba.bank_branch_id GROUP BY abb.bank_name, abb.bank_branch_name, abb.bank_num ORDER BY 1, 2;

For technical support, queries often join to related transmission setup tables (AP_TRANSMISSIONS_SETUP, AP_BANK_TRANSMISSIONS) to diagnose electronic payment failures.

Related Objects

As indicated by its extensive foreign key relationships, AP_BANK_BRANCHES is a hub table referenced by numerous objects across financial modules. Its most direct child is AP_BANK_ACCOUNTS_ALL, which holds the specific accounts at each branch. Within Payables, it is referenced by AP_BANK_CHARGES, AP_BANK_TRANSMISSIONS, and AP_TRANSMISSIONS_SETUP for payment processing. It also integrates with Receivables (AR), where tables like AR_CASH_RECEIPTS_ALL store historical bank branch IDs. Furthermore, relationships with CE_UPG_* tables support Cash Management upgrades, and the link to ECE_TP_HEADERS facilitates electronic payment transmissions, underscoring its enterprise-wide role.