Deleting Methods from Parent Class

[Former Member]

Hello,

In advanced, thank you for any advice that can be offered for this basic question.

Problem:

I am having issues deleting custom methods and classes, that I have created using SE24 or SE80.  I am working on a development machine, so these classes may be safely deleted.  Basically, I am developing a solution for a customer and during the development stage I wanted to make sure things were working the way I expected.  So, I created many classes, inheritance methods, etc.  But now, I want to go back through and clean up my mess.  In JAVA, C#, C++, or any other language I simply find those objects and delete them and then go back through and clean up.  However, in SAP I find that the transport organizer gets in the way.  Is there a way to flush the memory of the transport organizer, so that I can activate my classes and not get bogged down in non-sense error messages?  If I try to activate the objects, while marking the methods to be deleted, then the system typically "times-out" after a long period of 15 minutes.  I would think that SAP could delete a method in under 15 minutes.....

Attempted so far:

1) I have tried to use all the options in Utilities-->Clean Up.

2) I have tried to release those dependent transports using SE09, but SAP tells me that some "CM00# is inactive", I think this is telling me that the methods I deleted are inactive (no kidding, I deleted them).

3) I have tried to manually add the methods back, then activate, transport, and finally delete, but I still get the same "loop dependency" problem. 

I have found many related issues on SCN, but never a answer.  Is this the price we pay for trying to conform ABAP to a OO language?

Thank you,

Greg

[Former Member]

Hello,

In advanced, thank you for any advice that can be offered for this basic question.

Problem:

I am having issues deleting custom methods and classes, that I have created using SE24 or SE80.  I am working on a development machine, so these classes may be safely deleted.  Basically, I am developing a solution for a customer and during the development stage I wanted to make sure things were working the way I expected.  So, I created many classes, inheritance methods, etc.  But now, I want to go back through and clean up my mess.  In JAVA, C#, C++, or any other language I simply find those objects and delete them and then go back through and clean up.  However, in SAP I find that the transport organizer gets in the way.  Is there a way to flush the memory of the transport organizer, so that I can activate my classes and not get bogged down in non-sense error messages?  If I try to activate the objects, while marking the methods to be deleted, then the system typically "times-out" after a long period of 15 minutes.  I would think that SAP could delete a method in under 15 minutes.....

Attempted so far:

1) I have tried to use all the options in Utilities-->Clean Up.

2) I have tried to release those dependent transports using SE09, but SAP tells me that some "CM00# is inactive", I think this is telling me that the methods I deleted are inactive (no kidding, I deleted them).

3) I have tried to manually add the methods back, then activate, transport, and finally delete, but I still get the same "loop dependency" problem. 

I have found many related issues on SCN, but never a answer.  Is this the price we pay for trying to conform ABAP to a OO language?

Thank you,

Greg

[Former Member]

After playing around for a few hours I figured out a "non-optimal" way to solve this problem.

You need to add back every single method and object that you created, since the last time you released.  You can leave the method body blank, SAP just needs to see it as part of the definition.  That means there will be a lot of incremental adding and activating.  Once, you are able to release the transport do so.  Now go back and create a new transport to delete each method and object one at a time and release those incrementally.

If someone knows a better way, please post. 

Thank you,

Greg

[matt]

This is not an OO problem. You'd get pretty much the same with a function group. It's the way CTS works.

Go to SE03, and unlock your transports. Then go to SE09 and delete all the entries relating to classes. Then add in every class you want to keep as R3TR CLAS classname. Lock all the objects again and release.

Or, delete all your transports (after unlocking), and create new ones directly by adding them in (in SE09) from the package that you created just for your development. (Insert objects).

If you activate everything in your worklist, ignoring errors, the ....CM... error won't appear any more. But if you release the transports, you'll end up with stuff you don't want in your test system.

If you've transported classes to test that you now want deleting, make sure the class is deleted in dev, then create entries (R3TR CLAS) in a transport for those classes - release and import.

I've been developing in ABAP Objects for years. I've never encountered problems like yours.

[Former Member]

Thanks Matthew this clears things up.  As a follow on to your response, I found the following information about (R3TR CLAS) useful.

http://help.sap.com/saphelp_nw04/helpdata/en/0a/bb6736c4b411d2958b00a0c94260a5/content.htm