Results for “foreign_payment_use_flag”

50+ results




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

Overview

IBY_PAYEE_ALL_BANKACCT_V is a reporting view owned by the APPS schema within the Oracle Payments (IBY) product family. It consolidates payee bank account information into a single, denormalized presentation layer that joins account-owner records to their associated external bank accounts and their corresponding bank and branch descriptive information. The view is classified as a VIEW and carries a status of VALID in ETRM 12.2.2, and it is equally available in the 12.1.1 code line. Its principal role is to expose historical and current payee account data for reporting, integration, and inquiry purposes without requiring consumers to reassemble the underlying Payments data model manually.

The view returns every external bank account belonging to every account owner, which is why the name contains the ALL token: it does not filter by operating unit or by a single payee, leaving that restriction to the calling query. This makes it a common building block for custom reports, extracts, and interfaces that must reconcile payee banking details against treasury or payment instructions.

Underlying Base Objects

Per the documented ETRM metadata, the view is defined over three referenced objects:

The view therefore performs a three-way join: account owners to external bank accounts, and external bank accounts to bank/branch information. Note that CE_BANK_BRANCHES_V is itself a view rather than a base table, so the effective query depth extends through Cash Management objects.

Key Columns

Common Use Cases and Queries

The most common driver for querying this view is branch resolution. A typical requirement is to report all bank accounts and their branch-level detail for a set of payees, filtering explicitly on BRANCH_ID:

SELECT party_id,
       ext_bank_account_id,
       bank_account_num,
       bank_name,
       branch_name,
       branch_number,
       country_code,
       currency_code
FROM   apps.iby_payee_all_bankacct_v
WHERE  branch_id = :p_branch_id
AND    (end_date IS NULL OR end_date > SYSDATE);

A second frequent pattern is payee-level bank account listing, joining the view to supplier or customer tables on PARTY_ID. Extracts feeding payment reconciliation, treasury verification, and bank-master validation all rely on the view because it already blends account and institution context. When building such queries, restrict by PARTY_ID or BANK_ID where possible, and honour the START_DATE/END_DATE effective dating to avoid returning expired account records. Because the view carries no operating-unit filter, any organizational segregation must be applied by the calling query.