Search Results ap_bank_accounts_all




Overview
Explore in AI Chat

Overview

The AP_BANK_ACCOUNTS_ALL table is a core data object within the Oracle E-Business Suite Payables (AP) module, serving as the master repository for all bank accounts defined for payment and receipt processing. It is a multi-organization table, as indicated by the "_ALL" suffix, meaning it stores records for all operating units within an EBS instance, typically distinguished by the ORG_ID column. This table is fundamental to the Cash Management and Payables functions, enabling the configuration of bank accounts for electronic funds transfers (EFT), check payments, and bank statement reconciliation. Each record defines the account's banking details, associated general ledger (GL) accounts for various accounting activities, and control parameters for payment processing.

Key Information Stored

The table's structure is defined by its primary and foreign keys, which highlight its critical data elements and integrations. The primary key is BANK_ACCOUNT_ID, a unique system identifier. A unique key on BANK_ACCOUNT_NAME enforces naming uniqueness. Crucially, the table maintains a foreign key relationship to AP_BANK_BRANCHES (via BANK_BRANCH_ID), linking the account to its specific bank branch. It also holds the account CURRENCY_CODE, linked to FND_CURRENCIES. The most significant set of foreign keys are to GL_CODE_COMBINATIONS, defining the specific GL accounts used for different transaction types. These include columns such as ASSET_CODE_COMBINATION_ID (the main cash account), BANK_ERRORS_CCID, UNAPPLIED_CCID, UNIDENTIFIED_CCID, and FUTURE_DATED_PAYMENT_CCID, among others listed in the metadata. This design centralizes the complete financial and operational setup for a bank account.

Common Use Cases and Queries

This table is central to reporting and troubleshooting payment-related processes. A common use case is generating a list of all bank accounts for a specific operating unit, including their associated cash GL account. Another critical scenario involves validating the setup before a payment batch is submitted, ensuring all required accounting flexfields (CCIDs) are populated. Sample queries often join to AP_BANK_BRANCHES and GL_CODE_COMBINATIONS.

  • Listing Bank Accounts by Operating Unit: SELECT BANK_ACCOUNT_NAME, BANK_ACCOUNT_NUM, CURRENCY_CODE FROM AP_BANK_ACCOUNTS_ALL WHERE ORG_ID = :org_id ORDER BY 1;
  • Verifying GL Account Assignments: SELECT aba.BANK_ACCOUNT_NAME, aba.ASSET_CODE_COMBINATION_ID, gcc.segment1 FROM AP_BANK_ACCOUNTS_ALL aba, GL_CODE_COMBINATIONS gcc WHERE aba.ASSET_CODE_COMBINATION_ID = gcc.CODE_COMBINATION_ID AND aba.ORG_ID = :org_id;

Related Objects

As evidenced by its extensive foreign key constraints, AP_BANK_ACCOUNTS_ALL is a hub table with dependencies across financial modules. Its primary relationship is with AP_BANK_BRANCHES, which stores branch details. The numerous links to GL_CODE_COMBINATIONS underpin all accounting entries for bank transactions. The link to AR_RECEIVABLES_TRX_ALL (via BR_STD_RECEIVABLES_TRX_ID) supports automatic receipt creation in Receivables. For payment processing, it is referenced by payment documents in tables like AP_CHECKS_ALL and AP_INVOICES_ALL. In Cash Management, it is essential for bank statement reconciliation (CE_STATEMENTS). The Oracle Payables API AP_BANK_ACCOUNT_PKG is the primary programmatic interface for creating and maintaining records in this table.