Page tree
Skip to end of metadata
Go to start of metadata


With the following customizing you will be able to define a virtual system to use it in a SAP Solution Manager 7.2 ChaRM change cycle.

This blog is valid for Solution Manager 7.2, the screenshots were taken from a Solution Manager 7.2 SP03.


Before replacing the virtual system for a real system ensure that SAP Note 2699125 - Fix for missing IBASE object in TMS system has been implemented.


We will see the required steps to define the virtual system firstly in the TMS landscape of the managed systems landscape and after in LMDB.

Virtual System is a type of SAP Systems which can be used to solve the problem that you face when you don´t install all the systems you have planned for your system landscape at the same time, e.g., when the project is just started.

In Transport Management System (TMS), you can configure SAP Systems as Virtual Systems so that you can model the transport routes of your whole system landscape before having all systems in place.  More importantly, in ChaRM those Virtual Systems can be used as place holders in the task list, which means the project cycle can be generated and change processes can be started without any delay even if some physical systems are not yet ready. Most of the TMS display functions can be used for Virtual Systems, but no real transport can be performed in them.

Please be aware that the development systems (source systems) must not be Virtual System, otherwise the project task list in ChaRM cannot be generated successfully because we need a real IMG project and a CTS project here.

1. Defining virtual system in TMS and in LMDB

1.1. Managed systems TMS configuration

The same procedure explained in wiki page can be follow.

These would be the screenshots for the creation process.

Always you need to logon into the domain controller system of the managed landscape in client 000.

I selected VI1 SID for the virtual system but ensure you enter the SID of the expected final system.





Ensure that SAP notes are implemented in the domain controller system of the managed landscape (also in the other systems):

  • 1977240 - Extension of the AS ABAP SLD Data Supplier (RZ70)
  • 2148577 - RZ70 always sets communication client to 000 for non-ABAP system

With this you ensure that the domain controller system is sending the information of the virtual system created to the SLD of the solution manager.

Then job SAP_LMDB_LDB_0000000001 will detect the SLD changes:


1.2 LMDB configuration

Once the job is detecting the SLD changes you will see in LMDB an entry for the virtual system VI1 under Transport Domains tab, when selecting the domain name of the system where you created the virual system.

Select the transport domain of your managed landscape where the virtual system is created:


In Virtual systems tab you will find the VI1:


Click on the details tab to see when the system was created:


Now you need to create the Technical system for this virtual system VI1 as initially not technical system is created by the job.

This is indicated in solman_setup-> Change Control Management -> Managed system setup activity “Map Systems in LMDB”.

Select the system and click on Generate Technical System button:

Here select the technical system type, these are the options:


Select also a client, enter the expected client number of the real system that will substitute the virtual one:

Now you can see the technical system created to be selected in a Solution inside a logical component group.

Note: Ensure that the Lifecycle status is for virtual system is Planned, if not this virtual system could not be added to a cluster if you are using cCTS scenario.


In the Information point you can read:

“In most cases, installation numbers and system numbers are delivered automatically by SLD data supplier, and you do not need to edit them manually. In the following cases, manual editing can be required:

  • The technical system was created manually in the editor for technical systems.
  • For the technical system, no SLD data supplier can be used.
  • The technical system type does not store information about installation number and system number on the system, so the SLD data supplier does not deliver this information.

The following system types do provide system number and installation number: AS ABAP, AS Java, SAP HANA Database. “

If you try to change the installation number for a virtual system with ABAP tecnical system, there is not option to change it.

So it looks the installation number cannot be changed manually for an ABAP system type.

See that the client 100 appears created.

Note: However if you want to create a technical system  of type Java (or any other non-ABAP tye) you need to indicate in the technical system an installation number, if not no ibase component will be created.

2. Change request management configuration

As soon as the system appears as technical system in LMDB you can see the system in solman_setup in Managed system configuration.

Then in Change Control Management ->Managed System Setup you can see also the system:

No additional settings needs to be done here for the virtual system itself.

The ibase text/object component for VI1 100 was created automatically when the technical system was created in LMDB. Job SAP_LMDB_NOTIFY_LDB_0000000001 will be the one doing this.

2. Include your virtual system in a solution

Now you can create a Logical component group that contains VI1:100 as production system:

Real TMS:


3. Use the virtual system in a change cycle


Note: if you want to use a virtual system in a change cycle with cCTS activated please read SAP Note 2407837 - ChaRM&QGM: Virtual system validation error in cCTS configuration

4. Replace Virtual System with Physical System

Ensure that you from the beginning you create the virtual system in TMS with the future SID name and the future client.

Before replacing the virtual system for a real system ensure that SAP Note 2699125 - Fix for missing IBASE object in TMS system has been implemented.

Basically there are three steps to replace a Virtual System in ChaRM:

1. Delete Virtual System in STMS

Go to client 000 of the domain controller system, enter transaction STMS and delete the relevant Virtual System. Note that this action will only delete the system from the list, the transport buffer and directory on the operation system level will not be touched. So when the new physical system is created with the same system ID it can inherit all those old transport data automatically.


2. Create Physical System in STMS with the same SID

Include the new physical system to this domain and approve it in the domain controller. After that you need to re-configure all those transport parameters and make sure the transport route settings are still correct and consistent.


3. Refresh system data in LMDB

After the installation of the real system, the system is registered to the SLD and LMDB.

LMDB notification job will merge the virtual system and physical system in LMDB automatically in case SID and transport domain of both systems are the same.


"If the SID or the transport domain of both systems are not the same then a new technical system VI100001 will be created (original virtual system SID was VI1 in this example):

a. Go to LMDB and edit technical system VI1 and change the extended SID from VI1 to VI100002, save the change.

To change the extended system ID, choose Advanced... -> Change Extended System ID. (Caution: Read the documentation in the popup). For more information, see SAP Note 1851430 and SAP Note 1694004.

b. Change the extended SID of VI100001 from VI100001 to VI1, save the change.

c. If everything works fine with the physical system VI1, you may delete the virtual system VI100002 in LMDB.

All logical components groups remain valid and refer immediately to the real system.

For ABAP stack systems then you will also need to generate the RFC destinations in the working clients of the system."


4. Then go to the change cycle documenr and under More option select “Redefine landscape”action.

As long as there is no error during the “Refine landscape” action you may continue to work with this change cycle. All those change documents can be used without any issue and those transport requests which are already in the import buffer for the new physical system can now be transported directly without any other manual activities or adjustments.


Related Content

Related Documentation

Related Notes

1977240 - Extension of the AS ABAP SLD Data Supplier (RZ70)

2148577 - RZ70 always sets communication client to 000 for non-ABAP system

1687980 Virtual transport system in SMSY 7.1

1694004 Dealing with duplicate technical system names (SIDs)

1767384 Maintenance of installation no. & system no. in SolMan 7.1

2407837 - ChaRM&QGM: Virtual system validation error in cCTS configuration

2699125 - Fix for missing IBASE object in TMS system



  1. Hello Dolores,

    thanks for you Wiky, it's very interesting. I have followed your wiki to implement SAP Charm with Virtual System in Solution Manager 7.2 SP03.

    In the beginning I have configured Charm for a S/4 Hana Landascape only with Real Development System, I have used Virtual System for Quality and Production System.

    I have subsequently replaced Virtual Quality System with Real Quality System.

    Lastly I have replaced Production System with real Production System and I have found the following problem: all Change Document in "Configuration Item" in Reference Objects

    have old value for Production System. These because in the passage from Virtual System to Real System  the "Component" and "Object ID" in Installed base have been changed.

    (from "7100000114 PRD UNDEFINED 100" to "7100000290 PRD 0020951571 100").

    Compared what you did in wiki Section "4. Replace Virtual System with Physical System" in Point "3. Refresh system data in LMDB" I did the following:


    a. Delete the virtual system "PRD" in LMDB, save the change.

    b. Change the extended SID of "PRD00001" from "PRD00001" to "PRD" save the change.


    and not as you've shown in your wiki


    a. Go to LMDB and edit technical system "PRD" and change the extended SID from VI1 to "PRD00002", save the change.

    b. Change the extended SID of "PRD00001" from "PRD00001" to "PRD", save the change.

    c. If everything works fine with the physical system "PRD", you may delete the virtual system "PRD00002" in LMDB.


    Is it possible that this "different action" has created the problem with Ibase?

    Thanks in advance.




  2. I am facing the exact same problem with Edoardo.  All old IBase values were deleted and new ones created for the physical production systems.  I have an oss message created for this issue as i have over 3600+ CHARM documents with the invalid IBase values.  Hope to hear back soon otherwise it will impact our production golive.

  3. Hi Dolores, we are starting an implementation project and we have now only a development system, so, I have created two virtual systems (QA and PRD) and I have set up the transport routes.We created the LCG (one for solman and another for S/4). I tried to create a scenario with QGM (Solman 7.2) and only Solman landscape system appears. We sent a message to SAP support and they told me "virtual systems are not supported in QGM". This seems to be strange because we have used virtual systems in QGM (solman 7.1) without problems.

    Is this correct? Virtual systems are not longer supported in QGM 7.2?

    Thanks a lot!

    1. Hi Luciano, 

      Virtual systems can also be used in QGM 7.2.

      Best regards,