Yes we do!
Virtual Systems can be part of your landscape.
If a transport request is waiting in the import queue, we are considering it like an performed import, if there is a follow-up system. We are here assuming that the virtual system should be used for quality gate or tracability reasons.
If a transport request is waiting in the import queue, we are considering it like a waiting import, if there is no follow-up system. We are here assuming that the virtual system will be replaced by a real system later on.
If the transport request is not waiting but the virtual system will be the next system in the transport track, the virtual system will be considered as system where the import can be performed next using the CC5 import feature. If the import will be triggered, it the transport request will not be imported (since this is not possible) but it will be added to the import queue.
A virtual system is virtual but CC5 still need to find a way to read the import queue. Therefore you have to establish a working connection somehow:
The virtual system is defined in the domain controller. CC5 is installed on this domain controller or on a system directly connected to this domain controller. → Nothing to do. The virtual system is defined locally and can be accessed by TMS services.
The virtual system is defined in a foreign transport domain. There is a domain link established. → Nothing to do. The virtual system is known locally and can be accessed by TMS services.
The virtual system is defined in a foreign transport domain. There is no domain link established. → In SAP Solution Manager there might be a solution. Maybe SAP Solution Manager is using the domain controller as communication system. If you are not using SAP Solution Manager as contolling system, you have to define a TMSORG RFC destination pointing to any real system of the same transport domain, e.g. the domain controller itself. → This solution has to be verified. It is just an idea for now.