Skip to Content

How to configure product system and technical system to run Maintenance Optimizer

This post is based on SAP note 1344564. If they differ, the current SAP official Maintenance Optimizer and system landscape management documentation applies.

Configure Solution Manager System Landscape (SMSY) automatically with the Landscape Verification Wizard (LVW) to reach better consistency. Refer to: Landscape Verification 1.0 for SAP Solution Manager – General Availability, Landscape Verification.

This post identifies manual actions in configuration of systems which are prone to error, especially of your product system, and explains how the behavior of MOpz depends on the landscape pattern.


1. Identify your technical systems and product systems 
2. Assign the correct product versions to the product system 
3. Examples: run maintenance transaction and update the system configuration 
  3.1 Install EhP1 for CRM 7.0 on CRM product system CCD with a sidecar 
  3.2 Install EhP5 for ERP 6.0 on ERP product system ERP_0007 with a hub 
  3.3 Upgrade R/3 to ERP 6.0 for product system ERP_0002


SAP system landscape has been evolving dynamically in realities of thousands of SAP customers; this required corresponding changes to SAP system landscape management and maintenance tools.

For instance, there was no the product system concept in Maintenance Optimizer (MOpz) 7.00/7.01 SP21 and previous SPs. The term sub-system was used to express the inter-dependencies of technical systems; it was no longer adequate in MOpz SP22 and higher SPs – the concept product system clearly disclosed the new stage in SAP system evolution.

On the one hand there is the reality of your SAP system landscape; on the other hand, the landscape that you configure in SAP tools is a kind of map. It’s critical for the map to reflect your real terrain. This post describes how to configure your systems in Solution Manager System Landscape (SMSY) to run Maintenance Optimizer (MOpz), with examples. The information and screenshots are based on MOpz SP22 or higher SPs, and ST 400 SPs till to SP26.


1. Identify your technical systems and product systems

Technical system means the same as the term SAP system which has been used for long time. It is identified by a 3-character system ID. Your system landscape may contain more than one technical system with the same system ID; but they must be in different databases, so that the system ID and database server uniquely identify a technical system (ABAP, Java or dual stack) in your landscape.

In SMSY, a technical system is expressed via technical system entry

That the term technical system entry is used in this post is because one technical system may be represented by more than one entry in SMSY.

For example, the Process Integration product instance of system PIQ is dual stack (a product instance is the smallest installable entity of a product, and it needs to be installed inside one technical system): 

Figure: product system PIQ

There is a technical system entry PIQ (maximum 8 characters, the first 3 characters are the system ID) to for the ABAP stack:

There is a technical system entry PIQ for the Java stack:

The server host of the database of the two SMSY entries of one technical system must be the same; otherwise, due to misconfiguration, the two entries will be regarded as two tehcnical systems:

A product system comprises one or more technical systems which cooperate in business scenarios of one product. The name of the product system is the same as its ABAP technical system entry, if there is one in SMSY. In the PIQ example, product system PIQ comprises only technical system PIQ. The product system connects the business relevant technical systems together. You assign roles (system landscape pattern) to technical systems – you need to identify the relationships according to your reality to determine the roles. You choose product system(s) other than technical system(s) for maintenance in MOpz. With the inter-linkage and landscape pattern data, MOpz gives most precise calculation for your update – MOpz calculates for the constellation of inter-dependent technical systems altogether other than one by one separately.

In SMSY, you can navigate to non-ABAP technical system entry from its product system(s) or from the Landscape Components tree node Technical System (previously System Component). You can only navigate to the view of an ABAP technical system entry from its product system by clicking on the assigned relevant ABAP product instance.


2. Assign product versions to the product system

Correct assignment of product version(s) to the product system is important for update delta calculation.

Assign the stand-alone product version to the product system. For example, a CRM product system is SAP CRM 7.0/NW 7.01. Assign this CRM product version to it.

If you have also installed a CRM EhP, you can assign the CRM EhP product version to this product system too and mark the installed CRM EhP product instance, to reach more precise calculation.

There are 2 kinds of EhP product versions: add-on EhP and stand-alone EhP. For example, ERP 6.0 EhP 5 is an add-on product version which requires its stand-alone ERP 6.0. EhP1 of NetWeaver 7.0 is a stand-alone product version, a minor release of NetWeaver after NetWeaver 7.0, which replaces NetWeaver 7.0, rather than being based it; the same applies to EhP1 of SAP Solution Manager 7.0.

A system also has a technical product version layer, NetWeaver, which is also a stand-alone product version. You usually do not need to assign the NetWeaver product version to the product system. Sometimes, one product system may comprise technical systems on different NetWeaver releases. If you intend to run a technical-driven maintenance to update only NetWeaver, assign NetWeaver product version to the product system and select the NetWeaver product version in MOpz step Planning Maintenance.

If you installed non-EhP add-ons on this system, you usually do not need to assign add-on product versions in SMSY for MOpz calculation.

Example of assigned product versions for a product system:

Select stand-alone product version in MOpz, either normal stand-alone one such as SAP ERP 6.0 or stand-alone EhP such as NW 7.01 or SolMan 7.01:

3. Examples: run maintenance transaction and update the system configuration

Here are 3 examples of system maintenance:

1. The EhP installation calculation of a CRM product system involving a sidecar technical system.

2. The EhP installation calculation of an ERP product system involving a hub technical system, which is also used in a CRM product system.

3. The upgrade calculation of an R/3 product system, with the targeted product system involving a new sidecar technical system.

Figure: Legend of illustration below

3.1 Install EhP1 for CRM 7.0 on CRM product system CCD with a sidecar

1. You have a product system CCD which comprises a technical system CCD (ABAP only) and a technical system DCD (Java only); its product version is SAP CRM 7.0/NW7.01:

Figure: Product system CCD before update

The mapping of the above reality in SMSY.

Figure: Product system CCD and its product instances in technical systems

Figure: Technical system CCD

Figure: Technical system DCD

Since Java technical system DCD is only used by product system CCD in your landscape, you assign landscape pattern sidecar to it. Landscape pattern sidecar (in case it’s correctly set) ensures the most restricted variation of the connected technical systems in the product system – the calculated target technical NetWeaver layer of technical system DCD keeps as consistent with CCD as possible.

2. Choose product system CCD for maintenance in MOpz, choose EhP1 for CRM 7.0 for as the target; choose the installable technical usages.

Since you need to update both technical system CCD and DCD, choose the technical usages of both CRM AS ABAP and CRM AS Java:

Figure: Choose target

Select the target (EhP product stack in this example). MOpz calculates the corresponding (equivalent) target stand-alone product stack of CRM 7.0/NW7.01, and the technical NetWeaver stack. Because the rule of restricted variation is applied for sidecar, the calculated target NetWeaver of CCD and DCD is the same:

Figure: Selected and calculated targets

3.  After update, your system landscape is changed and you need to update the SMSY with the changes.

Figure: Product system CCD after update

You have selected a new product instance Finbasis in the above maintenance, which is not defined in CRM 7.0/NW7.01 product version. Assign a new product version EhP1 for SAP CRM 7.0 to CCD, and point the new installed product instance Finbasis to the technical system on which it’s installed.

Figure: Assign active product versions

Figure: Assign active product versions

3.2 Install EhP5 for ERP 6.0 on ERP product system ERP_0007 with a hub

1. You have an ERP product system ERP_0007, which references a technical system NW7 in addition to a ERP technical system. The technical system NW7 is also referenced by a CRM product system CRM_0002.

Suppose you want to update ERP_0007 with new SAP innovations.

In this example, you need to assign landscape pattern hub to NW7. Landscape pattern hub ensures minimum impact on the technical systems of the linked product systems – the calculated target NetWeaver of hub NW7 will have less changes required to enable the ERP_0007 to work with the new innovations and preserve the current status of CRM_0002.

Figure: Product system ERP_0007 (target system to be maintained) and the linked product system CRM_0002

Figure: Product system ERP_0007 (a)

Figure: Product system ERP_0007 (b)

Figure: Product system CRM_0002

Figure: NW7 landscape pattern

2. Choose product version ERP 6.0 and product system ERP_0007 for maintenance in MOpz. Choose EhP5 for ERP 6.0 for as the target. Choose the installable technical usages.

Figure: Select target stack and technical usages

You select the target (here is ERP 6.0 EhP5 stack). Other calculated target stacks are shown below. For technical system ERP, both EhP and NetWeaver product versions are updated. The hub technical system NW7 is updated to product version ERP 6.0 EhP5 product version too; while its NetWeaver release is unchanged in this example, for minimum impact. There are no product versions changes for technical system CRM in this example.

Figure: Selected and calculated targets

3. After the update, the system landscape is:

Figure: Product system ERP_0007 and CRM_0002 after update

3.3 Upgrade R/3 to ERP 6.0 for product system ERP_0002 with a new sidecar

1. You have R/3 4.6C product system.

Figure: Product system ERP_0002

You want to update ERP_0002 to ERP 6.0 EhP5 and install new product instances such as XSS and enterprise portal, for this product system, on a sidecar technical system.

Upgrade the R/3 technical system to ERP 6.0 EhP5, and install a new sidecar technical system with product instance XSS and enterprise portal.

2. In MOpz, choose the product version R/3 4.6C and product system ERP_0002 for maintenance. Choose target stack ERP 6.0 EhP5:

Figure: Choose target stack

The targets are calculated for the product system ERP_0002:

Figure: Selected and calculated targets

Updgrade technical system ERP.

Install the sidecar technical system, say NWR, with XSS and enterprise portal.

3. After upgrade and installation, the product system ERP_0002 is ERP 6.0 instead of R/3 4.6C. Update the product version and product instances assignment in SMSY.

Figure: product system ERP_0002 after upgrade

You must be Logged on to comment or reply to a post.