Search Results transaction_calendar_name




Overview
Explore in AI Chat

Overview

CE_FORECAST_HEADERS_V is an Oracle Applications (APPS) view in the Cash Management (CE) product family, delivered as a retrofit artifact in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes forecast header definitions used by the Cash Forecasting feature, presenting a denormalized, display-ready representation of the CE_FORECAST_HEADERS table joined to several supporting objects. Rather than returning raw foreign keys, the view resolves lookup codes, calendar identifiers, and project identifiers into their human-readable values, which simplifies reporting, concurrent program logic, and integration extraction.

The view is most relevant to users and developers who need to identify forecast definitions by the projects they cover. Because it exposes both START_PROJECT_NUMBER and END_PROJECT_NUMBER, the view is frequently the starting point for queries that filter forecasts by a specific project number, including the commonly searched END_PROJECT_NUMBER attribute.

Underlying Base Objects

The view is defined over four documented referenced objects:

All project and calendar joins use the Oracle outer-join operator (+), so forecast headers are still returned when no matching calendar or project exists. The lookup join, however, is an inner join, meaning an aging type with no valid FORECAST_AGING_TYPE lookup will suppress the row.

Key Columns

Common Use Cases and Queries

The principal use case is locating forecast definitions that span or terminate at a particular project. The following query returns all forecasts whose end project number matches a supplied value:

  • SELECT forecast_header_id, name, start_project_number, end_project_number FROM ce_forecast_headers_v WHERE end_project_number = :p_project_number;

Additional practical patterns include listing all forecasts and their decoded aging types for reporting, and joining the view to forecast lines via FORECAST_HEADER_ID to build detailed cash position extracts. Because project resolution relies on PA_PROJECTS_ALL, forecasts whose project IDs no longer resolve to a project will return a null project number; queries searching by END_PROJECT_NUMBER therefore implicitly exclude such rows. Consumers should also be aware that the view is documented as retrofitted and that TRANSACTION_CALENDAR_NAME and the project numbers are outer-join derivations rather than stored values.