Search Results ce_cp_disc_target_v




Overview
Explore in AI Chat

Overview

CE_CP_DISC_TARGET_V is a Cash Management (CE) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to serve as a "Cash Positioning Discoverer View for Target Balances." It is a lightweight, purpose-built projection designed for consumption by Oracle Discoverer (and, by extension, equivalent BI Publisher or OBIEE reporting layers) that support the Cash Positioning workbook. Rather than exposing the full CE_BANK_ACCOUNTS record, the view isolates the subset of data relevant to target balance reporting, exposing only the bank account identifier and its corresponding target balance figure. The view is registered in ETRM with a VALID status, indicating that it compiles and resolves against its referenced object at the documented release levels. Because its grain is one row per bank account, it is not an aggregating or transactional view; it is a simple column-mapping view intended to simplify downstream report definitions and to decouple report SQL from the physical column naming in the base table. Users searching for the term "target_balance" encounter this view because TARGET_BALANCE is the aliased output column that carries the value from CE_BANK_ACCOUNTS.MAX_TARGET_BALANCE.

Underlying Base Objects

The view is defined over a single referenced base object, CE_BANK_ACCOUNTS (documented in ETRM as a SYNONYM resolving to the APPS-owned bank accounts table). The view text as documented is:

SELECT CBA.BANK_ACCOUNT_ID, CBA.MAX_TARGET_BALANCE TARGET_BALANCE FROM CE_BANK_ACCOUNTS CBA

There are no joins, filters, or aggregation in the view definition. Consequently, the row count of CE_CP_DISC_TARGET_V equals the row count of CE_BANK_ACCOUNTS, and every eligible bank account record is represented exactly once. There is a one-to-one relationship between the view and its base object, with the view acting purely as a rename-and-project layer. No WHERE clause restricts the population, so the view does not itself implement any business rule about which accounts are "active" for cash positioning; such filtering must be applied by the reporting query or by the Discoverer workbook definition.

Key Columns

  • BANK_ACCOUNT_ID — The internal, system-generated primary key of the bank account as stored in CE_BANK_ACCOUNTS. It uniquely identifies each cash account and is the natural join key to other Cash Management and Payables/Receivables bank account views.
  • TARGET_BALANCE — The alias applied to CE_BANK_ACCOUNTS.MAX_TARGET_BALANCE. It represents the maximum target balance configured for the bank account, typically the threshold the treasury user wishes to maintain or not exceed when reviewing cash positioning. The alias exists so that report authors can reference a clean, descriptive column name rather than the underlying base column.

Common Use Cases and Queries

The view is most commonly used when building or troubleshooting Cash Positioning Discoverer workbooks that need to display target balances alongside actual account balances. A representative query is:

SELECT bank_account_id, target_balance FROM apps.ce_cp_disc_target_v ORDER BY bank_account_id;

Because the view carries no account names, currencies, or institution details, it is normally joined to complementary Cash Management views to produce a usable report, for example:

SELECT t.bank_account_id, t.target_balance FROM apps.ce_cp_disc_target_v t WHERE t.target_balance IS NOT NULL;

Typical scenarios include reconciling configured maximum target balances against actual end-of-day account balances, validating that treasury parameters were entered during bank account setup, and feeding target balance thresholds into a cash positioning dashboard. Administrators investigating a missing or incorrect target balance in a Discoverer report should verify the value of MAX_TARGET_BALANCE on the corresponding CE_BANK_ACCOUNTS row and confirm that the account has been created under the correct operating unit and legal entity context.