Search Results ce_cp_disc_xto_v




Overview

CE_CP_DISC_XTO_V is a Cash Management (CE) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is documented in the ETRM as the "Cash Positioning Discoverer View for Treasury Outflow." Its purpose is to expose cash flow records with a negative amount (outflows) from the Treasury (XTO) module, filtered by the current system date and by inclusion flags held on Cash Positioning Worksheet lines, so that they can be reported and analyzed through Oracle Discoverer or equivalent reporting tools.

The view returns one row per qualifying worksheet line, combining attributes of the cash positioning worksheet line with attributes of the underlying treasury cash flow. Because it is a read-only reporting object, it plays no role in transaction processing; it is consumed by Analytics/Discoverer workbooks and, potentially, by custom SQL reports and integrations that need a pre-filtered list of same-day treasury outflows.

Underlying Base Objects

The view is defined over two documented base objects:

  • CE_XTR_CASHFLOWS_V (VIEW) — the treasury cash flow view, aliased as XTO in the definition. It supplies the deal number, amount, bank account, transaction date, reconciliation status, DDA deal type/subtype, and reference identifier.
  • CE_CP_WORKSHEET_LINES (SYNONYM) — the Cash Positioning Worksheet lines, aliased as WSL. It supplies the worksheet header identifier, worksheet line identifier, line description, source type, include flag, cleared transaction flag, and indicative flag.

The join between the two objects is implicit rather than key-based: rows are combined on a set of date and flag predicates cast as a filter, with the transaction date constrained to the current system date (TRX_DATE = TO_DATE(SYSDATE,'YYYY/MM/DD')). Filters applied include SOURCE_TYPE = 'XTO', INCLUDE_FLAG = 'Y', AMOUNT < 0 (outflows only), and the reconciliation condition (CLEARED_TRX_FLAG = 'Y' OR XTO.RECONCILED_REFERENCE IS NULL). An additional clause excludes certain indicative deals, keeping a row unless the deal type/subtype is the EXP/INDIC combination or the line is flagged as indicative.

Key Columns

  • WORKSHEET_HEADER_ID — identifies the Cash Positioning Worksheet header to which the line belongs.
  • WORKSHEET_LINE_ID — identifier of the individual worksheet line.
  • BANK_ACCOUNT_ID — the bank account associated with the treasury cash flow.
  • DESCRIPTION — the worksheet line description shown in the report.
  • DETAIL — the deal number rendered as text via TO_CHAR(XTO.DEAL_NUMBER).
  • BALANCE — the cash flow amount (XTO.AMOUNT), negative for outflows.
  • REFERENCE_ID — the reference identifier from the treasury cash flow, used for traceability and drilldown.

These aliases correspond directly to the SELECT list in the documented view text, where DESCRIPTION, DETAIL, BALANCE, and REFERENCE_ID map to WSL.DESCRIPTION, TO_CHAR(XTO.DEAL_NUMBER), XTO.AMOUNT, and XTO.REFERENCE_ID respectively.

Common Use Cases and Queries

Typical uses include daily cash positioning reports that isolate same-day treasury outflows, reconciliation reviews of cleared or not-yet-reconciled items, and exclusion of indicative deals from reported balances. A representative query:

SELECT worksheet_header_id, bank_account_id, worksheet_line_id,
       description, detail, balance, reference_id
FROM   apps.ce_cp_disc_xto_v
WHERE  bank_account_id = :p_bank_account_id
ORDER  BY detail;

Aggregate reporting at the account level follows the same pattern:

SELECT bank_account_id, SUM(balance) total_outflow, COUNT(*) line_count
FROM   apps.ce_cp_disc_xto_v
GROUP  BY bank_account_id;

Because the view filters on SYSDATE, results are inherently "as of today"; historical reporting requires querying the underlying worksheet and cash flow objects directly. Access should be granted through the APPS schema with standard Cash Management responsibilities.