Debug message

[Former Member]

Hi

I have a error message raising from a standard program and want to debug it. What are the best ways of debugging from where the message is tirggered? I had seen a blog on it but now dont have the refernce of it. Pls help

Chaks

[Former Member]

HI,

put /h and run your tcode. In debugger

Breakpoints->Break points at Statement--> here write MESSAGE and then start pressing F8

Then debugger will stop at every message trigger in program, Just check when your message gets trigger.

[Former Member]

hi

while doing mb1b transfer stock between one plant to another in different company codes the error facing is

"No postings can be made to profit center in company code "

Message no. KM183.

the client is doing this process in mb1b because they want to finish in one step

how to solve the issue we are getting the the Message no. KM183.

please guide us

regards

sree

[Former Member]

The breakpoint at every message can be a bit of a hassle depending on where you got to debug. It can be you cross a thousand messages before you get to your one.

My advice would be to lay a watchpoint on field SY-MSGNO. Make a watchpoint when sy-msgno = YOUR ERROR MESSAGE NUMBER. and press F8, then it should stop at your message..

that should go quite fast.

[Former Member]

Is there an reference to the blog i'm looking for?

[kiran_k8]

Chaku,

Best way is

1.Double click on the error message

2.Get the message Number and Class

3.Go to SE80 Using the Program name of the transaction check whereall this above message number is used.

4.If you take the help of a technical consultant you can zeroon which message is actually triggered in your case or you can put a break point on all the places where this message is used in the program.

5.Execute the transaction,it will stop at the break poinit,from there you analys which statement is trggering this error message and why.

Thanks,

Kiran.

[kesavadas_thekkillath]

Hi ,

If you have the message class and message no.

Then check the where used list of that message.

It will show the areas where its used inyour program, instead debugging through all the message statements.

[Former Member]

oh, well i stopped using the "where used" thing for messages. They are too often called dynamically so this wont help.

[kesavadas_thekkillath]

Hi Florian ,

But for my luck there is always a 1 = 2 maintained for such type of messages.

Keshav

[kiran_k8]

Florian,

Thanks for sharing this trick.I guess your trick works damn faster.

Thanks,

K.Kiran