Show TOC

Function documentationOther Settings and Functions in the Technical System Editor Locate this document in the navigation structure


The Landscape Management Database (LMDB) offers several functions to manually edit technical system information, which are explained in the following.

For more information, also see the expandable help tray directly in the UI.

Note Note

Avoid manual editing of technical system information. Retrieve as much information as possible by automatic SLD data suppliers. For more information, see Connect LMDB to System Landscape Directory (SLD).

End of the note.
Overview Screen
  • Installation Number and System Number

    In a few cases, it can be required to edit this key information manually. For more information, see the section Tab: SAP Support Portal.

  • Technical System Status

    For some SAP Solution Manager activities, it can be required to temporarily mark a technical system as inactive, for example for Change Request Management. In this case, you can change the Technical System Status on the Overview screen. Choose the value Inactive.

  • Landscape Pattern: Hub or Sidecar

    When the technical system is used in several product systems, the pattern is Hub, when it is used in a single product system, it is Sidecar.

    The landscape pattern indicates the dependencies between product instances in technical systems, which results from the way products are combined into business processes in your solution landscape. You can restrict maintenance transactions to one selected product version, and avoid additional maintenance requirements due to dependencies on other product versions.

    For more information, see and the Maintenance Planning Guide at

  • Assign Java Stack

    When an Application Server ABAP technical system is part of a dual-stack, you can assign the AS Java stack. This is only required, is the technical system was created manually. Otherwise SAP Solution Manager recognizes dual-stacks automatically.

    Prerequisites: The AS ABAP and AS Java technical systems must have the same system ID, and the other system must yet not be assigned to a different dual-stack.

  • Tab: Custom Attributes

    In the LMDB, you can maintain custom attributes for product systems, technical systems, and hosts. The information is transported to, and used by, transaction SMSY (for example to filter systems by location). Standard attributes are Location, Manufacturer, Monitoring System, and Release.

    You can maintain custom attributes on the Overview screen, on the Custom Attributes tab.

    Create New Custom Attributes and Input Help:

    To create new custom attributes, access transaction SMSY and choose   Utilities   Attribute Definition   and enter the required information. After saving a new attribute definition, the new attribute will be available for selection in the technical system editor of the LMDB.

    To maintain the selectable values for the input help, double-click an attribute. To use existing value tables and search help, either enter a table name under Value Table and a field name from this table under Values Field, or enter a search help under Search Help Name and specify the return parameter for this search help under Search Help Field. To define your own values for the input help, right-click on an attribute, choose New Entries and enter the required information.

  • Tab: SAP Support Portal

    • Trigger or stop upload to SAP Support Portal

      By default, the LMDB data for all technical systems is synchronized with the SAP Support Portal regularly. This is defined globally for all technical systems. For more information, see Synchronize with SAP Support Portal.

      For a selected technical system, you can change the default on the SAP Support Portal tab.

      Under Cross-System Setting, you can see the global setting for all technical system types, which is Synchronize with SAP Support Portal by default.

      Under System Synchronization, you can change the setting for the selected system. There are two options: Use Cross-System Setting or Do Not Synchronize Selected Technical System.

      You can choose Upload to SAP Support Portal to update information about installed software component versions (including Support Packages), which enables correct note search results in the SAP Support Portal, and to update technical instances, for a correct support service connection setup.

    • Edit System Number and Installation Number

      Edit Installation Number and System Number. For more information, read the instructions and messages in the popup.

      When you have edited the values, upload the information to the SAP Support Portal by choosing Upload to SAP Support Portal.

    • Edit data on the SAP Support Portal

      Some data can only be edited on the SAP Support Portal itself, such as the add-on product version or use type. To do so, choose the System Number or Installation Number link, which directs you to the SAP Support Portal.

  • Advanced

    • Change Extended System ID

      In the SAP Solution Manager, a technical system is uniquely identified by its system type and an eight-character extended system ID. The system itself does not know the extended SID, it is an identification used locally in the SAP Solution Manager. By default, the extended SID is defined automatically by the LMDB when the system is created.

      Most of the technical systems have a predefined, three-digit system ID (SID) from which the extended SID is derived. SID and extended SID are identical, if possible. If a new technical system with an SID identical to an existing one is created, a suffix with 5 digits is appended to the SID to build the extended SID. Example: If a technical system C1D with extended SID C1D exists, the second system, with the same SID C1D, gets the external SID C1D00001, automatically.

      Many SAP Solution Manager applications use the extended SID and system type to identify a technical system. Therefore the extended SIDs should not be changed as soon as it has been used by any SAP Solution Manager application, because this can result in data inconsistencies. You can change the extended SID, manually, until you execute the Managed System Setup in the SAP Solution Manager Setup for this system.

      Use cases requiring a change of the extended system ID:

      • Changing the extended SID can be required if the system is not configured yet and if the automatically assigned extended SID does not meet the expectations. For example, extended SIDs reserved in SMSY can block the desired extended SID; in this case, you can change the extended SID in the LMDB to overwrite the SMSY data.

      • In case of a dual stack, the automatic generation of extended SIDs cannot ensure that the extended SIDs of AS ABAP and AS Java are identical. If you want to have identical extended SIDs for both parts, adjust one of the extended SIDs immediately after the system has been created in the LMDB. (The three-digit SIDs of dual-stack partner must always be identical.)

      To change the extended system ID, choose   Advanced   Change Extended System ID  . You can enter three to eight characters, which can be upper-case letters and numbers. If you enter less than three characters, manually, the LMDB adds zeros. Special characters and Unicode characters are not supported.

    • Resynchronize Technical System Information from SLD

    • Delete Technical System Information

Software Screen

This screen shows you which product versions, product instances, and software component versions are installed on the technical system.

Note Note

This information should always be provided automatically by SLD data suppliers. Avoid manual entries.

End of the note.
  • Installed Flag for Product Instances

    Shows which product instances are installed on the system and is set automatically. It is only used for documentation purposes and to enable value help in other applications, like the product system editor, to indicate which product instances are selectable and installed.

  • Diagnostics-Relevant Flag for Product Instances

    You can set the Diagnostics-Relevant flag to define which product instances are considered by the diagnostics applications in SAP Solution Manager.

    In some cases, the installation of add-ons can update the software component version of a product, but you want diagnostics to still refer to the older version of the product. In this case, use the flag to specify content that should be used for diagnostics instead of the installed content.

    For more information, see the SAP Community Network at

  • Assign to Product System

    You can choose Assign to Product System to assign a selected product instance and the technical system to an existing product system. Here, you can also create a new product system and assign the product instance. For more information, see Create Product System Information.

  • Installed Flag for Software Component Version

    Select a product instance from the upper table to see the included software component versions in the table below. Set the Installed flag for those software component versions that are physically installed on the technical system. Software is sometimes assigned although the corresponding executables are not physically installed; in this case the flag is not set. The flag is also not set if the software is diagnostics-relevant but not installed.

    Note Note

    Only change the list of installed software components if there is an explicit request for modification.

    End of the note.