cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

BPC 10.1 on Hana: Script Logic - SELECT error "CALC=Y"

Former Member
0 Likes
706

Hello,

After the BPC update from v. 10.0 to v. 10.1 on HANA we noticed that the BPC Script Logic function SELECT has a different behaviour.

In BPC 10.0 we have Script Logics with SELECT and condition "different from":

*SELECT(%VAR%,ID, DIM, "[PROP]<>X")

where "PROP" is a dimension's property for which we evalueted with "X" some base members.

In BPC 10.0 it works properly.

After the migration to BPC 10.1 on HANA the same script logic gives the following error:

RUN_LOGIC:"DIM" in "VAL" CALC=Y

This happen in different Script Logics but only for some dimensions and we can't understand the reason.

As the property CALC determines whether the value of the member should be calculated (i.e. nodes) or not, It seems that the SELECT doesn't automatically exclude the calculated members.

For the dimensions that give this issue we can solve adding the condition CALC=N:

*SELECT(%VAR%,ID, DIM, "[PROP]<>X AND CALC=N")

or evaluating the property with "X" for the calculated members.

However we would like to undestand the reason why it happen only for some dimension and not for all.

Thanks in advance for any help you are able to provide.

Daniela

Accepted Solutions (1)

Accepted Solutions (1)

former_member186338
Active Contributor
0 Likes

Please show the full test script, generating the error! Simple test case!

P.S. To my mind the error is generated not by SELECT statement...

Former Member
0 Likes

The script logic simple test case is:

Partly commenting the script logic, we receive a similar error for the dimension T_DOC but not for the dimensions ACCOUNT and M_TYPE.

Thank you,

Daniela

former_member186338
Active Contributor
0 Likes

I think the reason of this error is usage of XDIM_MEMBERSET with not base member...

In general it's useless to scope not base members because WHEN/ENDWHEN loop only base members!

Then simply add " AND CALC=N" and everything will be fine. Just a minor issue, in previous version not base members were ignored.

Vadim

Former Member
0 Likes

Ok, thanks! We'll do it.

Just I do not undestand why in same cases the script works as well.

Regards,

Daniela

former_member186338
Active Contributor
0 Likes

No magic!

Please show the working script!

May be the result of SELECT has no parents...

former_member186338
Active Contributor
0 Likes

P.S. To test script please use transaction UJKT:

Try

*SELECT(%ACCT%,ID,ACCOUNT,[P_BLOCK]<>X)

*XDIM_MEMBERSET ACCOUNT=%ACCT%

What do you have in LGX?

Former Member
0 Likes

Thanks for the suggestion to use UJKT!

At the end, as expected the issue is on all dimensions and we will solve it adding the condition CALC=N.

Best regards,

Daniela

Answers (0)