Results for “pa_fcst_proj_hdr_v”

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

Overview

PA_FCST_PROJ_HDR_V is an Oracle E-Business Suite view owned by the APPS schema and defined within the Projects (PA) product family. It presents project forecasting information in a pivoted, reporting-friendly layout, exposing planned revenue, cost, labor hours, margin, and margin percentage values aggregated by project and accounting period. The view is a header-level forecasting construct, intended to feed forecast inquiries, project status reports, and downstream reporting or integration layers that require a condensed period-by-period forecast picture rather than raw budget line detail.

The view carries a VALID status in the ETRM 12.2.2 repository and is documented identically for 12.1.1 and 12.2.2 deployments, meaning no structural differences are introduced by the online patching architecture of 12.2.x. Its behavior is governed at runtime by the PA_FCST_GLOBAL package, which supplies profile-driven parameters such as the forecast display amount type, probability weighting flag, probability percentage, project identifier, and start/end date range.

Underlying Base Objects

The documented referenced base objects include PA_PROJECTS_ALL, PA_RESOURCE_ASSIGNMENTS, PA_BUDGET_LINES, PA_BUDGET_VERSIONS, PA_FCST_GLOBAL, PA_FCST_PERIODS_TMP_V, PA_PERIOD_PROCESS_PKG, FND_PROFILE, and DUAL. In practice, the view joins PA_PROJECTS_ALL to PA_RESOURCE_ASSIGNMENTS on PROJECT_ID, then to PA_BUDGET_LINES and PA_BUDGET_VERSIONS to obtain period-level revenue, burdened cost, and quantity figures. The project identifier supplied by PA_FCST_GLOBAL.GETPROJECTID restricts output to a single project, while GETPROJFCSTSTARTDATE and GETPROJFCSTENDDATE bound the period range. PA_PERIOD_PROCESS_PKG and PA_FCST_PERIODS_TMP_V support period-name resolution and sequencing, and FND_PROFILE supplies the profile option values consumed by the PA_FCST_GLOBAL wrapper functions.

Key Columns

• PROJECT_ID — Identifier of the project, sourced from PA_PROJECTS_ALL.
• Y1 — The project segment (SEGMENT1), used as the partition key for the analytical DENSE_RANK ordering.
• Y1_SEQ — Sequence value associated with the Y1 grouping, seeded at zero in the inner query.
• Y1_RIGHTATTRIBUTE1 — Formatted rounded amount for the project, driven by the GETPROJFCSTSHOWAMOUNT profile flag and optionally multiplied by GETPROBABILITYPER when probability weighting is enabled.
• Y1_LEFTATTRIBUTE1 — Formatted value of RA.AVERAGE_DISCOUNT_PERCENTAGE.
• X1 — The accounting period name (BL.PERIOD_NAME) representing the forecast bucket.
• X1_SEQ — Dense rank computed over PERIOD_START_DATE partitioned by Y1, establishing chronological ordering of periods.
• VALUE — The period-level measure, resolved via DECODE against the display amount setting: revenue, cost, labor hours, margin, or margin percentage, with probability weighting applied when configured.
• PERIOD_START_DATE — The start date of the reporting period, used both as a display attribute and as the sort basis for X1_SEQ.

Common Use Cases and Queries

Typical usage includes project forecasting dashboards, forecast-versus-budget variance analysis, and extracts feeding data warehouses or third-party reporting tools. Because the display measure is controlled by profile options rather than by a parameter, callers must ensure the relevant PA_FCST_GLOBAL settings (show amount type, probability flag, probability percentage, project, and date range) are established in the session before querying.

A representative query returns the period-ordered forecast series for the project currently resolved in the session context:

• SELECT project_id, x1, x1_seq, value FROM apps.pa_fcst_proj_hdr_v ORDER BY x1_seq;
• SELECT project_id, y1, x1, value FROM apps.pa_fcst_proj_hdr_v WHERE period_start_date BETWEEN :start_date AND :end_date ORDER BY x1_seq;
• SELECT y1, SUM(value) FROM apps.pa_fcst_proj_hdr_v WHERE x1 = :period_name GROUP BY y1;

Because PA_FCST_GLOBAL resolves a single PROJECT_ID and a bounded date range, result sets are inherently narrow. Queries intended to span multiple projects should not rely on this view alone; instead they should invoke PA_FCST_GLOBAL initialization per project or use the underlying budget and resource assignment tables directly.