RFC Using the ABAP Debugger 

You can use the full functionality of the ABAP debugger when developing or testing an application using RFC.

An RFC client program can use this feature with one of the following options:

·        environment variable RFC_DEBUG

Set this environment variable to any value to enter debugging mode.

·        set -debug on the command line

If the RFC client program uses RfcConnArgv for scanning the command line, set -debug on the command line to enter debugging mode.

·        set the trace field to D or E

If you can modify the coding of the RFC client program you are using, you can set the trace field in the structure RFC_OPTIONS to the value D or E before calling RfcOpen:

¡        D: debugging without activated RFC trace

¡        E: debugging with activated RFC trace

·        use the saprfc.ini file

Define an entry in the saprfc.ini file which includes all necessary connection parameters and the RFC-specific parameter RFC_DEBUG (=1). An RFC client program can then issue the RfcOpen call with the mode RFC_MODE_PARAMETER and a destination pointed to this defined entry. See The SAPRFC.INI File for more details.

·         This feature is available on all supported UNIX platforms (Motif).

·         On Windows NT or Windows 95, it is only available with the 32-bit RFC library together with a 32-bit SAPGUI. In particular, this functionality is not supported for the 16-bit RFC library or for the 16-bit SAPGUI (Windows 3.x, as well as the 16-bit subsystems of Windows NT and Windows 95).

·         Under Windows NT and Windows 95 the SAPGUI program and its DLLs and auxiliary programs can be installed anywhere. However, you must have started SAPGUI once before it can be started automatically by RFC, because the SAPGUI must register itself in the Windows registry.

·         On SAP-based UNIX systems, the SAPGUI program must be installed on the default ‘SAP path’ /usr/sap/<system name>/SYS/exe/run.