When trying to 'Populate from Investment Team' or 'Populate from Task Assignments' on a financial cost plan, the following error is displayed:
REVMGR-20728: Rates and Costs are both missing for one or more roles/resources
The cost plan cannot be created as there is no matching row to fully populate the cost plan.
All Clarity versions
Step through the following sequential steps. At the end of each step, try the cost plan population to see if the issue is resolved.
If the error persists, proceed to the next step.
1. Is there a rate matrix defined to associate the labor type that exists on the project team?
Go to the Project > Settings > Financial page
The matrix can be set at the project or entity level.
Check that there is a rate matrix defined for the labor types used on the project.
If it is not set, confirm if it is set on the Administration > Finance > Setup > Entity page
2. Does the rate matrix satisfy the project team?
Go to the Project > Team page.
Click 'Show All' to display all labor and non-labor resources.
Take note of the resource/roles that appear on this list page.
3. Does the rate matrix satisfy the project date range?
Go to the Project > Properties page
Take note of the project start and finish dates, as this will be used to obtain rates in the rate matrix.
The cost plan population takes the whole project date range, not just the cost plan dates. The auto-populate uses the investment start and finish dates to determine active fiscal time periods defined on the associated entity. All fiscal time periods are populated ignoring the freeze date defined in the entity plan defaults.
4. Go to the Administration > Finance > Manage Matrix page.
Check if that there is a row that satisfies both
a. the project date range and
b. the configured columns in the rate matrix.
If there is not, create a 'catch-all' row for testing purposes and try to populate the cost plan.
Click 'New' and enter the all-inclusive date range with asterisks (*) for a all columns. Click Save.
If the error no longer appears, either the configured column and/or the date range in the rate matrix did not previously satisfy the rate association.