topic Re: breakpoint is not triggering in Application Development and Automation Discussions

breakpoint is not triggering

Former Member — Thu, 04 Oct 2012 04:41:37 GMT

Hi all,

In nace for v3 we configured the custom output type and in processing routines our custom program and smartform is assigned for transmission medium 5(external send) and after creating billing document in vf01 and once we press save our custom program has to trigger and for the related mail address the billing document data has to be sent now that is working fine but in my program if i place the breakpoint after saving breakpoint is not triggering but the mail is going to customer but i want to know how my custom program will trigger.

Regards,

Karthik

Re: breakpoint is not triggering

matt — Thu, 04 Oct 2012 05:16:16 GMT

If a breakpoint isn't triggering, there are a a few possibilities

1. The breakpoint has been placed in an object marked as system. Then you need to switch system debugging on

2. The breakpoint has been placed in a bit of code that doesn't, in fact, execute

3. You've set the breakpoint but not restarted the transaction

4. You need to set an external breakpoint

5. The code in question is executed in another task, possibly in background.

6. The breakpoint has been placed in a bit of code that executes in the update task. You need to switch update task debugging.

7. The code to be debugged is in an inactive BADI.

If the breakpoint is in your own code, add a MESSAGE x000(s1) to it, at the place you wanted to break - that way you can check your code is in fact being run.

Re: breakpoint is not triggering

Former Member — Thu, 04 Oct 2012 06:56:32 GMT

After setting up the break point. you need to make update debugging ON as shown below.

Re: breakpoint is not triggering

sandeep_katoch — Thu, 04 Oct 2012 07:36:51 GMT

Hi Vinu,

Mathew has explained allll the relevant cases but just to add one more thing.

Put a breakpoint in the form routine also and make update debugging as ON ann system debugging also as ON .

Go to breakpoints tab and check whether you are able to see any active breakpoints.

You can also use the calls stack to check from where the execution of program started and where are you during debugging . You can easily find the way out.

Rgds,

Sandeep Katoch