Search Results est_at_completion_cost




Overview

APPS.PA_ASSIGNMENT_PROG_HIST_V is a reporting view in Oracle EBS Projects (PA) that consolidates assignment-level progress history for project tasks. It exposes actual cost and effort, estimated remaining work, and estimated-at-completion values, all denominated in the functional currency or quantity basis appropriate to the resource class of each assignment. The view draws on the task assignment rollup infrastructure and, through the PA_PROGRESS_UTILS package, resolves estimated-to-complete (ETC) computations consistently with the standard Oracle Projects progress reporting engine.

Because it is a view rather than a table, PA_ASSIGNMENT_PROG_HIST_V applies no storage of its own; it materializes results at query time by joining progress rollup data to task assignment definitions and project element structure. This makes it a natural source for custom reports, extracts, and integration interfaces that require assignment-grain progress figures without re-implementing the ETC logic embedded in the utility package. In EBS 12.1.1 and 12.2.2 the object is owned by APPS and is ordinarily queried from a reporting or custom schema with the appropriate synonym and grants.

Underlying Base Objects

The documented base objects reveal the view's layered construction. PA_PROGRESS_ROLLUP (accessed via synonym) supplies the rolled-up progress figures such as actual cost to date, actual effort to date, ETC cost, ETC effort, and the as-of date. PA_TASK_ASGMTS_V provides the assignment attributes, including resource class code and baselined start and end dates. PA_PROJECTS_ALL, PA_PROJECT_STATUSES, PA_PROJ_ELEMENTS, PA_PROJ_ELEMENT_VERSIONS, and PA_PROJ_ELEM_VER_STRUCTURE supply the project, task, and structure context that qualifies an assignment and ties it to its owning project.

Supporting reference data comes from PA_TASK_TYPES and PA_PROJ_PROGRESS_ATTR, which govern task type behavior and progress attributes. Two PL/SQL packages are referenced: PA_PROGRESS_UTILS, used to sum ETC values across resource categories, and PA_TASK_ASSIGNMENT_UTILS, used to derive assignment-level calculations. The result is a denormalized read model that shields the consumer from the many-to-many relationships between projects, elements, versions, and assignments.

Key Columns

  • actual_cost and actual_effort: Amounts for the assignment, decoded by resource class so that PEOPLE, EQUIPMENT, and other resources return the correct cost or quantity column.
  • actual_start_date and actual_finish_date: Physical execution dates for the assignment's work.
  • baselined_asgmt_start_date and baselined_asgmt_end_date: The approved baseline window of the assignment.
  • as_of_date: The point in time at which progress figures were last rolled up.
  • estimated_start_date and estimated_finish_date: Forecast dates based on remaining effort.
  • estimated_remaining_effort: Effort still to be performed, computed through PA_PROGRESS_UTILS.SUM_ETC_VALUES.
  • ETC_COST_TC: Estimated cost to complete the assignment.
  • Est_at_Completion_Cost and Est_at_Completion_Effort: Actual-to-date plus ETC, giving the projected final cost and effort for the assignment.

Common Use Cases and Queries

A typical use is to report total projected cost at the assignment level for a project, combining actuals with ETC. For example:

  • SELECT assignment_id, actual_cost, ETC_COST_TC, Est_at_Completion_Cost FROM pa_assignment_prog_hist_v WHERE project_id = :p_project_id;
  • Comparing projected effort against baselined dates to identify assignments trending to overrun.
  • Feeding a data warehouse or project performance dashboard with assignment-grain progress history.

Because ETC calculations invoke PA_PROGRESS_UTILS and PA_TASK_ASSIGNMENT_UTILS, query performance benefits from restricting the result set by project, task, or as-of date rather than scanning the full view. Filtering with project_id and as_of_date is the recommended pattern for production reporting.