You use the Maintenance Optimizer guided procedure to calculate stack delta files. Check the information below to ensure that your system landscape is correctly configured.
This is a checklist and guideline for Solution Manager System Landscape configurations for Maintenance Optimizer use.
This Note contains important checks for the configurations of the system landscape.
Check Solution Manager System Landscape
Guidelines regarding the Solution Manager System Landscape are available in SAP help portal and application help. You can access this information from the following path:
http://help.sap.com -> SAP Solution Manager -> Basic Settings -> Solution Manager System Landscape.
After configuration of the system landscape, perform the following:
1. Call transaction code SMSY. SLD is strongly recommended as the only data source for SMSY.
2. Check the Product System (SMSY System).
Product Systems are defined under the node: Landscape Components -> Systems ->
A Product System comprises one or multiple Technical Systems. A Technical System is a physically-installed SAP system.
a) Product System, tab Header Data.
Check the major product version for MOpz maintenance is assigned to the Product System: in table "Assigned Product Versions", check that column "Leading" is marked, e.g. SAP ERP 6.0; or depending on the Solution Manager system SP stack level, you need to click button "Change Product Assignment", check that column "Active" is marked in case there are more than one product version assigned.
You can assign an add-on EhP product version and its base major product version to the product system at the same time in SMSY, e.g. EHP3 for SAP ERP 6.0 and SAP ERP 6.0. While don't choose an add-on EhP product version of the product system in MOpz step "Plan Maintenance", e.g. EHP3 FOR SAP ERP 6.0; but choose its base major product version, e.g. SAP ERP 6.0. You can choose non-add-on EhP product version of the product system in MOpz step "Plan Maintenance", e.g. SAP EHP1 FOR SAP NETWEAVER 7.0.
In particular for a system of the product SAP ERP, assign the product version of SAP ERP, not SAP ECC.
b) Product System, tab Selection of Main Instances.
Check that column "Relevant" or "Also Installed in Relevant ABAP Main Instance" is marked for all installed Main Instances.
Main Instances are distinguished as either ABAP or non-ABAP ones. For ABAP installed Main Instances, only one can be marked as "Relevant"; the others need to be marked as "Also Installed in Relevant ABAP Main Instance". Non-ABAP installed Main Instances need to be marked as "Relevant".
For relevant non-ABAP Main Instances, also check that column "System Component Assignment" is marked, column "System Component" is linked to the correct System Component, and column "Type" is selected. For Java Main Instances, select the type as Java; for TREX Main Instances, select the type as TREX; for other non-ABAP Main Instances, select the type as Java and link them to a Java System Component.
For relevant TREX Main Instances, if your Solution Manager system is at SP stack level lower than ST 400 SPS 22, see Note 1305862 Maintenance Optimizer: Enhanced support of TREX instances; otherwise, you only need to link the TREX Main Instance to its System Component.
Read more information for selection of Main Instances:
I. It's recommended that only one ABAP standalone Main Instance is marked for relevance for one Product System. Each ABAP standalone Main Instance includes the Netweaver Application Server ABAP Main Instance. E.g. The product version SAP ERP 6.0 have the following ABAP standalone Main Instances:
- SAP Application Platform - IPC
- SAP ECC Server
- SAP NW - Business Intelligence
- SAP NW - Mobile Infrastructure
- SAP NW - Process Integration
- SAP SEM
- SAP SRM - Catalog Content Mgmt
- SAP SRM - Server
- SAP SRM - Server ECC Add-On
If one Technical System has multiple ABAP standalone Main Instances installed, it's recommended to create separate Product Systems for each ABAP standalone Main Instance.
II. Some Main Instances contain both ABAP and Java components (e.g., SAP NW - Mobile Infrastructure, SAP NW - Process Integration). If such a Main Instance is installed, you need to link it to the relevant Java System Component; this Java System Component is the Java part of the same Technical System of this Main Instance.
III.Some Main Instances include other Main Instances (E.g., in SAP ERP 6.0, Main Instance SAP NW - Enterprise Portal includes SAP NW - EP Core.). If the including Main Instance is installed, it's not necessary to mark the included Main Instance(s) for relevance.
3. Check the ABAP part of the Technical System.
Double-click the relevant ABAP Main Instance from tab Selection of Main Instances of the Product System. You will enter the configuration view for ABAP Main Instances, which shows the ABAP part of the Technical System.
a) ABAP Main Instance, tab Header Data.
Check that fields Installation Number, Message Server, and Database are filled correctly. Double-click field Database, and check that field Server is filled correctly.
b) ABAP Main Instance, tab Clients.
If you need to collect data of activated switch framework components for later delta calculation, or you need to use the service of latest HR package calculation (from ST 400 SP23), the RFC Read Access needs to be available.
Select a row with "RFC Read Access" defined, click button Check RFC Destinations, click buttton Check RFC Destinations on the pop-up window, the checking of read access RFC needs to be ended with green icon and without manual logon required.
c) ABAP Main Instance, tab Software Components.
Check that ABAP Software Components are configured correctly in accordance with the actually-installed ones.
d) ABAP Main Instance, tab Other Attributes.
Check that attribute Landscape Pattern is configured correctly. The landscape pattern is an attribute of the Technical System. There are 3 landscape patterns:
SIDECAR - The Technical System is assigned to one Product System.
HUB - The Technical System is assigned to at least 2 different Product Systems.
DEFAULT - If the pattern is not configured, it is regarded as DEFAULT. With the landscape pattern DEFAULT, the stack delta calculation may be completed successfully, or may be stopped due to failure of auto-recognizing the actual landscape pattern SIDECAR or HUB.
It's recommended to fill the attribute with SIDECAR or HUB starting from ST 400 SP22.
4. Check non-ABAP part of the Technical System.
Double-click the System Components of non-ABAP Main Instances from tab Selection of Main Instances of the Product System; you will enter the configuration view for System Components, which shows the non-ABAP part of the Technical System(s). (System Components are defined under the node Landscape Components -> System Components.)
For the Java System Component of a dual stack Technical System, check that the first 3 chars (SAP system ID) of the System Component name are identical to those of the Product System name which links the ABAP Main Instance(s) of this Technical System.
a) System Component, tab Header Data.
For the Java System Component, check that fields Installation Number, Message Server, and Database are filled correctly. Double-click field Database, and check that field Server is filled correctly. If this Technical System is of type dual stack, check that the above fields are consistent with those of its ABAP stack.
For the TREX System Component, check that field Server is filled correctly for instances with a Server Role of "Server".
If you link a non-ABAP Main Instance which is of type neither Java nor TREX to the Java System Component, you need to manually maintain its software component(s) in this System Component.
b) System Component, tab Software Components.
Check that non-ABAP Software Components are configured correctly in accordance with the actually-installed ones.
c) System Component, tab Other Attributes.
Check that attribute Landscape Pattern is configured correctly. This attribute needs to be filled starting from ST 400 SP20. If this Technical System is of type dual stack, check that this Landscape Pattern is consistent with that of its ABAP stack.