Search Results cumulative_work_quantity




Overview

PA_PROGRESS_HIST_DET_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Projects (PA) product family. It exposes progress history detail at the workplan element level, combining percent-complete entries from PA_PERCENT_COMPLETES with progress rollup figures from PA_PROGRESS_ROLLUP and structural attributes of project elements and element versions. The view is designed to drive Progress Workbench and progress history inquiries, returning one row per percent-complete record joined to its corresponding project, element version, and schedule attributes.

In 12.1.1 and 12.2.2 the view is a critical integration point for customers who need to report against physical progress measures, particularly the CUMULATIVE_WORK_QUANTITY and INCREMENTAL_WORK_QUANTITY columns that appear on the progress history. These columns are not stored on PA_PERCENT_COMPLETES itself but are sourced from PA_PROGRESS_ROLLUP, which is why reporting directly against the base percent-complete table is insufficient for work-quantity reporting. The view also carries a documented INDEX hint on the temporary accumulation structure PJI_FM_XBS_ACCUM_TMP1, indicating performance tuning for large progress datasets.

Underlying Base Objects

The documented base objects include:

Key Columns

Common Use Cases and Queries

The most frequent query pattern filters on project and as-of date to retrieve the latest published progress record, together with the cumulative work quantity. A typical statement is:

SELECT project_id, proj_element_id, element_name, as_of_date, completed_percentage, incremental_work_quantity, cumulative_work_quantity FROM apps.pa_progress_hist_det_v WHERE project_id = :p_project_id AND current_flag = 'Y' AND published_flag = 'Y' ORDER BY as_of_date DESC;

Additional scenarios include reconciling progress rollup quantities against manual percent-complete entries, validating summary versus detail element progress for a workplan, and extracting progress history for third-party earned-value or project-controls dashboards. Because the view already carries the DECODE logic for status codes and work-quantity enablement, it is preferable to PA_PERCENT_COMPLETES for any report requiring cumulative work quantity, remaining effort, or full workplan context.