Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

ABAP debugger, stop at pop up

Former Member
0 Likes
2,739

Hi Experts,

Is it possible to view the source code of a standard SAP transaction just after an error pop up message is displayed? In Visual Basic, there is an option F9 to jump to the current source code. Rather than debugging using /H in SAP is there any other option? Whenever a pop up message is displayed, I need to check the source code of the program being called.

Regards,

Sibin

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
1,775

Above approaches will work for a popup screen and not for the information message you may be talking about.

If you are talking about the information/error message you receive, there is no easy way to reach the source code.

1. Note the mesage number, go to SE91 and do a where used.

But again, this may not work always, since a message may be populated dynamically and it wont be traced in where used.

2. You need some patience for this. Whenever you run a transaction, just before the step you get error, start a debugger with /H.

Then navigate to below screen, and give command 'Message'.

You might come across some irrelevant messages, but you will succeed in time.

Hi Experts,

Is it possible to view the source code of a standard SAP transaction just after an error pop up message is displayed? In Visual Basic, there is an option F9 to jump to the current source code. Rather than debugging using /H in SAP is there any other option? Whenever a pop up message is displayed, I need to check the source code of the program being called.

Regards,

Sibin

5 REPLIES 5
Read only

Former Member
0 Likes
1,775

I have the following saved in a .txt file saved on my desktop:

[FUNCTION]

Command=/H

Title=Debugger

Type=SystemCommand

Once you received the popup, drag over the .txt file and execute.  Hope this helps!

Read only

0 Likes
1,775

Dear Scott,

   A good way to debug popup screen,

can you explain me how it exactly works(mechanism) when txt file is drag and drop on to popup screen then after it switched on to debugger ?

Thank you.,

Avirat

Read only

Former Member
0 Likes
1,775

Hi sibin,

     according to scott , this process will help you to debug only pop up screen....... suppose when you create a material through MM01 tcode then a pop up will display...view: basic data 1, basic data2. then you drag your txt.file and drop it on this pop up...........debugging start for this pop up screen.....

hope you understand........

thanks

Sabyasachi

Read only

Former Member
0 Likes
1,776

Above approaches will work for a popup screen and not for the information message you may be talking about.

If you are talking about the information/error message you receive, there is no easy way to reach the source code.

1. Note the mesage number, go to SE91 and do a where used.

But again, this may not work always, since a message may be populated dynamically and it wont be traced in where used.

2. You need some patience for this. Whenever you run a transaction, just before the step you get error, start a debugger with /H.

Then navigate to below screen, and give command 'Message'.

You might come across some irrelevant messages, but you will succeed in time.

Read only

0 Likes
1,775

Resolved.

Thanks to you all.

Regards,

Sibin