You can use this document to perform a simple transport from the standard area of your system. The prerequisite for this is that you have all of the required authorizations. The procedure described below deliberately does not explain specific details; these are contained in the following detailed documentation.
Global Area Objects
Objects that were created in the global area are entirely within the scope of the connection to the Transport Organizer. When creating the query component, you define the transport package in which the object is to be stored. In this case, therefore, no additional steps are possible. For more information, see Transporting Global Area Objects.
Standard Area Objects
Query objects are frequently created in the standard area, however. In this case, they are not automatically in a transport package, and, if necessary, need to be transported using the query transport tool. The following procedure describes the steps of a simple standard case. If you require additional information about this topic, you will find it in the subsequent sections.
You can use the SAP Query transport tool to both
Transport query objects from a source system to a target system
Copy query objects from the standard area to the global area (or from the global area to the standard area)
Both usage types can be used independently. For this reason, you can also call the transport tool from the global area.
Transporting Query Objects from the Standard Area
To transport query objects, you must have sufficient authorization. The export in the source system and the import in the target system require the value "Maintain environment" (23) for authorization object S_QUERY in both systems.
The transport itself is a system administrator task.
The transport essentially consists of three steps:
In the source system:
You can call the transport tool from the initial screens of the InfoSet transactions SQ02 or SQ03.
Choose the Transports button (Ctrl + F3).
Selecting the transport action:
To transport a query component, leave the default setting Export set here. For more information about other transport actions, see General Transport Description.
In the subsequent selection group, again leave the default setting, Test Run, set. When you later execute the transport, it then first leads to a test run that shows you in a results list all of the events that would occur during an actual transport. To avoid undesired overwrites, you should always ensure that you perform this step before you start an actual transport.
Selecting the transport options:
At this point, first select the type of query object that you want to transport.
You can only ever transport query objects in groups of the same object type. The only exception to this is that it is possible to bundle queries and InfoSets.
Enter the object name of the object to be transported. If you want to transport multiple objects simultaneously, you can specify a range of the list of existing objects here by specifying the first and last objects.
Selecting the import options:
You should usually select the import option REPLACE. This is therefore the default setting in the system. If there is already an object with the same name in the target system, the option REPLACE means that the data contained there is overwritten by the newly-imported data. More information about the other possible import options is available in Transport Type and in the documentation in the system.
Choose the Execute button (F8).
All objects to be exported are listed on the following screen.
Once you have checked the list, return to the transport tool screen and remove the Test Run selection.
Then choose the Execute button (F8) again to start the actual export. The transport request that you created is displayed on the following screen. You can now display and release the request in the Transport Organizer (transaction SE01).
The transport between system:
At this point, a transport takes place using the standard resources of the Transport Organizer. Contact your system administration team to have this transport performed.
In the target system:
After the transport has been successfully performed, you need to import the object into the target system. Call transaction SQ02 again in the standard area of the target system, and choose the Transports button to branch to the query transport tool.
Now select the transport action Import.
In the Dataset with Imports row, enter the number of the transport request that contains the transported query objects.
You can also perform a test run before the import. To do so, select the corresponding checkbox.
After you have performed the test import, the import log is displayed, and you can check the import of the individual objects.
To finally perform the import, return to the transport tool screen, and repeat the procedure after removing the Test Run selection.
For a detailed description of this transport process, see Transporting Standard Area Objects.
Copying Query Objects
You can copy query objects from the standard to the global area (or from the global area to the standard area) using the query transport tool. Note the following in this context, however:
If one or more query objects are moved from the standard area to the global area (or from the global area to the standard area), all relationships between the original and the copy are lost; two objects that are completely independent of each other are created. You should therefore avoid copying an object from the standard area to the global area just for the purpose of a simpler transport. If an object was first developed in the standard area and is now to be transported from the global area, it certainly makes sense then only to edit the object in the global area. It might be useful to delete the original object from the standard area in order to avoid misunderstandings.
The prerequisites and procedure are the same as when transporting query objects.