ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Actual Cost (ACWP) on task removed when a sub-project proxy task is indented

book

Article ID: 226348

calendar_today

Updated On:

Products

Clarity PPM On Premise Clarity PPM SaaS

Issue/Introduction

In the Classic PPM Gantt for a project, when a Task (which is a proxy task for the subproject) is out dented, after running 'Update Cost Totals' (from 'Actions' drop-down on the Classic Tasks tab list page), the Actual Cost data is populated correctly. However, when the task is indented in the PPM Gantt, then the Actual Cost becomes zero after running 'Update Cost totals'. 

STEPS TO REPRODUCE: 

  1. Create three financially enabled projects (P1, P2, P3) and allocate financially enabled labor resources
  2. Create a Phase task in Project P1
  3. Assign the resources to tasks on the projects
  4. Run the below jobs in the order listed below:
    • Rate Matrix job
    • Post Timesheets job
    • Post Transactions to Financials job
    • Post to WIP job
  5. Run the 'Update Cost Totals' on the task list page of the projects to populate ACWP
  6. Make project P2 and P3 sub-projects of P1
  7. Open Project P1 and go to the Task list page. All Tasks are displayed including Project P2 and P3
  8. Open the PPM Gantt chart for Project P1 and you see that ACWP is displayed for all the Tasks (which are really sub-projects)
  9. Now Indent Task P2 under the Phase task created in step 2
  10. In Project P1, go to the Task list page and run 'Update Cost Totals'  

Expected Results: ACWP for Task P2 to remain intact and on the Gantt chart, Actual Cost also to remain intact. 

Actual Results: ACWP on Task P2 becomes zero. On The Gantt chart, Actuals for Task P2 are intact but the Actual Cost becomes zero. 

Cause

Defect ID: DE61096

Environment

Release : 15.8.1, 15.9.1, 15.9.2, 15.9.3

Component : CLARITY PROJECT MANAGEMENT

Resolution

Resolved in Clarity version 16.0 and patched in 15.9.3.2