"Object is original and not local" in STDR. How to fix?

[Astashonok]

I'm trying to fix outdated entries in TADIR created by me and facing this problem.

The objects were already deleted but the entries are still in the TADIR. I do not understand about which originality it means, all the Z objects in my system has the current system SID in TADIR-SRCSYSTEM, even the local ones in $TMP, both existing and deleted.

Yes, I read 1915580 note, but the solution steps described there did not help. I added those faulty object into TR, released it and nothing. The entry in TADIR left intact.

Any other workaround or dirty hack?

[FredericGirod]

Did you check 1915543 - An object that has been deleted still exists in TADIR ?

[raymond_giuseppi]

Did you already read STDR : Is this safe to run in all systems for SAP and customer objects

[Astashonok]

frdric.girod thanks for reply. Note 1915543 say the same as 1915580 (which is now unavailable), it describes how to use STDR. I did all by its steps, and still receive "Object is original and not local". Any suggestions?

[Astashonok]

raymond.giuseppi thanks for the link. What should I pick from those help article? That "not all inconsistencies are real inconsistencies"?

[raymond_giuseppi]

To be sure, did you use the 'delete' icon to get this message (can you paste a screenshot with the message)

• You can delete local TADIR entries without transport request ($TMP and local defined packages)
• For the other ones (original but not local ones, package with a transport layer) a TR is required (Did you look for unreleased TR, did somedy do some dirty delete or remove manually objects from TR?)

[Astashonok]

> did you use the 'delete' icon to get this message (can you paste a screenshot with the message)

yes, the above message from the question screenshot pops out just after I press Delete button on STDR object.

Yes, I tried putting it into TR and release but that didn't help. Does it matter this is local TR or TR with a proper target group?

The more weird thing I face that I has two objects, both are listed within "object directory entries without objects" but when adding them into TR, the 2nd one throws following error, but the first one is added fine.

How the 2nd object can lack the record in obj directory if it is listed in this section?

[raymond_giuseppi]

Did you notice that you clicked on the (customer) ZCL object and the error message is on the (sap) CL object? ?

The transaction may be wrong, it may not be a class but an enhancement, look for an R3TR ENHO object with a similar case (this is one of the cases described in the linked document).

[Astashonok]

sorry, it was a typo, now it was added to TR finely. The only thing it didn't help in anything.

I released that TR, imported into subsequent system. Re-run STDR task and these objects are still in the list "object directory entries without objects" and I still cannot delete ti with the same error.