dynamic calls

[Former Member]

Hi,

if a message is pop-up by dynamic calls, what should I do?

thanks a lot!

kitty

[ferry_lianto · Accepted solution]

Hi Kitty,

Please try to put break point at system exception.

Hope this will help.

Regards,

Ferry Lianto

[Former Member · Accepted solution]

yes, put break-point at system exception, then how to do?

how to get to this exception, F8 will directly go out.

thanks a lot!

kitty

[former_member186741 · Accepted solution]

what Ferry is suggesting is after /h do 'settings->system debugging' before setting the 'message' breakpoint.

[Former Member · Accepted solution]

even so, still I didn't get the message, /h-setting-message(breakpoint).

any other ways?

thanks for your help.

kitty

[former_member186741 · Accepted solution]

do you still get the message if you now run it outside debugging? What is the message?

[Former Member · Accepted solution]

it is a customer message class, not SAP standard message class.

Group number

Sales document number 0008503002

Item number of the SD document 000000

Schedule line number 0018

Counter in control tables 00

Message identification Z1

System message number 018

Output type E

Message variable 01 0000027985

Message variable 02 027985

Message variable 03

Message variable 04

Group type F

Old-customer number for customer 0000027985 is not correct (027985)

thanks a lot!

kitty

[Former Member · Accepted solution]

redundant....

same as above mentioned.

Message was edited by: kitty

[former_member186741 · Accepted solution]

if it's one custom abap, search it and look at all the message statements. It could be one which is after a function module call which may have filled the 'sy' fields via a 'raising' command.

[former_member186741 · Accepted solution]

Hey Kitty,

thanks for the points but out of interest what was the solution?

[ferry_lianto]

Hello Kitty,

Other alternative ... if you know the error message class and number, you can go to transaction code <b>SE91</b> and clik on button where is used. The system should display list of progams, include, function module and so on.

Then you can check one by one until you find the program which give you an error message with specific cause error condition.

Hope this will help you to narrow down the issue.

Regards,

Ferry Lianto

[Former Member]

I have done this, that's why I asked if it is a dynamic calls how to track the message.

kitty

[former_member186741]

go into debug mode on the transaction you are using. Type /H in the command area in the top left of the screen. Hit enter twice. do Breakpoints->Breakpoint at->statement. put 'message' in the popup and hit enter. Hit the 'continue' button. Now proceed to get your message displayed. You may have to hit continue several times to get to the message you want. When it stops you will know which program/subroutine/function module you are in.

[RichHeilman]

I see, do just like Neil has suggested, you will eventually find it. Then you can see why you are getting the message by the logic around the message.

Regards,

Rich Heilman

[Former Member]

I have put /h and press F8 several times, I have seen other messages, didn't get the message I want, so what should I do next?

thanks in advance.

kitty

[RichHeilman]

About what?

Regards,

Rich Heilman

[Former Member]

it is in the billing process, i got an error message, but when I go to SE91 to find which program use this message, it popup could be dynamic calls.