Sie sind auf Seite 1von 15

Transport of SAP Query with Variants and Layouts from STANDARD or GLOBAL Query Areas

SAP queries can be defined in two areas namely Standard Area (Client-Specific) or Global Area (Cross Client). Here are the basic differences between the Standard and Global query areas based on query perspective. Standard Area: In standard area the query objects are client specific. These query objects are not attached to the workbench organizer, this means they cannot be created and transported according to standard correction and transport procedure. We cannot create system variants in standard area. We can still initiate the transport process using the Query transport tools (Export and Import).For the transport of a standard area query with variants and layouts we can use the program RSAQR3TR also. The variants and layouts cannot be overwritten in target client using the standard area transport. Standard area queries can be really helpful if we need the queries to be available in that particular client only. Global Area: In Global area the query objects are cross client.We transport the global area queries with Variants using the transport organizer. They can be created and transported using the normal correction and transport procedure. We can create system variants for Global area queries with the naming convention CUS&variant name.The Layouts for a global area query will need to be transported separately by a customizing workbench request.The advantage of this being, they can be overwritten in target client. We will take a query and will walkthrough the transport process from Standard area as well as Global area.

Standard Area Query Transport

A transport must be exported multiple times in order to transport the infosets, user groups and queries. We would need to follow the below order for transport 1) Transport the Usergroup 2) Transport the Infoset 3) Transport the Query along with variants and Layouts 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. 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

Page 1 of 15

Transporting a query means only the query itself is transported. Importing a query is possible only if a corresponding user group and a corresponding InfoSet exist in the target client and if the InfoSet is assigned to the user group Here we would invoke the program RSAQR3TR for the transport of a standard area query. Invoke transaction SE38 and run the program RSAQR3TR

The below screen appears

Page 2 of 15

First we would do a test run of the query Click on radio button Transport queries. Fill up user group and queries tab. Click on Radio Button Export You should also check the following boxes Test Run Overwriting allowed (only with Import/upload/Copy) Transport Query Variants (only with Import/upload/Copy) Transport of Query Layout Variants This ensures that the query needs to be overwritten if already exists in target client and we need to transport the Variants and Layouts attached to query also. Note: If Variants and Layouts with same name already exists for the query in target clients you should delete it before transporting, else would get the error message Variant (name) not Accepted (Already exists) Layout Variant (name) Not Transferred (Already exists)

Execute the query. The below screen appears

Page 3 of 15

Verity the Export whether the variants and layouts are properly attached to the query Once the export look good, you can go ahead with the real run Remove the test run and execute. This creates a transport request

Invoke transaction SE10 and you can release the Transport request ECDK905778.This creates an entry in the transport table AQTDB

This completes the EXPORT Process.

Now we will see the IMPORT process in the Target Client

Page 4 of 15

Log in to the target client Invoke transaction SE38 .Run the program RSAQR3TR and do an import with Test run. Here you will need to give the Dataset Name with Import (ECDK905778)

Once the import looks good, you can uncheck the test run and import the query

Cross check whether the Query along with Layouts and variants and transferred correctly without errors.

Page 5 of 15

Here are the Pros and Cons of using a Standard area Query Pros: Query is always client Specific. Users can create and maintain on individual clients Can be created as a local object Cons Can only Select all Variants or None for a particular query for transport Variants cannot be overwritten Layouts cannot be over written

Note: One other way of transporting SAP query from Standard area is by using Tcode SQ02 (SAP Query Infoset) or SQ03 (SAP Query User Group); Go to ENVIRONMENT > TRANSPORTS

Rest of the steps would be the same as stated above for Standard area Transports Page 6 of 15

Global Area Query Transport

The Global Area queries are transported through normal workbench request. Once after you create the SAP query you will need to assign it to a package. Here we are assigning it to a package called ZQY

Once we assign the query to a package, it would ask to include the query in a Transportable Workbench request.

Once you invoke the transaction SE10, you could see your Request number under Modifiable workbench request. Creation of Variant for a Global Area Query Invoke transaction SQ01 Select the Query and hit the Execute button Page 7 of 15

Once your input Screen populates click on the save button which pops out a screen for saving the variant attributes of the screen.

You can save the variant as CUS&xxxx where xxxx the name of variant. By prefixing CUS& with the variant name it would create as a system variant which is transportable automatically.

Page 8 of 15

You may include it in the same transport request which we had assigned for the query.

Once you login to SE10 you could see the query as well as the variant under workbench request

Creation of Layout for a Global Area Query Note: The Layouts for the Global Area query will need to be transported separately since it is created as a Customizing workbench request For creating the Layout transport follow the below steps Once your query output comes, Click on Settings Layout Saving

Page 9 of 15

Save the Layout under a desired name

Goto the Layout Management

Click on Layout Transport

Page 10 of 15

You can include it in a Transport request

Invoke SE10, and under customizing workbench request you could see your request

Page 11 of 15

The advantage of Global Area queries are They are easily maintainable The Layouts can be overwritten The Variants can be overwritten Have the option of transferring the layouts and variants attached to a query selectively

Page 12 of 15

Steps for creating Transaction for SAP queries

1) Invoke transaction SE93 2) Enter the transaction code and click create

3) The below screen populates. Enter the short description of the query and click on
Transaction with parameters (parameter Transaction) and press Enter

Page 13 of 15

4.1) In the below screen fill in all the columns as stated below
In Transaction tab enter START_REPORT Check Skip initial screen Check SAPGUI for HTML Check SAPGUI for Java Check SAPGUI for Windows

Page 14 of 15

4.2) In Default values tab you will need to enter the following values

Name of Screen field


AQ Parameter indicating ABAP query this value is default for all queries ZKY_PA G here ZKY_PA represents the user group for the query and G staring at 13th position represents that the Query is global. Test You will need to enter the query name here CUS&Test This represents the Variant used with the Query


5) Once you have entered all the above you can save the transaction which will ask you
to enter it into a package like below. Once you assign to a package the transaction is ready for the transport process

Page 15 of 15