A system is displayed in transaction SMSY with an incorrect product assignment. The assigned product version is either not installed at all, or the instances that are flagged as relevant in the product are incorrect.
The information about the installed products in the technical systems is incomplete. Transaction SMSY therefore attempts to calculate the installed products from the list of installed software components. To do this, the installed software components are compared with the PPMS product description. In the result, the system can classify none, one, or several product instances as matching.
In a significant number of cases, the result of the calculation is ambiguous, and can, therefore, be incorrect. The same applies for the calculation of the relevant product instances (main instances). If there are several similar combined instances in one product, the instance that was automatically calculated may be the wrong one. Using the example of the product version "SAP ERP 6.0", this note describes what you should do in this case.
The product calculation is used at three points in SMSY:
1. When a new system is created in the landscape fetch
As of Release 7. 0 Enhancement Package 1, SMSY automatically tries to identify product systems. It is prerequisite that at least one product instance matches the installed software components. Due to the unexpectedly high incidence of ambiguities, the automatic calculation is not included in the next release of Solution Manager.
A new technical system of the type ABAP results in a product system with one instance flagged as relevant. A new technical system of the type Java either results in a new product system with one or more instances flagged as relevant, or it is recognized as dual stack and assigned to an existing product system.
2. When the input help is used for manually assigning a product
The input help for the product assignment displays only the matching product versions in the first step. It is possible to switch to a free product assignment without any restrictions.
3. When system consistency is calculated (yellow exclamation marks)
If the list of installed software components does not match the PPMS product description (any longer), a yellow exclamation mark is displayed in SMSY. However, this does not always mean that there is an actual inconsistency, as shown in the ERP example in the solution section.
You must manually correct the product assignment and the assignment of product instances in SMSY. The data that is entered is not overwritten by the next landscape fetch.
Which product versions should I assign to my product system?
You must assign all product versions that are included in the installed software for the product system. This will be at least the product with which the technical systems were originally installed. You must always specify the currently installed version, for example, "SAP ERP 6.0", after an upgrade from "SAP ERP 2004" to "SAP ERP 6.0".
In addition to the original product, you must assign the installed add-on products. The Enhancement Packages for ERP such as "EHP4 FOR SAP ERP 6.0" are modeled in the PPMS as add-ons to "SAP ERP 6.0". In the system, therefore, ERP 6.0 is installed as the base product, as well as Enhancement Package 4 as an add-on. Depending on the Solution Manager application, only one of the two assignments may be required. For example, the maintenance optimizer requires only ERP 6.0. Nevertheless, you must assign both product versions. This configuration is interpreted correctly by all applications.
As of SolMan 7.0 Support Package 22, product assignments can be flagged as "active". Set all of the product versions that actually exist as active. Set old product versions that are still used in logical components as inactive. You must also set product assignments that describe subproducts, such as "SAP NetWeaver 7.0 (2004s)" (which is contained in parts of "SAP ERP 6.0") as inactive.
Which product instances should I flag as relevant?
The product system in SMSY is grouped around an AS ABAP. For product version "SAP ERP 6.0", the instance "SAP ECC Server" is mainly used. For product version "EhP4 FOR SAP ERP 6.0", the corresponding instance is called "Central Applications". Start the definition of the product system with this central instance and flag it as relevant. You must flag other product instances that are installed on this AS ABAP as "Additionally Installed".
Assign other technical systems that are not AS ABAP to the product system after the selection of ABAP instances. Flag the instances ("SAP NW - Enterprise Portal" or "SAP XSS (Self Services)", for example) as relevant and assign the technical system that was installed for this purpose.
Other technical systems of the type ABAP cannot be assigned to the product system. If a second ABAP product instance is installed as a customer-specific technical system, this second AS ABAP can be included only in a customer-specific second product system.
What should I do if warnings are issued in the product assignment?
A yellow exclamation mark in the product assignment indicates either missing software components or unexpected versions of the installed software components. This state may occur as the result of an upgrade, for example. Generally, you must then change the product assignment. If you encounter difficulties making this change, refer to Note 1429697 for further assistance.
The Enhancement Packages for ERP change the software component versions of the prerequisite product. For example, importing "EHP4 FOR SAP ERP 6.0" changes Version 600 of SAP_ABA to Version 604. A yellow exclamation mark is displayed in SMSY as a result. Nevertheless, product version ERP 6.0 is still installed as the base product. Ignore the yellow exclamation mark for this exception. As of SolMan 7.0 Support Package 23, this case is taken into account in SMSY.