Extended System ID (Extended SID)

In the SAP Solution Manager, a technical system is uniquely identified by its system type and an eight-character extended SID. 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. Do not change it later.

Changing the extended SID can be helpful 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.

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.

The extended SID must consist of upper-case letters and numbers, and of three to eight characters. If you enter less than three characters, manually, the LMDB adds zeros. An extended SID of more than eight characters is truncated. The LMDB deletes special characters and Unicode characters.

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.

The preferred way to change an extended SID is manually. You can also use a BAdI implementation (LMDB_EXTSID_GENERATOR) to change the proposed value of the extended system IDs.

Landscape Pattern: Hub and 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 Landscape Pattern.

Dual-Stack Assignment

Whether an Application Server (AS) ABAP or AS Java technical system is part of a dual-stack is registered by the AS ABAP data supplier. But if the AS ABAP and AS Java system are created manually, this information is missing and you need to maintain it manually.

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.

Assign to Product System

Under Software, 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

Set the Installed flag for the software component version of a selected product instance if it is installed physically on the 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.

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

Diagnostics-Relevant Flag for Product Versions

You can set the Diagnostics-Relevant flag for product versions to define which entities will be considered by the diagnostics applications in SAP Solution Manager.

Background: 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.

Custom Attributes

In the LMDB, you can maintain custom attributes for servers, 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 in the System Overview, 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.

System-Specific Synchronization with the 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 System Information with the SAP Support Portal.

For an individual technical system, you can define a different setting: