Search Results line_flow_status_code




Overview
Explore in AI Chat

Overview

APPS.CE_SO_FC_ORDERS_NO_TERMS_V is a cash management forecasting view in Oracle E-Business Suite, deployed across both 12.1.1 and 12.2.2. It exposes sales order lines from Oracle Order Management that are open, not yet fully interfaced to Accounts Receivable, and that carry no payment terms at either the line or header level. The view derives a signed sales order amount per line, using line category codes to invert the sign for returns, and projects an anticipated cash receipt date.

The view is part of the Cash Forecasting (CE) family of objects used by the Cash Management module and by the ETRM/Financials reporting layer. Its distinction from sibling forecast views is the NO_TERMS predicate: records qualify only when both OE_ORDER_LINES_ALL.PAYMENT_TERM_ID and OE_ORDER_HEADERS_ALL.PAYMENT_TERM_ID are null. Such orders cannot have due dates computed from terms, so downstream cash forecasting consumers must apply an alternative date derivation, which this view supplies through ordered and requested dates.

Underlying Base Objects

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

The join between headers and lines is on HEADER_ID. The customer profile join is lineage-based rather than direct foreign key: CP_CLASS.PROFILE_CLASS_ID resolves to the site profile class when a site profile exists (CP_SITE.CUST_ACCOUNT_PROFILE_ID is not null), otherwise to the account profile class (CP_CUST.PROFILE_CLASS_ID). NVL(H.INVOICE_TO_ORG_ID, H.SHIP_TO_ORG_ID) is matched to CP_SITE.SITE_USE_ID as an outer join, and H.SOLD_TO_ORG_ID is matched to CP_CUST.CUST_ACCOUNT_ID with the restriction CP_CUST.SITE_USE_ID IS NULL so only the account-level profile row is used.

Key Columns

  • ORG_ID — operating unit identifier from the order header; drives multi-org security and reporting partitions.
  • TRANSACTIONAL_CURR_CODE — transactional currency of the order; the currency in which the forecast amount is denominated.
  • Signed amount columns — two positional DECODE-based expressions compute (ordered quantity − invoiced quantity) × unit selling price plus tax, multiplied by 1 for ORDER, −1 for RETURN, and 0 for any other line category code. Tax is included only when the residual quantity is non-zero.
  • Date columns — TRUNC(NVL(H.ORDERED_DATE, SYSDATE)) and TRUNC(NVL(L.REQUEST_DATE, NVL(H.REQUEST_DATE, SYSDATE))) provide order and request dates for cash timing.
  • BOOKED_FLAG, CONVERSION_TYPE_CODE, CONVERSION_RATE_DATE — booking status and currency conversion attributes; the rate date defaults to the request date, then to SYSDATE.
  • COMMITMENT_ID, PROJECT_ID — linkage to commitments and projects for commitment-based cash forecasting.
  • CP_CLASS.NAME / PROFILE_CLASS_ID — the resolved customer profile class name and identifier.
  • FLOW_STATUS_CODE, ORDER_NUMBER, LINE_NUMBER, ORDER_TYPE_ID — line workflow state and order/line identity for traceability.
  • TO_CHAR(LINE_ID) — line identifier exposed as a character string.
  • A literal 1 is projected in the position of a row-count/sequence indicator.

Common Use Cases and Queries

The view is typically consumed in cash forecasting and receivables-projection reporting where terms-based due dates are unavailable; the forecast date must instead be inferred from order and request dates. A representative query:

  • Filter by operating unit and currency: SELECT org_id, transactional_curr_code, order_number, line_number, cp_class.name, flow_status_code FROM apps.ce_so_fc_orders_no_terms_v WHERE org_id = :p_org_id AND transactional_curr_code = :p_currency;
  • Aggregate forecast exposure by operating unit: SELECT org_id, transactional_curr_code, SUM(signed_amount) FROM apps.ce_so_fc_orders_no_terms_v GROUP BY org_id, transactional_curr_code;
  • Isolate unbooked orders: SELECT order_number, line_number, booked_flag FROM apps.ce_so_fc_orders_no_terms_v WHERE booked_flag = 'N';
  • Join to commitments and projects via commitment_id and project_id for project cash forecasting.

Because the view filters on OPEN_FLAG = 'Y', INVOICE_INTERFACE_STATUS_CODE IN ('NO','PARTIAL') (with null defaulted to 'NO'), and null payment terms at both line and header, results are restricted to genuinely open, uninvoiced, terms-less order lines. The outer join on the site profile means rows are retained even where no site-level customer profile exists, in which case the account-level profile class governs the CP_CLASS result.