
You can use the preselect request function for non-ABAP transport requests to simplify the attaching of objects to a transport request in the application for end users. Once a developer creates or modifies objects in the application, and wants to include them in a transport request, the application system tries to find a suitable transport request for this user. If a transport request is preselected for this user in CTS, it is usually proposed as the default request.
The transport strategy that has been configured for the source system also influences the preselection of transport requests. If the parameter WBO_GET_REQ_STRATEGY is set to the value Smart in the source systems, and no request is preselected, the transport system creates a transport request for this user and flags it as the preselected request. The Create value for the WBO_GET_REQ_STRATEGY parameter means that one new transport request is always used that is preselected as default, even when another request was already preselected. In these cases, users can attach their objects to this request from within the application, without having to use Transport Organizer Web UI.
For more information, see Choosing a Transport Strategy.
You have created a transport request in Transport Organizer Web UI.
The transport request has the status Modifiable.
There are the following ways to set a transport request as a preselected request for your user:
When creating the transport request
In the Create a New Transport Request dialog box, set the Preselect Request flag.
After creating the transport request
Select the required transport request in your request list and choose Preselect Request.
On the Preselection tab in the Details view, you can preselect transport requests. Like this, you can also preselect transport request for other users.