Search Results pa_assignment_progress_v




Overview
Explore in AI Chat

Overview

The PA_ASSIGNMENT_PROGRESS_V view in the Oracle E-Business Suite Projects (PA) module provides a consolidated, reporting-ready representation of assignment-level progress information. It is owned by the APPS schema and is documented as a valid view in both EBS 12.1.1 and 12.2.2. The view sits atop the Projects progress-management infrastructure and exposes derived metrics such as schedule variances, actual and estimated effort, and cycle-related date computations for individual task assignments. Its primary role is to support progress reporting, effort tracking, and integration of assignment-level data into dashboards, concurrent programs, and custom reports without requiring consumers to reconstruct the underlying business logic.

Because the view encapsulates calls to PA_PROGRESS_UTILS and other progress utilities, it delivers calculated values that would otherwise demand complex procedural logic. This makes it particularly valuable in reporting layers where standard progress rollup figures must be reconciled against assignment baselines.

Underlying Base Objects

The documented base objects underlying PA_ASSIGNMENT_PROGRESS_V span progress, project structure, and utility components. These include the package PA_CURRENCY, the synonym-backed tables PA_PERCENT_COMPLETES, PA_PROGRESS_ROLLUP, PA_PROJECTS_ALL, PA_PROJ_ELEMENTS, PA_PROJ_ELEMENT_VERSIONS, PA_PROJ_ELEM_VER_STRUCTURE, and PA_PROJ_PROGRESS_ATTR. The view also references the utility package PA_PROGRESS_UTILS and PA_TASK_ASSIGNMENT_UTILS, along with the PA_TASK_ASGMTS_LPV_V view (aliased internally as PTAV) and the PA_TASK_TYPES synonym.

In practical terms, PA_TASK_ASGMTS_LPV_V supplies baseline and planned assignment attributes such as ASSIGNMENT_START_DATE, ASSIGNMENT_END_DATE, and BASELINED_PLANNED_QTY. Progress attribute and rollup objects contribute actual and estimated effort figures, while PA_PROJECTS_ALL and the project element structures provide the project and task hierarchy context. The packages supply dynamic computations invoked directly within the view text.

Key Columns

Common Use Cases and Queries

Typical uses include assignment progress monitoring, effort-at-completion analysis, and variance reporting against baselines. A representative query follows:

  • SELECT project_id, object_id, actual_effort, estimated_remaining_effort, est_at_completion_effort, days_until_progress_due FROM pa_assignment_progress_v WHERE days_until_progress_due <= 7; — identifies assignments with imminent progress cycles.
  • SELECT object_id, act_sch_start_var, act_sch_finish_var, est_bas_finish_var FROM pa_assignment_progress_v ORDER BY est_bas_finish_var DESC; — ranks assignments by schedule slippage.

Because the view invokes PL/SQL utility functions, queries should be scoped with predicates where possible to limit execution cost on large project portfolios.