Results for “ce_forecasts_v”

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

Overview

CE_FORECASTS_V is a Cash Management (CE) reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is documented in ETRM as a retrofitted object, meaning it was carried forward and republished for currency and structural compatibility in the current release. The view denormalizes forecast line records from CE_FORECASTS and joins them to their parent forecast header, period calendar, currency conversion, lookup, and project information. It exposes both the line-level forecast definition and the header-level attributes — including the header name, matching the commonly searched column name HEADER_NAME — in a single flattened result set. Because Cash Management forecast generation, drilldown reports (such as the Cash Forecast Report and Forecast Drilldown), and external cash-positioning integrations all require header and line context together, this view serves as the canonical query surface for forecast data rather than requiring callers to join the underlying tables manually.

Underlying Base Objects

The view text defines CE_FORECASTS_V over six documented base objects:

• CE_FORECASTS (alias F) — the driving table, supplying forecast lines, amounts, thresholds, attributes, and currency parameters.
• CE_FORECAST_HEADERS (alias H) — joined on FORECAST_HEADER_ID; supplies header name, description, aging type, and overdue-transaction flag.
• GL_PERIODS (alias GP) — joined to resolve the period start date for the forecast's period set.
• GL_DAILY_CONVERSION_TYPES (alias G) — outer-joined to translate the exchange rate type into a user-facing conversion type.
• CE_LOOKUPS (alias L1) — supplies the decoded aging type display value.
• PA_PROJECTS_ALL (alias P) — supplies PROJECT_NUMBER (SEGMENT1) for project-sourced forecasts.

All base objects are referenced through APPS synonyms, with CE_LOOKUPS resolved as a view. The outer join on GL_DAILY_CONVERSION_TYPES indicates forecasts may exist without a defined conversion type.

Key Columns

• ROW_ID, FORECAST_ID, FORECAST_HEADER_ID — unique row identifier and primary/foreign keys linking line to header.
• NAME, DESCRIPTION — forecast line name and description.
• HEADER_NAME, HEADER_DSP, OVERDUE_TRANSACTIONS, AGING_TYPE — header-level context; HEADER_NAME is the most frequently searched attribute.
• START_TIME, START_PERIOD, START_DATE, PERIOD_SET_NAME, PERIOD_START_DATE — timing attributes; START_TIME is decoded to a formatted date for aging-type 'D' headers.
• FORECAST_CURRENCY, CURRENCY_TYPE, SOURCE_CURRENCY, EXCHANGE_RATE_TYPE, USER_EXCHANGE_RATE_TYPE, EXCHANGE_DATE, EXCHANGE_RATE — currency conversion parameters.
• AMOUNT_THRESHOLD, ERROR_STATUS, BANK_BALANCE_TYPE, FLOAT_TYPE, VIEW_BY, INCLUDE_SUB_ACCOUNT, FACTOR, DRILLDOWN_FLAG — generation and drilldown control attributes.
• PROJECT_ID, PROJECT_NUMBER — project linkage for project-driven forecasts.
• ATTRIBUTE1–ATTRIBUTE15, ATTRIBUTE_CATEGORY — descriptive flexfield columns.
• Standard WHO columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.
• REQUEST_ID — concurrent request that created or refreshed the forecast.

Common Use Cases and Queries

Typical uses include forecast header/line reporting, drilldown navigation from summary to detail, reconciliation of generated forecasts, and extraction feeds for treasury or bank-positioning systems.

• List forecasts by header name:

  SELECT forecast_id, name, header_name, start_time, forecast_currency
  FROM   ce_forecasts_v
  WHERE  header_name LIKE :p_header_name
  ORDER BY header_name, name;

• Currency and conversion detail for a header:

  SELECT name, forecast_currency, exchange_rate_type, exchange_rate
  FROM   ce_forecasts_v
  WHERE  forecast_header_id = :p_header_id;

• Project-linked forecast lines:

  SELECT project_number, name, header_name, start_date
  FROM   ce_forecasts_v
  WHERE  project_id IS NOT NULL;

• Forecasts by aging type and overdue handling:

  SELECT forecast_id, header_name, aging_type, aging_type_dsp, overdue_transactions
  FROM   ce_forecasts_v
  WHERE  aging_type = 'D';

Because the view joins GL_PERIODS and PA_PROJECTS_ALL, queries should filter on indexed identifiers such as FORECAST_HEADER_ID or FORECAST_ID wherever possible to avoid full scans of the period and project tables.