Search Results ap_bank_account_uses_all




Overview
Explore in AI Chat

Overview

The AP_BANK_ACCOUNT_USES_ALL table is a core data object within the Oracle E-Business Suite Payables (AP) module, specifically for releases 12.1.1 and 12.2.2. It functions as the central repository for defining and managing the relationships between external bank accounts and the business entities that utilize them for payment and receipt transactions. This table enables the assignment of a single bank account to multiple parties, such as suppliers and customers, and conversely, allows a single party to be associated with multiple bank accounts. Its role is critical in the configuration of payment processes, ensuring funds are disbursed to or received from the correct financial institution accounts. As an "ALL" table, it is designed to support the multi-organization architecture (Multi-Org) of Oracle EBS, storing data partitioned by the ORG_ID column.

Key Information Stored

The table's primary purpose is to store linkage records, with its key columns defining the relationships between entities. The primary key is BANK_ACCOUNT_USES_ID. The most significant foreign key columns are EXTERNAL_BANK_ACCOUNT_ID, which references AP_BANK_ACCOUNTS_ALL to identify the specific bank branch and account, and the paired columns that identify the associated business entity. For suppliers, this includes VENDOR_ID (referencing PO_VENDORS) and optionally VENDOR_SITE_ID (referencing PO_VENDOR_SITES_ALL). For customers, it includes CUSTOMER_ID (referencing HZ_CUST_ACCOUNTS) and CUSTOMER_SITE_USE_ID (referencing HZ_CUST_SITE_USES_ALL). Additional columns typically manage the usage context, such as the primary payment method for the association, start and end dates for the assignment's validity, and the ORG_ID for multi-org partitioning.

Common Use Cases and Queries

A primary use case is troubleshooting payment setup issues or generating reports on bank account utilization. For instance, to list all supplier sites linked to a specific bank account, a common query would join AP_BANK_ACCOUNT_USES_ALL to AP_BANK_ACCOUNTS_ALL and PO_VENDOR_SITES_ALL. Another critical scenario is validating payment instructions before a check or electronic funds transfer (EFT) run, ensuring the payee has a valid, active bank account assignment. Sample SQL to find bank accounts for a specific vendor might be:

  • SELECT aba.bank_account_name, aba.bank_account_num, abau.primary_payment_method
  • FROM ap_bank_account_uses_all abau, ap_bank_accounts_all aba, po_vendors pv
  • WHERE abau.external_bank_account_id = aba.bank_account_id
  • AND abau.vendor_id = pv.vendor_id
  • AND pv.vendor_name = '&VENDOR_NAME'
  • AND abau.org_id = &ORG_ID;

Related Objects

As indicated by the foreign key metadata, AP_BANK_ACCOUNT_USES_ALL has direct and essential relationships with several fundamental tables. Its main parent is AP_BANK_ACCOUNTS_ALL, which holds the master definition of the bank account itself. For supplier-facing assignments, it references PO_VENDORS and PO_VENDOR_SITES_ALL. For customer-facing assignments (relevant in the context of customer refunds), it references HZ_CUST_ACCOUNTS and HZ_CUST_SITE_USES_ALL from the Trading Community Architecture (TCA). This table is also heavily referenced by payment processing engines within Payables and is integral to the Supplier Bank Account and Customer Bank Account setup forms in the application.