ST01 RFC TRACE: Debugging ABAP RFC via JAVA Webdynpro Screen.

[Former Member]

   This Blog will be helpful to find the ABAP RFCs which get called from the Java webdynpro screen

   on applying any action on it. Most of the time in many projects client prefer any other technology screen

   or JAVA screen as Frontend but for Backend they use  ABAP code. If any problem appear on the

   Java screen due to ABAP code execution, then the ABAP code should be  debugged with the help of debugger .

   To search the name of RFC or the problematic code we can use

   SAP transaction ST01 ->RFC Trace.

   Procedure in short :

   Step 1) Go to ST01 and switch ON the trace

   Step2) Do the required actions on Java webdynpro screen such as   (Press any Button: Save/update/Delete)

   Step3) Go to ST01 and switch OFF the trace and Press analysis to see the required RFCs

   Step4) Go to SE37 and find the RFC name.  on the external debugging , put the break point

   Step5) Do the required actions on Java webdynpro screen as done in step 2 and find that the debugger is on.

   Procedure in brief:

1)      1) Go to ST01 and switch ON the trace: Tick the RFC Calls check box and Clicked on Trace on button.

                 

   2)  Here we can see the below Java Webdynpro screen , Fill in it the required fields and 

        Press GEM button to update the date in Backend (SAP Database tables).

   3)  The data is updated, we can see a record on Java webdynpro screen. This updation has

        happened in SAP database using ABAP code.

            

  4)  Again go to transaction ST01 to OFF the trace  by pressing  TRACE OFF button

       And see analysis report by pressing ANALYSIS button.

         

   5) Put the SAP user name , proper date / time fields value and press execute .

          

  6)  After Execute below screen will appear. In the Object Column you can see all the RFCs are listed which were hit

      by the action applied on java webdynpro screen. The RFC name may be not fully displayed due to limited length

      of OBJECT column in the report.

        

   7)  Go to transaction SE37 to find the full name of RFC

         put the name got from above screen Z_HR_RFC_UDLAAN_* in function module field

         press F4 to get its full name, here I got it Z_HR_RFC_UDLAAN_CREATE.

          

    😎 Now put the break point in the found RFC Z_HR_RFC_UDLAAN_CREATE .

         

9)  And using menu entry UTILITIES -> SETTINGS  set the external debugging on

   10) Now go to Java webdynpro screen and do the same actions  hown above you will find the debugger is activated

     and normally an ABAPer can start debugging.   :smile:

          

2