Search Results actual_cost_to_date

Overview

APPS.PA_TASK_DET_EFFORT_COST_V is a read-only database view in the Oracle E-Business Suite Projects (PA) schema. It exposes task-level effort and cost metrics for project elements, spanning project structures, progress attributes, and summarized effort/cost accumulation. The view is designated Oracle Internal Use Only; Oracle does not support direct data access through this object except by standard Oracle Applications programs. Consequently, it should be treated primarily as a reporting and integration endpoint, not as an extension surface.

The name embeds the object's purpose: "TASK_DET" indicates task-level detail, while "EFFORT_COST" indicates the dual presentation of effort (in hours) and cost (in currency amounts). The view therefore returns, for each project element (task), paired effective and cost measures such as planned, actual-to-date, percent complete, percent spent, estimate-to-complete (ETC), and estimate-at-completion (EAC). It also exposes earned value metrics: budgeted cost of work scheduled, cost performance index, cost variance, earned value, estimate at completion, schedule at completion, schedule performance index, and schedule variance. These are supplied for both effort and cost perspectives, making the view suitable for earned value management (EVM) reporting and progress analysis at the task level.

Critically for the searched term percent_spent_effort, this view provides a direct column of that name. PERCENT_SPENT_EFFORT represents the proportion of planned effort consumed relative to the applicable baseline or planned effort. It is paired with PERCENT_COMPLETE_EFFORT (physical progress against effort) and, on the cost side, with PERCENT_SPENT_COST and PERCENT_COMPLETE_COST. This pairing allows consumers to distinguish schedule-based consumption from objective-based progress.

Underlying Base Objects

The view is defined over project element, structure, scheduling, and progress objects within the PA schema, together with supporting packages and lookups. Documented base objects include:

• PA_PROJ_ELEMENTS, PA_PROJ_ELEMENT_VERSIONS, PA_PROJ_ELEM_VER_STRUCTURE, PA_PROJ_ELEM_VER_SCHEDULE — project element definitions, versioning, hierarchical structure, and scheduling.
• PA_PROJ_PROGRESS_ATTR and PA_PROJ_WORKPLAN_ATTR — progress attributes and workplan attributes governing percent-complete behavior.
• PA_PROGRESS_ROLLUP and PA_PROGRESS_UTILS, PA_CURRENCY — progress rollup logic and currency conversion utilities.
• PA_TASK_TYPES, PA_LOOKUPS — task classification and lookup validation.
• PJI_FM_XBS_ACCUM_TMP1 — an accumulation structure used for effort and cost aggregation.

These referenced objects confirm that PA_TASK_DET_EFFORT_COST_V is a composite view that joins task hierarchy and version metadata to progress configuration and accumulated effort/cost figures, converting monetary amounts using the project's functional currency where applicable. Because many dependencies are synonyms or packages rather than stored tables, the view is best understood as a dynamic projection rather than a persisted fact table.

Key Columns

Columns fall into identification, effort, cost, and performance categories:

• Identification: PROJECT_ID, PROJ_ELEMENT_ID, ELEMENT_VERSION_ID, PARENT_STRUCTURE_VERSION_ID, OBJECT_TYPE, HOURS.
• Effort measures: PLANNED_EFFORT, ACTUAL_EFFORT_TO_DATE, PERCENT_COMPLETE_EFFORT, PERCENT_SPENT_EFFORT, ETC_EFFORT, EAC_EFFORT, BASELINE_EFFORT.
• Cost measures: PLANNED_COST, ACTUAL_COST_TO_DATE, PERCENT_COMPLETE_COST, PERCENT_SPENT_COST, ETC_COST, EAC_COST, BASELINE_COST, EARNED_VALUE, ESTIMATE_AT_COMPLETION, BUDGETED_COST_OF_WORK_SCHEDULE.
• Performance indices: COST_PERFORMANCE_INDEX, SCHEDULE_PERFORMANCE_INDEX, COST_VARIANCE, SCHEDULE_VARIANCE, SCHEDULE_AT_COMPLETION.
• Progress configuration: PERCENT_COMPLETE_ID, PHYSICAL_PERCENT_COMPLETE, PROGRESS_ROLLUP_METHOD, ROLLUP_PERCENT_COMPLETE, PERCENT_COMP_ENABLED_FLAG, PROGRESS_ENTRY_ENABLED_FLAG.
• Currency: PROJECT_CURRENCY_CODE, PROJFUNC_CURRENCY_CODE.

PERCENT_SPENT_EFFORT is the requested metric and reflects effort consumption; it differs from PERCENT_COMPLETE_EFFORT, which reflects physical/objective completion per the progress rollup method.

Common Use Cases and Queries

Typical use cases include task-level percent-spent and percent-complete reporting, earned value analysis, and effort/cost variance dashboards. A representative query for the searched metric:

• SELECT project_id, proj_element_id, object_type, planned_effort, actual_effort_to_date, percent_complete_effort, percent_spent_effort, etc_effort, eac_effort FROM apps.pa_task_det_effort_cost_v WHERE project_id = :project_id ORDER BY proj_element_id;
• EVM reporting: SELECT project_id, proj_element_id, earned_value, budgeted_cost_of_work_schedule, cost_variance, cost_performance_index, schedule_variance FROM apps.pa_task_det_effort_cost_v WHERE project_id = :project_id;
• Progress configuration checks: SELECT project_id, proj_element_id, progress_rollup_method, progress_entry_enabled_flag, percent_complete_id FROM apps.pa_task_det_effort_cost_v;

Queries should always filter by PROJECT_ID, since the view spans all projects. Because access is unsupported outside standard Oracle programs, organizations should prefer certified reporting tools and Oracle-provided views where available, while treating this object as an internal, version-sensitive dependency.