Search Results iby_ext_banks_v




Overview
Explore in AI Chat

Overview

IBY_EXT_BANKS_V is an Oracle E-Business Suite (EBS) view owned by the APPS schema and registered as VALID in the ETRM metadata for release 12.2.2 (and equally applicable to 12.1.1). It sits within the IBY — Payments product family, the module responsible for payment processing, funds capture, payment instructions, and bank account validation across Payables, Receivables, Payroll, and Treasury flows. The view presents a flattened, integration-oriented projection of externally sourced bank information, exposing bank party identifiers, bank names, bank numbers, institution types, and address attributes drawn from the Cash Management bank repository.

Its architectural purpose is to provide a stable, denormalized interface for external systems, third-party payment factories, and reporting layers that must resolve bank master data without directly coupling to the more complex underlying Cash Management entity model. The literal constants embedded in the view text (CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER all hard-coded to 1, CREATION_DATE and LAST_UPDATE_DATE set to SYSDATE, and OPERATION_FLAG set to 'Y') indicate the view is designed as a read-only staging or extraction surface rather than a transactional entity. The OPERATION_FLAG = 'Y' convention is characteristic of EBS views used in interface and conversion pipelines, signalling that records are available for downstream processing.

Underlying Base Objects

Per the documented ETRM metadata, the sole referenced base object is CE_BANKS_V, itself a view in the Cash Management (CE) schema rather than a physical table. IBY_EXT_BANKS_V therefore inherits the join and filter logic already applied within CE_BANKS_V, which typically consolidates bank party records from HZ_PARTIES and related Cash Management tables such as CE_BANKS, CE_BANK_BRANCHES, and bank account models. Because the immediate source is a view, the effective performance characteristics depend on the CE_BANKS_V definition as shipped in the specific release; customer-specific modifications or seeded column changes in CE can propagate upward and affect IBY_EXT_BANKS_V.

The one-to-one column mapping between the two objects means IBY_EXT_BANKS_V adds no additional filtering, aggregation, or restriction beyond the SELECT list projections and the hard-coded audit columns. Consumers should therefore treat CE_BANKS_V as the authoritative definition and IBY_EXT_BANKS_V as a controlled presentation layer.

Key Columns

  • BANK_PARTY_ID — The identifier of the bank as a trading partner (party) record; the primary join key to HZ_PARTIES and to payment-related tables.
  • HOME_COUNTRY — The home country of the bank, distinct from the address COUNTRY column; this is the column most directly relevant to the "home_country" search, used in country-specific bank validation, IBAN/BIC processing, and regulatory routing rules.
  • BANK_NAME / BANK_NAME_ALT / SHORT_BANK_NAME — Primary, alternate, and abbreviated bank names for display and matching.
  • BANK_NUMBER — The bank's identifying number, typically the national bank code used in payment formatting.
  • BANK_INSTITUTION_TYPE — Classification of the institution (for example, bank versus branch or clearing institution).
  • ADDRESS1, ADDRESS2, ADDRESS3, CITY, STATE, POSTAL_CODE, COUNTRY — Standard address components for the bank's location.
  • DESCRIPTION, END_DATE — Free-text description and the effective end date restricting active use.
  • OPERATION_FLAG — Always 'Y'; indicates the row is eligible for interface processing.

Common Use Cases and Queries

Typical usages include extracting bank master data for external payment gateways, populating reporting repositories, reconciling bank lists between EBS and treasury systems, and diagnosing why a supplier or customer bank is unavailable for a payment method. Filtering by HOME_COUNTRY is common when building country-specific payment formats.

Sample query listing banks by home country:

  • SELECT bank_party_id, home_country, bank_name, bank_number, bank_institution_type, country, end_date FROM apps.iby_ext_banks_v WHERE home_country = 'US' AND (end_date IS NULL OR end_date > SYSDATE) ORDER BY bank_name;
  • SELECT bank_party_id, bank_name, bank_number, city, state, postal_code FROM apps.iby_ext_banks_v WHERE bank_number = :p_bank_num;
  • SELECT home_country, COUNT(*) FROM apps.iby_ext_banks_v GROUP BY home_country ORDER BY 2 DESC;