How to check what data is coming from RFC

[Former Member]

Hi,

We have one RFC for create sales order, that RFC we are running from cordys software,

now when we send data from cordys I want to analyz the what data is coming in SAP , how to do it.

for create Sales order we have use BAPI and after BAPI call we have use commit .

regards,

zafar

[Former Member]

Hi Zafar,

I don't quite remember when you cranked up the various traces if you'd see parameter data in readable format. Problem is that there's so many traces and I'm having a senior moment...

Good starting point for that is in your case OSS note [877979 - RFC tracing for external-to-ABAP communication|https://service.sap.com/sap/support/notes/877979] and referenced notes (see also [532918 - RFC trace generation scenarios|https://service.sap.com/sap/support/notes/532918]).

However, my personal favorite is switching the work process into debug mode. This only works if your RFC call takes at least a while (might work for sales order creation depending on the complexity), because you have to see it and then switch the work process into debug mode. You can do this via SM50, menu Program/Session -> Program -> Debugging. If the RFC lasts for less than a second you usually don't have a chance, because you need to refresh the list (keep hitting <F8>) and then quickly enable debug mode, when you see the RFC appearing (it helps to filter the list for example by the RFC user ID).

Cheers, harald

p.s.: If you look at some remote function modules you'll see that they have some kind of endless loop at the very beginning that can be activated via different methods. The sole reason is to keep the function waiting, so that you can switch into debug mode. This is of course only required if you don't have control over the RFC client (i.e. you cannot change the parameters there to trigger debug mode).

[Former Member]

OK