Search Results maximum_payment_amount

Overview

APBV_BANK_ACCOUNTS is a business view in the Oracle Payables (AP) module that consolidates bank account master data used for payment processing, electronic funds transfer (EFT), and treasury-related reporting. In Oracle EBS 12.1.1 and 12.2.2, this view serves as a simplified, read-only projection of the underlying bank account definition tables, exposing a single row per bank account alongside its branch, currency, and account holder attributes.

The view is particularly relevant to users and integrators searching for account_holder_name, which is the legal name of the party or entity that owns the bank account. This column is widely used in remittance advice generation, EFT payment files (for example NACHA, SEPA, and BACS outbound formats), positive pay extracts, and payment reconciliation reports. Because APBV_BANK_ACCOUNTS presents the account holder name together with the bank account number, bank branch identifier, currency, and EFT user number, it is a convenient single-source object for building payment-facing extracts without joining multiple tables manually.

The view is defined with the WITH READ ONLY clause, meaning it cannot be used for DML operations. It is intended strictly for query, reporting, and integration read paths.

Underlying Base Objects

The view text is defined entirely over AP_BANK_ACCOUNTS_ALL, aliased as ACC. This is the multi-organization (ALL) table that stores bank account definitions across all operating units. The WHERE clause references a bind-style token, '_BIS:ACC.ORG_ID' IS NOT NULL, which is the standard Business Intelligence System (BIS) multi-org security construct. At runtime in an Oracle EBS environment, this token is substituted so that the view returns only bank accounts belonging to the operating units the querying responsibility or user is authorized to access.

The ETRM metadata notes "Referenced base objects: none documented" and "Not implemented in this database," which indicates the view is documented in the ETRM repository but was not instantiated in the documentation authoring database. In a live EBS 12.1 or 12.2 instance, APBV_BANK_ACCOUNTS is created over AP_BANK_ACCOUNTS_ALL, which in turn draws its branch, currency, and payment attributes from the broader banking schema, including AP_BANK_BRANCHES and related lookup tables.

Key Columns

• BANK_ACCOUNT_ID — Primary identifier of the bank account; foreign key to AP_BANK_ACCOUNTS_ALL.
• BANK_ACCOUNT_NAME / ALTERNATE_BANK_ACCOUNT_NAME — Internal and alternate descriptive names for the account.
• BANK_ACCOUNT_NUMBER — The actual account number at the bank.
• ACCOUNT_HOLDER_NAME / ALTERNATE_ACCOUNT_HOLDER_NAME — The legal name of the account owner, essential for EFT files, remittance advices, and positive pay.
• BANK_BRANCH_ID — Identifies the bank branch associated with the account.
• CURRENCY_CODE — Currency in which the account is denominated.
• BANK_ACCOUNT_TYPE — Classification such as CHECKING or SAVINGS.
• EFT_USER_NUMBER — Reference identifier supplied by the bank for EFT processing.
• MULTICURRENCY_ALLOWED_FLAG / POOLED_ACCOUNT_FLAG — Flags controlling multi-currency use and pooled (zero-balance) account behavior.
• MINIMUM_PAYMENT_AMOUNT / MAXIMUM_PAYMENT_AMOUNT / MAXIMUM_PAYMENT_BATCH_OUTLAY — Payment amount thresholds governing disbursement.
• CONTACT_* columns — Contact name, title, phone, and area code for the account.
• INACTIVE_DATE — The date on which the account became inactive; useful for filtering to active accounts only.

Common Use Cases and Queries

Typical use cases include EFT payment file generation that requires the account holder name, positive pay reporting, banking master data extracts for data warehousing, and audit queries verifying that inactive accounts are no longer used for new payments.

Example 1 — retrieve account holder and account details for a specific internal account name:

SELECT bank_account_id, bank_account_name, bank_account_number, account_holder_name, bank_branch_id, currency_code, eft_user_number FROM apbv_bank_accounts WHERE bank_account_name = :p_name;

Example 2 — list of active accounts with their holders, for EFT and remittance preparation:

SELECT acc.bank_account_id, acc.bank_account_name, acc.account_holder_name, acc.bank_account_number, acc.bank_branch_id, acc.currency_code FROM apbv_bank_accounts acc WHERE acc.inactive_date IS NULL ORDER BY acc.bank_account_name;

Example 3 — locate accounts by EFT user number during bank file troubleshooting:

SELECT bank_account_id, bank_account_name, account_holder_name, eft_user_number, currency_code FROM apbv_bank_accounts WHERE eft_user_number = :p_eft_num;

Because the view is multi-org secured via the BIS token, queries automatically respect the operating unit context of the session. Where the account holder name is required for outbound banking formats, APBV_BANK_ACCOUNTS is the most direct documented source.