Start of Content Area

Procedure documentationStarting the Import of All Requests in an Import Queue  Locate the document in its SAP Library structure


Requests that are released in the development system are marked for import into the target system, for example into the QA system (see System Landscape). They are placed in the import queue of this system. The function Start import of all requests in import queue lets you import the objects of this request into the target system, or you can schedule the import to occur at a specific time.

After importing the objects into the target system, the requests are placed corresponding to the transport routes in the import queues of the delivery systems (for example, in the production system). You can start the import into these systems using this function after performing quality assurance tests (See TMS Quality Assurance).


You have chosen mass transports as your transport strategy.

To import all the ready requests, you need the authorization S_CTS_IMPALL. This authorization is in the profile S_A.SYSTEM.


To prevent change requests from being placed in the import queue shortly before the import, and perhaps being imported unintentionally, we recommend closing the import queue before the import.

Also read the notes on Precautionary Measures in the Target System.


To import all the requests in the import queue:

  1. Call Transaction STMS.
  2. Choose This graphic is explained in the accompanying text. The import overview appears.
  3. Position the cursor on the SAP System for which you want to start the import.
  4. Choose This graphic is explained in the accompanying text. The import queue of the selected SAP System appears.
  1. If you have activated extended transport control, and requests are waiting to be imported into different target clients, you can restrict the import to a single target client by choosing This graphic is explained in the accompanying text.
  2. If you want to ensure that only the displayed requests are imported, close the import queue. This prevents any other requests that are released, or that are forwarded to this transport route from being placed after the end of the import queue.


Only requests with the import status Request waiting to be imported or the status Request is ready for import again are imported.


You cannot import requests that have the status Request must still be approved (see TMS Quality Assurance). If you still want to import them, for example if the QA system is not available, you must activate the requests.

You cannot start the import of requests that are currently being imported, or for which an import is already scheduled.

  1. Choose This graphic is explained in the accompanying text. The dialog box Start Import appears.
  2. In this dialog box, you see the target system and the target client for the import. If extended transport control is not activated, you can define the target client for the import. (For more information, see Handling Target Clients.)
  3. On the tab Date/deadline, you can specify when you want the import to start.

    On the tab page Execution, you can specify how you want the transport control program tp to start.

    On the tab page Options, you can specify options for the import. You do not usually need to change the defaults.

  4. After you have made your settings in the Start Import dialog box, choose Continue.
  5. Check and confirm the information on the next dialog box. The dialog box shows you in which system and which target client the import is to be started or is scheduled for.
  6. If you are logged on to system A in the transport domain and start an import into system B in this domain, a logon screen for the target system appears (in this case system B). Your user name is already entered by default. Enter your password.


The target client and the logon language are irrelevant here.


The system checks if you are allowed to import these requests (see Project Status Switch). Even if the import is not allowed for just one project, the import does not start and an error message appears. If this is the case, ask the project manager when you should start the import.


TMS starts or schedules the import in the target system.

After the import has finished, you can view the import history to check the return codes for all import steps. You can also go to the corresponding transport logs from the import history.