Search Results ce_cp_disc_net_v




Overview
Explore in AI Chat

Overview

CE_CP_DISC_NET_V is an Oracle E-Business Suite view owned by the APPS schema within the Cash Management (CE) product family. ETRM documentation characterizes the object as "No longer Used," a status reinforced by its internal definition, which is a thin aggregation layer built on top of another view, CE_CP_DISC_TRX_V. The "CP" and "DISC" naming convention associates the object with the Cash Positioning and cash discount worksheet functionality used by treasury operations to consolidate and net cash discount transaction balances by bank account.

The view was designed to aggregate transaction balances by worksheet header and bank account, excluding a specific transaction type ('IDA'). This suggests its original purpose was to produce a summarized, net-of-exclusions figure for cash discount worksheets during Cash Positioning processing, likely feeding a worksheet summary form or report rather than a standalone reporting interface. Because the object is documented as no longer used and is not intended for direct customer consumption, it should be treated as a legacy, internal artifact. Organizations on 12.1.1 or 12.2.2 that encounter this view in custom SQL, reports, or interfaces should validate whether the underlying functionality it supports is still active before relying on its output.

Underlying Base Objects

The documented definition of CE_CP_DISC_NET_V selects from CE_CP_DISC_TRX_V, applying the filter TRX_TYPE <> 'IDA' and grouping by WORKSHEET_HEADER_ID and BANK_ACCOUNT_ID. The dependency chain therefore runs from CE_CP_DISC_NET_V to CE_CP_DISC_TRX_V, and the ETRM metadata lists additional referenced objects including the ARP_CASHBOOK package, FND_ACCESS_CONTROL_UTIL, FND_GLOBAL, FND_PROFILE, MO_GLOBAL, and XTR_USER_ACCESS. Because CE_CP_DISC_TRX_V is security-enabled, invoking the parent view indirectly triggers row-level access checks through the MO_GLOBAL and XTR_USER_ACCESS packages.

The dependency on FND_GLOBAL and FND_PROFILE indicates that the view logic evaluates session and profile option context at runtime, including the current user's operating unit and application security settings. ARP_CASHBOOK supplies cashbook and bank account configuration data used to interpret the bank account identifiers returned by the view. These dependencies mean the view is not a simple static snapshot; its effective result set is constrained by the security and session context of the querying user.

Key Columns

The view exposes three columns as documented in its projection. WORKSHEET_HEADER_ID identifies the cash positioning or cash discount worksheet to which the aggregated balances belong, and serves as the primary grouping key. BANK_ACCOUNT_ID identifies the internal bank account associated with the aggregated balance, and is the secondary grouping key.

BALANCE is a summed value representing the total of the individual transaction balances retrieved from CE_CP_DISC_TRX_V for each worksheet and bank account combination, after excluding transactions whose TRX_TYPE equals 'IDA'. Because the column is an aggregate, it has no meaning without the corresponding worksheet header and bank account context. The exclusion of 'IDA' transactions distinguishes this "net" view from the unaggregated transaction view, and indicates that 'IDA' type rows are intentionally omitted from the totals presented here.

Common Use Cases and Queries

Given its "No longer Used" designation, this view is primarily relevant for troubleshooting legacy customizations, migration analysis, and understanding the former cash positioning data model. A diagnostic query to inspect the view's output follows:

  • Aggregated balances per worksheet and bank account: SELECT WORKSHEET_HEADER_ID, BANK_ACCOUNT_ID, BALANCE FROM APPS.CE_CP_DISC_NET_V WHERE WORKSHEET_HEADER_ID = :worksheet_id; This returns the net summed balance per bank account for a specified worksheet.
  • Comparing net versus detail figures: join or pivot against CE_CP_DISC_TRX_V to confirm which 'IDA' transactions were excluded from the aggregation totals.
  • Impact assessment queries during upgrades: identify whether any custom reports, concurrent programs, or PL/SQL code still reference APPS.CE_CP_DISC_NET_V, since the object should not be used in new development.

Because the view enforces security context through its underlying security-enabled objects, results depend on NLS and profile settings. New implementations should avoid this view and instead use supported Cash Management tables and views for cash positioning reporting.