Results for “bank_name”

50+ results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The APPS.XTR_COMPANY_ACCT_LOV_V view is a Treasury (XTR) module dictionary object in Oracle E-Business Suite 12.1.1 and 12.2.2. It is a VALID database view owned by the APPS schema, and its purpose is to expose bank account short name, bank account number, and bank name data for a given company. It is typically used as the source for list-of-values (LOV) components within Treasury and adjacent modules where a user must select a company bank account.

The view does not store data; it derives its result set from underlying Treasury views and party information at query time. Because the object name carries the _LOV_V suffix, it is intended primarily as a presentation and selection layer rather than as a transactional or storage object. Its columns are optimized for lookup and display, matching the information a user or integration needs to identify a bank account unambiguously.

For reporting and integration purposes the view offers a stable, pre-joined projection of account and bank attributes. This spares callers from having to understand the join between the Treasury bank accounts view and party information, and it applies Treasury-specific filter conditions so that only accounts valid for selection are returned.

Underlying Base Objects

The documented referenced base objects are XTR_BANK_ACCOUNTS_V (a view) and XTR_PARTY_INFO (referenced through a synonym). The view text establishes the relationship explicitly:

Two filter predicates are applied to control which accounts appear. NVL(A.AUTHORISED,'N') = 'Y' ensures only authorised accounts are exposed. NVL(A.SETOFF_ACCOUNT_YN,'N') != 'Y' excludes accounts flagged as setoff accounts. Together these conditions restrict the LOV to active, selectable bank accounts.

Key Columns

  • COMPANY_CODE — taken from A.PARTY_CODE, identifies the company or party that owns the bank account.
  • CURRENCY — taken from A.CURRENCY, the currency in which the bank account is denominated; important for filtering accounts in multi-currency Treasury operations.
  • BANK_SHORT_CODE — taken from A.BANK_SHORT_CODE. This is the column users most frequently search on when looking for a bank identifier, and it is the attribute referenced by the search term "bank_short_code".
  • ACCOUNT_NUMBER — taken from A.ACCOUNT_NUMBER, the bank account number itself.
  • BANK_NAME — taken from B.SHORT_NAME of XTR_PARTY_INFO, the short name of the bank. Because the join is outer, this value may be null when no matching party record exists.

Common Use Cases and Queries

Typical scenarios include building a Treasury bank account list of values, validating a supplied bank short code or account number during data entry or interface processing, and joining account selection results to cash management or payment data. A simple account lookup for a single company and currency can be written as:

SELECT company_code, currency, bank_short_code, account_number, bank_name FROM apps.xtr_company_acct_lov_v WHERE company_code = :p_company AND currency = :p_currency ORDER BY bank_short_code, account_number;

To search specifically by the bank short code attribute:

SELECT company_code, currency, bank_short_code, account_number, bank_name FROM apps.xtr_company_acct_lov_v WHERE bank_short_code = :p_bank_short_code;

Because the view already enforces the AUTHORISED and SETOFF_ACCOUNT_YN conditions, callers need not repeat those predicates. Integrations should nonetheless treat BANK_NAME as nullable due to the outer join, and should filter on COMPANY_CODE and CURRENCY to keep result sets small and deterministic. All queries should be executed with the APPS schema or a synonym granting read access to this view.