Skip to Content

Learning SAP BW, The Twitter way – BW-Tweet #16

Thanks for all the support to this series and I look forward to your continued support. Now we are more than 350 on @sapbwtweet, many thanks for being there. Those of you who are still not there, be the part of group at


We are almost halfway through 2010, take a break rather take a deep breath and think –


  1. In last 6 months – Which event impacted or has potential to impact your chosen professional area most?
  2. Or what happened in Enterprise solution space to have impacted product or solution of your interest and how are you going to tackle it?


While you are thinking here is a small tip to help you in your present job –




I keep seeing lot many questions on SDN forum about BW transports, sequence etc. While going through those threads I realized each one of us in apprehensive about collecting BW objects in different transports and the sequence of those transports.


I discussed with quite a few seasoned consultants and each of them had his own comfortable way of handling those. But the one I liked most and found more generic to be used (based on my experience) came from a friend of mine (a BW expert) –


Source System Transport

  1. Source system transports – FIRST to GO


BW Transport (only one is needed)

  1. Collect your process chains (with necessary objects) in a transport – It shall bring in all the objects including your delta DTPs.
  2. Collect your Initial Infopackages, which are not part of process chain.
  3. Query / web templates / RRI – LAST to GO.


Send them (2, 3, 4 all in one) in one go after successful transport of 1. No need to create multiple transports; no need to worry about sequence etc.



Needless to say try it on Sandbox, development system before attempting on production environment.


See you soon!!!




Disclaimer – Idea is to learn something in couple of seconds without going through lengthy blogs or articles. BW-Tweet hopes to exist with blogs and articles rather than replacing those. Also this is reproduction of concepts and in no way qualify as an original piece of work.

You must be Logged on to comment or reply to a post.
    • +1.  I had a BW consultant that did exactly this and the Basis guy came running into the office…  wanted to know why the transport was larger than the last support pack he had downloaded and applied.

      Consider breaking them up by logical area; Finance, Sales, HR, etc.

      • Hello Nathan,

        Thanks for your interest and comment on the blog.

        I agree sometime we need to break into smaller ones. What I meant was breaking up like – infoobjects transports, dsos transports, cube transports etc and then keep wondering about the sequence.

        rather collect the process chain (not all process chains in one transport) wise transport and move those.



    • Thanks a lot Vitaliy for your interest and comment on the blog.

      I agree,sometimes it is advisable to break the transports. I shall rather break them as per process chain or by functional area rather than by Infoobjects, Infocubes, DSOs etc (unless there are some restrictions to do that).



  • This approach is very effective for the initial transports as part of cutover activity when there is no data in DSO’s or cubes in the QA or Prod Systems.I have been using the same for last couple of projects without any issues.

    This should not be used if you are clubbing all the objects with data in a single transport, transport will run forever or it may fail as well.

    Also, I would like to add point 4 for the people who have Bobj integrated in Netweaver. We should have Bobj ( Universes / Reports ) in a separate transport and imported after 3 is done.