Account Dimension not showing all members in the cube in Analysis Services

Question

Hi,        
         In SAP - BPC 5.1 after processing account dimension all the members are created under account dimension in analysis services but the same cannot be found in the data cube. Hence the reports generated through SAP - BPC is not showing all the members.
         The issue looks very strange as we can see the members getting created but the same is not getting populated in the cubes. I am not able to visualize what exacly the issue is? Is it with the application or with the analysis services?
Thanks
Sharath

Answer 1

Your sixth sense is correct, there is definitely support in MSAS and BPC 5.1 for multiple hierarchies in the account dimension.
I'm also referring to parentH1 and parentH2, but perhaps we're still speaking of different things.
In the past, I faced a very similar problem as you, and the root cause was because I had one member, let's call it FancyParent, which, in H1, had children Child1 and Child2.
But in H2 it had children Child1, Child2 and Child3. I forget now if that was how I wanted the setup to be, or if it was a mistake on my part, but either way, MSAS doesn't allow this. The admin consol didn't complain when processing the dimension -- this was in Outlooksoft 5.0; perhaps validation has improved now.
But the cube was completely unworkable. Certain things were calculating correctly, but everything in the account dimension in the area around FancyParent (above and below it, in both hierarchies) was quite unpredictable.
By disabling first one, and then the other, of the two hierarchies, and disabling blocks of accounts, I was eventually able to pinpoint the problem. But it took days to figure out what was the problem. (The account dimension had 2500 members and 4 hierarchies, and it was not a pretty sight.)
A parent must have the same definition of children in all hierarchies. It can't, as another example, have children in H1, and be a base member in H2. Each member can have different parents in the two hierarchies, but must always have the same children in both.
To work around this problem, I had to create two separate accounts NetIncomeH1 and NetIncomeH2 (and PretaxIncomeH1, PretaxIncomH2, etc. all the way down to the point where they branched off), to get the two separate aggregations of the P&L in the two hierarchies. Once I did that, it made sense to me why, but I also swore off on frivolous extra hierarchies ever again.