How to Start ABAP Program Debugging for a User?
Clarification of the Question
As a functional consultant, you were involved in the creation of a very important ABAP program that was moved to the production system some time ago. By “creation,” I don’t necessarily mean writing the ABAP code yourself.
Let’s assume your involvement was limited to preparing the functional specification. Now, the program is live, a business user starts working with it, and after some time encounters a situation they believe is an error. They reach out to you for help.
You try to reproduce the issue in the development or QA system, but nothing works—the error doesn’t reappear. So now, you need to see what’s actually happening in the production system.
How can you start debugging for a specific user without resorting to painful constructs like:
BREAK user_name;The Solution
As it turns out, SAP has anticipated such scenarios and provides a solution in SAP Note 1919888 - Debugging the applications of another user.
The note includes a lot of useful information, particularly regarding the required version of specific system components to make this functionality work.
In short, if all recommendations in the SAP note are followed, the process should look like this:
The diagram above shows a simple sequence of steps that need to be performed by both participants in the debugging process.
See also the following notes: