Search Results amount_threshold




Overview
Explore in AI Chat

Overview

CE_FORECASTS is the forecast definition table in the Oracle Cash Management (CE) module. It stores the header-level definition of each cash forecast, capturing the parameters that govern how Oracle EBS projects future cash positions from source transaction data such as payables, receivables, payroll, and purchase orders. Each row represents one forecast run configuration within a forecast header, including the currency, period set, exchange rate treatment, project scope, and threshold controls that determine what the forecast includes and how it is displayed.

In Oracle EBS 12.1.1 and 12.2.2, CE_FORECASTS functions as the parent of the detailed forecast result set. Downstream forecast cell values are not stored here; they are held in CE_FORECAST_CELLS, keyed by FORECAST_ID, and forecast generation problems are captured in CE_FORECAST_ERRORS, also keyed by FORECAST_ID. The table therefore participates directly in the Cash Management forecast engine and in the Cash Forecasting and Cash Position reports, as well as in any custom reporting built against the Cash Management schema.

Based on the mined foreign key structure, a heuristic Data Vault classification of this object is satellite-leaning. It carries descriptive attributes about a forecast (name, currency, dates, threshold, project, display options) and depends on a parent header, which suggests it behaves as a descriptive satellite attached to the CE_FORECAST_HEADERS business key rather than as an independent hub.

Key Information Stored

The physical schema for 12.2.2 documents 44 columns. The most operationally significant columns are listed below.

Common Use Cases and Queries

Typical use cases include listing forecasts by header name, validating currency and rate configuration before a run, and reconciling forecast headers against generated cells and errors.

  • List all forecasts belonging to a header: SELECT f.FORECAST_ID, f.NAME, f.FORECAST_CURRENCY FROM CE.CE_FORECASTS f WHERE f.FORECAST_HEADER_ID = :header_id;
  • Find forecasts with generation errors: SELECT FORECAST_ID, NAME, ERROR_STATUS FROM CE.CE_FORECASTS WHERE ERROR_STATUS IS NOT NULL;
  • Resolve currencies and rate types for reporting: join FORECAST_CURRENCY and SOURCE_CURRENCY to FND_CURRENCIES and EXCHANGE_RATE_TYPE to GL_DAILY_CONVERSION_TYPES.
  • Project-scoped analysis: join PROJECT_ID to PA_PROJECTS_ALL to report forecast coverage by project.
  • Cell-level reconciliation: join FORECAST_ID to CE_FORECAST_CELLS for line detail, and to CE_FORECAST_ERRORS for diagnostic messages.
  • Concurrent request traceability: join REQUEST_ID to FND_CONCURRENT_REQUESTS to identify the program run that produced the forecast.

Related Objects

  • CE_FORECAST_HEADERS — parent of CE_FORECASTS via FORECAST_HEADER_ID.
  • CE_FORECAST_CELLS — child table holding forecast amounts; join on FORECAST_ID.
  • CE_FORECAST_ERRORS — child table capturing generation errors; join on FORECAST_ID.
  • FND_CURRENCIES — referenced twice, through FORECAST_CURRENCY and SOURCE_CURRENCY.
  • GL_DAILY_CONVERSION_TYPES — referenced through EXCHANGE_RATE_TYPE.
  • PA_PROJECTS_ALL — referenced through PROJECT_ID for project-based forecasts.
  • FND_CONCURRENT_REQUESTS — relates through REQUEST_ID for concurrent program tracking.