Supported by
Supported by Inetum


images/thumbnail.jpg - Thumbnail

When you have a very large method, you should subdivide it into several smaller ones.

Clean ABAP says that methods should ideally have 3 to 5 commands and suggests a maximum of 20 in extreme cases. If you’re still making 300-line methods, think about it, be ashamed of yourself and go and subdivide them.

Mr Martin Fowler has studied in depth the optimum processes for refactoring programmes and has published his results in an excellent book called Refactoring which I strongly advise you to read. Alternatively, you can consult the website

The book Refactoring describes systematic processes for carrying out each of the cases. These are the steps it proposes for the Extract Method technique:

  1. Create a new method and name it in a way that makes its purpose self-evident.
  2. Copy the relevant code fragment to your new method. Delete the fragment from its old location and put a call for the new method there instead.
  3. Find all variables used in this code fragment. If they’re declared inside the fragment and not used outside of it, simply leave them unchanged—they’ll become local variables for the new method.
  4. If the variables are declared prior to the code that you’re extracting, you will need to pass these variables to the parameters of your new method in order to use the values previously contained in them. Sometimes it’s easier to get rid of these variables by resorting to Replace Temp with Query.
  5. If you see that a local variable changes in your extracted code in some way, this may mean that this changed value will be needed later in your main method. Double-check! And if this is indeed the case, return the value of this variable to the main method to keep everything functioning.


Right. Same old poo. If you want to extract part of the code from one method to another, you have to do it all by hand. There’s no automation here. No wonder people who use SAPGUI tend to make long methods. SAPGUI should be called an IUE instead of an IDE, the U standing for Underdeveloped.

In Eclipse ADT

  1. Select the code you want to extract
  2. Right button, Source code > Extract method
  3. Name the new method and adjust the parameters
  4. Next, next, finish.

There, that’s it. The 5 steps described above have been carried out automatically. Follow them.


So, if you’re still using SAPGUI and you could be using Eclipse ADT, you’re not the sharpest tool in the shed, are you?

Greetings from Abapinho