Skip to Content
author's profile photo Former Member
Former Member

Remote Debugging PROCESS DOCUMENT (or Workflow)

Hi everybody,

is it possible to set an external Breakpoint for the Debugging of Worksflows or any processes that are execute via the User WF-Batch?

If yes, how can I achieve that; what do I have to do?

I found know, that in ABAP-EDITOR -> Utilities -> Settings -> ABAP Editor -> Debugging

--> hier I can set a user.

But when I try to set WF-Batch, i get an error:

Debugging is only possible with a "Dialog" type user

Regards

Mario

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Dec 05, 2014 at 10:37 AM

    Hi all,

    to make it easier:

    The User WF-BATCH runs an ABAP. It is not possible to change this.

    How can I set a breakpoint, when user WF-Batch processes this ABAP.

    Thx, Regards

    Mario

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Rob Dielemans

      Hi Rob,

      unfortunatelly you did not take into consideration that some WF steps insert, update or delete the masterdata.

      So it is not so easy to repeat steps in dialog. I first have to fix the masterdata.

      Many thaks for your help.

      Regards Mario

  • Posted on Dec 05, 2014 at 09:53 AM

    Hi Mario,

    You should check the dedicated Workflow forum for answers to your question.

    Usually workflow debugging consists of first trying to isolate the executed code.

    For that you use the workflow log to find out the content of the parameters. Then the workflow step and the task definition to see how this data is eventually passed on to the method (sometimes literals are passed to a task/method).

    Then you instantiate the class/business object, fill in the importing parameters and you can debug it from there.

    In rare cases this is not sufficient and you want to debug it as close as possible as it is in runtime.

    For this case you have to temporarily change the user WF-BATCH to dialog, place your external breakpoint and then debug it. Take extreme caution when you have to do this on production. The sizing of a system user can be very differently from a dialog user and you can create bottle-necks this way.

    So only use that technique as a last resort and preferrably only on quality/dev.

    Kind regards, Rob Dielemans

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.