Search Results iby_ext_fd_prba_1_0_vd




Overview
Explore in AI Chat

Overview

The view APPS.IBY_XML_FD_PRBA_1_0_V is a database object within the Oracle E-Business Suite (EBS) Payments module, specifically part of the Payments XML generation infrastructure. Its name follows the EBS convention for XML-based extract views: IBY identifies the Payments (iPayment/IBY) product family, XML indicates XML output, FD denotes formatted data, and PRBA refers to Payee/Party/Remit-to Bank Account information, with 1_0 indicating the message/format version. This view is closely tied to the synonym-referenced object IBY_EXT_FD_PRBA_1_0_VD, which is the object commonly cited in external documentation and troubleshooting queries.

Functionally, IBY_XML_FD_PRBA_1_0_V produces an XMLType document describing bank account details associated with a payee, party, or remit-to party. It is consumed by the Payments formatting and extraction engine to build structured XML payloads for payment instructions, bank validation, and outbound messages to banks or clearing networks. Because the output is a single concatenated XML fragment, the view acts as a transformation layer rather than a conventional relational table source.

Underlying Base Objects

According to the documented ETRM metadata, this view references the following base objects:

  • IBY_EXT_FD_PRBA_1_0_VD (VIEW) — the parent/underlying extract definition view that supplies the bank account and party attributes.
  • IBY_EXTRACTGEN_PVT (PACKAGE) — helper package used in the view definition, notably for the Get_Dffs function, which retrieves descriptive flexfield values for base entities such as CE_BANK_ACCOUNTS and HZ_PARTIES.
  • IBY_FD_EXTRACT_GEN_PVT (PACKAGE) — used to obtain formatted address data via Get_account_Address, applying country-specific address formatting.
  • IBY_EXT_BANKACCT_PUB (PACKAGE) — provides the masking routine mask_bank_number, which obscures bank account numbers and IBANs based on security settings.
  • IBY_SYS_SECURITY_OPTIONS (SYNONYM) — supplies the masking configuration values (ext_ba_mask_setting, ext_ba_unmask_len) that govern how many characters remain visible.
  • XMLTYPE (TYPE) — the Oracle type that produces the final XML document through XMLConcat and XMLElement calls.

The view therefore sits on top of the bank account extraction definition and delegates specialized logic (masking, address formatting, flexfield retrieval) to the Payments public and private APIs.

Key Columns

Because the view returns an XMLType, its "columns" correspond to XML elements constructed within the query:

  • BankAccountInternalID — internal bank account identifier.
  • BankName, AlternateBankName, BankNumber — bank-level identification, including alternate language names.
  • BranchInternalID, BranchName, AlternateBranchName, BranchNumber — bank branch identification.
  • BankAccountName, AlternateBankAccountName, BankAccountNumber — account name and electronic account number.
  • MaskedBankAccountNumber, MaskedIBANNumber — security-masked variants produced by IBY_EXT_BANKACCT_PUB.mask_bank_number.
  • UserEnteredBankAccountNumber, BankAccountSuffix — original entered number and account suffix.
  • SwiftCode, IBANNumber, CheckDigits — international banking identifiers.
  • BankAccountType, BankAccountCurrency — nested elements containing Code and Meaning values.
  • BankAddress — formatted branch address from IBY_FD_EXTRACT_GEN_PVT.
  • DescriptiveFlexField, BranchDescriptiveFlexField — conditional DFF data for CE_BANK_ACCOUNTS and HZ_PARTIES.

Common Use Cases and Queries

This view is typically invoked by the Payments XML extract engine rather than queried directly by end users, but it can be used for diagnostics and integration testing.

  • Masking verification — confirming that account numbers and IBANs are correctly masked per security options.
  • Bank validation testing — validating that bank, branch, SWIFT, and IBAN values are correctly populated before sending payment instructions.
  • DFF inspection — verifying that bank account and party descriptive flexfields are included where required.

A representative query:

SELECT x.*
FROM   apps.iby_xml_fd_prba_1_0_v x
WHERE  x.bank_account_id = :p_bank_account_id;

Because the underlying extract view filters by the bind context of payee, party, and bank account, administrators generally pass the appropriate internal identifiers. The extracted XMLType can then be parsed using XMLTable or extractValue to inspect individual elements.