ABAP Query Transport request related

[Former Member]

Hi,

I have created a Abap query,

1) User group

2)Infoset

3) Query

But when i transport the request in to Quality, I can see only Infoset, not able to see User group and query which i created in the

Development

Please suggest, is this std behaviour or is anything missed

Rgds,

Jai

[Former Member]

have you kept them in one TR? check that TR in the system from which you have transported.

[Former Member]

Hi Soumya thanks for reply.

Yes, I have kept all three in one TR,

Ok to correct the issue, what needs to be done..

Rgds,

Jai

[Former Member]

Hi,

ABAP Queries can be transported to different clients by the following two ways:

1) By using the standard program u2018RSAQR3TRu2019

2) By using the transport option available on the application bar in Transactions SQ02 or SQ03.

Menu->Environement->Transport:

On the next screen, all the options come up for transporting the queries

The transports are to be made in the following order:

1. User Group transport

2. Infoset transport

3. Infoset and Query transport

4. Queries transport

Hope this helps you

Regards

Shiva

[Former Member]

Hi Shiva,

For Example.

User group: XYZ

Infoset :ABC

Query:PQRS

Now i have created the TR and imported in to quality and if I see in quality i can see only Infoset ABC in QA there is no User group and Query

as u suggested i have run the report RSAQR3TRu2019 in development in which i originally created query

but getting many options in that, could you pls suggest

1) which system I have to run this report

2) Already infoset is avialble in Qa

3)Do i need to create one more transport for missing user group and query

4) without TR is this report will transort the query in to Qa and production

Regards,

Jai

[GauthamV]

If all the three are in same transport request they will defnitely move to QAS.

You better do some minor changes and create a new request in DEV and include

all the three in 1 request and transport.

[Former Member]

Thanks to all,

I just created TR with new package for user group and included ifoset and query in the same TR

and imported, issue is resolved

But my question is,where we can utilize below help material, I have spent much time to understand below given explaination and finally left without any conclusion

*************************************************************************************************************************************

Short text

SAP Query: Transport tool

Description

The report RSAQR3TR handles all tasks concerning the transport of queries, InfoSets and user groups.

General information

Queries, InfoSets and user groups are stored in the table AQDB. This table is client-specific. For the transport of queries, InfoSets and user groups, there is a special client-independent transport table called TAQTS. You can carry out transports either

· from a client (source client) of an SAP system to another client (target client) in the same SAP system or

· from a client (source client) of an SAP system (source system) to a client (target client) in another SAP system (target system).

In both cases, you have to perform similar actions.

The objects to be transported must first be copied from the source client using an export from the table AQDB into the transport table TAQTS. At the same time, a transport request is created for the transport system that includes all entries created by the export from table TATQS (transport dataset). The name of this transport request conforms to the transport system naming conventions (sysKnnnnnn) and is included in the export log. The transport dataset is stored in the table TAQTS under a key which matches the name of the transport request.

If you are transporting within one SAP system (from one client to another), you can import the transport dataset from the target client. The name of the transport request to use for this purpose is that specified during the export, since it should match the key of the transport dataset in the table TAQTS. With this import, the transport dataset is read from the transport table TAQTS and inserted into the table AQDB, where extensive checks ensure that there are no inconsistent statuses in the table AQDB.

If you are transporting from one SAP system to another, you must first use the transport system to release and export the transport request generated by the export. This transports the transport dataset from the transport table TAQTS into the target system. Then, you can import from the target client of the target system, as described above.

The transport datasets generated by exports in the transport table TAQTS are not deleted after successful import unless this is explicitly requested. Therefore, you can import a transport dataset several times (when copying a functional area to several different clients, for example).

This report handles exports (generation of transport datasets), imports (reading of transport datasets) as well as the management (display and deletion) of transport datasets.

As transport action, you must specify one of the values EXPO (export), IMPO (import), SHOW (display transport dataset) or DELE (delete transport dataset).

Transport action EXPO (exports)

If you select the 'Test only' parameter when exporting (no blank characters), the system determines only those queries, InfoSets and user groups that would be selected according to the selections for transport described below and generates an appropriate log. A transport dataset is not generated in the table TAQTS. This allows you to check whether a selection really includes the queries, InfoSets and user groups to be transported.

With exports, there are four different options for selecting objects (user groups, InfoSets, queries) to be transported. These are 'Transport of user groups', 'Transport of InfoSets', 'Transport of InfoSets and queries' and 'Transport of queries'. You must choose exactly one of these transport types.

In each case, you can also define an import option depending on the transport type. This allows you to determine how the transport dataset is inserted in the table AQDB of the target client during a later import.

The import options, each of which has an abbreviated syntax,

are as follows:

REPLACE or R

MERGE or M

GROUP=ug or G=ug (ug = name of a user group)

UNASSIGN or U

If you use the transport type 'Transport of user groups', all user groups are transported according to the select option 'user groups' and the selected import option. The import options REPLACE and MERGE are allowed.

If you use the transport type 'Transport of InfoSets', all InfoSets are transported according to the select option 'InfoSet' and the selected import option. The import options REPLACE, MERGE, GROUP=ug and UNASSIGN are allowed.

If you select the transport type 'Transport of InfoSets and queries', all InfoSets are transported according to the select option 'InfoSets' and the selected import option. The import options REPLACE and MERGE are allowed. Also, all queries are transported for each functional area selected, according to the select option 'queries'. In this case, the user groups of the queries are irrelevant and only the import option REPLACE is allowed.

This transport type allows you to transport a modified InfoSet and all the associated queries.

For the transport type 'Transport of queries', all queries are transported according to the select option 'User groups' and the select option 'Queries' as well as the selected import option. The import options REPLACE and GROUP=ug are allowed.

The export log displays which user groups, which InfoSets and which queries are transported, as well as the import options used.

Transporting a user group

Transporting a user group means transporting all members of the group from the source client. However, the InfoSet assignment to the user group in the source client is NOT transported.

The import option REPLACE first deletes all members of the group in the target client and then enters the members from the source client.

The import option MERGE leaves all members of the group assigned in the target client and adds the members of the group from the source client.

Entering a new member in a user group in the target client is possible only if a user master record exists.

In the target client, the assignment of InfoSets to this user group remains.

Transporting an InfoSet

Transporting an InfoSet means transporting the InfoSet and the InfoSet assignment to user groups in the source client.

Importing an InfoSet is possible only if the same logical database exists in the target client. Extensive checking is also performed to ensure that there are no inconsistencies between the InfoSet and the logical database.

The import option REPLACE first deletes the assignment of the InfoSet to user groups in the target client, provided there are no queries dependent on the InfoSet. The InfoSet is then transported to the target client and the assignment of the InfoSet to user groups is copied from the source client, if user groups also exist in the target client.

The import option GROUP=ug first deletes the assignment of the InfoSet to user groups in the target client, provided there are no queries referring to the InfoSet. The InfoSet is then transported to the target client and assigned to the user group ug of the target client, if such a user group exists.

The import option MERGE leaves the assignment of the InfoSet to user groups in the target client and transports it to the target client. It then copies the assignment of the InfoSet to user groups from the source client if user groups also exist in the target client.

The import option UNASSIGN first deletes the assignment of the InfoSet to user groups in the target client, provided there are no queries referring to the InfoSet. The InfoSet is then transported to the target client. No assignment of the InfoSet to user groups is performed.

Transporting a query

Transporting a query means only the query itself is transported.

Importing a query is possible only if a corresponding user group (see below) and a corresponding InfoSet exist in the target client and if the InfoSet is assigned to the user group. To demonstrate the effect of the import options, suppose that the query has the name QU and belongs to the user group BQ in the source client.

The import option REPLACE overwrites the query QU of the user group BQ in the target client if the user group exists.

The import option GROUP=ug overwrites the query QU of the user group UG in the target client if the user group exists. In this case, the query is explicitly assigned to a user group in the target client. This target user group may be differnet from the user group in the source client.

Transport action IMPO (imports)

If you choose the 'Test only' parameter with imports, only a test import is performed. This means that the system performs checks as for a real import and generates an import log. The import log contains information on the locks that have to be set. With a test import, you can check whether a transport dataset can be imported without any problem and which changes it would make in the table AQDB of the target client. A test import itself never makes changes in the table AQDB of the target client.

All transport datasets are imported according to the select option 'transport request'. In this case, the system outputs a detailed log of all checks carried out and all changes made in the table AQDB.

If you select the parameter 'Delete after successful import', the transport dataset in the table TAQTS is deleted after the import of each transport dataset if no errors occur during the import.

Transport action SHOW (display)

All transport datasets included in the transport table TAQTS are output with name (also the name of the transport request) and contents in the form of an overview.

Transport action DELE (delete)

All transport datasets are deleted according to the select option 'transport request'. To avoid unintentional deletion, the select option 'transport request' must contain values, meaning that the transport action DELE is not performed if this select option is empty.

******************************************************************************************************************************************************

Transport of ABAP Query

I am involved in this upgrade project to 4.7

The users are not able to find any reports (in QA System) which were there before the upgrade in SQ01. But they can see them in production which is not yet upgraded. They want me to copy all the reports to the QA system now....I dont have any idea how to do that.

I remember a similar problem upgrading to 4.6C from 4.5B ......

Take a look at OOS note 672784.

You can transport queries between systems in SQ02 (hit the lorry button) or run program RSAQR3TR.

You download the infosets, queries etc into a file and load them into whichever system you wish.

Just wanted to share my experience of transporting queries:

I needed to move a user group, 2 infosets and 3 queries from a 4.6 system to a 4.7 system.

When I tried doing this via the SQ* transactions I did not get the import/export option, so instead ran RSAQR3TR.

Step 1. Run RSAQR3TR in 'old' system. Select EXPORT and specify the objects to be transported.

(System includes these in an automatically created transport request)

Step 2. Release this transport and request it be transported to 'new' system.

(This results in the entries being populated in transport table AQTDB in 'new' system).

Step 3. Run RSAQR3TR in 'new' system. Select IMPORT and tick the Overwrite checkbox. Specify the transport number in the field labelled 'dataset with imports'.

(RSAQR3TR gives the message that stuff has been imported OK).

Step 4. In my example I still couldn't find the queries, so ran RSAQR3TR one more time, this time specifying 'Copy Standard Area -> Global Area'.

(Now my queries etc were available in new system).

Perhaps there are better ways, but after 1.5 days of struggling I was glad to get this far.

*****************************************************************************************************************************************

regards,

Jai

[Former Member]

*

Edited by: M Jairaj on Aug 7, 2009 8:02 PM