Simpler way to create multiple TOCs?

[Jelena_Perfiljeva]

Is there a simpler way to create multiple transports of copies in SAP?

Lately we are frequently dealing with this odd but seemingly unavoidable process. There are multiple projects going on plus some SAP system realignment, etc. As a result, we end up with a temporary, isolated sandbox-like SAP system where configuration/ABAP changes are made. Later those changes (=transports) need to be moved to another system.

Management thinks it's a piece of cake, but what happens in reality is: we send a list of transports to the hosting provider asking to move them. In response we get - bwahaha, the TRs are "local", there are no files, so create TOC and then we talk. And here we go - SE01 -> create TOC -> include objects, wash-rinse-repeat about 20-30 times. (Yes, technically we could combine multiple transports into one TOC, but for some reason consultants are very particular about the order in which transports need to be moved even though there seems to be no reasonable explanation why unrelated configuration has to be moved in this exact order. Can you tell I've just done 24 TOCs manually? )

I looked everywhere but other than creating LSMW don't see any easier option for such activity. Is this really all we have in 2015?

And for the bonus points could someone please explain why when we do 'include objects' and enter the transport # the objects are not actually included and we have to do that using task number instead? Or am I doing something wrong?

Thank you!

[TomCenens · Accepted solution]

Hi Jelena

The best solution would be to avoid the "local" transport requests in the first place. To avoid it, you would need a transport target. If you only have a single system, this should still be feasible by using virtual systems.  Your SAP Basis resources should be able to help you out on this.

As long as you've got a target, you can change the target and in case of virtual systems, the virtual system(s) can be replaced by the actual system(s) once those are available thus avoiding the need to create TOC's out of local requests.

"And for the bonus points could someone please explain why when we do 'include objects' and enter the transport # the objects are not actually included and we have to do that using task number instead? Or am I doing something wrong?"

I would have to check that, dunno that by heart.

Kind regards

Tom