Search Results ce_forecast_columns_v




Overview
Explore in AI Chat

Overview

CE_FORECAST_COLUMNS_V is a view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Cash Management (CE) product family. Its ETRM status is VALID, and the reference documentation describes it with the single tag "Retrofitted," indicating the object was carried forward from an earlier release or schema layout without functional redesign. The view exposes the column definitions that make up a cash forecast template — that is, the individual time buckets or column layout used to present projected cash positions.

In EBS reporting and integration, the view functions as a flat, read-oriented projection over the forecast column definition table. Because it is a view rather than a table, it carries no independent storage and always reflects the current committed state of its base object. This makes it suitable for concurrent program queries, custom reports, and inbound/outbound interfaces that need to resolve the column structure of a given forecast header.

Underlying Base Objects

The view is defined over a single base object documented as CE_FORECAST_COLUMNS, referenced through a synonym. The view definition is a straight column projection with no joins, filters, or aggregations:

Because the mapping is one-to-one, every row in the view corresponds to exactly one row in CE_FORECAST_COLUMNS, and no data transformation, decoding, or translation occurs at the view layer.

Key Columns

  • FORECAST_COLUMN_ID — Primary identifier for a forecast column definition; the key to retrieve a specific column record.
  • FORECAST_HEADER_ID — Foreign key to the forecast header, grouping the columns that belong to one forecast template. This is the standard join path to the forecast header object.
  • COLUMN_NUMBER — The display or presentation sequence of the column within the forecast layout.
  • DAYS_FROM / DAYS_TO — Numeric offsets defining the date range (bucket) that the column represents relative to the forecast basis date.
  • DEVELOPER_COLUMN_NUM — The developer-assigned column number. This is the column most directly relevant to searches for "developer_column_num," since it is the physical/developer key used to programmatically identify a column independent of its user-facing display order.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — Descriptive flexfield segments, available for client-specific extensions and contextual reporting.
  • Audit columns — Standard WHO columns supporting change tracking and concurrency.

Common Use Cases and Queries

Typical scenarios include generating a listing of the column structure for a forecast template, validating bucket ranges before loading forecast amounts, and driving dynamic report layouts where the number of periods is configuration-driven.

Retrieve all columns for a given forecast header, ordered by presentation sequence:

  • SELECT FORECAST_COLUMN_ID, COLUMN_NUMBER, DAYS_FROM, DAYS_TO, DEVELOPER_COLUMN_NUM FROM CE_FORECAST_COLUMNS_V WHERE FORECAST_HEADER_ID = :p_header_id ORDER BY COLUMN_NUMBER;

Locate a column by its developer-assigned number:

  • SELECT FORECAST_COLUMN_ID, FORECAST_HEADER_ID, COLUMN_NUMBER, DAYS_FROM, DAYS_TO FROM CE_FORECAST_COLUMNS_V WHERE DEVELOPER_COLUMN_NUM = :p_dev_col_num;

Determine the widest bucket span configured across all headers, useful for validating forecasting horizons:

  • SELECT FORECAST_HEADER_ID, MAX(DAYS_TO) - MIN(DAYS_FROM) AS SPAN FROM CE_FORECAST_COLUMNS_V GROUP BY FORECAST_HEADER_ID;

Developers should note that the view is read-only for practical purposes and that any reporting on flexfield attributes requires joining or decoding against the relevant flexfield definitions.