Search Results structure_version_id




Overview
Explore in AI Chat

Overview

PA_ASSGN_COST_EFFORT_V is a Projects (PA) module view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It consolidates planned and actual cost, raw cost, effort, and date information for task assignments, joining the assignment-level data held in PA_TASK_ASGMTS_V with the rolled-up progress figures maintained by the progress rollup infrastructure through the PA_PROGRESS_ROLLUP synonym. Its purpose is to present, at the resource assignment and task version level, a single row that pairs planning values (planned cost, planned raw cost, planned effort) with the corresponding actuals to date (actual cost, actual raw cost, actual effort) together with estimate-to-complete (ETC) values.

Because the view resolves actuals and ETC through resource-class decoding and progress version handling, it is typically used in project cost reporting, effort analysis, and integrations that require assignment-level comparisons between plan and actual performance.

Underlying Base Objects

The documented base objects referenced by the view are:

Key Columns

Common Use Cases and Queries

Typical scenarios include comparing planned versus actual cost and effort at the assignment level, identifying assignments whose ACTUAL_FINISH_DATE is populated for completion reporting, and extracting ETC figures for forecast reconciliation.

Example — actual finish dates for completed assignments:

  • SELECT project_id, task_id, resource_assignment_id, actual_start_date, actual_finish_date FROM pa_assgn_cost_effort_v WHERE actual_finish_date IS NOT NULL;

Example — plan versus actual cost and effort variance:

  • SELECT project_id, task_id, planned_cost, actual_cost_tc, planned_effort, actual_effort FROM pa_assgn_cost_effort_v WHERE project_id = :p_project_id;

Example — assignments with ETC remaining:

  • SELECT project_id, task_id, etc_rawcost_tc, etc_cost_tc FROM pa_assgn_cost_effort_v WHERE etc_cost_tc > 0;

Because the view joins assignment and progress rollup data, queries should generally be filtered by PROJECT_ID or TASK_ID to bound result sets.