Results for “ce_bank_acct_uses”

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

Overview

CE_BANK_ACCT_USES is a VALID view owned by the APPS schema in Oracle E-Business Suite, belonging to the Cash Management (CE) product family. It presents bank account usage definitions — the association between an internal bank account and the operating unit or legal entity context in which that account may be used — together with the flags and identifiers that govern how each usage is enabled across the subledgers. In EBS 12.1.1 and 12.2.2, this view is the principal read interface consumed by reports, concurrent programs, and integration code that must determine which bank accounts are available to a given organization and which application (Payables, Receivables, Treasury, or Payroll) may transact against them. Because Cash Management maintains bank account data in a multi-organization model, the view applies row-level security at query time rather than exposing raw table contents, making it the recommended access path for custom reporting and data extraction.

Underlying Base Objects

The documented view definition is a UNION ALL of two branches. The first selects from the synonym CE_BANK_ACCT_USES_OU, which resolves to the operating-unit-partitioned usage records. The second branch selects DISTINCT rows from CE_BANK_ACCT_USES_ALL, the synonym for the underlying base table holding bank account uses across all organizations. The DISTINCT in the second branch intersects the multi-org rows against the same column list, ensuring that records not already surfaced by the operating unit branch, but legitimately visible to the session, are also returned. Row visibility is enforced through the supporting objects documented for the view: the views CE_SECURITY_PROFILES_V and the packages FND_ACCESS_CONTROL_UTIL, FND_GLOBAL, FND_PROFILE, MO_GLOBAL, and XTR_USER_ACCESS. Together these supply the MO (multi-organization) security predicates, profile option evaluation, and Treasury user-access logic that restrict output to the bank accounts the current responsibility and user are permitted to see. The view therefore functions as a security-filtered projection over the physical usage table rather than a simple join.

Key Columns

• BANK_ACCT_USE_ID — Primary identifier of the usage record; the join key used by downstream subledger tables.
• BANK_ACCOUNT_ID — Foreign key to the internal bank account being used.
• ORG_ID and ORG_PARTY_ID — Operating unit and party context in which the usage is valid.
• PRIMARY_FLAG — Indicates whether this usage is the primary one for the account.
• AP_USE_ENABLE_FLAG, AR_USE_ENABLE_FLAG, XTR_USE_ENABLE_FLAG, PAY_USE_ENABLE_FLAG — Enablement flags controlling availability to Payables, Receivables, Treasury, and Payroll respectively.
• AP_DEFAULT_SETTLEMENT_FLAG, XTR_DEFAULT_SETTLEMENT_FLAG, DEFAULT_ACCOUNT_FLAG — Designations for default settlement and default account behavior.
• LEGAL_ENTITY_ID — Legal entity associated with the usage, relevant to 12.2 legal entity architecture.
• END_DATE — Date on which the usage ceases to be effective.
• POOLED_FLAG, INVESTMENT_LIMIT_CODE, FUNDING_LIMIT_CODE, PORTFOLIO_CODE, PRICING_MODEL — Treasury and cash pooling attributes.
• AUTHORIZED_FLAG and the RECEIVABLES_TRX_ID columns — Authorization status and transaction defaults for receivables processing.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — Descriptive flexfield storage.
• WHO columns and OBJECT_VERSION_NUMBER — Audit and optimistic locking fields.

Common Use Cases and Queries

Typical scenarios include validating which bank accounts a Payables payment batch may draw upon, deriving the default settlement account for a given operating unit, and populating custom extracts of active Treasury usages. The following query lists active, Payables-enabled usages for a specific operating unit:

SELECT bank_acct_use_id, bank_account_id, primary_flag, ap_default_settlement_flag
FROM ce_bank_acct_uses
WHERE org_id = :p_org_id
AND ap_use_enable_flag = 'Y'
AND (end_date IS NULL OR end_date > SYSDATE);

Because access control is applied inside the view, joins to CE_BANK_ACCOUNTS for account numbers require no additional organization predicate. Queries that omit ORG_ID still return only rows permitted by the session's security profile. Reporting tools and interface programs should read this view rather than CE_BANK_ACCT_USES_ALL directly, since the ALL synonym bypasses the security filtering logic documented for the view.