Hi to All P6 users,
I found discrepancies in Budgeted Total Cost on activity column VS the Cumulative Budgeted Total Cost at the end of the project on the activity usage spreadsheet. Please be reminded to review your schedule & reports.
In the image above the Budgeted Total Cost is 502,798,675 but at the end of the Schedule on the 36th month, the Cumulative Budgeted Total Cost is 502,798,520.
Anyone had encounter the same problem?
What was your solution to it?
Regards,
Hi,
Thanks for the replies.
Dario,
The conversion is 1=1 as the Default US$ was replaced with the Local Currency.
Anning,
Your suggestion to copy Budget Cost into at Completion Cost is practical.
I suspect the reason behind was due to the resource curves assigned or some of the resource rates effectivity are during the duration of the project.
Thanks,
Try this exercise to solve the problem. In P6, include the Budgeted Total Costs, and At Completion Costs in the column display. You will notice that the costs are not exactly the same, even in some 100% complete items. If you want to really correct this either:
a) manually correct each item or;
b) export the file, copy budget cost to at completion cost and import the file again; or
c) do it in global change, but you will need a temporary user defined field.;
I recommend a) if not much activities or b) for large networks.
Hi,
check that the default currency is with conversion rate 1,000 and have a look at the db tables to see if that's really the currency used to store cost data.
Dario.
Hi,
The default currency is the same as the displayed currency.
Regards,
Hi,
my understanding is that this is due to the currency setting in your database. You are probably storing cost data into the db with a base currency other than the one you use to display costs. The difference between the two Budgeted Total Costs is due to the fact that one is calculated performing the sum with the base currency and then convertig to the display currency, the other one is calculated converting the single period costs, and then adding them. It seems in fact that numeric data is stored in Primavera with few decimals, and truncation causes many problems.
You will probably see this weird behaviour fixed if you have the db store data with the matching currency.
Dario
Raymund -
I think its pretty common knowledge that P6 is not good at handling costs. Everyone I know that is using P6 for scheduling, keeps their cost data separate, usually in Excel.
- Lawrence
To all P6 users,
Please be reminded to verify your schedule and reports as happened above.
Do not always rely on what is generated by the software.
Keep a look on what is shown on the screen.