Olap values differ from project values

[Willian T. Atherton]

The cost value of a project in PWA shows 84k and when a I see it on Cube
views it shows zero.

I research the problem, using project server database documentation, I did
this:
1. I selected values from MSP_CUBE_ASSN_FACT, column ASSN_COST and it had 0
for the project
2. After, I selected the value from MSP_VIEW_PROJ_ASSN_STD, column
AssignmentCost, and it was zero too. Documentation says
MSP_VIEW_PROJ_ASSN_STD is the origin for values of MSP_CUBE_ASSN_FACT.
3. I imagined that cube views will show only costs where the project has
assignments with costs rates.
4. My projects has costs not associated with resources assignments, we type
costs in project professional.
5. Looking for examples to find out what is happening, I found a project
that doesn’t have resources and the cube view is showing the correct value.
However when I selected values from MSP_VIEW_PROJ_ASSN_STD it was zero too,
but when I did the same in MSP_CUBE_ASSN_FACT the values was there.

So I ask: Where or how the values go from project tables to project server
tables, and from it to views tables, and again, from it to cube tables? How
can I solve my problem?
Regards,

ps.: I have rebuilt the cube many times

Willian Atherton
EPM Consulting Services

 

[Carl Dalton]

My thinking based on some rather large assumptions.............

OLAP contains only timephase data from the plans, so as a nice basic
rule, if it isnt in the Task/Resource usage view in Project, it isnt
going to display.
As the cost entry you are doing is (i presume) in task fields, then it
isnt timephased in any way. you really need to rethink your costing
approach, or take the hit that you cant viably display these costs in
this manner.

point 5 confused me though so maybe i have the wrong end of the stick

you can perform olap extentions... but this is a statement againt base
olap functionality

Carl