Results for “ce_forecast_headers”

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

Overview

CE_FORECAST_HEADERS is the master definition table for Cash Forecasting in Oracle E-Business Suite Cash Management (CE). Each row in this table represents a forecast template header — the reusable definition that governs how Oracle Cash Management builds a cash forecast for a given business requirement. A header captures the forecast's identity, the aging and cutoff rules to apply, the GL transaction calendar used to bucket time periods, and optional project filters. The forecast itself is not stored here; instead, the header acts as the anchor definition from which forecast runs, layout rows, columns, periods, and generated cells are derived. It is therefore the entry point of the entire cash forecast model and is required for both the Cash Forecasting window in the application and for any programmatic or reporting access to forecast definitions.

In Data Vault modeling terms, the documented foreign key structure classifies this table heuristically as a hub. It holds the durable business key of the forecast template (the template NAME) along with the surrogate identifier, while the surrounding forecast, column, row, period, cell, and error tables behave as dependent satellites or links that reference this hub through the FORECAST_HEADER_ID. This classification is a modeling suggestion derived from the referential structure rather than a statement about the physical schema.

Key Information Stored

The table contains 32 documented columns in release 12.2.2. The most significant are:

• FORECAST_HEADER_ID — surrogate primary key, defined by CE_FORECAST_HEADERS_PK and reinforced by unique index CE_FORECAST_HEADERS_U1. Every dependent forecast table joins on this column.
• NAME — the business-key candidate, enforced by unique index CE_FORECAST_HEADERS_U2 and the unique constraint CE_FORECAST_HEADERS_UK1. This is the user-visible template name.
• DESCRIPTION — free-text explanation of the template's purpose.
• AGING_TYPE — controls how transactions are aged within the forecast (for example, by days or by accounting period).
• OVERDUE_TRANSACTIONS — flag governing whether overdue transactions are included in the forecast.
• CUTOFF_PERIOD — the cutoff used when selecting transactions for inclusion.
• TRANSACTION_CALENDAR_ID — foreign key to GL_TRANSACTION_CALENDAR, supplying the calendar that defines forecast periods.
• START_PROJECT_ID and END_PROJECT_ID — foreign keys to PA_PROJECTS_ALL that bound the range of projects included in the forecast.
• TREASURY_TEMPLATE and COLUMN_SETUP — control the template's linkage to Treasury forecasting and its column layout behavior.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS WHO columns used for audit and change tracking.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard DFF-enabled descriptive flexfield segment columns.

Common Use Cases and Queries

Typical usage includes identifying which forecast template produced a given forecast, listing all templates with their aging and calendar rules, and resolving project-scoped templates. A common reporting pattern joins the header to its forecasts:

SELECT h.forecast_header_id, h.name, h.aging_type, f.forecast_id
FROM ce.ce_forecast_headers h, ce.ce_forecasts f
WHERE h.forecast_header_id = f.forecast_header_id;

To find templates bound to a specific calendar or project range:

SELECT name, transaction_calendar_id, start_project_id, end_project_id
FROM ce.ce_forecast_headers
WHERE transaction_calendar_id = :calendar_id;

Metadata and change-audit queries use LAST_UPDATE_DATE and LAST_UPDATED_BY. Flexfield reporting selects the ATTRIBUTE columns where ATTRIBUTE_CATEGORY matches an enabled context. Operational diagnostics often join to CE_FORECAST_ERRORS to trace forecast generation failures back to the originating template.

Related Objects

The following objects reference this table via FORECAST_HEADER_ID and are the most significant for joins:

• CE_FORECASTS — generated forecast instances produced from the header.
• CE_FORECAST_ROWS — row definitions that make up the forecast layout.
• CE_FORECAST_COLUMNS — column definitions for the forecast layout.
• CE_FORECAST_PERIODS — period buckets belonging to the header.
• CE_FORECAST_CELLS — intersection cells holding forecast values.
• CE_FORECAST_TRX_CELLS — transaction-level detail populating cells.
• CE_FORECAST_ERRORS — errors raised while generating forecasts from the template.
• XTR_FORECAST_PERIODS — Treasury-related periods tied to the header.
• GL_TRANSACTION_CALENDAR — referenced via TRANSACTION_CALENDAR_ID for period definition.
• PA_PROJECTS_ALL — referenced via START_PROJECT_ID and END_PROJECT_ID for project filtering.