Search Results zero_amount_allowed




Overview
Explore in AI Chat

Overview

CE_BANK_ACCTS_SEARCH_GT_V is an APPS-owned database view in the Oracle E-Business Suite Cash Management (CE) module. It is a VALID object in both EBS 12.1.1 and 12.2.2 and forms part of the bank account search infrastructure used by Cash Management and by integrating modules such as Payables, Receivables, Payments, and Treasury. The "GT_V" suffix indicates that the view is a global temporary view — a reporting/selection layer built on top of a global temporary table (GTT) that temporarily holds a filtered subset of bank accounts returned by a search operation. Rather than exposing the entire CE_BANK_ACCOUNTS population, it presents the working set of accounts that matched a user's search criteria within a session.

Its principal role is to expose bank account attributes — identity, holder information, numbering, currency, tolerances, and usage flags — in a form that the Cash Management account search UI and downstream concurrent programs can query directly. Because the view projects a wide column list from the underlying bank account entity, it functions as a denormalised read model for account selection screens.

Underlying Base Objects

Per the documented view metadata, CE_BANK_ACCTS_SEARCH_GT_V references three base objects, all exposed to APPS as synonyms:

  • CE_BANK_ACCOUNTS — the primary bank account definition table, supplying the majority of projected columns such as BANK_ACCOUNT_ID, BANK_ACCOUNT_NAME, BANK_ACCOUNT_NUM, CURRENCY_CODE, and the ACCOUNT_HOLDER_* attributes.
  • CE_BANK_ACCT_USES_ALL — the account usage table that links a bank account to an operating unit, application (AP, AR, XTR, PAY) and its associated flags and tolerances. This governs whether a given account is usable in a given context.
  • CE_SECURITY_PROFILES_GT — the global temporary structure holding the security profile access set for the current user, which restricts the accounts visible through the search to those the user is authorised to see.

The alias BA prefixing every projected column in the documented view text confirms that CE_BANK_ACCOUNTS (or its synonym) is the driving table of the join.

Key Columns

The view exposes the full attribute set of CE_BANK_ACCOUNTS. Columns of particular interest include:

Common Use Cases and Queries

The view is most commonly queried after a search has populated the temporary structure, or directly where the caller wants the joined bank account/usage/security result set. A typical query locating an account by holder is:

  • SELECT bank_account_id, bank_account_name, bank_account_num, account_holder_id, account_holder_name, currency_code FROM ce_bank_accts_search_gt_v WHERE account_holder_id = :p_holder_id;
  • SELECT bank_account_id, bank_account_name FROM ce_bank_accts_search_gt_v WHERE ap_use_allowed_flag = 'Y' AND currency_code = 'USD';
  • SELECT a.bank_account_id, a.bank_account_num, a.account_holder_name FROM ce_bank_accts_search_gt_v a WHERE a.bank_account_id IN (SELECT bank_account_id FROM ce_bank_acct_uses_all WHERE org_id = :p_org_id);

Typical scenarios include LOV population on payment and receipt entry forms, Cash Management account search screens, and custom extensions that need a security-filtered view of usable bank accounts for a given operating unit. Because the underlying structure is session-scoped, queries should always be issued within the context in which the search population logic has run.