Search Results vendor_site_code_alt




Overview
Explore in AI Chat

Overview

AP_BANK_ACCOUNT_USES_V is a Payables (AP) reporting view that presents bank account usage assignments in a denormalized form suitable for inquiry, integration, and reporting purposes. In Oracle E-Business Suite 12.1.1 and 12.2.2, the view exposes the association between a bank account and the parties authorized to use it — vendors, vendor sites, customers, and customer site uses — together with descriptive bank and bank branch attributes. The view combines the transactional usage record with the descriptive bank account header and bank information, allowing a single query to return the account name, currency, and multi-currency designation alongside the specific use assignment.

Note that the ETRM documentation marks this object as "(Release 10SC only)" and states "Not implemented in this database." This historical annotation reflects an earlier release context; in 12.1.1 and 12.2.2 the same logical data is delivered through the standard bank account uses entities. The MULTI_CURRENCY_FLAG column identified in the user search is a bank account header attribute surfaced by the view, indicating whether the underlying bank account is enabled to hold balances in more than one currency.

Underlying Base Objects

The view is defined over two principal base objects referenced by their aliases in the view text:

The view joins the usage row to its parent bank account and branch so that each usage record is reported with fully qualified bank context. No base objects are separately documented in the ETRM entry, but the view text confirms ABAU as the driving table and ABA/ABB as the descriptive sources.

Key Columns

  • BANK_ACCOUNT_USES_ID — primary identifier of the usage assignment.
  • EXTERNAL_BANK_ACCOUNT_ID — the bank account being used, linking usage to account header.
  • VENDOR_ID, VENDOR_SITE_ID, CUSTOMER_ID, CUSTOMER_SITE_USE_ID — the party or site authorized to use the account.
  • PRIMARY_FLAG — indicates whether the usage is the primary assignment.
  • START_DATE, END_DATE — effective dating of the assignment.
  • MULTI_CURRENCY_FLAG — whether the bank account supports multiple currencies.
  • CURRENCY_CODE, SET_OF_BOOKS_ID, BANK_ACCOUNT_TYPE, ACCOUNT_TYPE — account-level classification and ledger context.
  • BANK_ACCOUNT_NAME, BANK_NAME, BANK_NUMBER — human-readable bank and account identifiers.
  • WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE) — audit tracking.

Common Use Cases and Queries

Typical scenarios include identifying all suppliers authorized on a bank account, confirming which accounts permit multi-currency disbursements, and reconciling payment setup against vendor records.

SELECT bank_account_uses_id,
       bank_account_name,
       bank_name,
       currency_code,
       multi_currency_flag,
       vendor_id,
       primary_flag
FROM   ap_bank_account_uses_v
WHERE  multi_currency_flag = 'Y'
AND    (end_date IS NULL OR end_date > SYSDATE);

A second common query lists active vendor assignments for a specific bank account:

SELECT vendor_id, vendor_site_id, start_date
FROM   ap_bank_account_uses_v
WHERE  external_bank_account_id = :account_id
AND    vendor_id IS NOT NULL;

Because the view already denormalizes account, branch, and usage data, it reduces the need for multi-table joins in custom reports and interfaces, though performance should be validated against the underlying base tables when large volumes of assignments exist.