Problems with FLAGR, FLAGLH fields of table RSZGLOBV - formula variable

[Former Member]

Hi experts,

I defined formula variable with client exit and added the needed ABAP code to ZXRSRU01. It was working fine until now.

I keep having warning messages

"FLAGLH not correct for variable XXX. Changed from 1 to 0"

"FLAGR not correct for variable XXX. Changed from 1 to 0"

N° message : BRAIN243

Now, my calculation using the variable is not done.

Has anyone faced this problem before?

Thanks

[Former Member · Accepted solution]

Hi,

Just check in your ABAP code, I guess the definition of your variable used for FLAGR & FLAGLH needs to be changed.

I hope it will help.

Thanks,

S

[Former Member]

A solution that worked for me was to edit the variable and save it again.

I do not know if a way exists to re generate all BEX variables rather than doing one by one.

That would probably solve the problem too.

Cheers,

[Former Member]

Hello, All.

Found note for resolution of this issue: 1482843.

Symptom

Formula variables processed by Manual Input / Default Value, Customer Exit

or SAP Exit return the warning messages during query check or generate:

- FLAGLH is not correct for variable XXX... Changed from '1' to '0':

- FLAGR is not correct for variable XXX... Changed from '1' to '0'.

Also, check out relevant note 1091323.

[Former Member]

We are also experiencing this error for our input-ready variables.

I tried re-saving the variable, but the issue persists.

Please share the resolution if you have been able to resolve the issue on your end.

[Former Member]

Hi,

I am facing the same warning message, but the calculation of the variable is done correctly. So it might be the case that you have to check your coding again.

In case you hava a correct coding and want to suppress the warning message you can do it by using transaction RSRT -> Messages ->Suppress Messages -> variables. Here you will find your message number!

The alternative I tried first was to change the corresponding entry in table RSZGLOBV for columns FLAGLH and FLAGR, but unfortunately "0" is not a valid entry.

Best regards

Bjoern

[Former Member]

We are also getting this same warning on a customer exit variable that has existed for a long time. We don't think it is directly related to the code because as a test, we created a new customer exit variable that has no code behind it. We get the same warning even when no code exists. Our warning is only for FLAGR. It says that it has changed from 1 to 0.

Has anyone resolved this issue in the past?

Thanks,

Doug