Search Results weighted_or_full_code

Overview

PA_FORECASTING_OPTIONS_V is a Projects (PA) module view in Oracle E-Business Suite 12.1.1 and 12.2.2 that exposes the configuration parameters and system defaults governing project forecasting. The view is defined over the table PA_FORECASTING_OPTIONS_ALL (referenced internally as PA_FORECASTING_OPTIONS) and stores one row per operating unit, making it the authoritative source for how forecast versions are generated, how historical periods are selected, and how unassigned time and expenses are handled.

Because forecasting behavior is largely deterministic — driven by stored defaults rather than user input at run time — this view is the primary reference for reporting on, auditing, and integrating with the forecasting engine. It is commonly consumed by concurrent program logic, by inquiry-only custom reports, and by interfaces that must replicate forecast period selection outside of standard Oracle forms. The presence and ordering of columns such as ORG_FCST_PERIOD_TYPE, START_PERIOD_NAME, and NUMBER_OF_PERIODS is particularly relevant to users investigating how many forecast periods are generated and starting from which period.

Underlying Base Objects

ETRM documentation identifies PA_FORECASTING_OPTIONS_ALL as the single underlying base table. Notably, the view text selects from a synonym or table named PA_FORECASTING_OPTIONS, which resolves to the same logical object. No additional base objects are documented as referenced, so joins are not required to retrieve option values — the grain is one row per ORG_ID. The ETRM note "Not implemented in this database" indicates the view exists only where the Projects forecasting feature has been installed and seeded with option rows; in environments without forecasting configuration, the view returns no rows. Because it is a simple single-table view, it inherits the organization-level partitioning of its base table and is subject to the same multi-org security rules.

Key Columns

• ORG_ID — Operating unit identifier; the natural key for the view.
• ORG_FCST_PERIOD_TYPE — Controls the period basis (for example GL periods versus PA periods) used when expanding the forecast horizon.
• START_PERIOD_NAME — The period from which forecast generation begins.
• NUMBER_OF_PERIODS — The count of periods to be forecast; this is the column most frequently queried by users searching "number_of_periods."
• GL_PERIOD_FLAG / PA_PERIOD_FLAG — Flags indicating whether GL and PA period definitions are used.
• FORECAST_THRU_DATE / ACTUALS_THRU_DATE — Date boundaries separating actuals from forecasted values.
• MAX_HISTORICAL_VERSIONS — Limits historical forecast versions retained.
• UTIL_CALC_METHOD — Method used to calculate utilization.
• DEFAULT_ASSIGN_EXP_TYPE_CLASS / DEFAULT_ASSIGN_EXP_TYPE — Default expenditure type class and type for assignments.
• DEFAULT_TP_AMOUNT_TYPE — Default transfer price amount type.
• BILL_UNASSIGN_TIME_FLAG / NONBILL_UNASSIGN_TIME_FLAG — Treatment of unassigned billable and non-billable time.
• BILL_UNASSIGN_PROJ_ID, BILL_UNASSIGN_EXP_TYPE_CLASS, BILL_UNASSIGN_EXP_TYPE — Targets for unassigned billable time.
• NONBILL_UNASSIGN_PROJ_ID, NONBILL_UNASSIGN_EXP_TYP_CLS, NONBILL_UNASSIGN_EXP_TYPE — Targets for unassigned non-billable time.
• JOB_COST_RATE_SCHEDULE_ID, KEY_MEMBER_ROLE_ID — Rate schedule and role references used in costing forecast members.
• FORECAST_CLASS_CATEGORY, ORG_FCST_PROJECT_TEMPLATE_ID, WEIGHTED_OR_FULL_CODE — Forecast classification, source project template, and weighting/valuation mode.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, and ROWID.

Common Use Cases and Queries

The most frequent use case is confirming how many forecast periods are configured, typically to reconcile forecast output against expected period counts or to diagnose forecasting errors. A representative query is:

• SELECT org_id, org_fcst_period_type, start_period_name, number_of_periods FROM pa_forecasting_options_v ORDER BY org_id;
• SELECT forecast_thru_date, actuals_thru_date, max_historical_versions FROM pa_forecasting_options_v WHERE org_id = :p_org_id;
• SELECT bill_unassign_proj_id, nonbill_unassign_proj_id, util_calc_method FROM pa_forecasting_options_v WHERE org_id = :p_org_id;

Administrators also use the view to validate multi-org seeding — one row per operating unit — before running forecast generation, and integration developers read NUMBER_OF_PERIODS and START_PERIOD_NAME to mirror period selection in external planning tools. Because the view is read-only and derived from a single table, it is safe for high-volume inquiry reporting.