This is second post dealing with the Variable limitations in Calc manager.
I had to create a rule with limitations on variables that are used in the rule.
I’m using Sample Application to describe the issue.
I’m using Sample Application to describe the issue.
Two variables are created, one to limit “Account” (@CHILDREN(CapitalExpenditures))
and another one to limit “Segments” (@ATTRIBUTE(“US_Electronics”))
This rule was running fine for couple of days and one day when I tried to run the rule, it gave me an error saying “One or more runtime prompt values are invalid.”.
However all the runtime values were valid ones and I opened up the “Select members” and found that the limits on the variable is removed. (I can see the entire “Account” and “Segments” hierarchy)
I checked Variable Designer to see whether someone removed the limits. But the limits were intact.
We had to search a lot to find a solution for this (restarting services,……..), atlast my friend and colleague Lingaraj found out the solution.
It was to unnlock the outline. (Yes someone locked the outline to search for some missing members).
I’ve checked this in Classic Planning applications and it seems to be working there, but with an EPMA 11.1.2 Planning application it is not. (EPMA 11.1.2.1 is also working fine)
Even though it is a good practice to unlock the outline, I’m curious to know whether anyone else has encountered this error.
Hi Celvin,
Are you using Essbase console for the planning rather than EPMA for accounts search?
Worked like a Charm!
Thanks Buddy! You saved me a lot of time!
Mj
Thanks alot it helped us in resolving the issue.
Great, thanks! That helped. I'm working on 11.1.2.1, so it seems to be problem there as well…
Thank you very much for this. We had this exact issue and it drove us crazy because we knew that no one had changed anything — consultant or client. I am personally grateful but you have probably saved hundreds of other people (too shy to comment) many hours of frustration.
Cheers!
@Brian Good to know that it helped.
I was having the exact same issue using @ILSIBLINGS in a ruleset. Would work in one environment, but not the other. The locked outline was the issue. Thank you! Great article.