Results for “ce_forecast_errors”

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

Overview

CE_FORECAST_ERRORS is a Cash Management (CE) module table that captures errors encountered during cash forecast generation runs in Oracle E-Business Suite 12.1.1 and 12.2.2. When the Cash Forecasting engine processes forecast templates, rows, and headers, any conditions that prevent successful completion of a row-level calculation—such as invalid source data, missing exchange rates, or configuration conflicts—are recorded here rather than aborting the entire run. This design allows the forecast to complete partially while giving administrators a diagnostic trail of what failed and why.

The table resides in the CE schema and is classified as VALID in the ETRM repository. It contains 10 documented columns and participates in three foreign key relationships, all of which point to parent forecast objects. Under a heuristic Data Vault classification, CE_FORECAST_ERRORS behaves as a link table: it connects three parent entities—forecast header, forecast, and forecast row—while carrying descriptive error attributes. This classification is a modeling suggestion only, not a physical design implemented by Oracle.

Key Information Stored

The table's identifying and descriptive columns fall into three groups:

• Relationship keys: FORECAST_HEADER_ID, FORECAST_ID, and FORECAST_ROW_ID. These foreign keys tie each error record to its originating forecast header (CE_FORECAST_HEADERS), forecast (CE_FORECASTS), and forecast row (CE_FORECAST_ROWS) respectively. Together they form the effective business key for any given error instance.
• Error content: MESSAGE_NAME holds the internal error code or message identifier, while MESSAGE_TEXT contains the human-readable description of the failure. Together these provide the diagnostic payload.
• Context and audit columns: FORECAST_RUN_NAME identifies the forecast run instance; APPLICATION_ID and APPLICATION_SHORT_NAME identify the source application that contributed the failing data; and CREATED_BY, CREATION_DATE provide standard EBS audit tracking (who and when the record was written).

No surrogate system-generated primary key is documented; the combination of the three FK columns serves as the operational key for locating errors.

Common Use Cases and Queries

The primary use case is post-run troubleshooting of cash forecasts. Administrators query this table after a forecast completes with warnings to determine which rows failed. A typical query joins to the parent header to surface context:

SELECT e.forecast_run_name, e.message_name, e.message_text,
       e.application_short_name, h.forecast_header_name
FROM   ce_forecast_errors e,
       ce_forecast_headers h
WHERE  e.forecast_header_id = h.forecast_header_id
AND    e.forecast_run_name = :run_name;

Reporting scenarios include error frequency by message name, which highlights recurring configuration problems, and error counts by source application, which isolates which subledger feeds most often produce failures. Because the table retains CREATED_BY and CREATION_DATE, it also supports audit queries that reconstruct the sequence of forecast failures over a period. A common pattern is aggregating errors by FORECAST_ID to compare error rates across successive forecast definitions.

Related Objects

The documented foreign keys establish the following direct relationships, and these are the most significant objects with which CE_FORECAST_ERRORS interacts:

• CE_FORECAST_HEADERS — joined via FORECAST_HEADER_ID; the header record defining a forecast request.
• CE_FORECASTS — joined via FORECAST_ID; the individual forecast instance generated from a template.
• CE_FORECAST_ROWS — joined via FORECAST_ROW_ID; the specific line-level forecast row that generated the error.

Related application objects include CE_FORECAST_TEMPLATES and CE_FORECAST_ROW_SOURCES, which supply the configuration the forecast engine consumes, and the concurrent program that executes forecasts, which is the process that inserts into this table. Administrators generally join CE_FORECAST_ERRORS upward through CE_FORECAST_HEADERS to obtain the user-facing forecast name before presenting error results.