In Change Request Management, you should always create transport requests using the means provided by Change Request Management only – in other words, using a change document or a task list. Any transport requests that you have created manually in the transport management system are not known to Change Request Management. However, if you start using Change Request Management, you can assign your existing transport requests to change documents and control them using Change Request Management.
How to identify these transport requests and make them known to Change Request Management is described below.
Change managers or developers can assign the following transport requests to change documents:
Decoupled transport requests
Freely created transport requests
External transport requests, that is, from another system landscape
Note
You can assign Workbench and Customizing transport requests but not transports of copies.
You can assign a transport request multiple times, as long as it is assigned to different change cycles whose landscape does not have the same production system.
Recommendation
While transport requests for release cycles and continual cycles can only be assigned in the WebClient UI, transport requests for phase cycles can be assigned directly in the task list. However, we recommend that you use the WebClient UI to assign transport requests.
For urgent changes without a change document, you can only use the task list.
To assign released transport requests, you must have activated the central Change and Transport System (central CTS) for your change cycle. Otherwise, you can only assign changeable transport requests.
In the WebClient UI, in the Transport Management
assignment block, choose .
In the task list, choose the Assign Transport Request
task under the development system.
The system displays a dialog box with a transport request search screen.
Search for the transport request. Select the requests and choose Assign Transport Request
.
If you have activated downgrade protection, the system might issue messages about potential downgrade conflicts. For more information, see Downgrade Protection.
You have activated the central Change and Transport System (central CTS) for your change cycle.
In TMS, you have defined a delivery route to transport the external transport request from the development system to the consolidation system, and from the development cluster to the consolidation cluster.
You have defined the source system of the external transport request in the transport target area of the target clusters of your imports to transport the external transport request.
Before you can assign an external transport request, it has to be imported into the development system.
In the transport management system (transaction STMS
), in the development system of the landscape from which you want to import a transport request, choose Import Overview
.
In the displayed list, select the development system by double-clicking.
Choose
.In the dialog window, enter the transport request ID and the target client of the system to which you want to import.
Select the transport request and choose
.In the dialog window, confirm the import to the development system.
The transport request is now available in the import buffer of the quality system in the new target system landscape.
Go to the WebClient UI and in the Transport Management
assignment block, choose for the change document to which you want to assign the transport request.
In the task list, choose the Assign Transport Request
task under the development system.
The system displays a dialog box with a transport request search screen. Search for the transport request you just imported to the development system.
Select the request and choose Assign Transport Request
.
If you have activated downgrade protection, the system might issue messages about potential downgrade conflicts. For more information, see Downgrade Protection.
The transport request is now assigned to the change document.