Interesting observation. Just out of curiosity, what Rev are you working on?
In our scenario, the calculated column was in the attribute view itself. If you still have that test model handy, can you perform an IF statement on the dimension instead and see what the VizPlan spits out?
I did receive a response from SAP about the problem query. The analysis correlates with my findings as well, but they also offered a solution, so thought I would share. The developer had put the calculated column in the attribute view and it used the now() expression as discussed below.
>>
Regarding the high CPU Utilization, it is due the now() function in
the complex expression in the calculated column FPY_FLG. the function
now() if repeatedly call during runtime whereas it should be replace
by the correct value during compile phase.
So the workaround would be to create a mandatory input parameter
with default value as now() then use this input parameter in place of
now() in the FPY_FLG calculate column.
<<
As a side note and related to tuning explorer, we are having fun with resultcache testing over in this thread.
Regards,
Justin