Every so often we find that the ACWP calculated for timesheets posted applies the rate of $1. It happens randomly for for some project task assignments.
A project might show the issue for a specific task assignment, but other assignments on the same project might be OK.
One timesheet might have 5 tasks posted and only 1 of them might show the issue. It looks pretty random.
Below can be found some STR to get this reproducible.
STEPS TO REPRODUCE:
Expected Results: ACWP at assignment level is calculated based on the rate available at matrix
Actual results: ACWP at assignment level is calculated at a rate of $1
Any supported Clarity release
the post timesheet job has modified the assignment dates due to the time posted at the timesheet and the NBI_PROJ_RES_RATES_AND_COSTS table does not contain a rate for the resulting whole assignment.
In order to get around this:
Please open a support ticket if you have never run the Posting Repair and Actual Cost Curve Regeneration job or you do not find it on the list of available jobs
The original assignment dates where for a single day and the NBI_PROJ_RES_RATES_AND_COSTS table has only got a rate for a single day
Notice that the post timesheet job modifies the assignment dates due to the time posted at the timesheet where the Start Date will be the first timesheet day where time is entered and the Finish Date will be the last timesheet cell where time is entered. The NBI_PROJ_RES_RATES_AND_COSTS table does not contain a rate for the resulting whole assignment and that is why the $1 rate is applied.
The RME job will update the NBI_PROJ_RES_RATES_AND_COSTS table so a rate exists for calculating the whole assignment.
The Posting Repair and Actual Cost Curve Regeneration job will be needed to rebuild the cost curve. This is hidden by default and is recommended to run it under Support supervision: