Error Cancelling Release of Basic Type

[Former Member]

Hi,

Im using WE30 to make changes to a BASIC type. So in the menu EDIT->Cancel Release an error prompted these messages:

The release of the basis types cannot be reset

Message no. EA506

Diagnosis

The release can only be reset if the basis type has been released in the current Release. Basis type ZPADET01 has already been released in Release 46C, so this release can no longer be removed.

Procedure

Create a successor to basis type ZPADET01 so this new basis type can be further developed.

I usually modify BASIC type with WE30 successfully. But this error message I'm at a lost.

Please Help,

Sid

[Former Member]

i'm no developer, but i think the longtext of that message is pretty obvious. seems, the basis type ZPADET01is from an elder release, knows about it, and you cannot reset it.

i have been trying to test it with this scenario: basis type created in release 4.5B (now in ECC 5.0), WE30 -> modify. i get error E0 690 saying that this type has alredy been released and thus cannot be modified. i tried the same test with another basis type, dto. created in 4.5B -> it is modifiable. the difference between the two is one filed only: the field 'basis release' says 610 in the first case and is empty in the second ...

[Former Member]

Hi Mylene,

Thanks for the reply. Yes we were in version 4.6c before and we upgraded to ECC 6.0. So are you saying that this BASIC type was released and transported to ECC 6.0 and hence it cannot be un-released anymore in this version? So I wonder what then does it mean:

Create a successor to basis type ZPADET01 so this new basis type can be further developed

Does it mean i just have to delete it and create entirely new BASIC type with the same name, structures and hierarchy?

Thanks,

Sid

[Former Member]

i wouldn't go about and delete it. just create a new one, let's say YPADET01. when you clicked the button 'create' there comes a pop-up where you can decide how to proceed. it is there where you can decide whether you want the new one to be a successor of ZPADET01.

actually, i have been doing some reading on the subject and found about that release-thing:

http://help.sap.com/saphelp_erp2004/helpdata/DE/dc/6b832543d711d1893e0000e8323c4f/frameset.htm

start there and dig a bit around, so you can get a better clue on how to go on.

sorry, that was the german link, here you go in english:

http://help.sap.com/saphelp_erp2004/helpdata/EN/dc/6b832543d711d1893e0000e8323c4f/frameset.htm

Edited by: Mylene Euridice Dorias on Aug 11, 2009 8:13 AM

[Former Member]

Hi Mylene,

Thanks again for the reply. I tried to explore the link you've given. I tried to find a way to simply "cancel release" and make changes to its child segment by adding new field, but unfortunately I don't find it in the documentation. I still can't "cancel release" because apparently it was transported from earlier 4.6c to ECC6 with the "release status on".

Creating a new BASIC type or extending the existing one seems problematic because there are number of programs dependent with the current name ("ZPADET01"). Choosing the "Create Successor" still won't allow you to add additional fields to existing child segments.

Anyway, thanks again with your effort of helping me.

Regards,

Sid;-)

[PatrickVermeire]

Hi Sid,

This is how I solved this problem.

For transaction WE30:

Go to SE11 for table EDBAS and go to change mode. Here you can change the release.

For transaction WE31 (I had the same problem here):

Go to transaction SE16N for table EDISDEF and use &SAP_EDIT for change mode.

Here you can also change the release.

Kind regards,

Patrick Vermeire

[Former Member]

Hi Sid,

Make sure that you have Debugging access (to use &SAP_EDIT functionality with in SE16N) in the system and ALSO lock the changes in Customizing transport request. This is important as you may not have have debugg access in your Production environment.

I am looking for a cleaner way of achieving this activity as I also did in same way of modifing table EDISDEF. I am searching for any other method and came accross this discussion.

Thanks,

Kishore.

[Former Member]

Hi Patrick,

I've tried your solution and it worked for me. Now, I would like to ask you how did you transport those objects and if you had any problems doing that.

Many thanks,

Vanesa.