Starting the Import for Single Requests
As well as giving you the option of importing all requests in the import queue, or all requests in a project, TMS also lets you import one or more single requests. The requests are imported in the order in which they are placed in the import queue.
This import method is best used for a few individual requests; it is less suitable for large numbers of requests.
Importing single requests can either be
To find out about the requirements you need to meet, we recommend that you read the following information:
To import your own requests, you need the authorization S_CTS_IMPSGL. This authorization is in the profile S_A.SYSTEM.
Note for the system administrator:
If you want to give members of your development team the authorization to import their own requests into a certain system, then you should create an authorization profile for these users and the system. This profile must then contain the authorization S_CTS_IMPSGL. The profile S_A.SYSTEM usually contains too many authorizations.
To import individual requests from more than one user into a system, you need the authorizations S_CTS_IMPSGL and S_CTS_IMPALL. These authorizations are in the profile S_A.SYSTEM.
Also read the notes on
To import single change requests:
You cannot import requests that have the status Request must still be approved (seeTMS Quality Assurance). If you still want to import them, for example if the QA system is not available, you must activate the requests.
Note that you cannot import requests with the import status Request was rejected, Import is running or Request is already imported. For more information, see the long text of the corresponding error message.
The box displays the requests you chose, and the import target.
On the tabDate/deadline, you can specify when you want the import to start.
On the tabExecution, you can specify how you want the transport control program tp to start.
On the tab pageOptions, you can specify options for the import.
The option Leave transport request in queue for later import is activated as a default; this means that individual imports will be handled as preliminary transports.
The target client and the logon language are irrelevant here.
TMS starts or schedules the import in the target system.
After the import has finished, you can view theimport history to check the return codes for all import steps. You can also go to the corresponding transport logs from the import history.