Conditional logic execution

Question

Hi folks,
I'm pretty sure that, strictly speaking, this isn't possible, but I'm hoping someone has found a workaround.
I want to run logic on a set of data ONLY if the dimension members used contain certain flags (for example, only run logic when the CATEGORY.ID property is "PLAN2").
Sounds easy enough, but when the *WHEN / *IS statement hits a value that is TRUE, I want to trigger another script, rather than a simple *REC statement.
Does anyone know a way to do this? We are using BPC MS version 7 sp7.
Thanks,
Jason

Answer 1

You can try using the *TEST_WHEN command and also some *INCLUDE command for what you are trying to do:
The instruction TEST_WHEN
Sometimes it may happen that a condition could be tested only once, because such condition is not dependent on the records being scanned. For example one might want to test that in the selected set of members for a given dimension there is a specific keyword or that a certain cell of the cube has a specific value. Instead of applying the condition to the entire set or records to scan, the condition may be evaluated before the WHEN / ENDWHEN loop, with the following instruction:
*TEST_WHEN( )
The is a string that the logic engine will pass to VB script for evaluation. If the returned value is TRUE the subsequent WHEN / ENDWHEN loop will be processed. Otherwise the entire loop will be skipped.
Example:
// skip the loop if Budget is not among the passed categories
*TEST_WHEN(instr("%CATEGORY_SET%","BUDGET")>0)
*WHEN *
//u2026..
*ENDWHEN
*GO
// skip the loop if account FLAG is zero for a certain time,intco combination
*TEST_WHEN(GET(ACCOUNT="FLAG",INTCO="NON_INTERCO",TIME="2004.JAN")<>0)
*WHEN *
//u2026..
*ENDWHEN
As shown in the above example, the instruction supports the use of the %_SET% keyword. It also supports the GET instruction, to retrieve a value from the recordset. When one or more GET instructions are used in the evaluation of the condition, it must be remembered that all required dimensions must be specified. The non specified dimensions will default to the values they have in the first record of the source record set. In other words, the user can only omit dimensions that do not vary in the recordset being scanned.
Another syntax supported anywhere in this instruction is the FLD( ) keyword. Here is a valid example:
*CALC_EACH_PERIOD                         // handle periods one by one
*XDIM_MEMBERSET TIME=PRIOR, %TIME_SET%     // include prior period to selected dates
// This will test that the evaluated period is not the prior period
*TEST_WHEN(instr("%TIME_SET%","FLD(TIME.ID)")>0)
*WHENu2026.
The TEST_WHEN instruction is specific to the current GO section. If no GO section is specified, it is specific to the current COMMIT section.