on 02-21-2018 2:32 PM
Hello, sorry to borrow the title from this thread 4 years ago by julius.vondembussche, but I have exactly the same question, and the solution given by Julius looks promising but I can't make it work :
I need to revert the changes of tens of objects (including new objects) to deimplement a few SAP notes applied one year ago (concerned people have left), each note having several manual actions. All these notes and objects are in one transport request (which is released but never transported).
The simplest way to make sure everything comes back to normal, is to take the original objects from another system, and transport them to overwrite the objects to revert. Of course, I made sure that the objects were not changed by other transport requests.
Unfortunately, the issue is that I want to add non-existent objects in the transport request so that the new objects are deleted automatically during the import. But it's not permitted -> error TK313 Object requires an object directory entry.
If I apply the solution by Julius, I'm stuck in the third step, maybe the ABAP release is different between Julius' system and mine and possibly the issue originates from the second step:
Do you have any idea how I could apply Julius solution, or any other solution to "transport non-existent objects" automatically to delete them in the target system?
Thanks a lot!
Sandra
PS: my SAP release is ABAP 7.40 SP 7 (ECC 617 SP 5).
I wouldn’t recommend this to just anyone, but why not try to just programmatically insert the entries into E071*? You can do a little test transport in a sandbox and see. The transport system is pretty old and has a reasonably simple structure.
Alternatively an enhancement to bypass TK313 temporarily and add the objects.
Thinking about it, I’d try option 2 first.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks. I tried the first option by using the transaction SE16N (as it's an ERP system). I had thousands of entries to add in E071K too. I released the transport request, no error message. The import changed and deleted the objects as expected.
So, no official way, but easy to do! 🙂
This, and a little RFCing. Quick, dirty and dangerous, but amazingly effective.
Glad to hear it worked even better than I hoped.
It occurred to me that I’m usually the one banging on about "no direct updates", sticking to SAP processes and BAPIs and such. So I thought it’s probably appropriate to explain to other readers why this was one of the rare occasions to throw the rule book out the window.
In short, the factors that made me think this is the best approach is:
User | Count |
---|---|
88 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.