Results for “account_classification”

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

Overview

IBY_EXT_BANK_ACCOUNTS_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the IBY (Payments) product. It presents externally defined bank account information — records held in the IBY_EXT_BANK_ACCOUNTS base table — joined to the Trading Community Architecture (TCA) party model so that account, bank, branch, and account owner details are available in a single denormalized result set. In Release 12.1.1 and 12.2.2 the view is a standard, dictionary-registered object (Status: VALID) and is widely used by payment formats, external integration extracts, and custom reporting that requires a flattened picture of a payer's or payee's bank account.

The view is read-only by nature: as a join-based view over transactional and reference tables, it is not designed for direct DML. Its principal role is to supply bank account attributes — masked account numbers, IBAN, currency, exchange rate agreement data, and specifically the ACCOUNT_CLASSIFICATION column — to downstream consumers such as Oracle Payments, cash management integrations, and external bank file generation.

Underlying Base Objects

The ETRM metadata documents the following referenced base objects, all resolved through APPS synonyms:

• IBY_EXT_BANK_ACCOUNTS — the primary table holding external bank account records.
• IBY_ACCOUNT_OWNERS — associates an external bank account with an owning party and a primary flag.
• HZ_PARTIES — supplies the bank party name (BP) and the account owner party name (OP).
• HZ_ORGANIZATION_PROFILES — supplies bank or branch number (BANK_OR_BRANCH_NUMBER) with effective-dating handled through EFFECTIVE_START_DATE and EFFECTIVE_END_DATE.
• HZ_PARTY_SITES — supplies the location identifier, joined on the identifying address flag.
• CE_BANK_BRANCHES_V — supplies branch name, branch number, branch type, and EFT/SWIFT code.
• HZ_CODE_ASSIGNMENTS and HZ_CONTACT_POINTS — supplemental TCA reference objects used in the TCA join paths.

All joins to the TCA tables are outer joins (+), so an external bank account row is always returned even where the corresponding party, branch, or owner data is missing. The owner join is further constrained to the primary owner (OW.PRIMARY_FLAG = 'Y') and to owners whose end date has not passed.

Key Columns

• EXT_BANK_ACCOUNT_ID — primary identifier of the external bank account.
• BANK_PARTY_ID / BANK_NAME / BANK_NUMBER — the financial institution party and its identifying numbers.
• BRANCH_PARTY_ID / BANK_BRANCH_NAME / BRANCH_NUMBER / BRANCH_TYPE / EFT_SWIFT_CODE — branch-level detail used in payment routing.
• BANK_ACCOUNT_NAME / BANK_ACCOUNT_NAME_ALT / SHORT_ACCT_NAME — the account display names.
• MASKED_BANK_ACCOUNT_NUM / MASKED_IBAN / CHECK_DIGITS / ACCOUNT_SUFFIX — masked and supplementary account identifiers.
• CURRENCY_CODE, and a DECODE that returns 'Y' when the currency is null and 'N' otherwise.
• ACCOUNT_CLASSIFICATION and BANK_ACCOUNT_TYPE — the classification of the account (for example, internal, external, or customer/supplier usage), which is the column most frequently sought by users searching on "account_classification".
• ACCOUNT_OWNER_PARTY_ID and owner PARTY_NAME — the party that owns the account.
• START_DATE / END_DATE — the effective period of the account.
• PAYMENT_FACTOR_FLAG, FOREIGN_PAYMENT_USE_FLAG, EXCHANGE_RATE_AGREEMENT_NUM / _TYPE, EXCHANGE_RATE, HEDGING_CONTRACT_REFERENCE, SECONDARY_ACCOUNT_REFERENCE — payment and treasury attributes.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — descriptive flexfield segments.
• ROW_ID and OBJECT_VERSION_NUMBER — surrogate row identifier and optimistic locking column.

Common Use Cases and Queries

Typical uses include extracting bank account data for payment files, validating account classification before remittance processing, and reporting on the relationship between an account owner party and its bank. A representative query filtering on the account classification is:

• SELECT ext_bank_account_id, bank_account_name, masked_bank_account_num, currency_code, account_classification, bank_account_type FROM iby_ext_bank_accounts_v WHERE account_classification = :p_classification;
• SELECT v.bank_account_name, v.bank_name, v.bank_branch_name, v.eft_swift_code, v.party_name FROM iby_ext_bank_accounts_v v WHERE v.account_owner_party_id = :p_party_id;
• SELECT account_classification, COUNT(*) FROM iby_ext_bank_accounts_v GROUP BY account_classification;
• SELECT bank_account_name, currency_code, DECODE(currency_code, NULL, 'Y', 'N') AS has_no_currency FROM iby_ext_bank_accounts_v WHERE start_date >= :p_start;

Because most TCA joins are outer, queries should account for potential nulls in bank, branch, and owner columns. When used in concurrent programs or extracts, the view should be joined back to IBY_EXT_BANK_ACCOUNTS on EXT_BANK_ACCOUNT_ID if the base row identifier is required for subsequent update or reference.