Results for “bank_code”

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

Overview

IBY_INTERMEDIARY_ACCTS is a Payments (IBY) module table in the Oracle E-Business Suite that defines intermediary bank account information. Intermediary banks sit between the ordering party's bank and the beneficiary's bank, typically used in international wire transfers where correspondent banking relationships route funds across borders. The table allows an external or internal bank account to be associated with one or more intermediary institutions, each described by BIC, IBAN, account number, and routing details required for SWIFT or other payment networks to execute the transfer correctly. Records in this table are consumed by Oracle Payments during payment formatting and remittance instruction generation, and they are reflected in bank account setup flows within Payables, Receivables, and Treasury.

From a Data Vault modeling perspective, the metadata suggests classifying IBY_INTERMEDIARY_ACCTS as a link entity. The heuristic is based on the foreign key structure: the table does not carry descriptive history of a single business entity but rather associates an external bank account (IBY_EXT_BANK_ACCOUNTS) with an internal bank account (CE_BANK_ACCOUNTS) alongside intermediary routing attributes. The 19 documented columns are predominantly descriptive attributes of the relationship itself, which is characteristic of a link table in a Data Vault design.

Key Information Stored

The surrogate primary key is INTERMEDIARY_ACCT_ID, enforced by IBY_INTERMEDIARY_ACCTS_PK and also supported by the unique index IBY_INTERMEDIARY_ACCTS_U1. This identifier is system-generated and should be treated as the technical key rather than a business identifier. The business relationships are anchored by BANK_ACCT_ID, which references IBY_EXT_BANK_ACCOUNTS, and INTERNAL_BANK_ACCOUNT_ID, which references CE_BANK_ACCOUNTS. Together these two columns express the association that gives the table its link semantics.

The remaining significant columns describe the intermediary institution and the routable account. BANK_NAME, CITY, COUNTRY_CODE, BANK_CODE, and BRANCH_NUMBER capture the institution's identity and location. BIC holds the SWIFT Business Identifier Code, and IBAN holds the International Bank Account Number. ACCOUNT_NUMBER and CHECK_DIGITS provide the local account reference and validation digits. COMMENTS stores free-form user notes. Standard audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, and OBJECT_VERSION_NUMBER — provide Who columns and optimistic locking for concurrent update control.

Common Use Cases and Queries

A frequent requirement is to list all intermediary accounts attached to a given external bank account so payment instruction formatting can emit the correct correspondent chain. A representative query joins the link table to IBY_EXT_BANK_ACCOUNTS on BANK_ACCT_ID:

• Reporting on intermediary routing details (BIC, IBAN, ACCOUNT_NUMBER) for external bank accounts used in international payouts.
• Validating that every external bank account requiring cross-border payment has at least one intermediary account configured.
• Reconciling intermediary configurations against CE_BANK_ACCOUNTS internal accounts for Treasury oversight.
• Auditing changes via LAST_UPDATED_BY and LAST_UPDATE_DATE, and detecting stale configurations using OBJECT_VERSION_NUMBER.

Sample pattern: SELECT i.INTERMEDIARY_ACCT_ID, i.BANK_ACCT_ID, i.BANK_NAME, i.BIC, i.IBAN, i.ACCOUNT_NUMBER FROM IBY_INTERMEDIARY_ACCTS i WHERE i.BANK_ACCT_ID = :p_bank_acct_id. Additional filtering by COUNTRY_CODE or BIC supports network-specific reports.

Related Objects

The principal related objects follow directly from the documented foreign keys and the surrounding IBY bank account model:

• IBY_EXT_BANK_ACCOUNTS — referenced via IBY_INTERMEDIARY_ACCTS.BANK_ACCT_ID; the external bank account that owns the intermediary chain.
• CE_BANK_ACCOUNTS — referenced via IBY_INTERMEDIARY_ACCTS.INTERNAL_BANK_ACCOUNT_ID; the internal (company) bank account involved in the transfer.
• IBY_BANK_ACCOUNTS — the underlying bank account view/entity used across Payments setup.
• IBY_PAYMENT_INSTRUCTIONS — payment output that consumes intermediary routing data during formatting.
• IBY_PAYMENTS and payment process request tables — orchestration records that drive the formatting of instructions.
• CE_BANK_BRANCHES — branch reference data commonly joined for routing validation.

Together these objects form the bank account and payment instruction chain within Oracle Payments, with IBY_INTERMEDIARY_ACCTS supplying the correspondent routing layer.