Business rule optimization

Question

Hi all,
I have the following business rule:
FIX([TargetYr],[TargetVersion],"0000",@LDESCENDANTS([AllocAccount],0))
FIX([SourceMonth])
[TargetScenario] = ([SourceYr]->[SourceScenario]->[SourceVersion]->"0000")/([SourceYr]->[SourceScenario]->[SourceVersion]->"0000"->[AllocAccount]) * [AllocAccount];
ENDFIX;
FIX(@LIST([EndMonth]:[SourceMonth]))
[TargetScenario] = ([SourceMonth]->[TargetScenario])/([SourceMonth]->[SourceYr]->[SourceScenario]->[SourceVersion]->"0000") * ([SourceYr]->[SourceScenario]->[SourceVersion]->"0000");
ENDFIX;
ENDFIX;
It's a two-part script used for forecasting balance sheet accounts from a top-down perspective. The first part takes a balance in (say) June for a parent account, then allocates that amount down through its children accounts in June. The second part then takes the June balances for all the level 0 accounts and allocates them backwards through each month based on a source set of data, so that you how have a full year's worth of forecasted balances.
My questions are twofold:
1) Is there a way to change this rule so that I can enter a number of parent accounts in AllocAccount instead of just one at a time? Right now it only works if one parent is entered.
2) Is there a way to optimize this? It seems to take forever to run. I'm new to this so I doubt I'm doing this most efficiently.
Thanks for your time!

Answer 1

1) Is there a way to change this rule so that I can enter a number of parent accounts in AllocAccount instead of just one at a time? Right now it only works if one parent is entered.There's no reason you can't have multiple @LDESCENDANTS in your FIX. May I suggest that you tag these upper level members with a UDA and then FIX on those? Something like a @LDESCENDANTS(@UDA("Account", "ToBeAlloced")) should do it. You will need to maintain the outline with these hierarchies but that is likely (?) less painful than doing it in code.
2) Is there a way to optimize this? It seems to take forever to run. I'm new to this so I doubt I'm doing this most efficiently.Can you do this at level zero for your other dimensions/specific Scenarios and then agg up the results? If you have other dimensions, you are doing this allocation for all levels -- you can probably get away with level 0 of those other dims.
Regards,
Cameron Lackpour