Transport query not work-load program not found

[former_member709286]

Hi Expert team;

We have transport query by export as have new transport request number . Then we import to another client.

We also regenerated infoset and query too.

We can run query from SQ01 but we cannot run from new t.code which we set up in SE93 and link to query program name.

Error load program not found.

Any hint will be very helpful.

Thanks in advance.

[TammyPowlas]

On the surface, it sounds like you need to transport the query to another client, and not by importing. Importing is client dependent, transports are client independent and if you want to run it by transaction code, the query has to be client independent

[former_member709286]

hi Tammy

how to make query -client independent pls.

What is the steps to transport query pls.

What we have done is:

SQ02 export -we got the TR

We do SQ02 import TR again.

But when we link program name to t.code we cannot run query from new t.code.

Error:Load program not found.

[TammyPowlas]

You have to save the query in the global area - see https://dokumen.tips/documents/sap-abap-query-creation-tutorial.html

[jmodaal]

Hello,

the names of the generated ABAP programs for queries are not permanently valid - a regeneration could create ABAP programs with another name than before (and a regeneration could also be done implicitely at importing support packages, upgrades etc).

Therefore, don't use the names of the generated programs of queries. You can use the query in a transaction following this procedure (quite sure that somewhere there is an SAP note describing it).
Example: start a query 'USERS' in the user group 'BC'.

Create a transaction in SE80 ("Transaction with parameters (parameter transaction)")

This will be valid even after re-generations of the InfoSets (done explicitely, or implicitely after implementing support packages, upgrades etc.).

By adding D_SREPOVARI-VARIANT also a variant name can be given, if needed.

[jmodaal]

Hello,

found an SAP note: 393160.

There is also another solution available via program SAP_QUERY_CALL. In that case you would create a "Report transaction" and use SAP_QUERY_CALL with a variant, which specifies the User group and the query (and a variant if needed).