Search Results ce_po_fc_orders_terms_v




Overview
Explore in AI Chat

Overview

CE_PO_FC_ORDERS_TERMS_V is a Cash Management (CE) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to serve as a forecasting source for goods and services purchase orders that carry payment terms. In the Cash Management forecasting architecture, source views such as this one expose anticipated cash outflows derived from outstanding purchasing commitments. Each row represents the intersection of a purchase order distribution with an installment line from the payment terms assigned to the supplier or supplier site, translated into an expected due date and due amount.

The view is therefore the projection layer that Cash Management consumes when generating a purchase order–based cash forecast. Rather than reading transactional purchasing tables directly, the forecasting engine queries this pre-joined view, which already reconciles ordered, delivered, billed, and cancelled quantities or amounts and applies the term template to derive scheduled payments.

Underlying Base Objects

The documented metadata lists the base objects referenced by the view definition. Purchasing-side objects include PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, PO_DISTRIBUTIONS_ALL, PO_RELEASES_ALL, PO_DOCUMENT_TYPES_ALL, PO_VENDORS, and PO_VENDOR_SITES_ALL. Term and payment information is sourced from AP_TERMS_LINES via the TM alias, which supplies DUE_AMOUNT, DUE_PERCENT, FIXED_DATE, DUE_DAYS, DUE_MONTHS_FORWARD, and DUE_DAY_OF_MONTH. Currency defaults come from FINANCIALS_SYSTEM_PARAMS_ALL (alias FSP) and GL_SETS_OF_BOOKS (alias SOB). AP_INVOICE_LINES_ALL is referenced in the broader source set, and FND_GLOBAL is used by the forecasting framework for session context such as ORG_ID. The view joins PO distributions to term lines on TERM_ID and derives a composite key from PO_DISTRIBUTION_ID, TERM_ID, and SEQUENCE_NUM.

Key Columns

  • SEGMENT1 — the purchase order number from PO_HEADERS_ALL.
  • Due amount / Due percent — the amount computed using MATCHING_BASIS logic (AMOUNT versus QUANTITY) and the term line's DUE_AMOUNT or DUE_PERCENT. For amount-based matching, the calculation is GREATEST(AMOUNT_ORDERED − AMOUNT_DELIVERED − AMOUNT_CANCELLED + NONRECOVERABLE_TAX, 0) multiplied by the rate.
  • Promised/Need-by/Acceptance date — the expected payment trigger date, resolved through NVL over POLL.PROMISED_DATE, POLL.NEED_BY_DATE, POR.ACCEPTANCE_DUE_DATE, and creation or release date.
  • FIXED_DATE, DUE_DAYS, DUE_MONTHS_FORWARD, DUE_DAY_OF_MONTH — term attributes used by CE to compute the forecast date.
  • Currency code — derived from PO header currency, invoice currency, or set of books currency.
  • Authorization status — PO or release approval status, defaulting to 'INCOMPLETE'.
  • Payment priority, vendor type, pay group — defaulted from vendor or vendor site, with '-1' or 99 fallbacks.
  • ORG_ID, PROJECT_ID, TERM_ID, LINE_NUM, VALUE_BASIS — organizational and analytical keys.

Common Use Cases and Queries

Typical usage supports cash forecasting, terms exposure analysis, and reconciliation of open PO commitments by payment schedule. A representative query:

  • SELECT segment1, due_amount, due_days, currency_code, org_id FROM ce_po_fc_orders_terms_v WHERE org_id = :p_org_id AND currency_code = 'USD'; — extracts forecastable purchase order rows for a given operating unit and currency.
  • Aggregating DUE_AMOUNT by TERM_ID or DUE_DAYS supports term-abuse and discount analysis.
  • Joining back to PO_DISTRIBUTIONS_ALL on PO_DISTRIBUTION_ID enables drill-down from a forecast line to the underlying distribution.
  • Filtering PROJECT_ID supports project cash forecasting, while VALUE_BASIS isolates the field basis used by the terms engine.

Because the view embeds complex DECODE and NVL logic, consumers should not attempt to re-derive forecast amounts from base tables; the view is the authoritative source within the Cash Management forecasting flow.