Search Results term_l

Overview

APPS.CE_SO_FC_ORDERS_TERMS_V is a reporting view in Oracle E-Business Suite that projects order line revenue and payment-term scheduling information for open sales orders. It is designed for cash forecasting and cash management (CE) purposes, allowing expected cash inflows to be derived from outstanding order commitments and their associated payment terms. The view joins sales order header and line data from the Order Management tables with payment term line definitions from Receivables, producing one row per order line and payment term schedule line. In EBS 12.1.1 and 12.2.2 the object is delivered as an APPS-owned view and is typically consumed by cash forecasting, collections planning, and custom reporting rather than by transactional forms.

Underlying Base Objects

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

• OE_ORDER_HEADERS_ALL — order header attributes such as ORG_ID, ORDERED_DATE, REQUEST_DATE, BOOKED_FLAG, OPEN_FLAG, and the transactional currency.
• OE_ORDER_LINES_ALL — order line quantity, pricing, tax, invoicing, and project references.
• RA_TERMS_LINES — payment term schedule lines (aliased TERM_L), supplying due date, due days, due day of month, months forward, and relative amount.
• HZ_CUSTOMER_PROFILES — customer account and site-level profile records (aliased CP_SITE and CP_CUST).
• HZ_CUST_PROFILE_CLASSES — profile class definitions (aliased CP_CLASS).

Order lines are linked to headers on HEADER_ID, and to payment terms on the effective term (line-level PAYMENT_TERM_ID, falling back to header-level PAYMENT_TERM_ID). Customer profile joining resolves the applicable profile class via CP_CUST (account level, with NULL SITE_USE_ID) and CP_SITE (site level).

Key Columns

• ORG_ID, TRANSACTIONAL_CURR_CODE — operating unit and order currency.
• TERM_DUE_DATE, TERM_DUE_DAYS, TERM_DUE_DAY_OF_MONTH, TERM_DUE_MONTHS_FORWARD, RELATIVE_AMOUNT — the payment-term schedule attributes sourced from RA_TERMS_LINES.
• Amount expressions (two unnamed numeric columns) — computed as the signed remaining value: (ORDERED_QUANTITY − INVOICED_QUANTITY) × UNIT_SELLING_PRICE, plus TAX_VALUE when the remaining quantity is non-zero, multiplied by +1 for ORDER lines and −1 for RETURN lines.
• TRUNC(ORDERED_DATE) and TRUNC(REQUEST_DATE) — order and line request dates, defaulted to SYSDATE.
• BOOKED_FLAG, FLOW_STATUS_CODE, INVOICE_INTERFACE_STATUS_CODE — status indicators controlling inclusion of the row.
• COMMITMENT_ID, PROJECT_ID — links to commitments and project accounting where applicable.
• PROFILE_CLASS_ID, NAME — resolved customer profile class.
• A concatenated key of LINE_ID || 'X' || TERM_ID || 'X' || SEQUENCE_NUM — a unique identifier for line-term combinations.

Common Use Cases and Queries

The view is most commonly used to forecast expected receipts from open, booked orders by exploding each line across its payment term schedule. Because the WHERE clause restricts to OPEN_FLAG = 'Y' and lines whose INVOICE_INTERFACE_STATUS_CODE is 'NO' or 'PARTIAL', only uninvoiced or partially invoiced lines are returned, which is appropriate for remaining cash expectations. A typical query retrieves forecast amounts by due date and currency:

• SELECT org_id, transactional_curr_code, term_due_date, term_due_days, SUM(amount) FROM CE_SO_FC_ORDERS_TERMS_V GROUP BY org_id, transactional_curr_code, term_due_date, term_due_days;
• SELECT order_number, line_number, flow_status_code, term_due_date, relative_amount FROM CE_SO_FC_ORDERS_TERMS_V WHERE org_id = :p_org_id AND transactional_curr_code = :p_currency;
• SELECT profile_class_id, name, COUNT(*) FROM CE_SO_FC_ORDERS_TERMS_V GROUP BY profile_class_id, name;

Typical scenarios include cash forecasting by due date, aging of uninvoiced order backlog, and profile-class based analysis of expected collections. The view should not be used for transactional processing; it is read-only reporting metadata whose joins assume the standard EBS multi-org and trading-community model.