Skip to Content
0

How to debug a program in NACE

Aug 30, 2017 at 05:23 PM

279

avatar image

Trying to debug program setup in NACE. See attached screen shot. Basically this program gets called when adding message ZNEU to PO (externally sends a PO via email). I would like program to break in debug when i add message and save PO. Program executes but I can't get it to break in debug.

nace.jpg (91.7 kB)
10 |10000 characters needed characters left characters exceeded

It is totally unclear what you want to debug.

Do you want to debug the customizing or do you want to debug the purchase order?

0

I want to debug the custom program being pointed to in the screen shot, ZMMPO_EMAIL_PO. This program gets executed on save when message "ZNEU" gets added to a PO in ME29N. The result is an email with po attached. I would like to debug this program. Obviously setting an external breakpoint in it, does not work.

0
* Please Login or Register to Answer, Follow or Comment.

4 Answers

Jürgen L
Aug 30, 2017 at 08:58 PM
0

Try to follow the steps given in OSS note 1955591 - How to troubleshoot print / smartform and message output issues in MM-PUR

Show 2 Share
10 |10000 characters needed characters left characters exceeded

Also Google should be able to find very many SCN posts on how to debug output.

0

Thanks. Found the note and added breakpoint on suggested line of code in RSNAST00, however I still cant get it to break when reproducing output message on PO

0
Scott Carrick Aug 31, 2017 at 02:52 PM
0

Everyone,

Thank you for your time and responses. I figured out that if I debugged the preview but chose my message type, I was able to get it to break on my custom program. See screen shot. Still not able to debug the output but I can get what i need from debugging the preview.


output.jpg (193.3 kB)
Share
10 |10000 characters needed characters left characters exceeded
Hubert Heitzer Aug 31, 2017 at 05:28 AM
0

Hi Scott,

do you try to debug the preview or the creation of a new output?

If you want to debug the creation of a new output, check in transaction NACE the relevant condition records.

As "Dispatch Time" (or "Transmission Time") 4 should be costomised for your debugging.

Example:

Compare https://help.sap.com/saphelp_erp60_sp/helpdata/en/a0/86ce53118d4308e10000000a174cb4/frameset.htm

Regards,

Hubert


-ss.jpg (85.5 kB)
Share
10 |10000 characters needed characters left characters exceeded
Avik Mazumder Aug 31, 2017 at 05:28 AM
0

Hi Scott,

There are two ways to do it as below.

1st approach:

You have setup the further data of output as below,in this case it requires you to setup the update debugging.then it will stop at your desired breakpoint as suggested by Jurgen.(small trcik).Sometimes it si not required when the Standard FMs not called at update task,that is why SAP KBA has not mentioned it probably.

2nd approach: Whenever I need to debug, I follow this and it works 100% times.

Change PO->Messages-> repeat output->further data-> set 1

Then Run RSNAST00 it wil stop at your breakpoint.

RSNAST00 is actually the parent program of processing all kinds of output,however SAP has some specific programs and t-codes for individual output message processing in each process area though I have observed all can be processed by same RSNAST00.

Regards,

Avik


4-setup.png (3.6 kB)
1-setup.png (2.8 kB)
Share
10 |10000 characters needed characters left characters exceeded