Search Results ce_so_fc_orders_v




Overview
Explore in AI Chat

Overview

CE_SO_FC_ORDERS_V is a seeded, read-only view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Cash Management (CE) product and serves as a forecasting source for sales orders. Specifically, the view is designed to retrieve open sales order lines for use in cash forecasting when the user has not enabled the option to include payment terms in the forecast calculation. In this configuration, Cash Management projects anticipated cash inflows directly from unshipped or uninvoiced order lines rather than deriving them from payment term schedules.

Because it is a database view, CE_SO_FC_ORDERS_V exposes no storage of its own and performs no DML. Its status is recorded as VALID, and it is queried internally by the Cash Management forecasting engine, which aggregates its rows by organization, currency, and date to build the anticipated receipts component of the cash forecast. Report developers and integration specialists also use it to reconcile the forecast figures produced by standard Cash Management functionality.

Underlying Base Objects

The view is defined over four documented base objects, all accessed through APPS synonyms:

  • OE_ORDER_HEADERS_ALL — the order header, supplying organization, transactional currency, conversion type, ordered date, requested date, booking status, order type, and order number.
  • OE_ORDER_LINES_ALL — the order line, supplying line category, ordered quantity, invoiced quantity, unit selling price, tax value, requested date, commitment, project, flow status, and line identifiers.
  • HZ_CUSTOMER_PROFILES — accessed twice (aliased CP_SITE for the site/account profile and CP_CUST for the customer account profile) to resolve the applicable profile class.
  • HZ_CUST_PROFILE_CLASSES — aliased CP_CLASS, providing the profile class name and identifier used to associate the correct credit and payment terms profile for forecasting.

The joins restrict output to open orders (H.OPEN_FLAG = 'Y'), exclude fully interfaced lines (INVOICE_INTERFACE_STATUS_CODE in 'NO' or 'PARTIAL'), and resolve the profile class through an outer join on the site use with a fallback to the customer account level.

Key Columns

Common Use Cases and Queries

Typical scenarios include validating forecast receipts against open order backlog, analyzing residual order value by operating unit and currency, and diagnosing discrepancies between order entry and forecast output.

SELECT org_id, transactional_curr_code, SUM(forecast_amount)
FROM   ce_so_fc_orders_v
GROUP  BY org_id, transactional_curr_code;

Identifying open lines for a specific order number:

SELECT order_number, line_number, flow_status_code
FROM   ce_so_fc_orders_v
WHERE  order_number = :order_number
AND    booked_flag = 'Y';

Because the view excludes lines where payment terms are used in forecasting and filters on open, partially interfaced orders, results should be interpreted as the sales order contribution under the non-payment-term forecast option only.