Query transport

[Former Member]

Hi,

I often use the Transport Connection to transport new queries and query changes.

It always works fine.

But I actually don’t know how query elements are collected and I try to understand it now.

As an example, I created a new simple query. The generated name is 43E3SV5N2VIYTVIQYGCZT4KL0.

Using the standard procedure (Transport Connection), I put it in a transport.

I then look in the transport order (SE10) and find the different query elements with their technical name (they are of type "Elements of the Query Builder").

But I don't find the above mentioned technical name of my query.

Is it normal?

Does the system only need the query elements in the transport, and not the query itself?

How does the system then know what the name of my query is, to generate the same name after transport in production?

I know it works but I’d like to know how...

Best regards,

John

[former_member188975 · Accepted solution]

Hi John,

The transport always moves the query elements and these represent the various selection, calculations, etc in the query and also the query itself. You can see what a generated name like 43E3SV5N2VIYTVIQYGCZT4KL0 represents in tables like RSZCOMPDIR.

Hope this helps...

[Former Member · Accepted solution]

Hi Bhanu,

If the query is also of type query element and if it is also added in the transport order by the Transport Connection, why don't I see it among all other query elements in the transport order? By the technical name, I can identify all my formulas, variables, etc... But not my query.

Best regards,

John

[former_member188975 · Accepted solution]

Hi John/David,

I am able to see the query as a query element in SE16> RSZCOMPDIR and also in my transport request...

[Former Member · Accepted solution]

Hi Bhanu,

You're right, the request ID is in my transport order!

I looked for the <u>internal</u> request ID, which is different from the request ID in table RSZCOMPDIR and which is not in the transport order.

I don't know why this internal request ID is used for, but that was not the subject of my initial question.

Can you answer that further question?

Many thanks!

John

[former_member188975 · Accepted solution]

Hi David,

Which <u>internal</u> request ID are you refering to?

[Former Member · Accepted solution]

This is the one we see when we right click in a workbook result area.

The information tab gives this internal request ID + the ID of the workbook.

[Former Member]

Hi John,

you did you transport a new query or query in which you just changes something?

If you only changed something, it could be that the transport connection only collected the changed elements of the query.

Normaly if you transport a new query, you can find every element of the query in the transport request including the query itself identified by its generated id.

Regards,

Karen

[Former Member]

Yes it is normal, there is no difference between queries and othe query elements as formulas, variables... etc. All this objects have type query element.

In se10 you only see the reference to the object in transport request, not details as always and all object types in SAP.