Search Results bic_number




Overview
Explore in AI Chat

Overview

IBY_PAYEE_ASSIGNED_BANKACCT_V is an Oracle E-Business Suite view owned by the APPS schema within the IBY (Payments) product. It presents the association between external payees and the bank accounts assigned to them for disbursement purposes. In payment processing terminology, an "instrument assignment" links a payee to a specific payment instrument — in this case a bank account — and defines ordering, validity dates, and payment function. This view therefore exposes the effective set of bank account assignments that a payee may use when funds are disbursed.

Because the view joins payee header information with instrument assignment records and the corresponding external bank account details, it serves as a consolidated reporting surface for payables and payments integration. It is commonly referenced by reporting tools, custom concurrent programs, and interfaces that need to resolve which bank account, branch, and related identifiers belong to a given payee party. The availability of the BRANCH_NAME column makes it directly relevant to searches involving payee bank branch details.

Underlying Base Objects

The documented view definition references three base objects joined together. IBY_PMT_INSTR_USES_ALL supplies the instrument assignment rows; IBY_EXTERNAL_PAYEES_ALL supplies the payee party, site, and organization context; and IBY_PAYEE_ALL_BANKACCT_V supplies the external bank account attributes. The ETRM metadata further identifies the underlying base objects as CE_BANK_BRANCHES_V, IBY_EXTERNAL_PAYEES_ALL, IBY_EXT_BANK_ACCOUNTS, and IBY_PMT_INSTR_USES_ALL. The branch name and branch number attributes ultimately trace to the bank branch definition, exposed via CE_BANK_BRANCHES_V, while the account-level attributes are drawn from IBY_EXT_BANK_ACCOUNTS through the IBY_PAYEE_ALL_BANKACCT_V layer.

The join conditions are restrictive by design. Instrument assignments are joined to bank accounts on INSTRUMENT_ID = EXT_BANK_ACCOUNT_ID and to payees on EXT_PMT_PARTY_ID = EXT_PAYEE_ID. Only rows where INSTRUMENT_TYPE is 'BANKACCOUNT' and PAYMENT_FLOW is 'DISBURSEMENT' are returned, so the view reflects outbound payment assignments exclusively.

Key Columns

Common Use Cases and Queries

A frequent requirement is identifying the bank and branch assigned to a payee for disbursement. The following query returns payee assignments together with their branch details:

SELECT party_id, supplier_site_id, account_number, bank_name, branch_name, branch_number, currency_code FROM apps.iby_payee_assigned_bankacct_v WHERE branch_name IS NOT NULL;

To resolve the currently effective assignment for a payee, filter on the validity dates and order of preference:

SELECT party_id, instr_assignment_id, account_number, branch_name FROM apps.iby_payee_assigned_bankacct_v WHERE party_id = :p_party_id AND TRUNC(SYSDATE) BETWEEN start_date AND NVL(end_date, TRUNC(SYSDATE)) ORDER BY order_of_preference;

For reporting on bank branch distribution, aggregate by branch name and number. Because the view is restricted to the disbursement flow and bank account instruments, results reflect only outbound payment assignments and exclude other instrument types. Queries should therefore not be assumed to represent all payee instruments; they represent the disbursement bank account subset defined by the view predicate.