Search Results ce_cp_disc_pay_v




Overview

CE_CP_DISC_PAY_V is an APPS-owned database view within the Oracle Cash Management (CE) module, operating under Oracle E-Business Suite releases 12.1.1 and 12.2.2. Its documented purpose is to serve as a Cash Positioning Discoverer view for payroll expenses. In practical terms, it functions as a reporting projection that surfaces payroll-related cash movements against a specific bank account, expressed in a form suitable for consumption by Oracle Discoverer and similar ad hoc reporting tools that support the cash positioning workbook.

The view supplies the data needed to display a payroll worksheet line, its associated bank account, a display description, a computed balance amount, and a reference identifier within the cash positioning worksheet. It is a read-only reporting construct designed to feed the Cash Positioning worksheet interface rather than to store transactional data. Because cash positioning reconciles expected and actual cash activity across bank accounts, this view provides the payroll expense leg of that reconciliation, restricted to the current system date.

Underlying Base Objects

The view is defined over three referenced objects:

  • CE_CP_WORKSHEET_LINES (referenced as a SYNONYM) — the Cash Positioning worksheet line definition. It is the driver of the join, filtered to SOURCE_TYPE = 'PAY' and INCLUDE_FLAG = 'Y', identifying which payroll source lines are active on the worksheet.
  • CE_PAY_FC_PAYROLL_V (VIEW) — the payroll cash forecast view supplying transaction-level payroll amounts, currency, reference identifiers, transaction date, bank account, payroll identifier, and payment method.
  • CE_CP_XTR_BANK_ACCOUNTS_V (VIEW) — the bank account extraction view providing the account currency used in the amount decode logic.

The joins establish the payroll activity that belongs to each worksheet line, constrained by payroll identifier and receipt (payment) method, and anchored to a matching bank account. A hard condition, PAY.TRX_DATE = TO_DATE(SYSDATE,'YYYY/MM/DD'), restricts the result set to transactions dated the current day.

Key Columns

  • WORKSHEET_HEADER_ID — Identifier of the cash positioning worksheet header that owns the line, linking the row back to its parent worksheet.
  • WORKSHEET_LINE_ID — Identifier of the individual worksheet line, the detailed key for the payroll entry.
  • BANK_ACCOUNT_ID — The internal bank account against which the payroll cash movement is reported.
  • DESCRIPTION — Descriptive text for the worksheet line, inherited from the worksheet line definition.
  • DETAIL — Carries the payroll reference identifier, cast to character using TO_CHAR(PAY.REFERENCE_ID), for display purposes.
  • BALANCE — The signed payroll amount. The value is -DECODE(PAY.CURRENCY_CODE, XBA.CURRENCY_CODE, PAY.AMOUNT, PAY.BASE_AMOUNT), meaning that when the payroll transaction currency matches the bank account currency the transaction amount is used, otherwise the base amount is used; the sign is negated because payroll expenses represent an outflow.
  • REFERENCE_ID — The raw numeric reference identifier from the payroll view, exposed alongside its character equivalent for joins and drill-down.

Common Use Cases and Queries

Typical scenarios include building a cash positioning worksheet that incorporates same-day payroll disbursements, extending Discoverer workbooks for treasury and payroll reconciliation, and validating that payroll lines map correctly to bank accounts and payment methods. A representative query lists the current day's payroll cash impact by worksheet line:

  • SELECT worksheet_header_id, worksheet_line_id, bank_account_id, description, detail, balance, reference_id FROM apps.ce_cp_disc_pay_v ORDER BY worksheet_header_id, worksheet_line_id;

A treasury-oriented variant aggregates total payroll outflow per bank account:

  • SELECT bank_account_id, SUM(balance) total_payroll_outflow FROM apps.ce_cp_disc_pay_v GROUP BY bank_account_id;

Because results are implicitly limited to today's transactions and to lines flagged for inclusion, queries should not be relied upon for historical payroll reporting. Any output should be validated against the underlying payroll forecast view when reconciling balances.