Search Results bank_account_number

Overview

POS_SUP_AP_BANK_ACCOUNTS_V is an internal Oracle E-Business Suite view owned by the APPS schema and delivered as part of the POS (iSupplier Portal) product family. It exposes supplier bank account information sourced from Oracle Payables and Payments, presenting a denormalized projection tailored to supplier-facing and self-service functionality. The view is documented as a valid object in both Oracle EBS 12.1.1 and 12.2.2 and its definition is unchanged between those releases.

The view occupies an important position in the supplier bank account data model because bank account records in EBS are held in the Payments (IBY) schema rather than in Payables (AP) directly. By joining the external bank accounts view to the iSupplier supplier mapping table, POS_SUP_AP_BANK_ACCOUNTS_V provides a single row per supplier bank account with a VENDOR_ID available to callers that operate in the supplier portal context. This makes it a convenient integration and reporting surface for code that needs supplier bank details keyed by vendor rather than by trading partner party.

Underlying Base Objects

The view is defined over two documented objects:

• IBY_EXT_BANK_ACCOUNTS_V (VIEW) — the Payments external bank accounts view, aliased as X1. This object supplies the bank account identity, name, masked or formatted account number, currency, branch party identifier, and primary account owner party identifier.
• POS_SUPPLIER_MAPPINGS (SYNONYM) — aliased as PMAP. This object supplies the mapping between a trading partner party and the corresponding VENDOR_ID.

The join condition is X1.PRIMARY_ACCT_OWNER_PARTY_ID = PMAP.PARTY_ID, meaning each row returned corresponds to a bank account whose primary owner party is mapped to a supplier record. Because one of the underlying objects is itself a view, the effective data source resolves further into the IBY Payments table structures and the supplier/party model underneath POS_SUPPLIER_MAPPINGS.

Key Columns

• BANK_ACCOUNT_ID — Primary identifier of the supplier bank account as maintained in Payments. Used as the foreign key to bank account details in IBY.
• BANK_ACCOUNT_NAME — The user-defined name of the bank account.
• BANK_ACCOUNT_NUM — The bank account number, aliased from BANK_ACCOUNT_NUMBER in IBY_EXT_BANK_ACCOUNTS_V. Note the alias differs from the source column name.
• CURRENCY_CODE — The currency in which the bank account is denominated.
• BANK_BRANCH_ID — Aliased from BRANCH_PARTY_ID in the source view. This column corresponds to the bank branch party identifier and is the column most frequently searched for when resolving bank, branch, and account relationships. It is a party identifier, not a branch row identifier in the traditional AP_BANK_BRANCHES sense.
• VENDOR_ID — The supplier (vendor) identifier obtained from POS_SUPPLIER_MAPPINGS, allowing the bank account to be directly associated with a supplier record.

Common Use Cases and Queries

A typical use is to list the bank accounts belonging to a given supplier, or to confirm that a bank account identifier belongs to the supplier expected by a portal transaction.

SELECT bank_account_id,
       bank_account_name,
       bank_account_num,
       currency_code,
       bank_branch_id,
       vendor_id
FROM   apps.pos_sup_ap_bank_accounts_v
WHERE  vendor_id = :p_vendor_id;

When the search term is bank_branch_id, the view is frequently queried to enumerate all supplier bank accounts associated with a bank branch, which supports reconciliation of branch-level banking relationships and verification of remittance routing data.

SELECT vendor_id,
       bank_account_id,
       bank_account_num,
       currency_code
FROM   apps.pos_sup_ap_bank_accounts_v
WHERE  bank_branch_id = :p_bank_branch_id;

Integration scenarios include iSupplier Portal bank account validation, supplier onboarding checks, and custom reports that require bank account data keyed by vendor. Because the view derives from Payments views and a synonym rather than from base AP tables, consumers should treat it as a read-only convenience layer and be aware that its behavior depends on the security and filtering rules applied within IBY_EXT_BANK_ACCOUNTS_V.