Results for “planned_effort”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

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:

• PA_TASK_ASGMTS_V (VIEW) — supplies the assignment and planning side of the row, including PROJECT_ID, TASK_ID, TASK_VERSION_ID, RESOURCE_LIST_MEMBER_ID, RESOURCE_ASSIGNMENT_ID, PLANNED_BUR_COST_TXN_CUR, PLANNED_RAW_COST_TXN_CUR, PLANNED_QUANTITY, and RESOURCE_CLASS_CODE.
• PA_PROGRESS_ROLLUP (SYNONYM) — supplies the progress-measured actual and ETC columns (actual and estimated start/finish dates, ACT_*_TO_DATE_TC, ACT_*_RAWCOST_TO_DATE_TC, and ETC_* values).
• PA_PROJ_ELEMENT_VERSIONS and PA_PROJ_ELEM_VER_STRUCTURE (SYNONYMS) — provide element version and structure version context (ELEMENT_VERSION_ID exposed as STRUCTURE_VERSION_ID).
• PA_PROJ_WORKPLAN_ATTR (SYNONYM) — supplies the workplan attribute WP_ENABLE_VERSION_FLAG.
• PA_PROGRESS_UTILS (PACKAGE) — the SUM_ETC_VALUES function computes ETC raw cost and ETC cost.
• PA_FP_FCST_GEN_AMT_UTILS (PACKAGE) — GET_ETC_FROM_PLAN supplies forecast-derived ETC values.
• PA_TASK_ASSIGNMENT_UTILS (PACKAGE) — assignment utility logic.

Key Columns

• PROJECT_ID, TASK_ID, TASK_VERSION_ID — project/task context and version.
• STRUCTURE_VERSION_ID — element version of the project structure.
• RESOURCE_LIST_MEMBER_ID, RESOURCE_ASSIGNMENT_ID — assignment identifiers.
• ACTUAL_START_DATE, ACTUAL_FINISH_DATE, ESTIMATED_START_DATE, ESTIMATED_FINISH_DATE — dates sourced from the progress rollup. ACTUAL_FINISH_DATE identifies when the assignment actually completed.
• PLANNED_COST, PLANNED_RAWCOST, PLANNED_EFFORT — planned BUR cost, raw cost, and quantity.
• ACTUAL_RAWCOST_TC, ACTUAL_COST_TC — actual raw and burdened cost to date, decoded by RESOURCE_CLASS_CODE ('PEOPLE', 'EQUIPMENT', otherwise other).
• ACTUAL_EFFORT — actual quantity to date, decoded by resource class.
• ETC_RAWCOST_TC, ETC_COST_TC — estimate-to-complete, computed through PA_PROGRESS_UTILS.SUM_ETC_VALUES.

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.