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
we did a mass cleaning of our abapGit files with the command line.
We received a lot of parsing errors on files that contains dynpro logic.
Here is an example from the SAP Standard Function Group 0TZN Screen 500 (not part of our abapGit files ). I deactived all rules for testing and used the ABAP Release 750.
PROCESSBEFOREOUTPUT.
CALLSUBSCREEN NAVIGATION INCLUDING VIM_SBSCR_PROG VIM_SBSCR_DNUM.
MODULE LISTE_INITIALISIEREN.
LOOP ATEXTRACT WITHCONTROL
TCTRL_V_TTZZ CURSOR NEXTLINE.
MODULE LISTE_SHOW_LISTE.
ENDLOOP.
*PROCESSAFTERINPUT.
MODULE LISTE_EXIT_COMMAND ATEXIT-COMMAND.
MODULE LISTE_BEFORE_LOOP.
LOOP ATEXTRACT.
MODULE LISTE_INIT_WORKAREA.
CHAIN.
FIELD V_TTZZ-FLAGACTIVE.
FIELD V_TTZZ-DSTRULE.
FIELD V_TTZZ-ZONERULE.
FIELD V_TTZZ-DESCRIPT.
FIELD V_TTZZ-TZONE.
MODULE SET_UPDATE_FLAG ON CHAIN-REQUEST.
MODULE COMPLETE_V_TTZZ ON CHAIN-REQUEST.
ENDCHAIN.
FIELD VIM_MARKED MODULE LISTE_MARK_CHECKBOX.
CHAIN.
FIELD V_TTZZ-TZONE.
MODULE LISTE_UPDATE_LISTE.
ENDCHAIN.
ENDLOOP.
CALLSUBSCREEN NAVIGATION.
MODULE LISTE_AFTER_LOOP.
thanks for reporting this! Such processing blocks of dynpro flow logic are not supported by ABAP cleaner, so for the next ABAP cleaner release, I now improved the parser to immediately say "This language is not supported by ABAP cleaner" if code starts with PROCESS BEFORE OUTPUT, PROCESS AFTER INPUT etc. It would probably be best if you could exclude these objects from your mass cleaning runs.
Activity
fmabap commentedon Aug 7, 2025
If there is no loop at the dynpro, then following error occurs (looks like the same error).
jmgrassau commentedon Aug 11, 2025
Hi Frank,
thanks for reporting this! Such processing blocks of dynpro flow logic are not supported by ABAP cleaner, so for the next ABAP cleaner release, I now improved the parser to immediately say "This language is not supported by ABAP cleaner" if code starts with PROCESS BEFORE OUTPUT, PROCESS AFTER INPUT etc. It would probably be best if you could exclude these objects from your mass cleaning runs.
Kind regards,
Jörg-Michael
fix error message for dynpro flow logic processing blocks (SAP#432)
fix error message for dynpro flow logic processing blocks (#432)
jmgrassau commentedon Sep 11, 2025
Hi Frank,
the handling of these cases should now be improved with version 1.21.3, which was just released – thanks again for reporting this!
Kind regards,
Jörg-Michael