Trace the execution of RFCs from a java application

[Former Member]

Dear All,

I have a Java application which is calling multiple RFC function modules in R/3. This application is processing data for purchase orders and updating records in the Z tables. I want to know the way by which I can trace the execution of the function modules when I execute the application to see exactly which function modules are called and what parameters are affected.

Please help.

[Former Member]

Try the system trace with transaction ST01. For more information check [here|http://help.sap.com/saphelp_nw04/helpdata/en/1f/83114c4bc511d189750000e8322d00/frameset.htm]

[Former Member]

I'm assuming that you have a standalone Java program using the SAP Java Connector (JCo) - in that case your question is probably more appropriate here: . For the SAP Java connector you can enable tracing using the following command line options when invoking the application:

-Djco.trace_level=N (where 0 u2264 N u2264 10 with 10 = most detailed trace)
  and
-Djco.trace_path=<PATH>

Sounds like you don't have the source code available (or it's a really huge application), because otherwise you could just check there which functions are called and what parameters are used. In general I find the debugging option most useful; somewhere your connection parameters should be maintained. Here you should add the following two:

jco.client.abap_debug=1
jco.client.use_sapgui=1

Now each RFC call will trigger a SAPgui window with the ABAP debugger. You might get some overhead calls to retrieve the metadata from the repository (e.g. function definition, dictionary information), but this information is buffered. Note that if you're using JCo 3.x then the SAPgui debugging might not work depending on used JCo version and the backend you're accessing.

Cheers, harald

p.s.: Alternatively you can of course also try tracing on the backend (SAP) by activating traces on the server. However, I think you're better off with the two options I've described.