Search Results planned_work_quantity




Overview
Explore in AI Chat

Overview

APPS.PA_TASK_PROG_HIST_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes historical and current progress information for project tasks and work breakdown structure (WBS) elements maintained in Oracle Projects. The view consolidates task-level planning attributes, progress publication data, percent-complete calculations, and rollup metrics into a single denormalized result set, allowing project managers, reporting tools, and integration interfaces to query task progress history without joining numerous base tables directly.

The object is registered in Oracle's ETRM repository as an internal view type carrying the standard Oracle warning that data access is unsupported except through standard Oracle Applications programs. Consequently, the view should be treated as a reporting and integration convenience rather than a supported public API. Underlying structures such as PA_PROJ_ELEMENTS_UTILS remain Oracle Internal Use Only.

Underlying Base Objects

ETRM documents the following dependencies for PA_TASK_PROG_HIST_V:

  • PA_LATEST_PUB_STRUC_TASKS_V — view supplying the latest published task structure, the primary driver of task names, numbers, and WBS hierarchy.
  • PA_PROGRESS_ROLLUP — synonym holding rolled-up progress percentages and effort figures.
  • PA_PERCENT_COMPLETES — synonym providing percent-complete definitions and calculations.
  • PA_PROJECT_STATUSES — synonym resolving status codes to descriptions.
  • HZ_PARTIES — synonym used to resolve the publishing party name.
  • FND_GLOBAL — package supplying session context (user, responsibility, org) used to filter or secure the result set.
  • PA_PROJ_ELEMENTS_UTILS — package used internally to resolve element attributes.

The view joins these objects to present task structure, progress definitions, and rollup results in one row per task-element-version combination.

Key Columns

Columns addressing the user's search term, SUMMARY_ELEMENT_FLAG, is defined as VARCHAR2(4000). Despite the "_FLAG" suffix, its large width indicates it stores an aggregate or concatenated value rather than a simple Y/N indicator — typically used to mark whether a task is a summary (parent) element within the WBS hierarchy and to carry associated summary attributes.

Other significant columns include:

Common Use Cases and Queries

Typical uses include progress-trend reporting, dashboard extraction, and integration feeds to external scheduling tools. A representative query retrieving current task progress:

  • SELECT project_number, task_number, wbs_number, summary_element_flag, completed_percentage, eff_rollup_percent_comp, as_of_date FROM apps.pa_task_prog_hist_v WHERE project_id = :p_project_id AND current_flag = 'Y' ORDER BY wbs_number;

To identify summary elements specifically, filter on the flag column:

  • SELECT task_number, task_name, summary_element_flag FROM apps.pa_task_prog_hist_v WHERE project_id = :p_project_id AND summary_element_flag IS NOT NULL;

To trend historical progress for a task across published snapshots:

  • SELECT as_of_date, base_percent_complete, eff_rollup_percent_comp, published_flag FROM apps.pa_task_prog_hist_v WHERE task_id = :p_task_id ORDER BY as_of_date;

Because the view is unsupported for direct access, queries should be restricted to read-only reporting, and joins to FND_GLOBAL-based security should not be removed. Consumers should expect the SUMMARY_ELEMENT_FLAG semantics to vary with the underlying PA_PROJ_ELEMENTS_UTILS logic and validate values against their release patch level.