Search Results ce_cp_ws_ba_disc_v




Overview
Explore in AI Chat

Overview

CE_CP_WS_BA_DISC_V is a valid Oracle E-Business Suite view owned by the APPS schema and shipped as part of the Cash Management (CE) product. Its name encodes its purpose: a Cash Positioning (CP) worksheet (WS) viewer that discovers/displays (DISC) eligible bank accounts (BA) available for inclusion on a cash positioning worksheet. In the Cash Management cash positioning workflow, users build a worksheet by selecting the cash pools, bank accounts, and source documents whose balances should be consolidated and reported. This view supports that process by resolving, at query time, the bank accounts that satisfy the worksheet line criteria so that the application can present selectable accounts and the balances associated with them.

Because it is a view and not a table, it stores no data of its own. It is a runtime projection that joins the bank account definition views against the cash positioning worksheet lines, applying inclusion rules, legal entity restrictions, and account classification filters. It is therefore a reporting and integration object rather than a transactional one, and any content returned depends entirely on how the underlying worksheet lines have been configured.

Underlying Base Objects

The documented referenced objects, as recorded in ETRM for 12.2.2, are:

  • CE_BANK_ACCOUNTS_V (view) — the primary source of bank account attributes: account identifier, currency, legal entity owner, and name.
  • CE_BANK_BRANCHES_V (view) — supplies bank branch and bank name information used to match worksheet line criteria.
  • CE_CASHPOOL_SUB_ACCTS (synonym) — contains the pool-to-sub-account relationships used to expand cash pool membership into individual accounts.
  • CE_CASHPOOLS (synonym) — provides the cash pool header information against which worksheet lines are matched.
  • CE_CP_WORKSHEET_LINES (synonym) — the driving table, containing the worksheet header, source type, include flag, and account selection criteria entered by the user.
  • FND_ACCESS_CONTROL_UTIL, FND_GLOBAL, FND_PROFILE, MO_GLOBAL, XTR_USER_ACCESS (packages) — the multi-org and access-control framework packages referenced by the view definition to enforce organizational and user-level security.

Key Columns

  • WORKSHEET_HEADER_ID — links the returned account rows back to the parent cash positioning worksheet.
  • BANK_ACCOUNT_ID — the bank account identifier; for direct account selections, it comes from the worksheet line or bank account view, while for pool-derived rows it is sourced from CE_CASHPOOL_SUB_ACCTS.ACCOUNT_ID.
  • CURRENCY_CODE — the currency of the qualifying bank account, taken from CE_BANK_ACCOUNTS_V.
  • LEGAL_ENTITY_ID — the account owner organization, exposed as ACCOUNT_OWNER_ORG_ID from CE_BANK_ACCOUNTS_V, used to enforce legal entity restrictions on worksheet lines.
  • BANK_ACCOUNT_NAME — the descriptive name of the bank account for display on the worksheet.
  • BALANCE_TYPE and FLOAT_TYPE — carried from CE_CP_WORKSHEET_LINES, determining which balance/f loat conventions apply when the account is included.
  • Two numeric placeholder columns populated as NULL, reserved for values supplied elsewhere in the worksheet processing logic.

Common Use Cases and Queries

The view is typically consumed by cash positioning setup and diagnostic reports: identifying which internal bank accounts will be picked up by a given worksheet, verifying that legal entity and bank name restrictions behave as intended, and diagnosing why an expected account did not appear.

To list the accounts selected for a specific worksheet:

  • SELECT worksheet_header_id, bank_account_id, bank_account_name, currency_code, legal_entity_id, balance_type FROM apps.ce_cp_ws_ba_disc_v WHERE worksheet_header_id = :p_header_id;

To confirm account availability by currency and legal entity:

  • SELECT legal_entity_id, currency_code, COUNT(*) FROM apps.ce_cp_ws_ba_disc_v GROUP BY legal_entity_id, currency_code;

Because access-control packages are referenced, results are filtered by the responsibi lity's organization and user security context; queries should be executed under an APPS-enabled session with the correct MO profile options set.