Application Development and Automation 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: 
Read only

Program won't stop to debugging

Former Member
0 Likes
706

Hi!

I've copyed the standard printer program of the PO order (NEU output type) to ZAPFM06P program. Also copied the SAPSript to ZEDRUCK.

Now I would like to debug the program ZAPFM06P. There are many includes, so I've put my breakpoints right before the OPEN_FORM function element.

I've tried BREAK-POINT command also.

Anyhow it is not stopping, nor when I call the form from ME22N, nor from ME9F.

Any ideas?

Thank you in advance

Tamá

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
611

Hi,

Have you attached the program ZAPFM06P and the script ZMEDRUCK in the NACE transaction to the Correct Output type of PO(NEU is the std).

when you attach your program in Nace tcode then only it triggers.

Then search for Open_form in the program and keep abreak-point and it will surely stop.

reward if useful

regards,

ANJI

4 REPLIES 4
Read only

Former Member
0 Likes
612

Hi,

Have you attached the program ZAPFM06P and the script ZMEDRUCK in the NACE transaction to the Correct Output type of PO(NEU is the std).

when you attach your program in Nace tcode then only it triggers.

Then search for Open_form in the program and keep abreak-point and it will surely stop.

reward if useful

regards,

ANJI

Read only

Former Member
0 Likes
611

Have u replaced the standard prog with your z prog in

NACE transaction.

Read only

Former Member
0 Likes
611

You could do this:

1 Start your transaction with /h command, this allow you to turn into debugging env. imediatly.

2 Set a funtion break point with function "OPEN_FORM", this allow your program to stop when "OPEN_FORM" function is called.

3 Once OPEN_FORM is called, your program will stop there, if the code you want to be stopped is excecuted correctly, you will find it.

4 if it is a background job, or work flow triggered, that's would be more difficult to trace. but it should not be like this.

Read only

Former Member
0 Likes
611

Thank you for the answers. The customizing in NACE was fine.

Anyways it was not stopping, so I had to run it with a /h transaction and trace the program flow manually...

Now I put a break-point into elsewhere in the code and it is stopping normally.

Problem solved.