Results for “max_check_amount”

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

Overview

CE_BANK_ACCTS_GT_V is a view owned by the APPS schema within the Cash Management (CE) product of Oracle E-Business Suite, valid in releases 12.1.1 and 12.2.2. It exposes a flattened, security-filtered projection of bank account master data drawn primarily from CE_BANK_ACCOUNTS, together with usage attributes sourced from CE_BANK_ACCT_USES_ALL and access control information derived from CE_SECURITY_PROFILES_GT. The "_GT_V" suffix denotes a global temporary, session-scoped construct; the view is intended to return only the bank accounts that the currently connected user is authorized to see, based on their assigned Cash Management security profile. It therefore serves as the standard reporting and integration interface for bank account information, shielding callers from the complexity of joining the underlying account, usage, and security tables directly.

Underlying Base Objects

The documented referenced objects are:

• CE_BANK_ACCOUNTS (SYNONYM) — the master table holding bank account definitions, including account numbers, IBAN, currency, holder information, tolerance settings, and descriptive flexfield attributes.
• CE_BANK_ACCT_USES_ALL (SYNONYM) — the multi-organization usage table that records how a given bank account is used by a specific organization unit, including use-type flags (AP, AR, XTR, PAY), multi-currency allowances, amounts, and effective dates.
• CE_SECURITY_PROFILES_GT (SYNONYM) — a global temporary table populated at runtime with the set of bank accounts (or bank/branch combinations) permitted for the current user's security profile. It acts as the filtering mechanism that restricts the view's result set.

The view joins these objects so that account-level (master) columns and usage-level (transactional) columns are presented together for each authorized account/organization combination.

Key Columns

Columns exposed by the view include:

• BANK_ACCOUNT_ID, BANK_ACCOUNT_NAME, BANK_ACCOUNT_NUM — the primary identifier and human-readable identifiers of the account; MASKED_ACCOUNT_NUM and MASKED_IBAN provide masked variants for restricted display.
• BANK_ID, BANK_BRANCH_ID — foreign keys to the bank and branch definitions.
• CURRENCY_CODE, MULTI_CURRENCY_ALLOWED_FLAG — currency of the account and whether multiple currencies are permitted.
• AP_USE_ALLOWED_FLAG, AR_USE_ALLOWED_FLAG, XTR_USE_ALLOWED_FLAG, PAY_USE_ALLOWED_FLAG — flags indicating permitted usage by Payables, Receivables, Treasury, and Payments.
• START_DATE, END_DATE — the effective date range of the account/usage.
• ACCOUNT_OWNER_PARTY_ID, ACCOUNT_OWNER_ORG_ID, ACCOUNT_HOLDER_NAME — ownership and holder information.
• CHECK_DIGITS, IBAN_NUMBER, SECONDARY_ACCOUNT_REFERENCE, ACCOUNT_SUFFIX — account identifier components used in payment formatting and validation.
• ATTRIBUTE1–ATTRIBUTE15, ATTRIBUTE_CATEGORY — descriptive flexfield segments.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — standard audit columns.

Common Use Cases and Queries

Typical uses include validating account availability for a user, driving account selection lists in custom forms or reports, and extracting bank account data for external payment or reconciliation systems. Because the view already applies security-profile filtering, queries do not need to re-implement access control logic.

SELECT bank_account_id,
       bank_account_name,
       bank_account_num,
       currency_code,
       ap_use_allowed_flag,
       ar_use_allowed_flag
FROM   apps.ce_bank_accts_gt_v
WHERE  ap_use_allowed_flag = 'Y'
ORDER  BY bank_account_name;

To list accounts with their holder and masked number:

SELECT bank_account_id,
       account_holder_name,
       masked_account_num,
       iban_number
FROM   apps.ce_bank_accts_gt_v
WHERE  bank_id = :p_bank_id;

Since the view is backed by a global temporary table, its contents are session-specific and dependent on prior initialization of the security profile context, so results should always be treated as user- and session-scoped.