Starting the Import of All Requests in a Project
Use
The import queue shows which requests belong to which projects. You can filter requests by project. You can display the requests of one or more projects and then start the import for these requests.
For more information, see
Using Projects to Control Transports.Prerequisites
You need the authorization S_CTS_IMPALL to import all requests in a project. This authorization is in the profile S_A.SYSTEM (see
Authorizations in CTS).To prevent change requests from still being placed in the import queue shortly before the import, and perhaps being imported unintentionally, we recommend
Also read the notes on
Precautionary Measures in the Target System.Procedure
To import all the requests in one or more projects:
The column Project does not appear if there are no requests in the import queue that are assigned to a project.
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
You cannot start the import of requests that are currently being imported, or for which an import is already scheduled.
On the tab
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.This check is not made if you have chosen the import option Ignore predecessor relations.
If the system finds out that the import would conflict with predecessor relationships, it displays the requests involved. If necessary, stop the import and import all projects that are linked together in one import. If you want to ignore the relationships, continue the import with Continue. The import is started automatically with the option Ignore predecessor relations.
The target client and the logon language are irrelevant here.
The system checks if you are allowed to import requests from the selected projects (see
Result
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.