Search Results incremental_work_quantity




Overview
Explore in AI Chat

Overview

PA_BACK_PROJ_TASK_PROG_V is an APPS-owned database view in the Oracle EBS Projects (PA) module, defined for release levels 12.1.1 and 12.2.2. It exposes project, task, and structure progress information for the Oracle Project Management progress reporting and rollup functionality. The name prefix "PA_BACK" indicates that it is a backend view intended primarily for internal consumption by progress rollup and status processing logic rather than for direct end-user reporting. The view consolidates project header attributes, project element (task and structure) definitions, structure versions, scheduling flags, and progress status into a single flattened result set. A significant characteristic of the view is that it projects a number of progress measurement columns — including AS_OF_DATE, PERCENT_COMPLETE_ID, COMPLETED_PERCENTAGE, EFF_ROLLUP_PERCENT_COMP, BASE_PROGRESS_STATUS_CODE, and EFF_ROLLUP_PROG_STAT_CODE — as NULL placeholders. This design allows the view to act as a stub or base layer whose schema mirrors the columns required by progress rollup processing, with the effective rollup values being populated at a higher layer of the progress hierarchy or by companion views and package logic. The presence of the EFF_ROLLUP_PROG_STAT_CODE column reflects the effective rollup progress status code, which summarizes the aggregated progress state of a task or structure after child records roll up into it.

Underlying Base Objects

The documented base objects referenced by the view span project definition, element hierarchy, scheduling, and lookup metadata, including PA_PROJECTS_ALL, PA_PROJ_ELEMENTS, PA_PROJ_ELEMENT_VERSIONS, PA_PROJ_ELEM_VER_SCHEDULE, PA_PROJ_ELEM_VER_STRUCTURE, PA_PROJ_STRUCTURE_TYPES, PA_STRUCTURE_TYPES, PA_TASK_TYPES, PA_PROJECT_STATUSES, PA_OBJECT_RELATIONSHIPS, PA_PERCENT_COMPLETES, PA_PROGRESS_ROLLUP, PA_PROJ_PROGRESS_ATTR, and PA_LOOKUPS. The view also calls the PA_PROJ_ELEMENTS_UTILS package, specifically IS_SUMMARY_TASK_OR_STRUCTURE, to classify each element version as a summary task or structure. Project header data is drawn from PA_PROJECTS_ALL, element identity from PA_PROJ_ELEMENTS, and versioned hierarchy attributes such as WBS_NUMBER, WBS_LEVEL, and DISPLAY_SEQUENCE from PA_PROJ_ELEMENT_VERSIONS. Scheduling flags and dates come from PA_PROJ_ELEM_VER_SCHEDULE, while status context is contributed from PA_PROJECT_STATUSES and task type semantics from PA_TASK_TYPES. The relationship between PA_OBJECT_RELATIONSHIPS and the project structures is used to resolve structure name and version for structure-type elements, complementing the task-oriented DECODE logic.

Key Columns

Common Use Cases and Queries

Because effective progress values are exposed as placeholders, the view is typically queried in conjunction with PA_PROGRESS_ROLLUP and PA_PERCENT_COMPLETES, or joined to PA_PROJ_PROGRESS_ATTR, to obtain complete progress pictures. A representative query lists tasks belonging to a project with their WBS hierarchy and rollup status:

SELECT p.PROJECT_ID, p.NAME, v.WBS_NUMBER, v.WBS_LEVEL, v.EFF_ROLLUP_PROG_STAT_CODE, v.PLANNED_EFFORT FROM APPS.PA_BACK_PROJ_TASK_PROG_V v, APPS.PA_PROJECTS_ALL p WHERE v.PROJECT_ID = p.PROJECT_ID AND v.OBJECT_TYPE = 'PA_TASKS' ORDER BY v.WBS_LEVEL, v.DISPLAY_SEQUENCE;

Integration scenarios include feeding project progress dashboards, validating rollup calculations during implementations of Project Management, and diagnosing discrepancies in effective rollup status versus base progress status. When tracing the origin of an EFF_ROLLUP_PROG_STAT_CODE value, developers should check PA_PROGRESS_ROLLUP and PA_PROJ_PROGRESS_ATTR, as the backend view supplies the structural and descriptive foundation while these objects materialize the effective values.