Results for “masked_iban”

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

Overview

IBY_EXT_BANK_ACCOUNTS is the master repository for external (customer and trading partner) bank accounts within the Oracle Payments (IBY) module of Oracle E-Business Suite 12.1.1 and 12.2.2. The table stores bank account details for parties outside the organization — as opposed to internal disbursement or remittance accounts — and serves as the authoritative source for direct debit authorization, refund deposits, and payment transactions where a third-party bank account must be recorded and validated. Rows are owned by the IBY schema and are managed through the Payments account infrastructure, which supports encryption, masking, and security segment references for sensitive account data.

Under the heuristic Data Vault classification derived from its foreign-key structure, this table is a hub-leaning candidate: it defines a durable business entity (the external bank account) identified by a stable key, and multiple dependent tables attach descriptive attributes or transaction facts to it. Teams performing downstream warehouse modeling should treat EXT_BANK_ACCOUNT_ID as a hub key candidate, with satellite attributes such as account numbers and bank identifiers split into distinct satellite tables.

Key Information Stored

The table contains 69 documented columns. The most significant are:

• EXT_BANK_ACCOUNT_ID — surrogate primary key (IBY_EXT_BANK_ACCOUNTS_PK, unique index IBY_EXT_BANK_ACCOUNTS_U1) that uniquely identifies each external bank account record.
• BANK_ACCOUNT_NUM and MASKED_BANK_ACCOUNT_NUM — the raw and masked bank account number; masking is governed by BA_MASK_SETTING and BA_UNMASK_LENGTH.
• BANK_ACCOUNT_NUM_HASH1 and BANK_ACCOUNT_NUM_HASH2 — hash values used for duplicate detection and lookup without exposing the raw account number.
• IBAN, MASKED_IBAN, IBAN_HASH1, IBAN_HASH2 — the International Bank Account Number and its masking/hash counterparts for international accounts.
• BANK_ACCOUNT_TYPE, ACCOUNT_CLASSIFICATION, and ACCOUNT_SUFFIX — classify the account for payment instrument and routing rules.
• BANK_ID and BRANCH_ID — reference the bank and branch (BRANCH_ID joins to AMS_DLG_BRANCHES_B); COUNTRY_CODE and CURRENCY_CODE further qualify the account.
• BA_NUM_SEC_SEGMENT_ID, IBAN_SEC_SEGMENT_ID, and BA_NUM_ELEC_SEC_SEGMENT_ID — link account numbers to IBY_SECURITY_SEGMENTS for encryption/security key management.
• DESCRIPTION and BANK_ACCOUNT_NAME — descriptive identifiers used in reporting and inquiry screens.
• CREATION_DATE, LAST_UPDATE_DATE, and OBJECT_VERSION_NUMBER — standard audit and optimistic locking columns. The presence of START_DATE and END_DATE records the effective lifecycle of the account.

Common Use Cases and Queries

The table is most frequently queried to resolve a customer or partner bank account during payment processing and reconciliation. AR_PAYMENTS_INTERFACE_ALL, a common search target, holds CUSTOMER_BANK_ACCOUNT_ID as a foreign key pointing into this table, so analysts frequently join the two to reconcile inbound payment interface rows against the validated external account.

A representative query retrieves masked account details for interface rows:

• SELECT p.payment_interface_id, e.bank_account_name, e.masked_bank_account_num, e.currency_code FROM ar_payments_interface_all p, iby_ext_bank_accounts e WHERE p.customer_bank_account_id = e.ext_bank_account_id AND p.status = 'NEW'

Reporting uses include payment fraud screening (querying hash columns for duplicate account numbers across parties), audit reporting on encryption status using the ENCRYPTED flag and SALT_VERSION, and account expiry monitoring via END_DATE.

Related Objects

Several significant tables reference this object directly through documented foreign keys:

• AR_PAYMENTS_INTERFACE_ALL — via CUSTOMER_BANK_ACCOUNT_ID; the primary linkage for payment interface processing.
• AR_CASH_RECEIPTS_ALL and AR_INTERIM_CASH_RECEIPTS_ALL — via CUSTOMER_BANK_ACCOUNT_ID; ties received payments to the originating external account.
• IBY_ACCOUNT_OWNERS — via EXT_BANK_ACCOUNT_ID; associates the account with its owning party.
• IBY_INTERMEDIARY_ACCTS — via BANK_ACCT_ID; defines intermediary bank relationships for routed payments.
• CE_PAYMENT_TRANSACTIONS — via EXT_BANK_ACCOUNT_ID; links cash management transaction records.
• IBY_SECURITY_SEGMENTS — referenced by the security-segment columns for key management; AMS_DLG_BRANCHES_B supplies branch data via BRANCH_ID.