- SAP Managed Tags:
Save the Session and breakpoint for the RFC FM
When working on Integration tools like Business Connector/.Net connectors/XI, we use RFC call to process in the backend SAP R/3 system. Because when we call any SAP RFC function module from any integration tool, it will be processed on any available application server in the backend, where a user breakpoint cannot be triggered to debug the ABAP code in the backend system but if the RFC destination is the same client or if we want to save the debugging points and reload it next session the we can follow the simple steps.
Give the name of the session (here we have given as ‘Test’) and the name of the user.
We need to give the name of the session ‘Test’ and User.
And all the breakpoints will be loaded again.
The breakpoints will be loaded every time when we load the session.
When working on Integration tools like Business Connector/.Net connectors/XI, we use RFC call to process in the backend SAP R/3 system. Because when we call any SAP RFC function module from any integration tool, it will be processed on any available application server in the backend, where a user breakpoint cannot be triggered to debug the ABAP code in the backend system but if the RFC destination is the same client or if we want to save the debugging points and reload it next session the we can follow the simple steps.
- Debbuger->Debugger Session-> Save
Give the name of the session (here we have given as ‘Test’) and the name of the user.
- If we execute the FM again we can load the session by Debbuger->Debugger Session-> Load
We need to give the name of the session ‘Test’ and User.
And all the breakpoints will be loaded again.
The breakpoints will be loaded every time when we load the session.
1 Comment
