Skip to Content
What was your first feeling when you saw a transport with the query you wanted to transport? Did you feel lost? embarased? angry? entertained? I remember very well that I was really confused, when saw something like this for the firt time:
Example query transport

I looked at this transport content, and could not undertand why there are 323(!) objects with strange names, when all I wanted to move were just 3 queries… Do I tranport something extra, something that is not needed, or not required to be transported now? If there are so many objects for very few queries, how would I know that ALL needed objects are in the transport?

It took me some time before I learned to understand the content of transports created with BEx Suite, and this is the learnings I want to share with you in the series of my blogs. So, part two will be about what Query Elements ARE, and what ARE NOT.


To report this post you need to login first.


You must be Logged on to comment or reply to a post.

  1. Vitaliy,
    There has been a confusion for me about transporting the Bex query elements. And, I am looking forward to hear about the same from you…


  2. Former Member
    Well, you may be looking at BEx transport. BEx transports keep all BEx elements which has been changed by all query developers. The right way is to create your own transport using transport connection. If you release BEx transport before you create your own transport, it will give you less problem. Offcourse, you have to create another BEx transport before any one do query development.




Leave a Reply