Search Results ce_forecast_ext_temp




Overview
Explore in AI Chat

Overview

CE_FORECAST_EXT_TEMP is a staging and interface table owned by the CE (Cash Management) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It supports the Cash Forecasting module and, more specifically, the external forecast data loading process. When a forecast template is configured to draw balances or activity from an external source, the collected rows are written into this temporary structure before being validated, transformed, and merged into the permanent cash forecast tables. Its seven-column physical layout in the ETRM 12.2.2 documentation reflects a deliberately narrow scope: each row carries a request identifier, a context value, a date range, a target forecast column, and currency conversion inputs.

The object is classified as a standalone table under the heuristic Data Vault model derived from its foreign key structure. This is a modeling suggestion rather than a functional designation: the only documented foreign key relationship (FORECAST_COLUMN_ID → CE_FORECAST_COLUMNS) points outward to a reference table, and no inbound parent references are recorded, so the table does not behave as a hub or link with dependent satellites. Because the table is populated and consumed within a single forecast generation run, it is best understood as transient working storage rather than a durable analytical subject area.

Key Information Stored

The table's seven documented columns form a compact payload for a single forecast extraction cycle.

  • FORECAST_REQUEST_ID — Identifies the forecast request or generation run that produced the staging rows. This is the principal correlation key for the batch and is the most common filter in diagnostic queries.
  • FORECAST_COLUMN_ID — The only documented foreign key. It joins to CE_FORECAST_COLUMNS and designates which forecast template column (for example, a specific cash inflow or outflow line) the staged amount belongs to.
  • CONTEXT_VALUE — The external lookup value passed by the calling program, used to bind the staged data to the correct slice of the forecast, such as a bank account, counterparty, or transaction source.
  • START_DATE and END_DATE — The activity or balance window for the staged row. Together they position the amount on the forecast timeline and drive date-based bucketing in the forecast output.
  • FROM_CURRENCY_CODE — The currency of the externally supplied amount, required when the source differs from the forecast currency.
  • CONVERSION_RATE — The rate applied to translate FROM_CURRENCY_CODE into the forecast currency, making the conversion explicit and auditable per row.

No surrogate primary key or unique index is documented in the ETRM metadata. In practice, uniqueness of a staged row is implied by the combination of FORECAST_REQUEST_ID, CONTEXT_VALUE, the date range, and FORECAST_COLUMN_ID — the natural business key candidate. Administrators should verify the actual constraints against the live dictionary, since temporary structures frequently carry no enforced primary key.

Common Use Cases and Queries

The most frequent interaction with this table is troubleshooting an external forecast load. If a forecast generates with missing or zero amounts, the staged rows for the affected request reveal whether the population step succeeded.

  • Volume check per request: SELECT FORECAST_REQUEST_ID, COUNT(*) FROM CE.CE_FORECAST_EXT_TEMP GROUP BY FORECAST_REQUEST_ID;
  • Currency conversion audit: SELECT FORECAST_REQUEST_ID, FROM_CURRENCY_CODE, CONVERSION_RATE, COUNT(*) FROM CE.CE_FORECAST_EXT_TEMP GROUP BY FORECAST_REQUEST_ID, FROM_CURRENCY_CODE, CONVERSION_RATE; — rows with a null or zero rate will produce incorrect forecast values.
  • Column mapping validation: join FORECAST_COLUMN_ID to CE_FORECAST_COLUMNS to confirm each staged row targets an active template column.
  • Date coverage review: compare MIN(START_DATE) and MAX(END_DATE) per request against the intended forecast horizon to detect partial or truncated loads before posting.

Because the content is transient, reporting should normally target the consolidated forecast tables rather than this object. A custom extract can nevertheless use it as a control total: staged row counts and summed conversion-adjusted amounts provide a reconciliation point against the final forecast lines.

Related Objects

  • CE_FORECAST_COLUMNS — The documented parent of FORECAST_COLUMN_ID; defines the template columns that staged rows populate.
  • CE_FORECASTS / CE_FORECAST_HEADERS — Forecast definitions that bind a request to a template and currency context.
  • CE_FORECAST_LINES and related result tables — The consolidated forecast output populated from staged data.
  • CE_CASH_POOLS / CE_BANK_ACCOUNTS — Common sources of CONTEXT_VALUE for account-based external forecasts.
  • FND_CURRENCIES — Validates FROM_CURRENCY_CODE and supplies currency attributes.
  • Cash Forecasting concurrent programs and the CE_FORECAST APIs — The programs that insert into and consume this staging table.