Skip to content

Parsing Error for Dynpro Logic #432

Closed

Description

@fmabap

Hi,

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.

Image
PROCESS BEFORE OUTPUT.
 CALL SUBSCREEN NAVIGATION INCLUDING VIM_SBSCR_PROG VIM_SBSCR_DNUM.
 MODULE LISTE_INITIALISIEREN.
 LOOP AT EXTRACT WITH CONTROL
 TCTRL_V_TTZZ                         CURSOR NEXTLINE.
   MODULE LISTE_SHOW_LISTE.
 ENDLOOP.
*
PROCESS AFTER INPUT.
 MODULE LISTE_EXIT_COMMAND AT EXIT-COMMAND.
 MODULE LISTE_BEFORE_LOOP.
 LOOP AT EXTRACT.
   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.
 CALL SUBSCREEN NAVIGATION.
 MODULE LISTE_AFTER_LOOP.

Activity

  1. fmabap commented on Aug 7, 2025

    @fmabap
    Author

    If there is no loop at the dynpro, then following error occurs (looks like the same error).

    Image
  2. self-assigned this
    on Aug 11, 2025
  3. jmgrassau commented on Aug 11, 2025

    @jmgrassau
    Member

    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

  4. jmgrassau commented on Sep 11, 2025

    @jmgrassau
    Member

    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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions