Some configurations of a Rate Matrix will cause many rows to be generated in the NBI_PROJ_RES_RATES_AND_COSTS table that appear redundant because the rates are correct for the date ranges, but the extra rows in the NBI table is caused by the job taking into consideration the non-matching rows ; yet still gives the correct rate.
This issue was reported by a customer with a matrix configured with 'Resource Class', 'Transaction Classs' and 'Resource Role' columns configured. I tested the issue with that configuration and also with only 2 columns 'Resource Class' and 'Transaction Class' and is able to generate similar results. I also did another test only using 'Resource' as a matrix column and it is not reproduce - most likely because Resource is a column in the NBI table and is not varied.
There is an impact to performance, the amount of database table space and the use of Microsoft Project.
In MSP, select a resource and examine the Cost Table to view the costs associated with this resource on this specific project. The MSP Resource Cost Table is not correct or it is missing the correct cost rate.
MSP has a limitation of 25 rows in the Project, Resource, Cost table. When the CA PPM application loads the project data and the associated costs from the Rate Matrix Extraction table, only 25 rows from the NBI_PROJ_RES_RATES_AND_COSTS table (where TASK_ID = '-1' can be loaded.
After examining the customer data and also replicating the issue, it can be reproduced, where not all the costs are pulled into MSP due to this configuration.
Steps to Reproduce:
See document attachment for full steps and pictures of a specific use-case example.
Applies to all supported PAS environments for specified releases.
Caused by CLRT-77238
The job is trying to insert transition dates based on the rows in the matrix even though the rows may not have a matching resource class ; and thus it ends up that the correct rate is retrieved and inserted into the table, but the result is many rows that have the different transition dates.
Resolved in CA PPM 14.3
The issue is resolved with an update to the job query that inserts the -1 Task records into the table ; it performs a grouping for rows that have the same rates for adjacent date ranges.
None. Alternatively you can change the Matrix Configuration to remove the Resource Class or align the dates on the rows in the matrix to help reduce the number of rows generated in the NBI table. The Financial Administrator could reduce the number of rows generated in the NBI table by aligning the date ranges of all rows in the matrix. This idea may not be feasible for all customers due to their business data needs. There could be reasons for having different, overlapping date ranges for the other rows in the matrix that do not have any use for the specific project, resource combination.
Reference CA PPM Resolved Defects Index for CA PPM 14.3