Sometimes, you run into unexpected error messages which makes no sense. If the error message or the long text is not very helpful, now you can go a step further and try to find the reason or at least the location of the error message by debugging.
Step 1 – Note the message id and message number of the error message by double clicking the message.
Step 2 – Go to the transaction where error is coming and execute until the last step where the error comes. In the command window, write /H and press enter.
After pressing the enter, you should see a success message at the bottom of the screen.
Step 3 – Execute the last step when you get the error. But this time, a debugging screen will open. Please note – I am only showing the steps in New Debugger. If you have access to classical debugger only, please let me know and I will put screenshots for that one as well.
Step 4- From the top menu in the debugger screen, go to Breakpoints > Breakpoint at > Breakpoint at Message.
Step 5 – Enter the message id and message number. Click on the green tick. A success message will confirm that breakpoint is set.
Step 6 – Press F8. The program will stop at the exact message.
Now you know the place where the message is coming from. This may give some insight and if not, you can pass the information to the ABAPer.
Note: If the debugger does not stop, even if you have followed the steps accurately then it is possible then the message number or id is dynamically generated in the program. This will require deeper analysis, but it happens rarely.
