Queries, InfoSets and standard area user groups are usually stored in the client-specific table AQLDB. When transporting these objects, however, you use the transport table AQTDB, which is not client-specific.
You can transport objects either
from one client (the source client) to another client (the target client) within the same SAP system
or
from a client (source client) of an SAP system (source system) to a client (target client) of another SAP system (target system).
In both cases, you use similar procedures. For an overview, see the graphic in Transporting Query Objects.
There are two options for performing transports. The first of these involves using the transport table AQTDB and the transport actions Export and Import.
You must first export the objects for transport from table AQLDB to the transport table AQTDB.
This creates a transport request for the transport system that includes all entries created by the export from table AQTDB (transport dataset). This transport request is assigned a name in accordance with the conventions for the transport system (sysKnnnnnnn).
The name of the transport request is listed in the export log.
In table AQTDB, the transport dataset is stored under a key which matches the name of the transport request.
If you are transporting within one SAP system (that is, only from one client to another), you can also import the transport dataset from the target client.
In this case, you use the name of the transport request which is specified during the export and matches the key of the transport dataset in table AQTDB.
During this import, the system reads the transport dataset from the transport table AQTDB into table AQLDB. At the same time, it performs numerous checks that ensure that there are no inconsistencies in table AQLDB.
Both export and import are functions of the SAP Query transport tool.
If you are transporting from one SAP system to another, you must use the transport system to release and export the transport request created by the export.
This procedure transfers the transport dataset from the transport table AQTDB of the source system to the transport table AQTDB of the target system. Then, you can perform an import from the target client of the target system, as described above.
The transport datasets created in the transport table AQTDB by exports are not deleted after successful imports unless you specify this explicitly beforehand. For this reason, you cannot import a transport dataset several times, for example to transport an InfoSet to several clients.
The second transport option involves transferring files using the SAP system download/upload interface. To do this, you use the transport functions Download and Upload.
You must first download the source client objects for transport from table AQLDB to a file. When you do this, you specify the file name and exactly where it is stored in the file system. A file can only contain one transport dataset, meaning that any existing file is overwritten. Downloading a transport dataset to a file effectively means that it cannot be read back into table AQLDB.
Then, you can upload the transport dataset stored in the file. Here, the transport dataset is read and inserted in table AQLDB. As with an import, the system performs numerous checks which ensure that no inconsistencies occur in table AQLDB.
After this general overview, you can familiarize yourself more closely with the individual options offered by the transport tool. On the initial screen of the component Maintain InfoSets or Maintain User Groups, select Transports in which you want to make a series of entries. First, you choose one of the following transport actions by selecting the appropriate radio button:
Transport Action |
Meaning: |
---|---|
Export |
Generates a transport dataset in table AQTDB |
Import |
Reads a transport dataset from table AQTDB |
Download |
Generates a transport dataset in a file |
Upload |
Reads a transport dataset from a file |
Display |
Displays the transport dataset in table AQTDB |
Delete |
Deletes transport datasets from table AQTDB |
|
Copies query objects from the standard area to the global area |
|
Copies query objects from the global area to the standard area |
When you have selected the required fields, you can start the transport action by choosing Execute. The system always generates a log containing details of the individual actions executed.