Results for “check_digits”

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

Overview

IBY_BANKACCT_V is an Oracle E-Business Suite (EBS) view owned by the APPS schema and delivered as part of the IBY (Payments) product module. Its stated purpose within the ETRM metadata is to provide a consolidated, security-filtered read interface for working with registered bank accounts. Rather than querying the underlying bank account tables directly, external and internal consumers use this view to obtain a flattened, joined representation of bank account, instrument holder, and account type information.

The view is a critical integration point in the payments and disbursement flows of EBS 12.1.1 and 12.2.2. Because it exposes the ACCOUNT_HOLDER_NAME column — the field most relevant to the user's search — along with account identifiers, bank details, and ownership attributes, it supports reporting on the party or entity that owns or is registered against a given bank account. It is a read-only view; all maintenance operations must be performed against the underlying base tables.

Underlying Base Objects

The view is defined over three base objects as documented in the ETRM metadata:

• IBY_BANKACCT — the core registered bank account table, aliased B, supplying account, bank, routing, holder, and check digit attributes.
• IBY_INSTRHOLDER — the instrument holder table, aliased H, linking the bank account to its owning party in the instrument hierarchy.
• IBY_ACCTTYPE — the account type lookup table, aliased Y, resolving the account type identifier into a descriptive value.

The defined join is B.INSTRID = H.INSTRID with the constraint H.INSTRTYPE = 'BANKACCOUNT', plus B.ACCTTYPEID = Y.ACCTTYPEID. A further filter, H.ACTIVESTATUS = 1, restricts the result set to active instrument holders only, so inactive or end-dated bank account registrations are excluded automatically. This means the view returns only currently active registered bank accounts.

Key Columns

The view projects the following columns, each with retained or reassigned names from the base tables:

• INSTRID — the instrument identifier, the primary join key between the bank account and holder records.
• BANKACCOUNTID — the internal unique identifier for the bank account.
• FINAME — the financial institution (bank) name.
• BRANCHID — derived from B.BRANCHNAME, the bank branch identifier or name.
• ACCTTYPE — the account type description resolved from IBY_ACCTTYPE.
• INSTRNAME — the instrument name assigned to the bank account.
• ACCOUNT_HOLDER_NAME — the name of the account holder, the column most commonly searched for in this context.
• BANKID — mapped from B.ROUTINGNO, the routing or bank identifier.
• INSTRBUF — derived from B.DESCRIPTION, a buffer/description field.
• OWNERID / OWNERTYPE — from IBY_INSTRHOLDER, identifying the owning party and its type.
• CHECK_DIGITS — the check digit component of the account number.

Common Use Cases and Queries

Typical scenarios include reporting on active registered bank accounts, extracting account holder and ownership data for reconciliation, and feeding legacy or custom integrations that require bank account metadata without accessing base tables directly.

To locate a bank account by account holder name:

SELECT bankaccountid, finame, branchid, accttype,
       account_holder_name, bankid, ownerid, ownertype
FROM   apps.iby_bankacct_v
WHERE  UPPER(account_holder_name) LIKE UPPER('%&holder_name%');

To list all active accounts for a given owner:

SELECT instrid, bankaccountid, instname, account_holder_name
FROM   apps.iby_bankacct_v
WHERE  ownerid = :p_owner_id;

Because the view enforces ACTIVESTATUS = 1, no additional active-status predicate is required from the caller. All queries must be executed against the APPS schema or a synonym resolving to it.