Application Development 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: 

Tracing Error Message to Program

Former Member
0 Kudos

Dear All,

When I am executing standard transaction MIGO in SAP, I have a customised error message appearing.

Now I want to eactly navigate to the location of the error message in the program to check for the error.

But when I click the error message it gives like ZMM193 as message class and when I try to navigate and fins where used list, it gives only list of programs where message class ZMM is used.(Which runs into many includes / BADI's).

How do I exactly get into the place in the program where this message(ZMM193) is used?

Kindly suggest.

Thanx

Shyam.

5 REPLIES 5

Former Member
0 Kudos

Hi,

  select the message 193 in se91 for ZMM..then use where used list to find which program it is using..

  If you can debug..then execute Migo and put break points for the statement MESSAGE..then it will stop in all the message statements...and you can find the code when it reaches your message number and class..

Thanks

Naren

Former Member
0 Kudos

My thoughts:

  1. Run MIGO in debugging mode.
  2. From the menu, choose Breakpoints->Breakpoint At->Breakpoint At Message.
  3. Enter the ID, Number, and Type into the fields and click continue.
  4. Continue executing the program until you hit your breakpoint.
  5. Click the 'Standard' tab and view your ABAP and Screen Stack.

Best Wishes,

Eric

arindam_m
Active Contributor
0 Kudos

Hi,

If you can debug the same then BREAKPOINT AT feature in the debugger is your best bet.

Cheers,

Arindam

Sougata
Active Contributor
0 Kudos

Select the message number (and not the message class) then use the Where-Used list. That will give you a narrow list on which you can then set breakpoints on and run the transaction.

Sougata.

Sijin_Chandran
Active Contributor
0 Kudos

Hello Shyam ,

Adding with the above answers I would also like to give you one more suggestion regarding the same.

Start debugger while executing MIGO and create a WATCHPOINT on variable SY-MSGNO = '193'

This will navigate you to the exact location on reaching the watchpoint.