SAP ABAP External Debugging/Remote Debugging Steps

Today I realize that I am discussing an important concept when it comes to explaining debugging concepts and calling it external breakpoints.

So this is a quick demo on how to use external breakpoints and is very useful when you are trying to debug an application from an external application.

Suppose you are trying to hit the ECC box from a portal or web dentro application, so we are a pro and I want to explain everything regularly.

I don't know when I can do it while still alive or pending, but it's useful for people who are already working on these kinds of scenes.

So I understand that knowledge is good, so I went through it and understood how to debug using an external breakpoint, and this is not just about the web DynPro app or portal, it is also in ECC applications.

So let's say you are triggering a different user transaction and you want to debug this type of scenario on your system, so again I need some time.

I have different methods in this class and these methods are enabled when I am calling from an external web DynPro application.

I have a webbed intro portal here on this web DynPro portal so when I log in to this portal I mean I need to know what kind of assessment is going on in the back end or runtime.

So what I need to do here is I know this portal is going to have a test id, it is not my id if it is my id it is basically the same user but if it is a different id then it is a different id because it is an external application so it goes to an external breakpoint, But it's a different ID so I have to set an external breakpoint for that user so you can see the external breakpoint is deleted.

You can click here, so it gets a message that sets external debugging, and if you go to Utilities Settings and Debugging in the user, you need to provide your SAP with the username the external application will hit. The box can be a regular UCC or SRM or anything else.

This is a generic user id so you have to enter that user id here and then when you click on this external debugging then this external break point is now set specifically for the user who is going to hit the application BCC box.

When you do this and the icon here goes to a transaction called SR Debug, and then click on Activate Debugging in the Activate Debugging you need to give that user ID, so I replaced that user ID here.

It's OK and you get this pop-up remote about debugging because it comes to your app and login so I'm trying to access the portal by clicking on the login but I'm actually trying to access the UCC app, so it goes oh and it automatically opens the external breakpoint Here's what's common about triggers and debugging.

This is a quick tip so I wanted to share it with everyone, and then once you hit f8 you are done with your debugging, you are pushing this system back to the external application from where you really hit it so you basically gave it some input from the portal you came here, It does all the simple things and pushes that output back to the external application, so I clicked on F8 and how do I do external debugging so I have to return to my application.

What is a External Debugging?

External debugging allows you to stop and debug ABAP programs running in the context of another user's session by setting breakpoints. External debugging covers both situations:

The program to be tested is running in another session of the user who set breakpoints.

The program to be tested is running in a user session of another user other than the one who set the breakpoints.

External debugging is specifically designed for debugging ABAP programs that process the following types of requests:

HTTP requests (HTTP debugging)

RFC requests (RFC debugging)

Requirements

If you use load distribution for your system environment, the server group (logon group) is reduced to one server before debugging commences.

Ideally, the user who performs the debugging should not be a collective user.

Steps to do external/remote debugging

In transaction SICF, you can use the external debugger to set external breakpoints and check the debugging of the relevant section of code:

Select the required service in the service hierarchy.

Choose Edit  Debugging  Activate Debugging.

Enter the required data (if you have selected the service previously, the system will propose the service path for you).

or certain paths, you can also set the external breakpoints directly in the ABAP coding. Proceed as follows:

Log on to the application server on which you want to execute the HTTP requests.

In one of the Development Workbench transactions SE38, SE37, SE80, and so on, choose Utilities  Settings  Debugging  External Debugging.

Under User, enter the user with which you perform your HTTP application.

Use the Set/Delete External Breakpoints button to position the external breakpoints in the required locations in the ABAP code.

More ABAP Tutorials:

• SAP ABAP COURSE CONTENT
• 
  
• COMPLETE UNDERSTANDING OF NETWEAVER AS SAP ABAP
• 
  
• 10 REFERRAL BOOKS FOR SAP ABAP TUTORIALS-BEGINNERS
• 
  
• SAP ABAP Programming Tutorials - Free ABAP Course        
• 
  
• What are the Roles of SAP ABAP Consultant
•         
• SAP Programming Consultant Salary
•         
• SAP Projects Types 
•         
• ASAP Methodology
•         
• SD ,MM and FICO Flow
•         
• ABAP Coding Standards