My development system uses different clients for development and testing, which I think is common practice. Unfortunately, this leads to a rather unpleasant problem when it comes to debugging. While the breakpoints set in the development system will stick to their code and move through the insertion or deletion of lines, this obviously does not apply to breakpoints located on the same code in another client.
Since the system does not know exactly how the lines between the two versions were changed, breakpoints placed in the test client will remain on a specific line in the program. Therefore, any change to the code will break the breakpoints. To solve this problem, I have to: open another program or screen, and then return to the program to update the code (where is the SAP update button?), Find where the breakpoints were moved and delete them one by one (where does the package remove the control button SAP points?), and then set new breakpoints, usually in the same place.
This problem becomes so frequent in my work that I sometimes spend more time moving control points than I spend on actual development. In some cases, I just gave up and started coding at user control points, as they would at least remain in place. However, they have their drawbacks because they cannot be removed in the debugger, which makes them useless when you are forced to stop at each breakpoint in a loop with a thousand records.
My actual question is whether there is a better approach or best practice when it comes to debugging in this scenario. I'm relatively new to ABAP programming, so I hope more experienced developers have alternatives or tricks that they use to speed up this process. Is there an even better way to debug and break code in a secondary client?
source
share