topic Re: Debuging issue in Application Development and Automation Discussions

Debuging issue

former_member431412 — Thu, 03 Dec 2009 21:30:50 GMT

IW31/32 has been enhanced to call a functionmodule

CALL FUNCTION 'Z_RFC_STATUS_CHANGE' DESTINATION v_dest

the v_dest has a value of BIZTALK.

one of the parameters being sent is a status (text field)

I added a new status code to be sent and the Functionmodule Fails

I try debugging with internal and external breakpoints and I never manage to get to debug as the module executes.

how can I debug this FM so I can determine what causes the failure?

Any help will be appreciated.

Re: Debuging issue

Former Member — Thu, 03 Dec 2009 21:35:02 GMT

Hi,

May be the function module is called in Update task.

If you are in ECC, While in debug mode, go to "Settings -> Display/Change Debugger settings "

Here check the "Update Debugging" and hit OK.

Now all the function modules that is called in Update task can be debugged.

Happy Debugging.

Regards,

Subramanian

Re: Debuging issue

former_member431412 — Thu, 03 Dec 2009 21:52:36 GMT

I have tried the solution. I still get an error without ever seeing one line of code..

When I send a status code that does not cause the error, the debugger just steps over the funtioncal. I have tried the debuging with my user ID as well as the BIZTALK USER ID.

I have checked SM59 to see If I can find a different user ID to debug against.

Re: Debuging issue

brad_bohn — Thu, 03 Dec 2009 22:21:48 GMT

There is nothing for you to 'step-into'. Your .Net developer should be able to catch the call and debug the code on his/her side in the Biztalk code if that's what your intention is. From the SAP-side, you can analyze that the call parameters are correct before the call and then receive the result of the call and look at the response. You can also turn on a trace for the RFC destination in SM59.

What type of error are you referring to? Is it an update that doesn't happen on the Biztalk side or is it an exception that gets thrown?

Re: Debuging issue

former_member431412 — Thu, 03 Dec 2009 22:24:00 GMT

Thank you,

The FM being called is an SAP FM. So I should be able to debug

Re: Debuging issue

prasenjit_sharma — Thu, 03 Dec 2009 22:32:42 GMT

Hi,

Since the FM is in an external system you cannot debug it in the calling system. If you want to know what is happening inside the FM then note down the values of the parameters being passed to the FM. Then log in to the target system and create a test data for the FM using the values recorded earlier. And you can execute it in debug mode.

Regards

Prasenjit

Re: Debuging issue

brad_bohn — Fri, 04 Dec 2009 14:45:27 GMT


Thank you,
The FM being called is an SAP FM. So I should be able to debug

No, you can't. The function is only a shell. You are actually executing a program in another system (Biztalk) and receiving a response. Check out the help files on remote function calls...

Re: Debuging issue

former_member431412 — Fri, 04 Dec 2009 14:51:35 GMT

Ah, now I get it. When calling a FM with a destination, I am only sending parameters to the external app. I added the new status code to the filters in the Biztalk orchestration and the error went away. Thanks for helping me understand what really happens

Re: Debuging issue

SuhaSaha — Fri, 04 Dec 2009 14:54:20 GMT

I agree with Brad

As the call is made in an external system it can be debugged & analysed by the developer on the external system. He will be able to tell you exactly why the RFC fails.

BR,

Suhas