Search Results ce_so_fc_orders_terms_v




Overview
Explore in AI Chat

Overview

CE_SO_FC_ORDERS_TERMS_V is a Cash Management (CE) forecasting source view owned by the APPS schema. It exposes open sales order lines together with their associated payment term components, providing the data set that the Cash Management forecasting engine consumes when projecting future cash receipts from sales orders. The view name reflects its composition: CE (Cash Management), SO (sales order), FC (forecast), ORDERS, and TERMS, the last indicating that payment term schedule detail is joined into the result set. Because it is a view rather than a table, it is functionally read-only and derives every row at query time from Oracle Order Management, Receivables, and Trading Community Architecture base objects.

The object carries a VALID status in the ETRM 12.2.2 repository, meaning its definition compiles and its dependencies resolve in a supported configuration. The user search term term_due_date corresponds directly to the TERM_DUE_DATE column defined in the view text as TERM_L.DUE_DATE, sourced from RA_TERMS_LINES.

Underlying Base Objects

The view is defined over five referenced base objects, all reached through APPS synonyms:

The joins are outer where site-level profile data may be absent, and the customer account join enforces CP_CUST.SITE_USE_ID IS NULL so that only account-level profile records are matched.

Key Columns

  • TERM_DUE_DATE — the scheduled due date of the payment term line; the column most directly associated with the search term term_due_date.
  • TERM_DUE_DAYS, TERM_DUE_DAY_OF_MONTH, TERM_DUE_MONTHS_FORWARD — the relative components used to derive term schedules.
  • RELATIVE_AMOUNT — the portion of the term amount applicable to the schedule line.
  • ORG_ID, TRANSACTIONAL_CURR_CODE — operating unit and transaction currency context.
  • Forecast amount expressions — the two DECODE-based amount columns compute ordered less invoiced quantity multiplied by unit selling price, plus tax, signed positive for 'ORDER' and negative for 'RETURN' line categories.
  • ORDERED_DATE, REQUEST_DATE — truncated dates defaulting to SYSDATE where null, supporting forecast date placement.
  • BOOKED_FLAG, FLOW_STATUS_CODE, ORDER_NUMBER, LINE_NUMBER — identification and lifecycle status.
  • PROFILE_CLASS_ID, NAME — customer profile classification resolved through HZ tables.
  • The final concatenated expression (LINE_ID, TERM_ID, SEQUENCE_NUM) provides a synthetic unique key per forecast row.

Common Use Cases and Queries

Typical use is Cash Management forecast analysis and reconciliation of projected receipts by payment term due date. A representative query filters by operating unit and due date window:

SELECT order_number, line_number, transactional_curr_code,
       term_due_date, relative_amount
  FROM apps.ce_so_fc_orders_terms_v
 WHERE org_id = :p_org_id
   AND term_due_date BETWEEN :p_from_date AND :p_to_date
 ORDER BY term_due_date;

Aggregation by due date supports cash positioning:

SELECT TRUNC(term_due_date) due_date,
       transactional_curr_code,
       SUM(relative_amount) forecast_amount
  FROM apps.ce_so_fc_orders_terms_v
 WHERE org_id = :p_org_id
 GROUP BY TRUNC(term_due_date), transactional_curr_code;

Because the view is not indexed directly, performance depends on the underlying Order Management and Receivables indexes; queries should always be constrained by ORG_ID and a date range. Reporting tools and custom Cash Management forecast extensions frequently query this view as a substitute for the standard forecast generation program when line-level term detail is required.