Results for “ce_internal_bank_accts_v”

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

Overview

CE_INTERNAL_BANK_ACCTS_V is a public view owned by the APPS schema in Oracle E-Business Suite, belonging to the Cash Management (CE) product family. Its documented purpose is to present all internal bank accounts, including netting bank accounts, in a single consolidated reporting structure. The view is defined with a DISTINCT qualifier over CE_BANK_ACCOUNTS, which suppresses duplicate rows that can arise when a bank account is joined to its account-use records across multiple operating units or organizations. Because internal bank accounts are the source of cash transactions, reconciliation data, and payment/receipt activity, this view serves as a canonical reference object for reporting, integration, and diagnostic queries. In ETRM 12.1.1 and 12.2.2 the object holds a VALID status, confirming that its definition compiles and is available for querying at runtime.

Underlying Base Objects

The view text selects its columns from BA within the APPS synonym CE_BANK_ACCOUNTS. According to the documented ETRM metadata, the view depends on a set of referenced objects that provide both the persistence layer and the security enforcement layer:

• CE_BANK_ACCOUNTS (SYNONYM) — the primary source of bank account attributes, supplying the majority of columns returned.
• CE_BANK_ACCT_USES_ALL (SYNONYM) — account-use records that associate bank accounts with operating units and applications.
• CE_SECURITY_PROFILES_V (VIEW) — the security-profile definition used to determine which accounts a user may access.
• FND_ACCESS_CONTROL_UTIL, FND_GLOBAL, FND_PROFILE (PACKAGES) — access-control and session-context utilities.
• MO_GLOBAL (PACKAGE) — Multi-Org initialization and organization context resolution.
• XTR_USER_ACCESS (PACKAGE) — Treasury user-access validation logic.

The inclusion of these security and multi-org packages indicates that the view is security-aware and applies data-access restrictions based on the runtime FND session and operating unit context rather than returning an unrestricted set of rows.

Key Columns

The view exposes a broad set of account-identification, control, and tolerance columns. Principal identification attributes include BANK_ACCOUNT_ID, BANK_ACCOUNT_NAME, BANK_ACCOUNT_NUM, MASKED_ACCOUNT_NUM, SHORT_ACCOUNT_NAME, BANK_BRANCH_ID, BANK_ID, CURRENCY_CODE, and IBAN_NUMBER along with MASKED_IBAN. Ownership and classification are captured by ACCOUNT_HOLDER_ID, ACCOUNT_HOLDER_NAME, ACCOUNT_OWNER_PARTY_ID, ACCOUNT_OWNER_ORG_ID, ACCOUNT_CLASSIFICATION, and BANK_ACCOUNT_TYPE. Functional enablement flags govern which subledgers may use the account: AP_USE_ALLOWED_FLAG, AR_USE_ALLOWED_FLAG, XTR_USE_ALLOWED_FLAG, and PAY_USE_ALLOWED_FLAG. Currency handling is reflected in MULTI_CURRENCY_ALLOWED_FLAG, PAYMENT_MULTI_CURRENCY_FLAG, and RECEIPT_MULTI_CURRENCY_FLAG. Amount and percentage controls appear in MAX_OUTLAY, MAX_CHECK_AMOUNT, MIN_CHECK_AMOUNT, and the AP/AR/XTR/PAY AMOUNT_TOLERANCE and PERCENT_TOLERANCE columns. Date and audit columns include START_DATE, END_DATE, CREATION_DATE, LAST_UPDATE_DATE, and the standard WHO columns. The NETTING_ACCT column identifies accounts designated for netting arrangements, consistent with the documented description.

Common Use Cases and Queries

Typical uses include validating account setup before payment processing, driving cash-position reporting, and confirming netting account configuration. A basic listing of active, payment-enabled accounts can be obtained as follows:

• SELECT bank_account_id, bank_account_name, bank_account_num, currency_code FROM ce_internal_bank_accts_v WHERE pay_use_allowed_flag = 'Y';
• SELECT bank_account_id, account_holder_name, masked_account_num, iban_number FROM ce_internal_bank_accts_v WHERE currency_code = 'USD';
• SELECT bank_account_id, netting_acct FROM ce_internal_bank_accts_v WHERE netting_acct IS NOT NULL;

Because access is filtered through the referenced security packages, results reflect the responsibilities, security profiles, and operating unit context of the connected user. Applications integrating with Cash Management should query this view rather than the base table directly in order to inherit the same access controls and the DISTINCT de-duplication behavior.