Search Results pa_task_assignments_amg_v




Overview
Explore in AI Chat

Overview

PA_TASK_ASSIGNMENTS_AMG_V is a valid APPS-schema view within the Oracle E-Business Suite Projects (PA) module. Its documented description states that it provides progress data for task assignments. In practice the view consolidates progress rollup and earned value information at the granularity of an individual task assignment, joining progress data held at the project element version level to the assignment definition maintained by the task assignment view.

Within Oracle EBS 12.1.1 and 12.2.2 the _AMG suffix identifies views typically consumed by Oracle's Application Management and reporting layers, and this view serves as a reporting and integration surface for progress and performance measurement. Rather than storing data, it exposes derived values: variances between actual and scheduled assignment dates, actual cost and effort to date, baseline cost and effort, estimated-at-completion cost, earned value, and countdown metrics such as days until progress is due or days until an assignment starts. These are the same style of metrics surfaced in Progress Workbench and related earned value reporting, making the view suitable for extracting consistent progress snapshots without reimplementing PA_PROGRESS_UTILS logic.

Underlying Base Objects

The view text is defined over PA_PROGRESS_ROLLUP (aliased PPR), PA_TASK_ASSIGNMENTS_V (PTAV, a view), and PA_PROJ_PROGRESS_ATTR (PPA), and it invokes several public utility packages. The documented referenced base objects are:

Key correlations include PROJECT_ID, OBJECT_ID, OBJECT_VERSION_ID, PROJ_ELEMENT_ID and AS_OF_DATE. Assignment-level baseline and schedule attributes come from PA_TASK_ASSIGNMENTS_V, while period-to-date progress, cost, effort and earned value come from PA_PROGRESS_ROLLUP. Scalar functions such as PA_PROGRESS_UTILS.GET_ACT_COST_THIS_PERIOD, GET_ACT_EFFORT_THIS_PERIOD, GET_NEXT_PROGRESS_CYCLE and SUM_ETC_VALUES compute period amounts and estimated-at-completion totals. Because this is a view, results reflect the queries made through these base objects at run time.

Key Columns

Common Use Cases and Queries

Typical uses include progress and earned value reporting by project or assignment, monitoring assignments approaching their start or progress-due dates, and extracting actual versus baseline cost and effort for performance analysis. Always supply an AS_OF_DATE filter and restrict to the relevant project to keep volume manageable.

SELECT project_id, proj_element_id, actual_cost, actual_effort,
       earned_value, est_at_completion_cost, days_until_progress_due
FROM   apps.pa_task_assignments_amg_v
WHERE  as_of_date = TRUNC(SYSDATE)
AND    days_until_progress_due BETWEEN 0 AND 7;
SELECT proj_element_id, baseline_cost, actual_cost,
       est_at_completion_cost, actual_start_date, actual_finish_date
FROM   apps.pa_task_assignments_amg_v
WHERE  as_of_date = TRUNC(SYSDATE)
AND    project_id = :project_id;

Because the view embeds utility-package calls, queries can be resource-intensive; filter by PROJECT_ID and AS_OF_DATE, and grant SELECT to reporting users through the APPS schema rather than querying base tables directly.