Search Results ap_bank_accounts_all




The AP_BANK_ACCOUNTS_ALL table in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 is a critical repository for storing bank account information used by the Accounts Payable (AP) module. This table serves as the foundation for managing supplier payments, electronic funds transfers (EFT), and bank reconciliation processes. Below is a detailed technical overview of its structure, purpose, and integration within Oracle EBS.

Table Overview

AP_BANK_ACCOUNTS_ALL is a multi-organization-enabled table, meaning it stores data across operating units while adhering to the Oracle Multi-Org architecture. It contains details about bank accounts, including internal accounts (used by the organization) and external accounts (belonging to suppliers or other entities). Key columns include:
  • BANK_ACCOUNT_ID: Primary key, uniquely identifying each bank account record.
  • BANK_ACCOUNT_NAME: User-defined name for the account.
  • BANK_ACCOUNT_NUM: The actual bank account number.
  • CURRENCY_CODE: The currency associated with the account.
  • BANK_ID: Foreign key linking to CE_BANKS_V (bank master data).
  • BRANCH_ID: Foreign key linking to CE_BANK_BRANCHES_V (bank branch details).
  • ORG_ID: Operating Unit identifier for Multi-Org segregation.

Functional Role

The table supports core AP functionalities:
  1. Payment Processing: Enables payment methods like checks, wire transfers, or EFTs by storing account details for payees and payers.
  2. Bank Reconciliation: Integrates with Oracle Cash Management to reconcile transactions against bank statements.
  3. Supplier Payments: Links supplier bank accounts (AP_BANK_ACCOUNT_USES_ALL) to facilitate automated payments.

Integration with Other Modules

AP_BANK_ACCOUNTS_ALL interfaces with several Oracle EBS modules:
  • Cash Management (CE): Shares bank/branch data via CE_BANKS_V and CE_BANK_BRANCHES_V.
  • Payables (AP): Maps accounts to suppliers via AP_BANK_ACCOUNT_USES_ALL.
  • General Ledger (GL): Associates accounts with GL codes for accounting entries.

Key Dependencies

The table relies on:
  • CE_BANKS_V and CE_BANK_BRANCHES_V for bank/branch validation.
  • AP_BANK_ACCOUNT_USES_ALL to define account purposes (e.g., "Supplier Payments").
  • FND_CURRENCIES for valid currency codes.

Security and Access

Access is controlled via:
  • Operating Unit Security: Data visibility is restricted by ORG_ID.
  • Oracle Function Security: Requires privileges like "Maintain Bank Accounts" (AP_BANK_ACCOUNT_MAINT).

Customization Considerations

Common extensions include:
  • Adding custom columns for local regulatory requirements.
  • Creating triggers to enforce business rules (e.g., IBAN format validation).
  • Integrating with third-party payment gateways via APIs.

Data Maintenance

Standard Oracle forms (e.g., "Bank Accounts") or APIs like AP_BANK_ACCOUNT_PKG should be used for updates to ensure data integrity. Direct SQL manipulation is discouraged.

Conclusion

The AP_BANK_ACCOUNTS_ALL table is a cornerstone of Oracle EBS's payment infrastructure, enabling secure, multi-org-compliant bank account management. Its design ensures seamless integration with AP, Cash Management, and GL while supporting global banking standards. Proper configuration and maintenance of this table are essential for accurate payment processing and financial reporting.