Results for “ce_forecast_rows_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

CE_FORECAST_ROWS_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, defined within the Cash Management (CE) product. It exposes the row-level detail of cash forecasting definitions stored in CE_FORECAST_ROWS, denormalizing foreign keys into descriptive display values drawn from lookups, set of books, operating units, payment methods, sales stage references, and budget metadata. The view is classified as retrofitted, meaning it was reconstructed in the 12.2.2 documentation set to reflect cumulative patches applied to earlier releases while remaining valid across 12.1.1 and 12.2.2.

Each row of CE_FORECAST_ROWS_V represents a single forecasting line belonging to a forecast header. A forecast row defines the transaction class being projected, the forecasting method applied, order and lead-time parameters, currency and set of books context, and various inclusion flags. The user search term "sales_stage_name" maps directly to the SALES_STAGE_NAME column, which resolves the SALES_STAGE_ID against AS_SALES_STAGES_ALL to present a human-readable sales pipeline stage. This column supports sales-oriented cash forecasts where expected receipts are segmented by opportunity stage and weighted by WIN_PROBABILITY.

Underlying Base Objects

The view is defined primarily over CE_FORECAST_ROWS (the transactional base), joined to a broad set of descriptive and validation objects. The documented referenced objects include AR_RECEIPT_METHODS, AS_SALES_STAGES_ALL, CE_BANK_ACCOUNTS, CE_BANK_ACCT_USES_ALL, CE_LOOKUPS, GL_ENCUMBRANCE_TYPES, GL_SETS_OF_BOOKS, HR_OPERATING_UNITS, HZ_CUST_PROFILE_CLASSES, HZ_PARTIES, OE_ORDER_TYPES_V, PAY_ALL_PAYROLLS_F, PAY_ORG_PAYMENT_METHODS_F, PA_BUDGET_TYPES_V, PER_BUSINESS_GROUPS, and XLE_ENTITY_PROFILES.

Lookup resolution is performed through CE_LOOKUPS, which supplies the TRX_TYPE_DSP meaning. GL_SETS_OF_BOOKS provides SET_OF_BOOKS_NAME, while GL_ENCUMBRANCE_TYPES supplies ENCUMBRANCE_TYPE. Customer segmentation uses HZ_CUST_PROFILE_CLASSES. Receipt and payment method names come from AR_RECEIPT_METHODS and PAY_ORG_PAYMENT_METHODS_F respectively, with bank account display names derived through DECODE logic against CE_BANK_ACCOUNTS and CE_BANK_ACCT_USES_ALL. Operating unit and party context are resolved via HR_OPERATING_UNITS, HZ_PARTIES, PER_BUSINESS_GROUPS, and XLE_ENTITY_PROFILES. Because the view joins these objects without exposing them directly, reporting queries remain isolated from underlying schema changes.

Key Columns

• SALES_STAGE_ID / SALES_STAGE_NAME — Sales pipeline stage identifier and its resolved name from AS_SALES_STAGES_ALL.
• WIN_PROBABILITY — Weighting factor applied to forecasted sales amounts.
• TRX_TYPE / TRX_TYPE_DSP — Transaction class code and its lookup meaning.
• FORECAST_HEADER_ID / FORECAST_ROW_ID / ROW_NUMBER — Header and row identifiers with ordinal positioning.
• FORECAST_METHOD, LEAD_TIME, ROLL_FORWARD_TYPE, ROLL_FORWARD_PERIOD — Forecasting methodology parameters.
• SET_OF_BOOKS_ID / SET_OF_BOOKS_NAME — Ledger context for the forecast line.
• ORG_ID, CHART_OF_ACCOUNTS_ID, CODE_COMBINATION_ID — Organizational and accounting flexfield references.
• RECEIPT_METHOD_ID / RECEIPT_METHOD_NAME — Expected receipt method for AR-linked forecasts.
• BANK_ACCOUNT_ID / BANK_ACCOUNT_NAME — Resolved using DECODE against TRX_TYPE to select between payable and standard bank accounts.
• ORDER_DATE_TYPE / ORDER_DATE_TYPE_NAME — Order date basis resolved from lookups.
• INCLUDE_DISPUTE_FLAG, INCLUDE_HOLD_FLAG, INCLUDE_NET_CASH_FLAG — Inclusion controls for disputed items, holds, and net cash treatment.
• ATTRIBUTE1 through ATTRIBUTE15, DESCRIPTION — Descriptive flexfield and free-text columns.

Common Use Cases and Queries

The view is typically queried in cash forecasting reconciliation reports, sales pipeline cash impact analyses, and integration extracts feeding treasury or planning systems. The SALES_STAGE_NAME column is particularly relevant when business users filter forecast lines by pipeline maturity.

SELECT f.FORECAST_HEADER_ID,
       f.ROW_NUMBER,
       f.TRX_TYPE_DSP,
       f.SALES_STAGE_NAME,
       f.WIN_PROBABILITY,
       f.SET_OF_BOOKS_NAME,
       f.RECEIPT_METHOD_NAME,
       f.BANK_ACCOUNT_NAME,
       f.CURRENCY_CODE
FROM   APPS.CE_FORECAST_ROWS_V f
WHERE  f.SALES_STAGE_NAME IS NOT NULL
ORDER  BY f.FORECAST_HEADER_ID, f.ROW_NUMBER;

A second common pattern joins the view to CE_FORECAST_HEADERS_V to obtain header-level naming, while a third filters by ORG_ID and SET_OF_BOOKS_ID to isolate forecasts for a specific operating unit and ledger combination. Because all descriptive joins are pre-resolved, these queries avoid the complexity of independently joining AS_SALES_STAGES_ALL, AR_RECEIPT_METHODS, and CE_LOOKUPS.