Update Debugging

[Former Member]

Hi guys,

I am facing an issue with update debugging, let me expalin you the problem:

Am working in 4.6C, I have an output type configured for a PO. When am saving a PO, this output type gets triggered and updated. Now the problem, when am creating a PO and saving in the debuging mode, putting my Update debugging on, having a break point in the code, it does not break at my code, however after am done, I see the NAST update happening. The funny thing is when am changing a PO and saving it, it stops at my code.

Dont really understand whats happening...can someone please suggest me.

Thanks

JM

[Former Member]

Hi,

All the registered function module (CALL FM in UPDATE TASK) will be executed upon commit work statement is executed. Update debugging will allow you to go into these function modules and see what is happening.

Based on your information, you may have not put the break point at the correct place during PO creation.

Regards,

Lim...

[Former Member]

Hello Johan,

There are 2 ways to debug an outbound idoc triggered by an output type. One way is to set the output timing to 1, and save the purchase order and then execute RSNAST00 which will take the control to the breakpoint.

You can also debug the idoc with the output timing set as 4.

Here the idoc is triggered in update mode. Hence any breakpoints you may have set before will not reflect. Hence you need to activate update debugging.

Below are the steps for the same..

1. Add the output type in purchase order.

2. Enter '/h' to activate debugging in transaction window.

3. Save purchase order.

4. The process enters debugging mode.

5. In Settings tab, select checkbox for Update Debugging.

6. Click F8.

7. The control will appear to go out and re-enter debugging mode.

8. Now from the menu bar, in breakpoints option, choose Breakpoint At Function Module option, and give the name of the function module which is processing the idoc.

9. Once breakpoint set, click F8.

10. The control will now go to the function module. You can then debug the FM.

Hope this information is helpful.

Regards

Arindam