Results for “agency_location_code”

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

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):

• CE_BANK_ACCOUNTS — the synonym for the primary bank account entity supplying account number, IBAN, check digits, currency, EFT user number, and BANK_ACCOUNT_TYPE.
• CE_BANK_BRANCHES_V — a view that provides bank and branch level attributes including bank name, bank number, branch identifier, SWIFT code, and branch type.
• HZ_PARTY_SITES — the TCA party site table, joined via an outer join to retrieve the primary identifying address.
• HZ_CODE_ASSIGNMENTS — used with CLASS_CATEGORY = 'RFC_IDENTIFIER' to retrieve the RFC (tax/registration) class code for the branch party.
• AR_LOOKUPS and FND_LOOKUPS — joined with outer joins to resolve lookup meanings for bank branch type and bank account type respectively.
• IBY_UTILITY_PVT and IBY_FD_EXTRACT_GEN_PVT — server-side PL/SQL packages whose functions (GET_VIEW_PARAM, GET_ABBREVIATED_AGENCY_CODE, GET_FEIN) supply contextual values keyed on the current PMT_INSTR_ID view parameter.

Key Columns

• BANK_ACCOUNT_ID — unique identifier of the bank account.
• BANK_NAME, BANK_NUMBER, BANK_BRANCH_NAME, BRANCH_NUMBER — bank and branch identification attributes.
• BANK_ACCOUNT_NAME, BANK_ACCOUNT_NUM, IBAN_NUMBER, CHECK_DIGITS — account-level attributes used in payment file output.
• BANK_ACCOUNT_TYPE and BANK_ACCOUNT_TYPE_MEANING — the coded bank account type (for example, the lookup code) and its descriptive meaning from FND_LOOKUPS where LOOKUP_TYPE = 'BANK_ACCOUNT_TYPE'. This pair is the primary target when users search for bank_account_type.
• BANK_BRANCH_TYPE and BANK_BRANCH_TYPE_MEANING — similar coded/meaning pair for the branch type via AR_LOOKUPS.
• EFT_SWIFT_CODE, EFT_USER_NUMBER, EFT_USER_NUM — electronic funds transfer identifiers.
• CURRENCY_CODE, LOCATION_ID, ATTRIBUTE_CATEGORY, AGENCY_LOCATION_CODE, and the GET_FEIN / abbreviated agency code function outputs — supplementary context used by regional and regulatory payment formats.

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.