Decoupling Transport Requests

You can separate a transport request from its scenario and change it. This transport request is then no longer controlled by QGM.

Caution Caution

Although the software changes you have made are no longer controlled by QGM, they remain in the system and may impact later developments that use the same objects. We therefore recommend that you restore the changes and do not decouple them.

End of the caution.

Prerequisites

If you want to decouple released transport requests, you have activated the central Change and Transport System (cCTS) for your scenario. Otherwise, you can decouple only changeable transport requests.

Procedure

In the transport requests table, choose Actions... Decouple Transport Request .
Select the transport requests that you want to decouple.
Choose the Decouple pushbutton.

Result

The transport requests are decoupled from your QGM scenario.

If you want to manage a decoupled transport request again, you must reassign the request to a QGM scenario. For more information, see Assigning Transport Requests.

Example

You have performed software changes that you no longer require. The recommended way of handling these changes is to restore the changed objects to their original state. However, due to project or time restrictions, you are unable to reset the changes. You therefore decide to decouple the changes from your scenario, so that you can focus on finalizing the other parts of your scenario.