Is it safe to transport more than 100 of configs?

[Former Member]

Hi BASIS gurus,

We are about to go live and there are about more 100 configs per module that needs to be transported in prod. is it safe to transport those selected configs at the same time via import request button? or it is still best to transport it one by one? which is the best practice?

Thanks and regards,

Joel

[Former Member]

A practice to follow in the future is to have all transports assinged to a Project and import them together. Another rule of good practice is to transport everything into PROD excactly the same as they were tranported into QA, and make sure gets left in QA after a period of time it must go into prod ,

[Former Member]

Joel,

First of all check out with your functional guys of any dependencies that exist for those transport requests.

If there are none you can proceed with the import of transports but definitely not all the 100 configs at one go. It's always advisable to import them one by one but for ease you can probably select block of five requests at a time and import them.

Regards

Sourabh Majumdar

[Former Member]

Thank you all for the quick response. If you have a documentation or link or OSS to support this it would be highly appreciated.

Thanks and best regards,

Joel

[Former Member]

Hi,

Just check but it will not support the above answers

http://help.sap.com/saphelp_46c/helpdata/en/96/8a99386185c064e10000009b38f8cf/content.htm

It is the best way to keeping your system synchronized and consistent.

Practically avoid trasnport of multiple request unless must.

Regards,

[Former Member]

One by one is not the most efficient way of doing imports always. If you are sure about the sequence which you must normally be before moving transports to production ( i mean changes would have been tested out in quality) then use import all. Import all in way creates a single piece list of objects in transport keeping the version in mind and does the import. You may not save anry y time on actual import but definitely on generation of objects. Suppose there is an include in two separate transports used across several reports then SAP will try to generate all those reports for the first import and then again for the second one. Imagine if the same objects are in multiple transports then we are talking about a fair degree of redundancy. Import all avoids that by doing generation in the end. In my personal experince import all is much much quicker than import single provided you are sure about the sequence. It can save you a lot of time.

With Regards.

Ruchit

[Former Member]

Hi,

I would suggest you to do it one by one or atleast three to four requests at a time taking care of the sequence rather than importing all. This will help to find the transport which are going with errors properly and resolve them and also sequence of the transports.

Regards,

Sharath