Supported by
Supported by Inetum

Request Based Debugging

images/thumbnail.jpg - Thumbnail

If you look up the UNAME system variable in debug within a RFC call you may think it kind of odd to find a username that is not your own. What happens is that the system adopts a specific username for remote calls and a new session is started. A new session implies a new execution context and, hence, all our strategically placed breakpoints will no longer be recognised.

This problem can hinder a simple debug forcing us to run through the code looking for THAT remote call to THAT particular system.

SAP has a solution.

To avoid such situations SAP provides, since Netweaver Release 7.02, the debug by Terminal ID function. Terminal ID identifies the Microsoft Windows user who started the session and it is stored in the Windows registry under the HKEY_CURRENT_USER\Software\SAP\ABAP Debugging key.

This unique identifier ensures the debugger doesn’t get confused with the session changes and responds to all external breakpoints (subscribed at a particular Terminal ID ) with the serenity we are accustomed to.

The steps to start a debugging session per terminal ID are as follows:

  1. Login on the system we want to debug ;

  2. Open the object to be tested in the ABAP Editor (SE38, SE80, SE37, SE24) and input the required external breakpoints ;

  3. Open the debugging menu and choose the debug by terminal ID option: Tools>Settings>ABAP Editor>Debugging Note: A new ID will be generated and stored in the Windows Registry if one doesn’t already exist;

  4. On accepting, the system will ask if the already existing breakpoints should remain active. The answer to this is “yes”. At this point we now have external breakpoints associated with a terminal ID;

  5. In the source system we can now run the program that calls our RFC in debug , but instead of using the /h command we use the /htid command telling the debug that it must stop at all breakpoints associated with my terminal ID.

This is a very useful feature that can also be applied in HTTP calls. But this scenario requires the installation of a plug-in in the browser that allows the propagation of the terminal ID to the lower layers.

Note: In this scenario we assume that the user running the program is the same one that has added the breakpoints in the RFC to be tested, and the terminal ID will therefore be the same. There may, however, be two distinct users and for these cases we can use the following commands to enable/disable the terminal ID-based debugging:

/hset tid= | = of the user who inserted the breakpoints


/hget tid | Display the assigned terminal ID

/hdel tid | Remove assignment to a terminal ID

Abapinho thanks Miguel Jorge for writing this article.

Thanks to Howard Dickins for the photo.