Multi-dimensional allocation reference in calc script is locking up EAS

Question

I am trying to draft a calculation script that allocates 1 total number at a point of view that includes "Entity" "Product" and "Customer". This number is entered in at one entity, one customer, and one product. I have loaded allocation weights by entity, customer, and product to be used as the basis for allocating this number down to entity, customer, and product.
We have tried to use the @MDALLOCATE in a script as follows:
SET AGGMISSG ON;
SET UPDATECALC OFF;
SET CACHE HIGH;
SET CALCPARALLEL 3;
FIX("BU Version_1","Actual",&CurrFY,&CurMth)
"PL_AC_4502" = @MDALLOCATE ("PL_DP_1"->"PL_AC_4502", 3, @LEVMBRS ("Prod_Line",0),@LEVMBRS("Product",0),@LEVMBRS("Customer",0),"Abs_4502",,share);
ENDFIX
This locked up the EAS server everytime we tried it.
We decided to add an account to hold a calculated percentage for the allocation and tried the following calc script:
SET CACHE HIGH;
SET UPDATECALC OFF;
SET AGGMISSG ON;
SET CALCPARALLEL 3;
FIX ("FY10","Jan","BU Version_1","Actual",
@RELATIVE ("Entity",0),@RELATIVE ("Product",0), @RELATIVE ("Customer",0))
"Pct_Abs_4502"="Abs_4502",@LEVMBRS("Prod_Line",0),@LEVMBRS("TotCustomer",0),@LEVMBRS("TotProduct",0) / "Abs_4502"->"Prod_Line"->"TotCustomer"->"TotProduct";
ENDFIX
This also locked up the EAS server. Each time, it did not even finish the syntax check.
We have about 70 product numbers and about a dozen customer numbers with numbers in them. Can anyone suggest a modification that will allow either of these calc scripts to avoid locking up the servers?
Much appreciated in advance,
Rob

Answer 1

I just thought I would try to add a little more context to Glenn's response. A calculation on Essbase will step through every single member of every dimension by default. When you mention member "Abs_4502" in a calc script, you are not referencing ONLY "Abs_4502", you are also implying exactly one member from every other dimension in your database (every data value needs a member from every dimension. FIXes are there to limit which members of certain dimensions should be subject to your calculation.
The math you are doing to create a percentage should only reference one value in the numerator, and one value in the denominator. Your denominator is one value, but the numerator is undefined because it is referencing a range of member across three dimensions. I believe I understand what you are attempting here, but it is not necessary. Your FIX already explicitly states that the calculation will work across all the lev0 members of Entity, Product, and Customer. So, you don't need that in the math again. To restate Glenn's attempt...
/* Assumes Prod_Line is "Entity", TotCustomer is "Customer" , and TotProduct is "Product" member */
FIX ("FY10","Jan","BU Version_1","Actual",
@RELATIVE ("Entity",0),@RELATIVE ("Product",0), @RELATIVE ("Customer",0))
"Pct_Abs_4502" = "Abs_4502" / "Abs_4502"->"Prod_Line"->"TotCustomer"->"TotProduct";
ENDFIX
The very first calculation of this calc script is working on the first lev0 relative of "Entity", the first lev0 relative of "Product", and the first lev0 relative of "Customer", and divides the value in that intersection with the value at the "Prod_Line", "TotCustomer", and "TotProduct" intersection....which should be percentage (albeit probably very small...I'd warn against any rounding attempts). The fix then steps one by one through each of the lev0 members and does the same math.
You could step this up and go across all months in the FIX too, and it will step through all months, and calculate the percentages within each month.
Hopefully that helps a little.