DataSource from a productive package to local package

Question

I need to move a DataSource from a productive package (ZUPG) to the
local package ($TMP). From transaction RSA6, I've chosen the "Object
Directory" and tried to change the assignment.
However. the system prevents the user from moving an object from a
productive package to a local or test package. This is the message you
would get if you tried and changed the package to $TMP:
"Object R3TR OSOA 0REGION_TEXT has already been exported and is
therefore known in other systems. It is therefore not possible to
change the package from productive to local (private), since
inconsistencies and errors can occur."
In theory, this should be circumvented by deleting the DataSource, and
releasing the change request thereafter. The DataSource's entry in
TADIR should get deleted and it should be possible to choose the
package $TMP when re-activating the same DataSource again in the system.
However, this is not the case in my system. The entry is not deleted
from the TADIR, even after having released the request which contained
the (deleted) DataSource!
The question is: what could have caused such an inconsistency in
the system's TADIR? Why the entries aren't deleted after releasing the
change request, even though the DataSource had been deleted from the
repository?
Thanks!
Simo

Answer 1

Hello Kris,
unfortunately your suggestion doesn't work.
As Simone explained in his first message, in fact the system prevents the user from changing the DataSource's directory entry, with the following error message:
<i>Object R3TR OSOA 0REGION_TEXT has already been exported and is therefore known in other systems. It is therefore not possible to change the package from productive to local (private), since inconsistencies and errors can occur.</i>
The system documentation proposes the following steps to switch an object to a local package:
<i>1. Use the appropriate editor to copy the object to a local object with a different name.
2. Then delete the old object. A change request is used to transport this deletion to the other systems.</i>
Finally it is possible to rename the local object.
In other words, the DataSource is in a productive package, and it's been registered in a transport request.
As soon as an object is inserted in a productive package, you're not allowed to move it back to a local or test package anymore. You need to delete it, release the change request and recreate (re-activate in our case) the object again.
However, the system doesn't prompt the user for a package during re-activation (please refer to my previous post), because the involved entry in TADIR is not removed from the transport request at release time.
Cheers, <a href="https://wiki.sdn.sap.com/wiki/display/profile/Davide+Cavallari">Davide</a>