Results for “ce_forecast_cells”

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

Overview

CE_FORECAST_CELLS is a table in the Cash Management (CE) module of Oracle E-Business Suite, owned by the CE schema. It stores forecast amounts within the Cash Management forecasting framework. In Oracle EBS, cash forecasting allows treasury users to project future cash positions by defining reusable forecast templates composed of headers, rows, and columns, then populating the intersections of those rows and columns with monetary values. CE_FORECAST_CELLS is the physical container for those intersection values: each row in the table represents one populated cell of a forecast, holding the amount that falls at the meeting point of a specific forecast row and forecast column for a given forecast.

From a dimensional modeling perspective, the ETRM metadata classifies this object heuristically as a link table. This is a modeling suggestion rather than a declared property: the table's structure — a surrogate primary key surrounded almost entirely by foreign keys to parent dimensions (forecast, row, column, header) plus a single measure — is characteristic of an associative entity that resolves a many-to-many relationship between forecast rows and forecast columns, qualified by the owning forecast. Analysts building a data vault or star schema on CE forecasting data would typically treat CE_FORECAST_CELLS as the fact-bearing link carrying the AMOUNT measure.

Key Information Stored

The table contains 11 documented columns in the 12.2.2 physical schema. The most important are:

• FORECAST_CELL_ID — the surrogate primary key, enforced by CE_FORECAST_CELLS_PK and also by the unique index CE_FORECAST_CELLS_U1. It uniquely identifies each forecast cell record.
• FORECAST_ID — foreign key to CE_FORECASTS, identifying the forecast instance to which the cell belongs. This column participates in the unique index CE_FORECAST_CELLS_UK1 (FORECAST_ID, FORECAST_CELL_ID), a documented business-key candidate.
• FORECAST_HEADER_ID — foreign key to CE_FORECAST_HEADERS, tying the cell to its forecast header definition.
• FORECAST_ROW_ID — foreign key to CE_FORECAST_ROWS, identifying the row dimension of the cell.
• FORECAST_COLUMN_ID — foreign key to CE_FORECAST_COLUMNS, identifying the column (typically a time period or account dimension) of the cell.
• AMOUNT — the actual forecasted monetary value stored for that row/column intersection.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Oracle EBS WHO columns providing audit lineage and concurrency tracking.

The distinction between the surrogate key (FORECAST_CELL_ID) and the business-key candidate (FORECAST_ID plus FORECAST_CELL_ID) matters when de-duplicating or reconciling forecast extracts.

Common Use Cases and Queries

Typical scenarios include: reporting the projected cash position for a forecast by row and column, auditing which cells were populated versus left blank, and reconciling forecast amounts against actual cash transactions. A representative join pattern is:

• Join CE_FORECAST_CELLS to CE_FORECASTS on FORECAST_ID to filter a named forecast.
• Join to CE_FORECAST_ROWS on FORECAST_ROW_ID and to CE_FORECAST_COLUMNS on FORECAST_COLUMN_ID to resolve human-readable row and column labels.
• Join to CE_FORECAST_HEADERS on FORECAST_HEADER_ID for header-level attributes.
• Aggregate AMOUNT by FORECAST_COLUMN_ID to produce a period-by-period cash forecast curve.
• Use the CREATION_DATE and LAST_UPDATE_DATE columns to detect stale or recently amended forecast entries.

Because the table is narrow and heavily indexed on its foreign keys, queries should always constrain FORECAST_ID first to avoid scanning the full set of cells across all forecasts.

Related Objects

The following objects are the most significant dependencies, based on the documented foreign keys:

• CE_FORECASTS — parent forecast definition; joined on CE_FORECAST_CELLS.FORECAST_ID = CE_FORECASTS.FORECAST_ID.
• CE_FORECAST_HEADERS — header-level forecast metadata; joined on FORECAST_HEADER_ID.
• CE_FORECAST_ROWS — row dimension of each cell; joined on FORECAST_ROW_ID.
• CE_FORECAST_COLUMNS — column dimension of each cell; joined on FORECAST_COLUMN_ID.
• CE_FORECAST_CELLS_PK / CE_FORECAST_CELLS_U1 / CE_FORECAST_CELLS_UK1 — the primary, unique, and composite unique indexes that enforce identity and business-key integrity; the UK1 index on FORECAST_ID and FORECAST_CELL_ID is particularly useful for forecast-scoped lookups.

Together these objects form the complete Cash Management forecasting model, with CE_FORECAST_CELLS acting as the associative link that stores the forecast amounts themselves.