Search Results forecast_aging_type




Overview
Explore in AI Chat

Overview

APPS.CEFV_CASH_FORECASTS is a read-only reporting view in the Oracle Cash Management module of Oracle E-Business Suite, available in releases 12.1.1 and 12.2.2. It presents a fully denormalized, human-readable projection of cash forecast definitions by joining the core forecast tables to their associated lookup values, currency conversion types, transaction calendars, and project identifiers. Rather than exposing raw lookup codes such as aging type or currency type, the view resolves these codes through CE_LOOKUPS into their translated meanings, making it suitable for ad hoc queries, custom reports, and integration extracts without requiring the developer to re-implement the lookup logic.

The object is declared WITH READ ONLY, confirming that it is intended strictly for query and reporting access; it cannot be used as a DML target. Its role is therefore that of a presentation layer over the Cash Management forecast configuration schema.

Underlying Base Objects

The view is defined over the following documented objects:

  • CE_FORECASTS (synonym, alias CF) — the transaction-level forecast lines; supplies forecast_id, name, forecast_currency, currency_type, exchange_rate, source_currency, and audit columns.
  • CE_FORECAST_HEADERS (synonym, alias FH) — the forecast definition header; supplies aging_type, overdue_transactions, cutoff_period, and transaction_calendar_id.
  • CE_LOOKUPS (view, aliases L1, L2, L3) — resolves three distinct lookup types: FORECAST_AGING_TYPE, FORECAST_CURRENCY_TYPE, and FORECAST_OVERDUE_TRX.
  • GL_DAILY_CONVERSION_TYPES (synonym, alias DC) — joined via an outer join on exchange_rate_type to provide user_conversion_type.
  • GL_TRANSACTION_CALENDAR (synonym, alias TC) — outer-joined to supply the calendar name for the forecast header.
  • PA_PROJECTS_ALL (synonym, alias PA) — outer-joined on project_id to expose the project segment1 number.

The joins to conversion types, projects, and transaction calendars are all outer joins, meaning forecasts with no project, no conversion type, or no calendar are still returned.

Key Columns

Because the underlying transaction tables are highly normalized, several important attributes are exposed only as lookup meanings rather than codes:

Common Use Cases and Queries

The principal use case is auditing which forecasts are configured with a given aging type. A typical query is:

SELECT forecast_id, name, l1_meaning, forecast_currency, start_date
FROM   apps.cefv_cash_forecasts
WHERE  l1_meaning = 'Days';

Because the view resolves lookup codes, the filter can be expressed in user-facing terminology rather than the internal lookup code, which reduces errors and improves report readability. Other practical scenarios include extracting forecast definitions for a specific project, listing forecasts grouped by currency conversion type, and reconciling forecast calendar assignments against GL transaction calendars. The view is well suited to building custom BI Publisher reports or feeding downstream cash-position summaries, since a single query returns configuration, currency, timing, project, and audit context together.