Maintain Cost Rates in cProjects - Possible Performance issues ?

[Former Member]

Hello experts,

in cProjects Cost rates can be maintained in 2 ways:

1. in cProjects configuraion you can maintain the rate / Cost rate

2. in ECC - in transaction KP26 - if no amount is maintained in cProjects config.

we have a dillema which method to choose.

1. If we choose #1 - we will end potentially with hundreds of thousands of records over the years, as we have 50 rates for 500 Org units (cost centres). The rates change yearly, so we will have for each year 25 thousand records. Is this going to impact cProjects performance?

2. if we chose # 2 we will have one evergreen record for each Org Unit (cost centre) and the rate will yearly change in KP26 in ECC. This has the disadvantage that the rate maintained in KP26 does not show up in cProjects on the front end in the Cost ' Revenue Rate field. So the project managers will plan blindly not knowing the hourly rate they are using to plan the project.

Although option#1 requires a lot of maintenance, it displays the hourly rates on the front screen in cProjects. Due to the high volume of data we have second thoughts though, regarding performace which is slacking anyway.

Any advice based on your experience with this process will be much appreciated.

Regards,

LT

[Former Member]

Hello,

i'm also interested in the answer to this question.

Thanks.