Show TOC

Procedure documentationMigrate System Information from SMSY to LMDB Locate this document in the navigation structure


If you manually maintained product system information in the SAP Solution Manager System Landscape tool (transaction SMSY) in earlier releases, you may want to migrate this data to the Landscape Management Database (LMDB), which is the central storage for landscape information as of release 7.1 SP05, for both technical systems and product systems.

Migration from SMSY to LMDB is a one-time activity during the LMDB setup. Do not maintain data manually in SMSY subsequently.

There are two ways of migrating data from SMSY to the LMDB:

  • Aspect-oriented migration (noncritical, recommended)

  • System-oriented migration (handle with care)

    System-oriented migration is restricted to the case that the technical system description in LMDB cannot be filled from the SLD. Otherwise there is a risk of system duplicates in LMDB, with one system that was migrated from SMSY and the other one synchronized from the SLD.


Aspect-Oriented Migration

This is the recommended way to transfer additional information that could only be maintained manually in SMSY and cannot be provided by an SLD. This includes product system descriptions and individual aspects of the technical system information, for example custom attributes (in SMSY: “other attributes”).

Usually, all system types that are used in SMSY are supported.


  • You have setup the SLD synchronization as described under Connect LMDB to System Landscape Directory (SLD).

  • The technical systems to be considered for migration exist in both SMSY and LMDB. The migration process checks this based on the extended system ID (extended SID).

  • You have maintained the product systems in SMSY.

  • A clean-up in SMSY is recommended. Before migration, you can still start transaction SMSY and delete any product system that has not yet been migrated to the LMDB.

  • The aspect to be migrated is maintained in SMSY. For example, a system has values under Other Attributes.

    But the aspect must not yet be maintained in the LMDB. For example, a system in the LMDB must not have values under Custom Attributes. (If you already had entered any values in LMDB manually, they would have been synchronized into SMSY already, and a migration of SMSY data would be obsolete.)


  1. Start SAP Solution Manager Configuration (transaction SOLMAN_SETUP) and choose   System Preparation   Prepare Landscape Description   Migrate Data into LMDB  .

  2. Switch to Edit mode and choose the activity for the information you want to migrate.

    Start all existing activities, consecutively:

    • Migrate Product Systems (recommended)

      A SMSY product system should be either migrated to the LMDB or deleted.

    • Migrate Installed Product Instances (optional)

      Migrate the SMSY product assignment of systems about which you are sure that the assignments are correct. The data is migrated from the SMSY product system to the corresponding LMDB technical systems.

    • Migrate Custom Attributes (optional)

      Migrate the custom attributes of systems for which you have maintained any.

    • Migrate Host Router Data (optional)

      Migrate SAP router configurations if they were maintained in SMSY.

    • Migrate Diagnostics-Relevant Flags (optional)

      Migrate diagnostics relevant flags of systems, if you want to keep them.

    Depending on the number systems and their size, migration can take some time.

  3. Check the log section for details.

System-Oriented Migration

System-oriented migration transfers the technical system description including most aspects from the SMSY to LMDB.

Note Note

Avoid system—oriented migration

  • Only migrate systems for which you cannot configure data suppliers, for example because of a firewall. Automatically supplied data is usually more reliable than manually created data. Furthermore, data suppliers ensure that changes in a technical system are reflected in SLD and LMDB automatically.

    For more information, see Register Technical Systems Automatically by Data Suppliers.

  • Only system descriptions that are sufficient to create an LMDB entry are migrated.

  • To avoid superfluous effort, only migrate system descriptions that are really necessary. Consider a SMSY clean-up before migration.

End of the note.

For the following system types, system-oriented migration is supported:

  • System-Oriented Migration for AS ABAP

    System-oriented migration is supported for AS ABAP technical systems and all system entities, for example, clients, instances, software components, and other attributes.


    • You have performed the basic configuration of the LMDB.

    • You have initially synchronized SLD and LMDB.

    • You have at least maintained the following data in SMSY for ABAP application servers (ABAP):

      • Installation Number

      • Message Server

      • Database is assigned to the system

      • The server of the assigned database

      • The manufacturer of the assigned database

  • System-Oriented Migration of Master Data Management Server (MDM)

    Migration of instances, databases, software components, and other attributes is supported for technical systems of the type MDM.

    Example: You have a technical system of type MDM with a technical instance with server roleMDM Server, and a product system with product version SAP MDM 5.5. In this case, the technical system must be assigned to the Master Data Server product instance.

    Prerequisites for MDM Layout Server, Import Server, and Syndication Servers:

    • You have assigned the technical system to the product system by assigning the product instances.

    • The extended system IDs of technical systems and product systems must be identical.

    • The software components for the technical instances, for example the MDM_SERVER software component in the MDM Server server role, must be in the technical system.

    • The technical system has an instance in the MDM Server server role.

    • You have maintained the instance number and server.

    • You have maintained the instance according to the SMSY naming convention.

    • A database must be assigned to the system.

    • You have maintained the server of the assigned database.

    • You have maintained the manufacturer of the assigned database.

  • System-Oriented Migration of Unspecific Cluster System (UNSPECIFIC)

    Migration of instances, databases, software components, and other attributes is supported for Unspecific Cluster Systems.


    • You have assigned a database to the system in transaction SMSY.

    • You have maintained the server of the database.

    • You have maintained the manufacturer of the database.

    • You have assigned one or more product instances of a product system to the technical system.

    • The extended system IDs of technical systems and product systems must be the same. Software components must be maintained.


  1. Start SAP Solution Manager Configuration (transaction SOLMAN_SETUP) and choose   System Preparation   Prepare Landscape Description   Set Up LMDB  .

  2. Switch to Edit mode and choose Start Migration from SMSY to LMDB.

  3. Select the systems to migrate, and choose Migrate Selected Rows. The migration runs in a background job and takes a few minutes per system, depending on its type and size.

  4. When the background job has finished, you can choose Display Log for details.