Simpler way to create multiple TOCs?

[#1]

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!

[ceedee666]

Hi Jelena,

we use ToC in our normal development process to transport new or changed objects to QA. This has the advantage that development objects stay locked in the dev system. To simplify the process of generating the ToC we created a simple transaction that takes a transport request or a list of them as input and creates the ToC as a result. It's actually quite simple and works very well. I can share the core functionality if its helpful.

Furthermore, I created a eclipse plugin that does the same (cf. ).

As to your bonus questions; I guess your issue is that the task in the original transport request are not released. The standard functionality only adds objects form released tasks or requests when doing an include objects.

Christian

[SuhaSaha]

Hi Christian,

To simplify the process of generating the ToC we created a simple transaction that takes a transport request or a list of them as input and creates the ToC as a result. It's actually quite simple and works very well.  I can share the core functionality if its helpful.

If the program is not proprietary, can you share the code with the forum? Maybe a blog/document!

I have to deal with ToCs regularly & normally create one at the end-of-day for the config/dev objects. I was hoping there was a utility to automate the process for me

Do you follow any "best practices" w.r.t ToCs?

BR,

Suhas

[ceedee666]

Hi Suhas,

we basically use the best practices describe in the with respect to ToCs. It's a document written by the German SAP User Group (DSAG). We just recently started to work on a second version of the document. However, what is written in the document regarding ToCs is a very good starting point.

Regarding the transaction to create ToCs: I always though this is something everyone has in his toolbox. So I never thought it would be worthwhile sharing. I'll put the program in a shape I'm comfortable sharing with the critical eyes on SCN () and share it somewhere. Currently it'S still one of these things I have on my list of things that I should do right some day. So sharing it is a goot trigger to finally get this done .

Christian