Results for “contact_title”

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

Overview

CEBV_BANK_ACCOUNTS is a Business view owned by the APPS schema within the Cash Management (CE) product family of Oracle E-Business Suite. It is marked VALID and is exposed as a reporting and integration abstraction over the bank account definitions maintained in the EBS cash and payments infrastructure. The view consolidates two logically distinct sources of bank account data into a single uniform result set: internal bank accounts held in CE_BANK_ACCOUNTS and externally defined bank accounts surfaced through IBY_EXT_BANK_ACCOUNTS_V. Because it presents a stable, denormalized row shape covering account identity, account type, currency, payment constraints, and account holder details, it is well suited to ad-hoc reporting, concurrent program data sources, and inbound/outbound interface extracts where a single query must return both internal and external accounts.

The view name and its inclusion of the BANK_ACCOUNT_TYPE column make it the natural entry point for users searching on "bank_account_type," since account classification is exposed directly without requiring a join back to the CE_BANK_ACCOUNTS base table.

Underlying Base Objects

Per the documented ETRM 12.2.2 metadata, CEBV_BANK_ACCOUNTS is defined over two referenced base objects: CE_BANK_ACCOUNTS (referenced via a SYNONYM) and IBY_EXT_BANK_ACCOUNTS_V (a VIEW). The definition is a UNION ALL, meaning rows from both sources are concatenated without duplicate elimination and without a driving join key between them. Columns that do not exist in one branch are padded with typed NULLs (TO_CHAR(NULL), TO_NUMBER(NULL), TO_DATE(NULL)) to preserve positional alignment across the union.

• The CE_BANK_ACCOUNTS branch supplies internal accounts, contributing POOLED_FLAG, MAX_OUTLAY, MIN_CHECK_AMOUNT, MAX_CHECK_AMOUNT, ZERO_AMOUNT_ALLOWED, EFT_USER_NUM, BANK_BRANCH_ID, and the standard WHO audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY).
• The IBY_EXT_BANK_ACCOUNTS_V branch supplies external accounts, contributing BRANCH_PARTY_ID, CURRENCY_CODE, EXT_BANK_ACCOUNT_ID, and END_DATE, while audit and payment-control columns are returned as NULL.
• The view is defined WITH READ ONLY, so it cannot be used as an updateable entity in Forms or DML statements.

Key Columns

The BANK_ACCOUNT_ID column is the primary identifier in the internal branch, while the external branch populates the same position from EXT_BANK_ACCOUNT_ID. BANK_ACCOUNT_NAME and ALTERNATE_BANK_ACCOUNT_NAME carry the display and secondary names, and BANK_ACCOUNT_NUMBER holds the account number itself.

• BANK_ACCOUNT_TYPE — the classification of the account (the column most commonly searched for). It is populated from both branches, so external and internal accounts are typed consistently.
• CURRENCY_CODE — the currency in which the account is denominated; combined with MULTICURRENCY_ALLOWED_FLAG (MULTICURRENCYALLOWED_FLAG in the view output) it governs multi-currency payment behavior.
• Payment control columns — MAXIMUM_PAYMENT_BATCH_OUTLAY, MINIMUM_PAYMENT_AMOUNT, MAXIMUM_PAYMENT_AMOUNT, and ZERO_PAYMENTS_ALLOWED_FLAG are only meaningful for internal accounts and are NULL for external ones.
• POOLED_ACCOUNT_FLAG — indicates whether the internal account participates in a pooling arrangement.
• Account holder and EFT columns — ACCOUNT_HOLDER_NAME, ALTERNATE_ACCOUNT_HOLDER_NAME, and EFT_USER_NUMBER describe the beneficiary and electronic funds transfer routing. Contact columns (CONTACT_FIRST_NAME through CONTACT_PHONE) are projected but typically NULL.
• INACTIVE_DATE and END_DATE — effective end dating for the account record.

Common Use Cases and Queries

Typical usage includes listing all accounts of a given type, locating accounts by currency, and feeding downstream extracts that must include both internal and external accounts. A representative query filtering on the searched column is:

SELECT bank_account_id, bank_account_name, bank_account_number, bank_account_type, currency_code, multicurrency_allowed_flag FROM apps.cebv_bank_accounts WHERE bank_account_type = :p_type AND (inactive_date IS NULL OR inactive_date > SYSDATE);

To isolate internal accounts only, restrict on a column populated solely by the CE_BANK_ACCOUNTS branch, such as WHERE pooled_account_flag IS NOT NULL or the presence of an EFT user number. Because the view is a UNION ALL with NULL padding, filters on branch-specific columns effectively select a single source. Reporting on bank account types should therefore always qualify the type value to avoid mixing classifications that originate in the external branch.