topic How to debug migo transaction? in Application Development and Automation Discussions

How to debug migo transaction?

Former Member — Mon, 14 Oct 2013 20:33:50 GMT

Hello,

I have a Z program linked to migo transaction, I want to debug my program when migo call my program, I did set a break point, but migo never call my prgogram

Thanks

Re: How to debug migo transaction?

former_member192854 — Mon, 14 Oct 2013 21:42:28 GMT

Hi, before performing you 'Z' transaction, did you checked your settings:

SE38 > menu Utilities > Settings > tab ABAP Editor > tab Debugging

Make sure the user - or the user you're testing with - is filled out in 'Users'

And 'X' Session breakpoint active immediatly also comes in handy.

Another way, is to use transaction SE93 put in your transaction, type '/h' in the transactionbar, press enter, and test (F8).

Best,

Sander

Re: How to debug migo transaction?

Former Member — Tue, 15 Oct 2013 11:32:14 GMT

Hy Luis,

Did you tried the update debugging? some how your ZPROGRAM might be called in update task.

Try the following:

Put break points on the first executable line in you ZREPORT.

Go to MIGO

Press the debugging configurations:

Mark the check box "Update debuging" and save the options:

Make sure before doing F8, you have more sessions available. If you are using 6 sap windows the update debugging won't work.

A new debbuger window will appear, and you can press F8 to see if it stops on your ZREPORT.

NOTE: This session is triggered after commit work statement. All the function modules called with the addition "IN UPDATE TASK" will be called successively in the order they were submited.

Other ways to do this:

Is see you program's where used list and put breakpoints in every place.
Put breakpoints at statements "Submit" and "call transaction" during the MIGO online debugging and Update debugging. (press F9 after start the debugging and insert the mentioned values).

Hope it helps.

Best regards,

José Vília