You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
Are LINE_EXISTS suggestions correct for non-EQ search keys in READ or LOOP?
As far as I know, I can only specify keys in LINE_EXISTS() via EQ
Regards,
Günter
Example:
clear r_yes.
loop at gritab transporting no fields where ico_towork = abap_true
and ico_created <> zcl_zhplm_utils=>c_ico_created_complete.
r_yes = abap_true.
exit.
endloop.
The text was updated successfully, but these errors were encountered:
Yeah, this is a bug (the Cloud version of this check already doesn't have that anymore).
This implementation of the check does some analysis for LOOPs but there is no checking whether the condition is actually valid as a table expression (and hence could be transformed into line_exists).
Hello,
Are LINE_EXISTS suggestions correct for non-EQ search keys in READ or LOOP?
As far as I know, I can only specify keys in LINE_EXISTS() via EQ
Regards,
Günter
Example:
clear r_yes.
loop at gritab transporting no fields where ico_towork = abap_true
and ico_created <> zcl_zhplm_utils=>c_ico_created_complete.
r_yes = abap_true.
exit.
endloop.
The text was updated successfully, but these errors were encountered: