Cube Calculations To Date behaviour
2 posters
Page 1 of 1
Cube Calculations To Date behaviour
The cube developed is for an origanization that manages and conducts huge projects.
All project calculations are based on the life of a project, in other words beginning of time to date.
In other words:
Revenue Recognition to Date = Actual Cost to Date / Budget Cost to Date * Budget Revenue To Date
Revenue Recognition for Current Period =
([Time].[Year - Month].CurrentMember,[Measures].[Revenue Recognition to Date])-
([Year - Month].PrevMember,[Measures].[Revenue Recognition to Date])
This gives current period accurately, but when a user selects inidividual periods, say January 2012, March 2012, April 2012, the sum (Grand Total) of the report does not properly add up. It still reflects the total as the "To Date" value.
Any ideas how this behaviour can be changed?
All project calculations are based on the life of a project, in other words beginning of time to date.
In other words:
Revenue Recognition to Date = Actual Cost to Date / Budget Cost to Date * Budget Revenue To Date
Revenue Recognition for Current Period =
([Time].[Year - Month].CurrentMember,[Measures].[Revenue Recognition to Date])-
([Year - Month].PrevMember,[Measures].[Revenue Recognition to Date])
This gives current period accurately, but when a user selects inidividual periods, say January 2012, March 2012, April 2012, the sum (Grand Total) of the report does not properly add up. It still reflects the total as the "To Date" value.
Any ideas how this behaviour can be changed?
reportshack- Posts : 2
Join date : 2011-10-06
Re: Cube Calculations To Date behaviour
How have you defined [Measures].[Revenue Recognition to Date] ?
Re: Cube Calculations To Date behaviour
I actually show it in the post:
Revenue Recognition to Date = Actual Cost to Date / Budget Cost to Date * Budget Revenue To Date
mdx = [Measures].[Actual Cost to Date /([Measures].[Budget Cost to Date] * [Measures].[Budget Revenue To Date].
the problem is not the accuracy of the calculation or even the inidividual months, it is how it behaves when only certain months are selected.
If if every month is shown, it shows an accurate grand total, if only some months are selected, it still shows the same grand total as that of all the months added together.
Revenue Recognition to Date = Actual Cost to Date / Budget Cost to Date * Budget Revenue To Date
mdx = [Measures].[Actual Cost to Date /([Measures].[Budget Cost to Date] * [Measures].[Budget Revenue To Date].
the problem is not the accuracy of the calculation or even the inidividual months, it is how it behaves when only certain months are selected.
If if every month is shown, it shows an accurate grand total, if only some months are selected, it still shows the same grand total as that of all the months added together.
reportshack- Posts : 2
Join date : 2011-10-06
Similar topics
» Adding a fact table with start date and end date to a (SSAS) multidimensional cube
» SSAS Cube - zero downtime even during cube processing
» Simple Calculations
» SSAS, hiding Measures behind Calculations
» Date Dimension: Representing partial dates/Imputing date values
» SSAS Cube - zero downtime even during cube processing
» Simple Calculations
» SSAS, hiding Measures behind Calculations
» Date Dimension: Representing partial dates/Imputing date values
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum