Lars Hvam

however if the table is deep, then DATA has to be used

plus it seems that sometimes the pragma is placed wrong, it is only valid for CATCH statements(?) ```abap TRY. CALL FUNCTION 'FP_FUNCTION_MODULE_NAME' "#EC NO_HANDLER EXPORTING i_name = co_form_name IMPORTING e_funcname...

LOOP AT li_return INTO l_return. CHECK l_return-type = c_a OR l_return-type = c_e. ... ENDLOOP

add to check 62

```abap LOOP AT ct_valid_materials ASSIGNING FIELD-SYMBOL(). IF -rounding_value = 0. ...something... ENDIF. ENDLOOP. ```

```abap LOOP AT gt_final ASSIGNING . IF -ztext_approved = ' '. ...something... ENDIF. ENDLOOP. ```

oh, didnt test it 😄 I usually just dont do spaces in beginning or end of characters thanks

would be nice

Its all configurable, eg. http://docs.abapopenchecks.org/img/53_conf.png Plus it checks if something like "NEW" or "DATA()" works on the version before reporting to the user to use these constructs. So probably not,...

another example, ```abap loop at lt_table into ls_foo. if ls_foo-start le sy-datum. append ls_foo to lt_result. endif. endloop. ```