SET RUNTIMESUBVARS - my favorite new feature in 11.1.2.3

Question

Hi there,
I must say it!
My favorite new feature in 11.1.2.3: SET RUNTIMESUBVARS see here:
http://docs.oracle.com/cd/E40248_01/epm.1112/essbase_tech_ref/frameset.htm?set_runtimesubvars.html
No longer the need in a MaxL scipt to create and/or set server variables first to be used in calculation (csc) and no need to delete or reset or to tidy up them.
(And no more (these senseless) error messages in MaxL protokoll saying that a variable already exists)
It is much leaner and cleaner now.
Thats pretty cool! You should take a look...
Thank to the dev team and best Regards
Andre
PS: see also here:
https://blogs.oracle.com/proactivesupportEPM/entry/epm_11_1_2_31?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+orana+%28OraNA%29
Edited by: andreml on May 4, 2013 1:25 PM

Answer 1

I have often found that the pleasure related to the anticipation of an event or thing is often greater than the actual act or thing. We anticipate that it is gonna work. However here is the reality (or I think it is)
FIX(Jan,Sales,"100-10",@RELATIVE(Market,0))
     "Actual"(
        IF(@ISUDA(Market,"Major Market"))
                    @CREATEBLOCK (@UDA(Market,"Major Market"));
        100;
        ENDIF
ENDFIXI don't see it working. Techref says use @CREATEBLOCK under a FIX (If you use it without opening a block you get this error "Error: 1012000 Invalid Syntax - Not a CALC command [@CREATEBLOCK]")
SET RUNTIMESUBVARS works if you can assign a value to the variable.
SET RUNTIMESUBVARS
   myMarket ="New York";
   salesNum = 120;
   pointD ="Actual"->"Sales";
FIX(Jan,&myMarket)
     Actual(
          &pointD=&salesNum;
ENDFIXHowever if you use the prompt string (I'm not sure where the prompt will appear (Tech Ref says it is calc script, so I'm assuming that when we validate it should prompt for input)
SET RUNTIMESUBVARS
   myMarket <RTSV_HINT>myMarket: Input the value as a string, such as "New York"</RTSV_HINT>;
   salesNum <RTSV_HINT>salesNum: Input the value as an integer, such as 100</RTSV_HINT>;
   pointD <RTSV_HINT>pointD: Input the value as a member name or a member combination, such as "Actual"->"Sales"</RTSV_HINT>;
FIX(Jan,&myMarket)
     Actual(
          &pointD=&salesNum;
ENDFIXI think we've to wait for more inputs on these.
Regards
Celvin