Optimization

Question

Hi All,
I Have got the following Dimensions in Essbase. I am using Essbase 9.3.1
1. Accounts
2. Period
3. Year
4. Activity
5. Version
6. Currency
7. Company
8.Asset Type
9. Cost Centre
10.Invest_Char
11. Location
Of the above only Accounts and Period are Dense and the rest Sparse.
Following is the code for making the balance in a particular month equal to zero.
This Script takes more that 14 hours to run.
SET UPDATECALC OFF;
SET CACHE HIGH;
SET CREATENONMISSINGBLK ON;
FIX("Test","HSP_InputValue","SCNZ",@IDESCENDANTS("Location",0),@IDESCENDANTS(Activity,0),@IDESCENDANTS("Cost-Center",0),@IDESCENDANTS("Asset-Type",0),@IDESCENDANTS("Invest-Char",0))
FIX(&currfcst,&startyear)
FIX("PR_5163")
&currmth = 0;
ENDFIX
ENDFIX
ENDFIX;
Explaination to Above Code Terms
Test is Version
SCNZ is Location
&currfcst could be any Scenario
&startyear could be any year say FY10.
"PR_5163" is account code which needs to be zeroed out for given month.
&currmth = Month
Any inputs to reduce the run time will be thankful.
Once again thanks in advance.
BK

Answer 1

Beyond the different technique suggestions that have been outlined in other posts, I have to ask why you are setting the current month to zero. Block creation? Clearing out data values?
Block creation can always be handled at the time of calculation. CLEARDATA can wipe out data and sometimes blocks -- watch out on that latter one. I got severely burned on that to the point of blogging about my pain. CLEARBLOCK for sure can wipe out blocks and data. http://camerons-blog-for-essbase-hackers.blogspot.com/2011/01/stupid-programming-tricks-6_03.html
Remember, you are creating blocks for every potential combination of dimensions (I am going to guess that you are at least going to rewrite this as @RELATIVE instead of @IDESCENDANTS unless you well and truly want to calculate this for every level) and the data that goes into the calc almost certainly doesn't exist at all of the combinations you have touched. You end up creating blocks where they don't need to be, slowing down your calc, making your database bigger than it needs be, and generally threatening world peace. Okay, the last one you're not doing, but you get the idea.
Why not describe what you need to calc, and where, and then try different techniques to create blocks, e.g., DATACOPY, CREATENONMISSINGBLKS, CREATEBLOCKSONEQ, assign to sparse, cross-dim on the left hand of the equal sign, XWRITE with LOOPBACK, etc.
Regards,
Cameron Lackpour
Edited by: CL on Feb 6, 2011 9:12 AM
Whoops -- you can't do the XWRITE because you're on 9.3.1, but the rest of the techniques are fine.