Object Type with errors set to OBSOLETE.

[Clucking]

Hi,

We have a very seriously problem, hopefully some of you guys could come up with suggestions:

In a newly upgraded 7.0 system with SP 7, upgraded from 4.6C, we have got a problem with a custom object type (not a subtype). After upgrade, table SEWAFUBA is no longer in the system, but we have used this table as reference in an attribute of the object type. Therefore the object type could not be generated. We were not allowed to change the attribute since it was created in 4.6C so we decided to create a new attribute and set status for the old one to OBSOLETE.

By mistake the object type itself was set to obsolete and now we cannot get it back to a status where we can change it: If we try to set status IMPLEMENTED we are told that the new status should at leased be RELEASED. If we try to set RELEASED we are told that this is only possible if it is possible to generate the object type. But we cannot change the object type because it is in status OBSOLETE…

We are also not allowed to delete the object type because it was build in ver. 4.6C otherwise we could copy the object type, change it and copy the new one back to the old name.

The object type is used in a very large workflow in a lot of tasks so we would really appreciate a solution which makes it possible to still use the old object type.

Thanks in advance.

Best regards,

Claus Lücking.

[former_member186746]

Hi,

Here's a trick to force something in SAP.

Try to change the status.

The SAP system eill give an error message, note the message number.

Now type /hs in the transaction box and try to change the status again.

In debug mode go to watchpoints and click on the button Create watchpoint(Shift+F8)

Now create a watchpoint for sy-msgno = the error message number.

Press F8.

This will put the cursor to the place in the abap code where the error is generated. Usually these follow a condition met in an if-statement.

e.g:

if sy-subrc ne 0.

message e....

double click the if statement line, this will set a break-point.

Now press save.

by pressing F8 you'll return to the transaction.

Now for the third time try to change the status, you'll now be redirected to the if-statement (or something like that) change the returncode (in most cases) so that the message does not get shown.

And you're done.

Kind regards, Rob Dielemans

[Clucking]

Hi Rob,

Im sure your suggestion would have solved the problem but my customer prefered to report the problem to OSS. (Therefore this late respons).

There he got a very nice answer which Im glad to share with everybody:

Standard report RSWO_RELSTATE_CORRECT do the trick!

Best regards,

Claus.