Product system descriptions must be created manually. They are not provided by an SLD.

1.  SAP Solution Manager: Work Centers Solution Manager Administration Landscape Product Systems .

   (Alternatively, you can directly access the Landscape Management Database with transaction LMDB.)

2. Enter the product system name, which must consist of one to eight characters without blanks or special characters. Underscores (_) are supported. All letters will be converted to upper case. The first three characters should reflect the system ID.

3. Choose Create New Product System.

4. In the product system editor, you can enter a more detailed description for the product system.

The task is to define the technical systems and the installed product instances that belong to the product system. Whereas technical systems that are maintained together are well-known in most cases, the correct product instances are sometimes hard to find if they are not provided by the technical system. The product system editor as well as the technical system editor provides proposals that cover the set of installed software components best. At the end of this task, the verification in the product system editor must deliver a positive result. In addition, the maintained product instance assignments of the product system must match the manually maintained product instance assignment for the involved technical systems.

1. In the navigation tree of the product system editor, choose Technical Systems, then Add.

2. A separate window opens. Select the technical system type and the extended system ID and choose Select.

   You can search for product instances to assign to the product system in various ways:

   • By automatic Proposal, which shows the product instances assigned to the technical system. Further product instances from the SAP Support Portal can also be proposed.

   • By Product Version. Enter the product version name or parts of it and select an entry from the input help. Then choose Search

   • By Free Text search. Enter the product instance name, or a part of it, and choose Search.

   Select the instances that belong to the product system. You can also choose Assign All Unassigned if you want to assign all instances from the proposal list. The instances are assigned in the background.

   The product instances are automatically assigns to the product system, in the background, you do not need to save.

3. Choose Close.

   The assigned product instances are now listed in the table, sorted by technical system and product version.

The following steps describe the best practice to configure a correct product system.

1. Assign the primary (most important) AS ABAP technical system

   Product system descriptions are synchronized from the LMDB to SMSY in the same way as descriptions for technical systems and hosts. When a product system is saved in LMDB, it is copied to SMSY immediately to keep both stores equally up-to-date. Each AS ABAP technical system is automatically a product system in SMSY — therefore, the product system name should be equal to the extended SID of the primary AS ABAP. As long as the AS ABAP has not been assigned to the new product system in the LMDB, you get a warning that the product system already exists in SMSY when you try to save the data. Either assign the AS ABAP before you save the new product system in the LMDB, or check if you can temporarily overwrite the current SMSY product system definition and ignore the warning.

   If no AS ABAP is part of the product system, start with the primary technical system of a different type and use the extended SID of this system as product system name. In this case, a conflict warning with an existing SMSY product system should not be ignored.

2. Check the product instance assignment for any technical system before adding it to a product system

   If no product instance is assigned to a technical system yet, try to find at least one suitable product instance in the SAP software catalog and assign it to the technical system. The product instance assignment on technical system level defines a starting point for the iterative product system verification and in this way accelerates the verification process.

   Ideally, you know the product name and version from the product documentation and you can thereby easily find the product instance. If you do not have this information, try to cover the installed software components at best with the proposals offered in the technical system editor. If you cannot find a suitable product instance, start the product system definition without such an assignment.

3. Assign secondary AS ABAP technical systems

   When you get the warning that is described in step 1, check if you can overwrite the SMSY data before you ignore the warning. The synchronization from LMDB to SMSY sets all product instances for each individual AS ABAP part as relevant. Example: You have two AS ABAP in the LMDB product system, one has two product instances assigned and the other one has a third product instance assigned. In SMSY you find two product systems. The first SMSY product system has the first two product instances marked as relevant. The second product system has the third product instance marked as relevant.

   All non-AS-ABAP technical system assignments are synchronized with all SMSY product systems. An additional AS Java technical system, for example, would lead to an additional, relevant Java instance in both SMSY product systems.

4. Assign non-AS-ABAP technical systems

   Non-AS-ABAP technical systems do not automatically create new SMSY product systems, they just add relevant product instances in SMSY.

5. Verify the product system description

   The verification function in the product system editor checks the consistency of the product system description with the SAP Support Portal. This is the most reliable check and usually leads you iteratively to a consistent product system definition.

6. Synchronize product instance assignments between product system and contained technical systems

   Any deviation between the product instance assignments on technical and product system level must be critically investigated. If the product instance assignment of the technical system was automatically supplied, either the data in the technical system or the product system definition is wrong. If the product instance assignment of the technical system has been manually assigned, adapt the technical system definition according to verification result for the product system.