Search Results cefv_cash_forecasts




Overview
Explore in AI Chat

Overview

CEFV_CASH_FORECASTS is a Business View owned by the APPS schema within the Cash Management (CE) module of Oracle E-Business Suite. It presents a denormalized, read-only projection of cash forecast definitions, combining data from forecast line records, forecast header templates, lookup values, currency conversion types, transaction calendars, and project identifiers. In EBS 12.1.1 and 12.2.2, the view carries the status VALID and is defined with the WITH READ ONLY clause, which prevents DML operations and signals that it is intended exclusively for querying and reporting.

The view serves as a reporting and integration surface for cash forecasting functionality. Rather than requiring report authors to join seven separate base objects and resolve lookup meanings, CEFV_CASH_FORECASTS exposes decoded values such as aging type, currency type, and overdue transaction options directly as descriptive columns. This makes it well suited for use in Oracle Reports, BI Publisher data models, Discoverer workbooks, and custom PL/SQL extraction routines where forecast configuration data must be presented in business-friendly terms.

Underlying Base Objects

The view is defined over the following documented base objects: CE_FORECASTS, CE_FORECAST_HEADERS, CE_LOOKUPS, GL_DAILY_CONVERSION_TYPES, GL_TRANSACTION_CALENDAR, and PA_PROJECTS_ALL. The driving table is CE_FORECASTS (aliased CF), which joins to CE_FORECAST_HEADERS (FH) on FORECAST_HEADER_ID using an inner join. Three separate aliases of the CE_LOOKUPS view are joined to decode lookup codes: L1 resolves the aging type from FORECAST_AGING_TYPE, L2 resolves the currency type from FORECAST_CURRENCY_TYPE, and L3 resolves the overdue transaction setting from FORECAST_OVERDUE_TRX.

Three additional joins are outer joins: GL_DAILY_CONVERSION_TYPES (DC) is joined on CONVERSION_TYPE to CF.EXCHANGE_RATE_TYPE, PA_PROJECTS_ALL (PA) is joined on PROJECT_ID to CF.PROJECT_ID, and GL_TRANSACTION_CALENDAR (TC) is joined on TRANSACTION_CALENDAR_ID to FH.TRANSACTION_CALENDAR_ID. The outer joins ensure forecast rows are retained even when no conversion type, project, or calendar is assigned.

Key Columns

Common Use Cases and Queries

Typical scenarios include auditing forecast template configuration, validating exchange rate assignments, and reporting forecast scope by project or business calendar. A representative query listing project-linked forecasts follows:

SELECT forecast_id, name, forecast_currency, type, calendar_name, project_number
FROM apps.cefv_cash_forecasts
WHERE project_number IS NOT NULL
ORDER BY name;

Because the view is read-only and joins seven base objects with inner joins on lookups, rows whose lookup codes are absent from CE_LOOKUPS will be excluded. Callers should therefore treat missing rows as a potential lookup configuration issue rather than an absence of forecast data.