Results for “default_account_flag”

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

Overview

CE_BANK_ACCT_USES_GT_V is a Cash Management (CE) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes bank account usage records that are visible to the current user based on the security profile assigned to that user session. Unlike the transaction tables that store bank account usage data permanently, this view filters the underlying data through the CE_SECURITY_PROFILES_GT global temporary table population, returning only the bank account uses that fall within the user's authorized operating units, business groups, and legal entities.

The view inherits its "_GT_V" suffix convention because it derives from a global temporary table (CE_SECURITY_PROFILES_GT) that holds security profile organization identifiers populated at runtime. It is a read-only, security-scoped access layer rather than a storage object, and it is used throughout Cash Management, Payables, Receivables, Payments, and Treasury flows to resolve which bank accounts a user may reference. The INVESTMENT_LIMIT_CODE column, which is frequently sought by implementers, resides here as an attribute of each bank account use.

Underlying Base Objects

The view is defined over two documented objects, both exposed to the APPS schema as synonyms:

• CE_BANK_ACCT_USES_ALL — the primary transactional table holding bank account use assignments, aliased as BAU. It supplies every column projected by the view, including ORG_ID, LEGAL_ENTITY_ID, and INVESTMENT_LIMIT_CODE.
• CE_SECURITY_PROFILES_GT — a global temporary table aliased as OU, holding ORGANIZATION_ID and ORGANIZATION_TYPE values for the current security profile.

The join is:
(BAU.ORG_ID = OU.ORGANIZATION_ID AND OU.ORGANIZATION_TYPE IN ('BUSINESS_GROUP','OPERATING_UNIT'))
OR (BAU.LEGAL_ENTITY_ID = OU.ORGANIZATION_ID AND OU.ORGANIZATION_TYPE = 'LEGAL_ENTITY')

Because the join can produce duplicate rows when multiple security organizations map to the same bank account use, the view is defined with SELECT DISTINCT. The view therefore always reflects the access rights of the currently connected user and cannot be queried for another user's security context.

Key Columns

• BANK_ACCT_USE_ID / BANK_ACCOUNT_ID — primary key of the usage record and the parent bank account.
• ORG_ID / ORG_PARTY_ID — operating unit that owns the usage.
• LEGAL_ENTITY_ID — legal entity to which the bank account use belongs; also the driver of the legal entity branch of the security join.
• INVESTMENT_LIMIT_CODE / FUNDING_LIMIT_CODE — codes controlling investment and funding limits applied to the bank account use.
• AP_USE_ENABLE_FLAG, AR_USE_ENABLE_FLAG, XTR_USE_ENABLE_FLAG, PAY_USE_ENABLE_FLAG — flags indicating whether the account use is enabled for Payables, Receivables, Treasury, and Payments respectively.
• POOLED_FLAG, PORTFOLIO_CODE, AUTHORIZED_FLAG, PRICING_MODEL — cash pooling, portfolio, authorization, and pricing attributes.
• END_DATE — effective end date of the usage; NULL indicates an active use.
• ATTRIBUTE_CATEGORY through ATTRIBUTE15 — the standard descriptive flexfield columns.
• Audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY) and WHO columns (REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID) are carried through for traceability.

Common Use Cases and Queries

The view is typically queried to report on bank account usages within the user's security scope, to resolve the INVESTMENT_LIMIT_CODE or FUNDING_LIMIT_CODE for a given account, or to drive LOV and validation logic. A representative query filtered on the investment limit code is:

SELECT bank_acct_use_id, bank_account_id, org_id, legal_entity_id, investment_limit_code, funding_limit_code
FROM apps.ce_bank_acct_uses_gt_v
WHERE investment_limit_code IS NOT NULL
ORDER BY org_id, bank_acct_use_id;

To list only active usages enabled for Treasury:

SELECT bank_account_id, org_id, portfolio_code, investment_limit_code
FROM apps.ce_bank_acct_uses_gt_v
WHERE xtr_use_enable_flag = 'Y' AND end_date IS NULL;

Because the view is secured through a global temporary table, any query must execute within a properly initialized session context; ad hoc queries run outside that context may return no rows. Developers building custom reports should invoke the view from within the standard Cash Management security initialization or use the seeded security APIs rather than querying the base table directly.