Search Results pa_forecasting_options_all




Overview
Explore in AI Chat

Overview

PA_FORECASTING_OPTIONS_ALL is a configuration table in the Oracle EBS Projects (PA) module. It stores the parameters and defaults that control how forecasting is performed for projects within an operating unit. Each row defines a complete set of forecasting options — period source, historical version limits, actuals and forecast cutoff dates, utilization calculation method, default expenditure type assignments, and the forecast project template used to generate forecast structures. The table is named with the _ALL suffix because it is partitioned by operating unit via ORG_ID; in a multi-organization installation, one row is defined for each operating unit, so the table effectively holds one configuration record per org.

Under a heuristic Data Vault classification derived from its foreign key structure, this object leans toward the satellite pattern. It carries descriptive, versionable configuration attributes describing a parent business key (the operating unit) and references an external template through a foreign key rather than acting as a pure relationship table. Modelers should treat ORG_ID as the logical parent key and the remaining descriptive columns as satellite attributes when mapping to a Data Vault or dimensional model.

Key Information Stored

The table contains 32 documented columns. The most significant are grouped below.

Standard WHO audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) track row maintenance.

Common Use Cases and Queries

Administrators query this table when auditing how forecasting behaves for an operating unit, and reporting teams join it to forecast results to explain the derivation rules applied.

SELECT org_id, gl_period_flag, pa_period_flag,
       org_fcst_period_type, start_period_name, number_of_periods,
       forecast_thru_date, actuals_thru_date,
       util_calc_method, org_fcst_project_template_id
FROM   pa.pa_forecasting_options_all
WHERE  org_id = :p_org_id;

A common reporting pattern joins the template reference back to the project template in PA_PROJECTS_ALL:

SELECT f.org_id, p.name AS template_name
FROM   pa.pa_forecasting_options_all f,
       pa.pa_projects_all p
WHERE  f.org_forecast_template_id = p.project_id;

Typical scenarios include verifying the active period calendar before a forecast run, confirming the forecast horizon (START_PERIOD_NAME and NUMBER_OF_PERIODS) for planning cycles, and validating default expenditure type assignments after a configuration change.

Related Objects

  • PA_PROJECTS_ALL — referenced through the documented foreign key ORG_FCST_PROJECT_TEMPLATE_ID, which points to the forecast project template.
  • PA_FORECASTS / forecast generation logic — consumes the options defined here when generating forecast versions.
  • PA_PROJECT_TYPES / project setup tables — supply context for forecasting defaults applied during project entry.
  • PA_EXPENDITURE_TYPES — validates the DEFAULT_ASSIGN_EXP_TYPE, BILL_UNASSIGN_EXP_TYPE, and NONBILL_UNASSIGN_EXP_TYPE values.
  • HR_ALL_ORGANIZATION_UNITS / operating unit setup — defines the ORG_ID for which each configuration row exists.

Because the table is organization-partitioned via ORG_ID, all queries and joins should be filtered by operating unit to return the correct configuration for the context in which the forecast is executed.