Search Results primary_acct_owner_party_id




Overview
Explore in AI Chat

Overview

APPS.POS_SUP_AP_BANK_ACCOUNTS_V is a supplier-facing bank account view in Oracle E-Business Suite 12.1.1 and 12.2.2. It is owned by the APPS schema and is defined as a join between the external bank account view IBY_EXT_BANK_ACCOUNTS_V and the supplier mapping synonym POS_SUPPLIER_MAPPINGS. Its principal purpose is to expose banking details — account identifier, account name, account number, currency, and bank branch — alongside the corresponding Oracle Payables supplier (vendor) identifier. This correlation between a bank account and a vendor record is the view's central value proposition.

The join predicate is x1.primary_acct_owner_party_id = pmap.party_id. In other words, the view resolves the owning party of a bank account through the IBY Payments structure and maps that party to a vendor through the supplier mappings table. This makes the view a lightweight bridge between the Payments (IBY) and Payables (AP) schemas, suited to reporting and integration rather than transactional processing.

Underlying Base Objects

  • IBY_EXT_BANK_ACCOUNTS_V (VIEW). This is the primary source of banking attributes. It is the external bank account view in the IBY (Oracle Payments) product family, and it supplies bank_account_id, bank_account_name, bank_account_number, currency_code, branch_party_id, and the pivotal primary_acct_owner_party_id column used in the join.
  • POS_SUPPLIER_MAPPINGS (SYNONYM). The synonym referenced in the view definition resolves to the supplier mapping source that links a party_id to a vendor_id. It is the lookup that translates the account owner party into a supplier identifier recognizable throughout Payables and related modules.

The view therefore sits one abstraction layer above these two objects. It inherits bank data from the IBY view and supplier identity from POS_SUPPLIER_MAPPINGS, performing an inner join on party identity. Because it queries a view rather than base tables, it is read-only and best treated as a reporting surface.

Key Columns

  • bank_account_id — Unique identifier for the external bank account, sourced from IBY_EXT_BANK_ACCOUNTS_V.
  • bank_account_name — Descriptive account name.
  • bank_account_number (bank_account_num) — The account number itself, aliased in the view as bank_account_num.
  • currency_code — Currency in which the account is denominated.
  • bank_branch_id — The bank branch party identifier, aliased from branch_party_id.
  • vendor_id — The supplier identifier obtained via the join to POS_SUPPLIER_MAPPINGS.
  • primary_acct_owner_party_id — Although consumed internally in the join predicate rather than projected in the outer SELECT, this column is the linkage key users search on. It identifies the party that owns the account and is the basis for establishing the vendor relationship.

Common Use Cases and Queries

The view is typically used to reconcile supplier records against their bank accounts, to feed third-party payment or treasury reporting, or to validate that each vendor has a properly mapped account. A representative query joining the view to supplier header information follows:

  • SELECT bank_account_id, bank_account_name, bank_account_num, currency_code, bank_branch_id, vendor_id FROM ap_suppliers s, pos_sup_ap_bank_accounts_v b WHERE s.vendor_id = b.vendor_id;
  • SELECT vendor_id, currency_code, COUNT(*) FROM pos_sup_ap_bank_accounts_v GROUP BY vendor_id, currency_code;
  • SELECT * FROM pos_sup_ap_bank_accounts_v WHERE bank_account_num = :p_account_number;

Because the join on primary_acct_owner_party_id = party_id is an inner join, accounts whose owning party has no supplier mapping are excluded. Reports requiring full account coverage should therefore consider querying IBY_EXT_BANK_ACCOUNTS_V directly.