Skip to Content
Author's profile photo Himanshu Shrivastava

Create Virtual Transport system in STMS

Creation of Virtual System in STMS Configuration.

It is Not recommended by SAP and also it is not best practice.

But sometimes it required to release transport request from Quality System where we have make changes and created transport request. It is required when we are unable to check changes in our development sandbox & changes need to be created and checked directly in Quality system.

To do this first you login with your BASIS id in SAP System.

1. Open STMS


2. Select SAP System > Create > Virtual System


3. Fill New Virtual System ID and Description.


4. New created system will be displayed on screen.


5. Return to main screen and Open Transport Route


6. Open in change mode. Open Configuration > Standard Configuration > Development and Production System


7. Assign Development System as current system and Production as Virtual system


8. Route will be created


9. Save the configuration.


10. Distribute and activate configuration


Now you are able to release transport request from Quality system



Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Juan Reyes
      Juan Reyes

      Hi Himanshu,

      A virtual system is a TMS tool created to model/test transport routes where the landscape is not complete.

      Using a virtual system to release a transport in QA will mean that you'll find version inconsistencies in between your DEV and QA systems. Its important to highlight that in the case that this happen all changes should be applied in DEV and re-transported through the landscape. You might also find issues in your Change Management.

      So you really need to consider if this is a good option.

      Regards, Juan

      Author's profile photo Himanshu Shrivastava
      Himanshu Shrivastava
      Blog Post Author

      No Juan,

      This may be a requirement of anyone, when they are not able to make changes in dev system. I included in first line that "it is not Best Practice" but some time due to configuration issue/ lack of data developer may make changes in QA system then move physical request to Production.

      Author's profile photo Former Member
      Former Member

      Just to add a bit of information to the article.

      A Virtual System can be replaced at any time by real SAP Environment. Transport orders targeting the Virtual System will be automatically associated with the replacement System.


      Author's profile photo Steve Rumsby
      Steve Rumsby

      I'm curious about what sort of situations mean you need to do this. You mentioned being unable to check changes in DEV due to lack of data, for example. I'd much rather fix the data in DEV than restort to creating another transport route that starts in QA. Making changes directly in QA simply makes DEV even more incorrect and just compounds the problem, doesn't it. And if it is just test data you are missing then make the change in DEV anyway, untested, and test after transport to QA.

      Perhaps I've just been fortunate to have never come across such situations so I really am curious - what conditions in DEV would prevent you from making transportable changes?