topic Re: Debug to get Warning message source in Application Development and Automation Discussions

Debug to get Warning message source

Former Member — Wed, 15 Apr 2009 04:36:30 GMT

Hi friends,

There is an issue in VA02. When we save that, it trigers an 'Warning' message. We have to find the source of this warning message. We debugged it and could not find. These are the methods we followed.

1. Before clicking on 'Save', we activated the debugger (/h) - We could not get to the point of message.

2. In the debugger we put a break point at all 'Message' statement - it stops at all the messages but not at the one we need and still the message pop ups.

3. We searched in SE91 for the message id and also in table T100 for the message. Could not find the message there.

Any idea from where this pop up screen with the warning message coming from? Is there any other way apart from 'Message' statement to trigger the message?

Regards,

M....

Re: Debug to get Warning message source

Former Member — Wed, 15 Apr 2009 04:52:45 GMT

Dear

do one thing

copy this code to .txt file

[FUNCTION] 
Command=/H 
Title=Debugger 
Type=SystemCommand

Whenever a message occurs in any SAP program, either debug or where used list of message number to find from where the message is triggered, instead of doing the same please follow the below step to find the message location easily.

Just drag the attached file on the message and leave, automatically a debugger will be switched on. Then press Enter Button automatically it will take you to the next line of the code from where message is triggered.

regds ankit

Re: Debug to get Warning message source

Former Member — Wed, 15 Apr 2009 06:49:47 GMT

Hi,

first go to the particular program like

check goto~~>textelements~~>selectiontexts it display all texts used in particular program check that text number .

run the program /h debugging mode ,check with each message .

check with once above way

Regards,

Madhu

Re: Debug to get Warning message source

matt — Wed, 15 Apr 2009 06:51:58 GMT

If the message is & & & &, then you won't find the text in T100, but it could still be a message. When the message pops up, you should be able to get the technical information for the message and determine its message number.

Set a watchpoint on sy-msgno having the value of the message.

Also, you may need to switch on system debugging /hs.

matt

Re: Debug to get Warning message source

soumya_jose3 — Wed, 15 Apr 2009 10:32:04 GMT

Hi Madhu,

Is it a Pop-Up message?

Can you tell what message you are getting?

Regards,

Soumya.

Re: Debug to get Warning message source

Former Member — Wed, 15 Apr 2009 10:38:34 GMT

well he told us it is a warning message...

Re: Debug to get Warning message source

Former Member — Fri, 22 May 2009 12:51:48 GMT

Hi,

1) whenever this message is & & & & you can view the values for & in debugger.

2) also try to set break point at function module MESSAGE_STORE which is used to save message and then FM MESSAGES_SHOW is used to show all the list of messages.

3) break points don't work in programs with status S "System program" (see se38 -> Attrributes -> Display). May be the user-exit with such a wrong program status issues this message?

Pavel.