Accounts Dimension Hierarchy...Problems Please help

Question

Hi All,Iam designing a P&L Cube & a Balance sheet Cube.I have a specific problem---Please read below1. In JDE, Account number is the combination of the BU , Object Account & Sub Account.Seems the unique number of accounts (with Account Numbers) are 1.5 million.Upto (Level 6 in JDE) , Accounts are standard across the Companies or business unitsOne company has several business units.Building hierarchy till level 6(level 6 means level 6 in JDE) may not be a problem in Essbase.The real challenge is after level 6,level 7 level 8 level 9 accounts are there & these are not standard for all business units. They differ for each business unit.For example,Bank Account ( suppose at level 6) for a BU 41100000 , BU 41000000 , BU 40000000Bankone (level 7          ) for the 4110000053 bank (level 7          ) for the 41100000Firstunion ( level 7)          for 41000000FleetBank (level 7)          for 41000000FleetBank (level 7) for 40000000So in this case how to achieve uniqueness vis-a-vis Essbase.Answer is : Account number which is the combination of the BU , object account & Sub accountBut what worries me is if we have 20,000 (suppose) Business units & we have level 7 accounts on an average 10 per BU, then which means we have to build 20,000 * 10 which is equivalent to 200,000.... if we think of level 8 , same logic continues....so when we build hierarchy.... for 1.5 million unique records we might end up having atleast 500,000 stored members, I think.My solution to this was not to go to level of detail after 6th level in JDE.What is your opinion?Did anyone come across such a situation. The Business people want to see the level of detail till level 9 of JDE & report also on that...What is the solution for this kind of problem??Notes : Levels in JDE are equivalent to generations in Essbase

Answer 1

I hope I'm understanding you correctlyWhy don't you have Account and BU in seperate dimensions? You can train users to look for their account and BU in seperate dimensions orOnly create accounts that have values. In other words don't create every possible account BU combination in essbase. Make sure your load file for Essbase doesn't contain zero value and dimbuild from your data file.