Search Results ce_cp_disc_app_v




Overview
Explore in AI Chat

Overview

CE_CP_DISC_APP_V is an Oracle E-Business Suite view owned by the APPS schema in the Cash Management (CE) product. Its documented purpose is to serve as a Cash Positioning Discoverer View for AP Payments. It is one of a family of "CP_DISC" (Cash Positioning Discoverer) views that expose a flattened, query-friendly record set suitable for Oracle Discoverer workbooks, ad hoc reporting, and downstream integration extracts against cash positioning data.

The view consolidates worksheet line information with Accounts Payable payment details and bank account attributes so that users performing cash positioning can see, for a given bank account and worksheet, the AP payment lines that contribute to the projected cash balance. The view is delivered in both 12.1.1 and 12.2.2 and is registered as VALID in the ETRM data dictionary. It is a read-only presentation object: no DML is performed against it, and all values are derived from the referenced base objects at query time.

Underlying Base Objects

The view is defined over three principal referenced objects plus one package:

  • CE_AP_FC_PAYMENTS_V (VIEW) — the foreign-currency-aware AP payments source, aliased AP. Supplies the bank account, check number, currency, amount, base amount, value dates, payment method, status, and reference identifier.
  • CE_CP_WORKSHEET_LINES (SYNONYM) — the cash positioning worksheet line source, aliased WSL. Supplies the worksheet header and line identifiers, the description text, the source type, and the include, cleared transaction, and payment method filter flags.
  • CE_CP_XTR_BANK_ACCOUNTS_V (VIEW) — the bank account extraction view, aliased XBA. Supplies the functional currency used to decide whether the transaction amount or base amount is returned.
  • FND_GLOBAL (PACKAGE) — the standard EBS context package used by Discoverer and similar views for responsibility and user context resolution.

The join is a three-way equijoin: worksheet lines are restricted to SOURCE_TYPE = 'APP', the AP bank account must match the extracted bank account, and payment method compatibility is enforced through an optional predicate.

Key Columns

  • WORKSHEET_HEADER_ID — identifies the cash positioning worksheet that owns the line, enabling grouping by worksheet.
  • WORKSHEET_LINE_ID — the individual worksheet line, the natural grain of the view.
  • BANK_ACCOUNT_ID — the internal bank account identifier for the AP payment and the cash positioning worksheet.
  • DESCRIPTION — the worksheet line description, typically the payment or transaction narrative.
  • DETAIL — the check number rendered as a character string via TO_CHAR(AP.CHECK_NUMBER), used as the display detail for the line.
  • BALANCE — the signed cash impact of the payment. It is computed as the negative of AMOUNT when the payment currency equals the bank account currency, otherwise the negative of BASE_AMOUNT. The negation reflects the fact that AP payments reduce the bank balance.
  • REFERENCE_ID — the payment reference identifier from the AP source, supporting drill-down back to the originating payment record.

Common Use Cases and Queries

Typical usage includes Discoverer worksheets that display same-day AP disbursements by bank account, reconciliation extracts comparing worksheet lines to cleared payments, and diagnostic queries used to confirm why a payment does or does not appear on a cash positioning worksheet. Because the view filters on the current system date, results are inherently point-in-time.

A representative query that summarizes same-day AP payment impact by bank account:

  • SELECT bank_account_id, worksheet_header_id, COUNT(*) line_count, SUM(balance) total_balance
  • FROM apps.ce_cp_disc_app_v
  • GROUP BY bank_account_id, worksheet_header_id
  • ORDER BY bank_account_id;

To inspect individual worksheet lines for a specific worksheet:

  • SELECT worksheet_line_id, description, detail, balance, reference_id
  • FROM apps.ce_cp_disc_app_v
  • WHERE worksheet_header_id = :p_header_id;

The view honors the NVL chain on ACTUAL_VALUE_DATE, ANTICIPATED_VALUE_DATE, MATURITY_DATE, and PAYMENT_DATE, together with the INCLUDE_FLAG and cleared transaction or NEGOTIABLE status predicates, so results are already filtered to the transactions that legitimately belong on the current-day cash position. Any custom reporting should preserve these documented semantics rather than reimplementing them against the base tables.