Search Results ce_po_fc_orders_v




Overview
Explore in AI Chat

Overview

CE_PO_FC_ORDERS_V is a Cash Management (CE) forecasting view owned by the APPS schema. It is one of the standard forecasting source views used by the Oracle Cash Management cash forecast engine to project future cash outflows arising from open purchase orders for goods and services. The view consolidates purchase order commitments into a normalized, forecast-ready result set that returns one row per purchase order distribution, expressed in the functional (ledger) currency so that it can be aggregated alongside other forecasting sources such as AP invoices, AR transactions, and payroll.

The view is referenced internally by the Cash Management forecast generation programs and by the Cash Forecasting window when the "Purchase Orders" source is enabled. Third-party reporting and treasury dashboards also query it directly because it pre-applies the complex commitment logic (matching basis, price overrides, nonrecoverable tax, currency conversion via rate columns) that would otherwise have to be re-implemented by each consumer.

In Oracle EBS 12.1.1 and 12.2.2 the view is documented as VALID in the APPS schema. Its definition joins Purchasing tables to AP supplier tables, GL ledgers, and financials system parameters, making it a cross-product construct rather than a pure PO view.

Underlying Base Objects

The documented referenced base objects (via APPS synonyms) are:

Key Columns

  • SEGMENT1 (column 1) — the purchase order number, used as the forecast document reference.
  • Forecast amount (column 2) — the unconverted commitment amount, derived from either AMOUNT_ORDERED less delivered and cancelled amounts plus nonrecoverable tax, or quantity-based calculation multiplied by PRICE_OVERRIDE.
  • Forecast amount in ledger currency (column 3) — the same value multiplied by NVL(POD.RATE, NVL(POH.RATE, 1)).
  • Forecast date (column 4) — NVL of promised date, need-by date, acceptance due date, or creation/release date; this drives the cash forecast bucket.
  • Currency code (column 5) — NVL of PO currency, invoice currency, or ledger currency.
  • Authorization status (column 6) — header or release level; defaults to 'INCOMPLETE'.
  • Payment priority (column 7) and payment group (column 9) — inherited from supplier or supplier site, defaulting to 99 and '-1'.
  • Vendor type (column 8), ORG_ID (10), PROJECT_ID (11), LINE_NUM (12), PO_DISTRIBUTION_ID (13).
  • VALUE_BASIS (14), PURCHASE_BASIS (15), MATCHING_BASIS (16) — Purchasing control attributes passed through for downstream filtering.

Common Use Cases and Queries

Typical usage includes cash forecast reconciliation, PO commitment ageing, and treasury liquidity planning. A representative query:

SELECT segment1, forecast_date, forecast_amount
FROM   ce_po_fc_orders_v
WHERE  authorization_status = 'APPROVED'
AND    forecast_date BETWEEN :p_from AND :p_to
AND    org_id = :p_org_id;

Analysts commonly group by forecast_date to build weekly or monthly outflow buckets, or join to PO_HEADERS_ALL on SEGMENT1 for additional descriptors. Because the view returns one row per distribution, aggregates should sum both amount and quantity columns carefully to avoid double counting where multiple distributions exist on a single shipment.