Search Results eft_swift_code

Overview

AP_XML_PAYMENTACCOUNTLEVEL_V is a Payables module view that exposes bank account-level payment information for electronic payment processing and XML payment file generation in Oracle E-Business Suite 12.1.1 and 12.2.2. The view consolidates data from payment selection criteria and the underlying bank account and bank branch definitions, presenting a flattened result set that payment formats, remittance processes, and external integration layers can consume directly. It is particularly relevant where Payables must emit structured payment instruction files containing remitter bank details, EFT routing information, and account identifiers.

The identifier "account_key" referenced during searches corresponds to the ACCOUNT_KEY column documented in the view's column list. This column is the principal linkage used by payment format templates, XML Publisher data definitions, and downstream EFT orchestrations to resolve the correct bank account context for a given checkrun or batch.

Underlying Base Objects

Per the documented metadata, the view is defined over three base tables through an inner-join construct:

• AP_INVOICE_SELECTION_CRITERIA (AISC) — supplies CHECKRUN_NAME and CHECKRUN_ID, functioning as the driving batch/checkrun context.
• AP_BANK_ACCOUNTS (ABA) — supplies the account-level attributes including bank account number, account type, check digits, currency code, account name, and EFT user number.
• AP_BANK_BRANCHES (ABB) — supplies branch and institution attributes including branch type, bank number, bank name, branch name, contact details, address components, and the EFT SWIFT code.

The join predicates connect AISC.BANK_ACCOUNT_ID to ABA.BANK_ACCOUNT_ID, and ABA.BANK_BRANCH_ID to ABB.BANK_BRANCH_ID. The view therefore returns one row per qualifying selection-criteria record joined to its owning bank account and branch. Note that the ETRM metadata records this view as "Not implemented in this database" and lists no documented owner or referenced base objects, so deployments may encounter variations in availability across instances and patch levels. The select list aliases several columns differently from the underlying tables; for example, CHECKRUN_NAME is surfaced as BATCH_NAME, CHECKRUN_ID as BATCH_ID, CURRENCY_CODE as ACCOUNT_CURRENCY, and others are renamed to bank-oriented labels.

Key Columns

• ACCOUNT_KEY — The account-level key used by payment formats to correlate remitter bank information with a payment batch or checkrun.
• BATCH_NAME / BATCH_ID — Derived from CHECKRUN_NAME and CHECKRUN_ID; identify the payment batch or checkrun being processed.
• BANK_ACCOUNT_NUM / BANK_ACCOUNT_TYPE / ACCOUNT_NAME — The remitter's bank account number, account type, and descriptive account name.
• ACCOUNT_CURRENCY — Currency of the bank account, sourced from ABA.CURRENCY_CODE.
• BANK_NUMBER / BANK_NAME / BRANCH_NAME / BRANCH_NUMBER / BANK_ID_TYPE — Institution and branch identification values used in EFT and wire routing.
• EFT_USER_NUMBER / EFT_SWIFT_CODE — Electronic funds transfer identifiers required for cross-border and domestic payment instructions.
• BANK_CONTACT_NAME / BANK_CONTACT_TELEPHONE / BANK_CONTACT_TYPE — Concatenated contact name (first plus last) and phone, plus contact title.
• CITY / STATE / POSTAL_CODE / COUNTRY / ADDRESSLINE — Branch address attributes, with ADDRESSLINE built from concatenated address lines.

Common Use Cases and Queries

The view is typically queried by payment format SQL, XML Publisher data templates, and diagnostic reports that must print remitter bank details on payment files and advices. A representative query retrieving account-level detail for a specific batch:

• SELECT account_key, batch_name, batch_id, bank_account_num, account_currency, bank_name, branch_name, eft_swift_code FROM ap_xml_paymentaccountlevel_v WHERE batch_id = :p_checkrun_id;
• SELECT batch_name, bank_account_num, bank_number, account_currency FROM ap_xml_paymentaccountlevel_v WHERE account_key = :p_account_key;
• SELECT DISTINCT bank_name, branch_name, bank_contact_name FROM ap_xml_paymentaccountlevel_v ORDER BY bank_name;

Because the view aggregates selection criteria with account and branch data, it is well suited to troubleshooting mismatched EFT identifiers, validating that the intended remitter account was used for a payment run, and feeding downstream payment instruction generation.