Transporting Objects Between Query Areas (SAP Library - Human Resources Information System)

Transporting Objects Between Query Areas

Copying objects from one Query area to another is similar to transporting objects between different clients in a single system. Thus, you should go about copying objects between Query areas in much the same way as you would transport objects within the standard area. In principle, all objects may be copied to the other different Query area.

There are two transport options available on the initial screen of the Query transport tool that allow you to do this.

Copy Global Area ® Standard Area

Copy Standard Area ® Global Area

Both of these options are combinations made up of an export step and an import step. The only difference being that no transport dataset is created in transport table AQTDB and no transport request is generated in the Change and Transport Organizer. During import all of the usual checks are performed and a log is generated.

Copy Global Area ® Standard Area copies Query objects from the global Query area to the standard Query area. This corresponds to object export out of the global area and object import into the standard area. The options Test run, Overwriting allowed, and Transport Query variants perform the same functions as described in Generating Transport Datasets. You can choose which objects you want to transport by entering their names in the input fields on the transport maintenance screen.
The development classes of those objects copied from the global area are ignored, that is their copies in the standard area have no development class or are local objects.

Copy Standard Area ® Global Area copies Query objects from the standard Query area to the global Query area. This corresponds to object export out of the standard area and object import into the global area.

Pay attention to the following concerns related to development classes of objects copied into the global area:

If an object in the global area is overwritten, the new object copied in inherits the development class of the object overwritten.

If the object being copied into the global area is a new object, a window appears asking you to assign the object a development class.
Depending on what kind of development class you assign, it may or may not be necessary to assign a correction request as well. If the object being copied into the global area is a new Query whose assigned InfoSet or user group has a temporary development class, then the Query will automatically be assigned to development class $TMP. Whenever this happens, no dialog box asking you to assign a development class will appear.