ABAP ADT parallel locking issue for ABAP Classes

[former_member241558]

Dear Ladies and Gentlemen,

I have one issue which currently stops me to working on ABAP ADT instead of SAP GUI. It becomes more and more critical for me. The issue is very simple: it’s how the ABAP ADT locks ABAP classes when you start something typing in ADT source code editor. When ADT locks the ABAP class then that ABAP class is completely locked, all its sections and parts (all methods and class definitions). It completely blocks me and my colleagues to work in one ABAP class simultaneously.

For example: using SAP GUI (SE80) I can open ABAP class and go to a particular method of this class and starts changing one, so the system only locks that class method, not the whole class and all its methods, while my colleague had been already working on another class method. If we consider this case with ABAP ADT: If my colleague is working on one of method of the class and I’m trying to change another method of the same class via ABAP ADT then ADT sends me the lock error and vice versa, if I’m working on one of the method of the class my colleague will not be able to change another method of the same class which’s more worse because I’m blocking his/her work at all.

Does anybody know if it’s possible to set-up ABAP ADT, so that it will lock a particular ABAP class section (method) instead of the whole class?

Thanks.

PS: my software stuff: ABAP ADT eclipse Version: 2.50.1 and my back-end system is AS ABAP 740 SP11.

Best regards,

Aleh

[ThFiedler]

Hi Aleh,

this editor mode is not supported in eclipse. We have ideas in mind but nothing in the current backlog. 

Regards,

Thomas.

[former_member241558]

Hi Thomas,

Thanks for a quick reply. Hope the ABAP ADT will use the similar locking mechanism as well as the SAP GUI does.

Best regards,

Aleh

[vwegert]

Aleh,

are you talking about the long-term (i. e. transport-level) locks or the short-term, concurrent-editing locks?

Best regards

  Volker

[former_member241558]

Hi Volker,

I was mentioning the short-term, when you start editing the ABAP class within source-code editor. Actually there were some issues with transport locks as well , for example: one method of the class was changed in one Workbench (WB) transport, then the task of that WB transport was released (not the whole WB transport), then I’m trying to change another method of the same class and I’ve got an error message that my previous transport locked this class, there’s no issues when I’m using SAP GUI… anyway this issue isn’t so critical for me because such a case isn’t so frequent, but locking of ABAP classes in parallel is very critical when you’re working on a quite big project with a team.

Best regards,

Aleh

[vwegert]

Aleh,

maybe it's just me, but if you really need the option of multiple people changing the same class at the same time, I'd say there's probably something wrong with the way the project is organized and the code is structured. I for one would most certainly not have someone change parts of the class I'm currently working on.

  Volker

[former_member241558]

Hi Volker,

Usually you’re right, but currently a lot of new custom development uses BOPF, and this is exactly the case when several developers could change the same class which is responsible for BO node determination/action/validation etc…

Best regards,

Aleh

[i-ivd]

While ABAP in eclipse catched up quite nicely in the recent months/years when working "alone" on a developement, this issue is still a big no-go as soon as you are working in a team of developers. There is no way of using ADT to work on ABAP classes due to the missing fine grained locking.

This is a bit sad.

Maybe this is a reason why we should all start using GIT ?

[Tamas_Hoznek]

This thread was started almost nine years ago, yet the described problem is still not resolved. I cannot believe this long time would not be sufficient for coming up with a fix for this, which is a significant impediment of ADT compared to the good old SE80 ABAP workbench that was able to do selective locking for ages.

To get around the problem, I always start editing individual objects in SE80 instead of relying on ADT. The interesting thing is that once this happens, ADT happily accepts it and I can continue changing anything via ADT that is already part of that TR. So, this means it is able to recognize that the changed object is already locked in my transport task, but for some reason it is unable to place the proper lock by itself. This is weird, but then how hard should it be to make this happen?

[19KnarfRed81]

Hi @ThFiedler ,

is there still no way to implement this requirement in ADT? As you write, there were already ideas for this 9 years ago. It is simply totally unfortunate if the whole class is locked in a transport request, even though you only want to edit a single method. For this reason, I work with the SAP GUI again when maintaining classes that are already active. Surely it must be possible to solve this? I will try out @Tamas_Hoznek's suggestion.

Regards Frank