For every revision in our program, we usually want to compare and observe the changes applied to the original program. Most of the time, or should I say as a best practice, we create a copy of the original program into a temporary program name. This will ensure that we do not mess up the original program for every revision that we are doing. Note that even a small change in the program can affect the whole system or subsystems connected to it.
Sometimes a running program is not enough basis for us to conclude that the program will run perfectly. With T-code SE39 - Splitscreen Editor you can display the source texts of two ABAP programs or two methods of ABAP classes next to each other or you can compare them. Changes in the program will be highlighted so we can easily recognize and decide if these changes are correct and necessary. Also, most programmers are inserting temporary codes in the program for the sake of doing a test analysis or proving something. Then at the end of coding, we usually forget to remove those unnecessary codes or “dead codes”. It may not affect the program itself but it can be a confusion to the next programmer who will read the codes. Using this Split Screen Editor, we can easily detect programs that are added to the original program.
To compare a program in the current system with one in another system, choose Compare different systems from the initial screen of the splitscreen editor. A field appears on the screen in which you can enter the RFC destination of the R/3 System containing the required program.
No comments:
Post a Comment