Search Results labor_hours




Overview

APPS.PA_FCST_PROJ_PERIODIC_V is a forecasting view in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 that presents project forecast data aggregated at the intersection of assignment and accounting period. It is part of the Oracle Projects (PA) forecasting infrastructure, which supports the Project Forecasting and Resource Forecasting functionality used to project cost, revenue, margin, and labor quantities across future periods. The view consolidates rows from resource assignment records and budget/forecast period lines, applying business logic embedded in the PA_FCST_GLOBAL package to determine presentation formats based on the current forecasting profile settings.

The view's most notable characteristic is its profile-driven column behaviour. The amount-related columns are conditioned by calls to PA_FCST_GLOBAL.GetProjFcstShowAmount, which returns values such as 'REVENUE', 'COST', 'LABOR_HOURS', 'MARGIN', or 'MARGIN_PERCENTAGE'. This means that a single view dynamically exposes the correct measure — including labor hours — depending on how the deployment is configured. Because these values are resolved at query runtime via package functions, the view plays a central role in both reporting and integration scenarios where forecast figures must be interpreted consistently with the user's profile options.

Underlying Base Objects

The view is defined over a set of documented base objects:

  • PA_RESOURCE_ASSIGNMENTS (SYNONYM) — supplies the assignment-level forecast rows, including resource_assignment_id, standard bill rates, average bill rates, discount percentage, plan revenue, plan burdened cost, and plan quantity.
  • PA_PROJECT_ASSIGNMENTS (SYNONYM) — provides project_id, assignment_id, and assignment_name used to identify the assignment in context.
  • PA_BUDGET_LINES (SYNONYM) and PA_BUDGET_VERSIONS (SYNONYM) — supply the period-level budget/forecast lines (referenced as bl), including period_name, revenue, and burdened_cost.
  • PA_FCST_PERIODS_TMP_V (VIEW) — the period driver that generates the forecast period rows (period_name, period_start_date).
  • PA_FCST_GLOBAL (PACKAGE) — the core business logic package invoked for profile-driven formatting (GetProjFcstShowAmount, GetProbabilityPerFlag, GetProbabilityPer, find_project_fixed_price).
  • PA_PERIOD_PROCESS_PKG (PACKAGE) — supporting period processing logic.
  • FND_PROFILE (PACKAGE) and DUAL (SYNONYM) — profile-option lookup and scalar row support.

Key Columns

  • PROJECT_ID, ASSIGNMENT_ID, ASSIGNMENT_NAME — identify the project and the specific assignment being forecast.
  • RESOURCE_ASSIGNMENT_ID — the underlying resource assignment key.
  • PERIOD_NAME, PERIOD_START_DATE — the forecast accounting period and its start date.
  • PLAN_PROCESSING_CODE — derived from a DECODE on plan_error_code, returning '-1' when NULL and '0' otherwise; indicates whether the plan processed cleanly.
  • STD_BILL_RATE, AVG_BILL_RATE, AVG_DISCOUNT_PERCENTAGE — rate columns rounded to two decimals, populated or nulled according to the show-amount profile; returns NULL under 'LABOR_HOURS' and 'COST'.
  • PROJECT_TOTAL — the total measure for the project/period. For 'LABOR_HOURS' this resolves to total_plan_quantity, preserving the hours regardless of currency settings.
  • Period-level revenue and burdened cost columns — used to derive margin and margin-percentage values when the profile requests them.

Common Use Cases and Queries

The view is commonly used to report forecast labor hours, cost, revenue, and margin by period. A typical query filtering for labor-hour reporting is:

  • SELECT project_id, assignment_id, period_name, project_total FROM apps.pa_fcst_proj_periodic_v WHERE period_name = :period;
  • SELECT project_id, SUM(project_total) hours FROM apps.pa_fcst_proj_periodic_v WHERE assignment_name LIKE :pattern GROUP BY project_id;

Because the measure returned by PROJECT_TOTAL depends on the GetProjFcstShowAmount profile, report authors must confirm the active setting before interpreting results as labor hours. The view is also used as a validation source for plan_processing_code to detect assignments whose forecasts failed processing.