Search Results ce_ar_fc_receipts_v




Overview
Explore in AI Chat

Overview

CE_AR_FC_RECEIPTS_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 serves as a forecasting source for Accounts Receivable receipts, exposing the receipt-level data that the Cash Management cash forecasting engine consumes when projecting expected cash inflows. Rather than reading numerous AR and CE base tables directly, the forecast process queries this view to obtain a consolidated, filter-ready picture of receipts that have a projected value or clearing date.

The view is not a transactional entry point; it is a read-only reporting and integration object. Its design reflects the business rule that only receipts with a determinable cash date—either an actual value date or an anticipated clearing date—are meaningful for forecasting. Receipts that are fully reversed, in an unapproved state, or whose bank account is flagged for netting are excluded so that double counting does not occur in the forecast.

Underlying Base Objects

The documented base objects underlying CE_AR_FC_RECEIPTS_V are:

The receipt drives the join: CR.CASH_RECEIPT_ID equals CRH.CASH_RECEIPT_ID, with APS outer-joined on CASH_RECEIPT_ID and org-conformed across CR, CRH, and APS. The view is defined as a UNION ALL of two branches that differ in the cash-date logic (value/clearing date versus due date), producing a complete set of forecastable receipts.

Key Columns

  • ACCTD_AMOUNT and AMOUNT — receipt amount and its accounted equivalent, used as the forecast value.
  • CURRENCY_CODE — receipt currency from AR_CASH_RECEIPTS_ALL.
  • TRX_DATE and DUE_DATE — receipt transaction date and payment schedule due date.
  • ACTUAL_VALUE_DATE and ANTICIPATED_CLEARING_DATE — the value and clearing dates; NVL(ACTUAL_VALUE_DATE, ANTICIPATED_CLEARING_DATE) is used as the effective forecast date.
  • BANK_ACCOUNT_ID — derived via subquery on CE_BANK_ACCT_USES_ALL.
  • RECEIPT_METHOD_ID — receipt method reference for method-level forecasting.
  • Status expression — DECODE over ARP_CASHBOOK.RECEIPT_DEBIT_MEMO_REVERSED, yielding 'REVERSED' or the history status.
  • ORG_ID, RECEIPT_NUMBER, CASH_RECEIPT_ID — multi-org and receipt identity columns.

Common Use Cases and Queries

Typical uses include cash forecast validation, reconciliation of anticipated AR inflows, and diagnostic reporting on why a receipt did or did not feed the forecast. A representative query:

  • SELECT receipt_number, currency_code, amount, NVL(actual_value_date, anticipated_clearing_date) cash_date FROM ce_ar_fc_receipts_v WHERE org_id = :p_org ORDER BY cash_date;
  • Filter by RECEIPT_METHOD_ID or BANK_ACCOUNT_ID to analyze forecast contributions by method or bank account.
  • Compare SUM(amount) by currency against AR Aging to reconcile forecasted receipts to open AR.

Because the view already enforces the netting, reversal, and status exclusions, querying it directly yields the same population the Cash Management forecast consumes, making it the preferred reference for forecast reconciliation.