You may have had this problem before. For some reason you have deleted an object in your development system previously, but now you desperatly need to delete that object out of your QA or production system. Failed transports or client copies may be a reason.
One option would be to open the target system (make it changable) and delete the object manually. This can obvioulsy be quite a hassle, considering the red tape you have to go through to open up the production box (if you get it at all in the time of SOx).
The other option would be to find the transport which initially carried the deletion. You can do that via SE03 and most likely it would be the last transport in that list. You can copy the transport into a new transport and move it across (ignore the warnings when releasing it).
Another, more creative, option would be to use the TMS – transport management system (TMS Help on SAP) to do the job for you. With most objects the technical name between the systems does not change and you can influence it (cubes, DSO, reports). Therefore you can just create the object in development, save it in the transport and then save the deletion in the same transport. Simple as this.
However, for some objects you cannot influence the technical name (transformations) or the technical name is not even the same across all systems (DTP, info packages). When being faced with these objects you can ‘abuse’ the way the transport import works. It would first import all the objects and in the second step activate them. During the activation, it would delete all the temporary versions. Hence if you manage to tell the activation process to delete all versions without importing, you should be good.
You can do that by creating a transport and putting the objects into the transport manually. Just use the same technical name these objects have in the target system. In the case these objects do not exist anymore in the source, the system may prompt you with an error message that the object has no directory entry. Just create the directory entry and you can save the transport.
I managed to successfully apply this technique in a SAP BI 7 environment, but I don’t see a reason why it would not work in other (ABAP based) SAP systems. Please be careful with this approach, as I do not take any responsibility if you manage to kill your production system 😉
If you came across better ways to transport a deleted object please leave a hint in the comments.