Wait for RFC

[Former Member]

Hi,

We are experiencing RFC connection issues between two SAP instances. When putting a trace in place in ST12 in the destination instance, we see that a large % of ABAP time is spent in "wait for RFC" and looking at the code we see program SAPMSSY1. How do we go about finding out what the problem is? When we put a breakpoint in place, we find that the user is not appearing in SM66 or SM50 / SM51 so that we can't debug the RFC call. Any ideas that will help us figure out what arguments are being passed that result in the "Wait for RFC"?

Thank you,

Mike

[Former Member]

Not sure, this tip may helps u that, go to MENU>System debuggin->update debugging in debugging session.

Or go to SMQ1, then select your qeue and then go to MENU-->Debugging

By the way, the user is a DST_RFC_USER / WF_BATCH?

thanq

[Former Member]

Hi Michal Szopinski

Please share with me , how did you resolve this issue?

I am facing the same issue.

Regards,

Karthick Eswaran

[Former Member]

Hi Michael,

You can debug RFC with a simple trick.

Please use the following code for debugging ther RFC and then call the RFC from the remote system and then use the TCODE :SM50 (Select your session)--> Program/Session --> Program (Debugging).

Then change the value of the variable of Var to 1 or else it will be in infinite loop.

Then you can start debugging the RFC.

DATA : VAR TYPE i.

DO.

IF VAR = '1'.

EXIT.

ENDIF.

ENDDO.

[lauinator]

I have the same issue, SAT trace shows that 94% of the time for goods issue posting in EWM is used for WAIT_FOR_RFC. I'd like to know the issue around this? How can this be improved?