Search Results contact_area_code

Overview

APFV_BANK_ACCOUNTS is a business view in the Oracle Payables (AP) module of Oracle E-Business Suite. It exposes a subset of bank account information maintained in the Payables application, presenting the data in a form suited to reporting, inquiry, and integration scenarios. In EBS 12.1.1 the view surfaces data from the AP_BANK_ACCOUNTS table, which holds the operational bank account definitions; in 12.2.2, with the introduction of the Payments (IBY) module as the system of record for payment-related entities, the same AP_BANK_ACCOUNTS table continues to be exposed through the view for backward compatibility, though its contents may be maintained by IBY logic.

The view is described in the ETRM metadata as a "Business view" and is documented as not implemented in the reference database — meaning the definition is shipped with the product but the view may not exist in every environment, particularly where a given module or patch level was not applied. The view text carries a WITH READ ONLY clause, confirming its intended read-only consumption for reporting and integration.

Underlying Base Objects

The documented source object for APFV_BANK_ACCOUNTS is AP_BANK_ACCOUNTS_ALL. The view's WHERE clause filters on ORG_ID through the multi-org security predicate _SEC:ACC.ORG_ID, meaning the view is secured by the Oracle multi-org (MO) operating unit model. Only rows whose ORG_ID is accessible to the current responsibility are returned.

The view text also embeds two descriptor flexfield references — _DF:SQLAP:AP_BANK_ACCOUNTS:ACC and _DF:JG:JG_AP_BANK_ACCOUNTS:ACC — indicating that descriptive flexfield context and attribute columns are dynamically injected at runtime. This allows the view to carry DFF data without those columns being statically listed in the definition. The ETRM metadata documents no other referenced base objects.

Key Columns

The view exposes business-friendly aliases over the underlying table columns. Notable attributes include:

• BANK_ACCOUNT_ID — primary identifier for the bank account record.
• BANK_ACCOUNT_NAME and ALTERNATE_BANK_ACCOUNT_NAME — the primary and alternate display names of the bank account. The alternate name (sourced from BANK_ACCOUNT_NAME_ALT) is the object most frequently queried when users search for "alternate_bank_account_name," as it provides a secondary descriptive label often used for local-language or bank-specific naming.
• BANK_ACCOUNT_NUMBER — the account number itself.
• BANK_ACCOUNT_TYPE and the lookup-descriptor column _LA:ACCOUNT_TYPE — internal type code and its decoded lookup meaning from AP_LOOKUP_CODES.
• MULTICURRENCY_ALLOWED_FLAG and POOLED_ACCOUNT_FLAG — flags controlling multi-currency use and pooled account behavior.
• MAXIMUM_PAYMENT_BATCH_OUTLAY, MINIMUM_PAYMENT_AMOUNT, and MAXIMUM_PAYMENT_AMOUNT — payment control thresholds.
• ZERO_PAYMENTS_ALLOWED_FLAG — whether zero-value payments are permitted.
• ACCOUNT_HOLDER_NAME and ALTERNATE_ACCOUNT_HOLDER_NAME — the account holder's name and its alternate form.
• Contact columns (prefix, first, middle, last, title, area code, phone) and EFT_USER_NUMBER — bank contact and EFT routing details.
• BANK_BRANCH_ID and CURRENCY_CODE — branch linkage and default currency.
• INACTIVE_DATE — date on which the account becomes inactive.
• Audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY) and DFF columns (_DF, _DF:GLBL).

Common Use Cases and Queries

The view is commonly used by reporting tools, custom concurrent programs, and outbound integrations that need a flattened, security-filtered list of bank accounts. A typical use case is retrieving the alternate bank account name alongside the primary name for reconciliation or bank file generation.

Sample query to fetch bank accounts with their alternate names:

• SELECT BANK_ACCOUNT_ID, BANK_ACCOUNT_NAME, ALTERNATE_BANK_ACCOUNT_NAME, BANK_ACCOUNT_NUMBER, CURRENCY_CODE FROM APFV_BANK_ACCOUNTS WHERE INACTIVE_DATE IS NULL;

Because the view enforces the multi-org security predicate, running this query under a specific operating unit returns only the accounts accessible to that organization. Integrators should note the read-only nature of the view and avoid attempting DML against it. When the alternate name is not populated, it is typically because BANK_ACCOUNT_NAME_ALT was left blank on the account definition.