Search Results iby_ext_fd_prba_1_0_v




Overview
Explore in AI Chat

Overview

The view APPS.IBY_EXT_FD_PRBA_1_0_V belongs to the Oracle Payments (IBY) product family and is a denormalized reporting construct used to expose payer bank account information for external payment formatting and extraction. Its name follows the Oracle Payments extract view convention (IBY_EXT_FD_...), indicating that it is designed to be consumed by the Payments Formats and external formatting engines during the payment instruction build phase. In Oracle EBS 12.1.1 and 12.2.2 the view sits on top of the core bank, branch, and party model, joining bank account records to bank branch details, address information, and lookup meanings so that payment format programs can retrieve structured, human-readable bank data without navigating multiple base tables.

The view is registered with a VALID status in the APPS schema and is a key artifact when the bank_account_type attribute must be resolved for format fields. It exposes both the coded value (BANK_ACCOUNT_TYPE) and its decoded meaning via a lookup join, which is a frequent requirement in payment file specifications.

Underlying Base Objects

The view is defined over a set of core Oracle EBS objects that span Payments, Cash Management, and Trading Community Architecture (TCA):

Key Columns

Common Use Cases and Queries

This view is typically queried by payment format templates and diagnostic reports to validate that payer bank account data is complete before a payment instruction is formatted. A representative query to review the account type for a given payment instruction is:

  • SELECT bank_account_id, bank_account_num, bank_account_type, bank_account_type_meaning FROM iby_ext_fd_prba_1_0_v;
  • Filtering by currency or bank for reconciliation: SELECT bank_name, bank_account_num, bank_account_type_meaning, currency_code FROM iby_ext_fd_prba_1_0_v WHERE currency_code = 'USD';
  • Extracting RFC and EFT data for regional formats using the GET_FEIN output columns alongside eft_swift_code.

Because the view invokes package functions keyed on PMT_INSTR_ID, direct ad-hoc queries may return null values unless the view parameter context is initialized by the Payments extraction engine. Consequently, the view is most reliably used within the standard payment instruction build and formatting flows rather than as a standalone reporting source.