Search Results ap_bank_charges




Overview
Explore in AI Chat

Overview

The AP_BANK_CHARGES table is a core data object within the Oracle E-Business Suite Payables (AP) module. It serves as the master repository for defining bank charge rules, which are fees levied by financial institutions for processing payments. This table is essential for automating the calculation, accrual, and accounting of these charges during payment processing, particularly for electronic funds transfers (EFT) and wire payments. By maintaining these definitions centrally, the system ensures consistent application of bank fee policies across all payable transactions, directly impacting the accuracy of financial liabilities and cash management.

Key Information Stored

The table's primary key is BANK_CHARGE_ID, which uniquely identifies each charge rule. Critical foreign key columns establish relationships with other master data, defining the operational scope of the charge. The TRANSFERRING_BANK_BRANCH_ID and RECEIVING_BANK_BRANCH_ID link to AP_BANK_BRANCHES, allowing charges to be configured for specific sending and receiving bank accounts. The CURRENCY_CODE foreign key to FND_CURRENCIES specifies the currency for which the charge is valid. While the provided metadata does not list all columns, typical data stored includes charge calculation methods (flat fee, percentage-based, tiered), effective dates, charge types (e.g., "SWIFT"), and associated general ledger accounts for accrual and expense recognition.

Common Use Cases and Queries

A primary use case is the system's automatic selection of the appropriate bank charge during payment creation, based on the payment currency, bank accounts involved, and payment method. For reporting and analysis, common queries involve listing all active charge definitions or analyzing charges applied over a period. For instance, to audit charges for a specific bank branch, one might use:

  • SELECT abc.bank_charge_id, abc.currency_code, abb.bank_name FROM ap_bank_charges abc, ap_bank_branches abb WHERE abc.transferring_bank_branch_id = abb.bank_branch_id AND abb.bank_name LIKE '%BankName%';

Another critical scenario is troubleshooting payment batches where unexpected bank charges are applied, requiring joins between AP_BANK_CHARGES, AP_BANK_CHARGE_LINES (for detailed calculation components), and payment tables like AP_CHECKS_ALL.

Related Objects

AP_BANK_CHARGES is a central hub in the bank charges data model. Its most direct relationship is with the child table AP_BANK_CHARGE_LINES, which holds the detailed line-level calculation rules (e.g., minimum charge, maximum charge, rate) for each BANK_CHARGE_ID. It depends on reference tables AP_BANK_BRANCHES for bank account details and FND_CURRENCIES for valid currency codes. The charge definitions stored here are referenced by the payment engine within the Payables module when creating payments, influencing tables such as AP_SELECTED_INVOICES_ALL and AP_INVOICE_PAYMENTS_ALL for accruals, and ultimately AP_CHECKS_ALL for the final payment and charge accounting.