MaintPlan Guide

7/18/2019 MaintPlan Guide

http://slidepdf.com/reader/full/maintplan-guide-56d65f7663769 1/38

SAP Solution Manager

Maintenance Planning GuideUsing SAP Solution Manager 7.0 and 7.1 SP01-04

Target Audience:

■ Technology Consultants

■ System Administrators

■ Support Specialists

Public Version 1.2

March 2013



i

© Copyright 2013 SAP AG. All rights reserved.

No part of this publication may be reproduced or

transmitted in any form or for any purpose without the

express permission of SAP AG. The information contained

herein may be changed without prior notice.Some software products marketed by SAP AG and its

distributors contain proprietary software components of

other software vendors.

Microsoft, Windows, Outlook, and PowerPoint are

registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel

Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390,

OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP,

Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix,

i5/OS, POWER, POWER5, OpenPower and PowerPC are

trademarks or registered trademarks of IBM Corporation. Adobe, the Adobe logo, Acrobat, PostScript, and Reader

are either trademarks or registered trademarks of Adobe

Systems Incorporated in the United States and/or other

countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered

trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame,

WinFrame, VideoFrame, and MultiWin are trademarks or

registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or

registered trademarks of W3C®, World Wide Web

Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems,

Inc., used under license for technology invented and

implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP

NetWeaver, and other SAP products and services

mentioned herein as well as their respective logos are

trademarks or registered trademarks of SAP AG in

Germany and in several other countries all over the world.

All other product and service names mentioned are the

trademarks of their respective companies. Data contained

in this document serves informational purposes only.

National product specifications may vary.

These materials are subject to change without notice.

These materials are provided by SAP AG and its affiliated

companies ("SAP Group") for informational purposes only,

without representation or warranty of any kind, and SAP

Group shall not be liable for errors or omissions withrespect to the materials. The only warranties for SAP

Group products and services are those that are set forth in

the express warranty statements accompanying such

products and services, if any. Nothing herein should be

construed as constituting an additional warranty.

These materials are provided “as is” without a warranty of

any kind, either express or implied, including but not

limited to, the implied warranties of merchantability,

fitness for a particular purpose, or non-infringement.

SAP shall not be liable for damages of any kind including

without limitation direct, special, indirect, or consequential

damages that may result from the use of these materials.

SAP does not warrant the accuracy or completeness of the

information, text, graphics, links or other items contained

within these materials. SAP has no control over the

information that you may access through the use of hot

links contained in these materials and does not endorse

your use of third party web pages nor provide any warranty

whatsoever relating to third party web pages.

SAP NetWeaver “How -to” Guides are intended to simplify

the product implementation. While specific product

features and procedures typically are explained in a

practical business context, it is not implied that those

features and procedures are the only approach in solving a

specific business problem using SAP NetWeaver. Should

you wish to receive additional information, clarification or

support, please refer to SAP Consulting.

Any software coding and/or code lines / strings (“Code”)

included in this documentation are only examples and are

not intended to be used in a productive system

environment. The Code is only intended better explain and

visualize the syntax and phrasing rules of certain coding.

SAP does not warrant the correctness and completeness of

the Code given herein, and SAP shall not be liable forerrors or damages caused by the usage of the Code, except

if such damages were caused by SAP intentionally or

grossly negligent.

Disclaimer

Some components of this product are based on Java™. Any

code change in these components may cause unpredictable

and severe malfunctions and is therefore expressively

prohibited, as is any decompilation of these components.

Any Java™ Source Code delivered with this product is only

to be used by SAP’s Support Services and may not be

modified or altered in any way.



ii

Document History

Document Version Description

1.00 November 8, 2011

First version

1.01 November 29, 2011

Updated section User Maintenance for Maintenance Optimizer.

Updated section Technical and Product Systems.

1.1 May 2012

Complete text review

Deleted: references to Solution Manager System Landscape (SMSY)

Deleted: Table with usage types; not relevant for updates/upgradesIncluded: List of notes for the usage of technical usages

1.2 March 2013

Added chapter 5: Copying Stack Configuration Files for Identical Systems

Added chapter 6: Maintain System Tracks with Maintenance Optimizer

small text corrections

The latest version of this guide can be found in the SAP Service Marketplace at

http://service.sap.com/mopz.

http://service.sap.com/mopz





iii

Typographic Conventions

Type Style Description

Example Text Words or characters quoted

from the screen. These

include field names, screen

titles, pushbuttons labels,

menu names, menu paths,

and menu options.

Cross-references to other

documentation

Example text Emphasized words or

phrases in body text, graphic

titles, and table titles

Example text File and directory names and

their paths, messages,

names of variables and

parameters, source text, and

names of installation,

upgrade and database tools.

Example text User entry texts. These are

words or characters that you

enter in the system exactly as

they appear in the

documentation.

<Example

text>

Variable user entry. Angle

brackets indicate that you

replace these words and

characters with appropriate

entries to make entries in the

system.

EXAMPLE TEXT Keys on the keyboard, for

example, F2 or ENTER.

Icons

Icon Description

Caution

Important

Note

Recommendation or Tip

Example



iv

Table of Contents

1. About this Document .......................................................................................................... 1 2. SAP Solution Manager Prerequisites ................................................................................ 1

2.1 Update SAP Solution Manager ..................................................................................... 2 2.2 Install Implementation Content Add-On ....................................................................... 2 2.3 Install the Landscape Verification Add-On ................................................................... 2 2.4 Complete SAP Solution Manager Basic Configuration ................................................ 3 2.5 User Maintenance for the Maintenance Optimizer ....................................................... 3

3. System Landscape Data Maintenance .............................................................................. 4 3.1 Setup the System Landscape Directory (SLD) ............................................................. 6

3.1.1 Set Up Automatic Data Suppliers .................................................................... 6 3.1.2

Forward Data from Central SLD to Local SLD in SAP Solution Manager ....... 6

3.2 Transfer Data from SLD to SAP Solution Manager System Landscape (SMSY) ........ 7 3.3 Overview: System Landscape Modeling in SAP Solution Manager ............................. 8 3.4 System Landscape Description in Solution Manager System Landscape (SMSY) ... 11

3.4.1 Create and Check Product Systems .............................................................. 11 3.4.2 Assign and Check Product Versions ............................................................. 12 3.4.3 Select Product Instances ............................................................................... 15 3.4.4 Assign Landscape Patterns ........................................................................... 15 3.4.5 Example: SAP CRM with a Sidecar Deployment........................................... 16 3.4.6 Example: SAP ERP 6.0 EHP 5 with a Hub Deployment ............................... 17

3.5 System Landscape Verification .................................................................................. 22 3.5.1 Prerequisites for Landscape Verification ....................................................... 22 3.5.2 Run Landscape Verification ........................................................................... 22 3.5.3 Check Product Systems ................................................................................. 24 3.5.4 Using the Product System Wizard ................................................................. 25 3.5.5 Using the Technical System Wizard .............................................................. 26 3.5.6 Typical Errors ................................................................................................. 26

4. Start a Maintenance Transaction – Select and Download Software Packages ........... 26 4.1 Plan Maintenance ....................................................................................................... 27 4.2 Select Files ................................................................................................................. 28 4.3 Download Files ........................................................................................................... 32 4.4 Implement ................................................................................................................... 32 4.5 End Maintenance ........................................................................................................ 32

5. Maintaining System Tracks with Maintenance Optimizer ............................................. 32 6. Copying Stack Configuration Files for Identical Systems ............................................ 33



Maintenance Planning Guide – Using SAP Solution Manager 7.0-7.1 SP04

Page 1

1. About this DocumentThe Maintenance Optimizer in SAP Solution Manager plays a central role to maintain SAP systems and toinstall and upgrade enhancement package.

It is mandatory to use the Maintenance Optimizer (MOpz) to calculate the required enhancement packagefiles, support package stacks, and additional update packages as well as to create the stack configuration file(XML) that is read by the SAP Enhancement Package Installer (SAPehpi) or Software Update Manager(SUM) during an enhancement package installation or other update process and is used as an input file forthe installation.

The guide is intended for Technology Consultants, System Administrators, and Support Specialists.

It provides information on the following topics:

Required SAP Solution Manager version

Required add-ons for the upgrade and update process

Basic configuration of SAP Solution Manager and configuration of the Maintenance Optimizer

Correct maintenance of your system landscape description in SAP Solution Manager:

o How to add data to your SAP system landscape description in SAP Solution Manager,o How to model technical systems and product systems in SAP Solution Manager for additional

updates

o How to check the correctness of your SAP system landscape description with the landscapeverification tool

o How to calculate and download required software packages with the Maintenance Optimizer

2. SAP Solution Manager PrerequisitesIn order to use the SAP Solution Manager and the Maintenance Optimizer functions for updates or upgrades

as well as for enhancement package (EHP) installation, you need to perform the following tasks:

Task DescriptionUpdate SAP Solution Manager You need to check that you have the

required SAP Solution Manager release.

You require at least SAP Solution Manager7.0 SP23 for the installation of the latest SAPBusiness Suite enhancement packages.

Install the Implementation Content Add-On If you plan to use the implementation contentfor the latest SAP Business Suiteenhancement packages, you require at leastST-ICO 150_700 SP 31.

Install the Landscape Verification Add-On You need to check that you are using the

add-on Landscape Verification 1.0 for SAPSolution Manager. We recommend that youuse at least ST-LV 100 SP2.

Complete SAP Solution Manager BasicConfiguration

You need to ensure that you have done theinitial and basic configuration of SAP SolutionManager in transaction SOLMAN_SETUP.

User Maintenance for the MaintenanceOptimizer

Ensure that you have the correct user andauthorization to work with MaintenanceOptimizer in SAP Solution Manager.

The tasks listed in the above table are explained in detail in the following sections.




Page 2

2.1 Update SAP Solution ManagerFor the installation of the SAP Business Suite EHP5, you require at least SAP Solution Manager 7.0 SP23.(Using the Maintenance Optimizer is mandatory as of SAP Business Suite EHP4.)

We recommend that you always update SAP Solution Manager to the latest support package.

To find the version of SAP Solution Manager in the SAP Solution Manager system choose System → Status

→ Component information. For software component ST, the release must be 400, the SP level should be at

least SP23.

If you are not using the required SAP Solution Manager version, update the application. For more information,see SAP Note 1088980 and the Master Guide SAP Solution Manager 7.1 at http://service.sap.com/instguides → Installation & Upgrade Guides → SAP Components → SAP Solution Manager → Release 7.0 EHP1 (resp. 7.1) → Planning .

2.2 Install Implementation Content Add-OnWe recommend that you use the implementation content add-on.

The implementation content add-on (ST-ICO) provides information on how to implement and configure SAPbusiness scenarios and processes in SAP Solution Manager. This includes scenario and process descriptionsas well as integrated configuration information supported by SAP implementation, operations and upgraderoadmaps.

For SAP Business Suite EHP5, you require at least the implementation content ST-ICO 150_700 SP 31.

ST-ICO 150_700 SP 31 is not included in SAP Solution Manager SP 23, that is, you have to downloadit separately.

To find out which ST-ICO version is deployed on your SAP Solution Manager system, log on to the SAP

Solution Manager system with SAP GUI and choose System → Status → Component information , and

check the level information for the software component ST-ICO. It should be 0031 at least.

For more information about the implementation content, see SAP Note 631042 and SAP Solution Manager for

the SAP Business Suite 7i2011 at http://service.sap.com/solutionmanager → Media Library → Presentations.

2.3 Install the Landscape Verification Add-On

SAP Solution Manager contains a description of your SAP system landscape. The landscape description must

be correct and complete because it is the prerequisite to maintain your applications.

The landscape verification tool helps you to detect and correct errors. It analyzes the landscape description in

your SAP Solution Manager, searches for errors, and displays information on how to correct them. You can

carry out your maintenance transactions more quickly, with fewer errors, and at a lower cost. You can also

correct the detected problems using the landscape verification tool itself.

The landscape verification tool is available as an add-on (ST-LV) to the SAP Solution Manager application.

We highly recommend the use of the landscape verification tool. This document assumes thatlandscape verification tool is installed.

The landscape verification tool only checks technical systems registered via System LandscapeDirectory (SLD) – it does not check technical systems maintained manually in Solution Manager System

Landscape (transaction SMSY or LMDB as of 7.1 SP05 respectively). The procedures listed in this

document require that all systems are registered in the SAP Solution Manager system landscape via theSystem Landscape Directory (SLD).

For more information, see:

SAP Note 1468605 with information about the add-on installation

Landscape Verification page at http://scn.sap.com/docs/DOC-8793. Especially see Documentation ofSP0/1/3 of landscape verification with a detailed documentation.

For a detailed list of restrictions, see SAP Note 1704937.

https://service.sap.com/sap/support/notes/1088980



http://service.sap.com/instguides






http://service.sap.com/solutionmanager






http://scn.sap.com/docs/DOC-8793
















Page 3

2.4 Complete SAP Solution Manager Basic Configuration

To use SAP Solution Manager for enhancement package installation or other maintenance processes, ensure

that the basic configuration was successfully done:

1. Log on to the SAP Solution Manager system.

2. Start transaction SOLMAN_SETUP.

3. In the Overview , check the statuses for System Preparation and Basic Configuration. Both should becompleted.If there are warnings or errors, resolve the issues and complete all open tasks.

The activities Diagnostics Prerequisites at the step Installation Check and DiagnosticsConfiguration at the step Automatic Configuration do not influence the selection and download ofenhancement package files. You may therefore omit these activities at this point.

Ensure that the latest version of SAP Note 1590226 is implemented in your system as it ensures that the

latest version of the Maintenance Optimizer is available in your system (including any corrections).

SAP Solution Manager configuration from an initial state is described in the Solution Operations Guide forSAP Solution Manager , section Software Change Management for more information. You find this guide at

http://service.sap.com/instguides → Installation & Upgrade Guides → SAP Components → SAP SolutionManager → Release 7.0 EHP1 (resp 7.1) → Operations. After the configuration, all statuses must beConfirmed (green icon).

2.5 User Maintenance for the Maintenance OptimizerThe Maintenance Optimizer (MOpz) client of SAP Solution Manager communicates with the MOpz backendon the SAP Service Marketplace to calculate the required download stack for your SAP system landscapemaintenance.

The MOpz was configured during the basic configuration of SAP Solution Manager. Make sure that your userin SAP Solution Manager and your s-user for the SAP Service Marketplace have the required authorizationsto use the MOpz functions and that the two users match:

Your user in the SAP Solution Manager system requires the following roles:

SAP_MAINT_OPT_ADMIN : Full authorization for the Maintenance Optimizer

SAP_MAINT_OPT_ADD : Authorization to write the XML into the EPS inbox directory

SAP_SMWORK_BASIC : Authorization for the work center frame, navigation and table control

SAP_SMWORK_CHANGE_MAN : Access to Change Request Management work center.

Copy the standard roles to your own (customer) namespace, maintain the authorizations, generate theprofiles and perform a user comparison to ensure that the authorizations were assigned to the users.


SAP Note 1032322 for details about additional authorization checks for MOpz, for example, how torestrict specific transactions or functions

Security Guide for SAP Solution Manager for additional information about standard roles athttp://service.sap.com/instguides → Installation & Upgrade Guides → SAP Components → SAPSolution Manager → Release 7.1 → Operations

You need an SAP Service Marketplace (SMP) s-user . If you do not have one, you can request it athttp://service.sap.com/user-admin → Request New Users.

Your s-user needs the SWCATALOG authorization to execute MOpz and to order software from the SAPSoftware Catalog. To check authorizations, goto http://service.sap.com/user-admin, log on with your user, andchoose Search and Maintain Users. The authorization for the Execute Maintenance Optimizer activity must be

assigned.

Assign your s-user to the SAP Solution Manager user that works with MOpz:

1. In your SAP Solution Manager system, start transaction AISUSER .











http://service.sap.com/user-admin














Page 4

The value help for the Contact Person field only shows entries if the background jobREFRESH_ADMIN_DATA_FROM_SUPPORT has already been run. If this is not the case, thereis no value help and manual entries cause a warning message because the s-user is not found.

Assign the contact person for the system administrator user first and maintain the contact personsfor all other project members when the administrator has run the background job.

2. Choose New Entries. Under User , enter an SAP Solution Manager system user and under ContactPerson assign an SAP Service Marketplace (= SAP Support Portal) contact person (an s-user IDwithout the „s‟).

If three instead of two columns are visible in transaction AISUSER , you are running the BAdi

Business Add-In to Manage Several SAP Customer Numbers, which is applicable if you manageseveral SAP customer numbers in your SAP Solution Manager system. If you do not manageseveral SAP customer numbers, deactivate this BAdI:

a. Start transaction SPRO in the SAP Solution Manager system.

You find the BAdI in the SAP Reference IMG under SAP Solution Manager → BasicSettings → Connection to SAP → Several SAP Customer Numbers -> Business Add-In toManage Several SAP Customer Numbers.

b. The dialog will ask you whether you want to deactivate the BAdI implementation

AI_SDK_SP_RFC_RP AI_SDK_SP_RFC_RP. Choose Yes.c. Check transaction AISUSER . It now shows only two columns.

For more information on the Maintenance Optimizer, see the SAP Service Marketplace athttp://service.sap.com/mopz.

3. System Landscape Data MaintenanceThe SAP NetWeaver System Landscape Directory (SLD) is the central directory the information on the

technical systems of your landscape relevant for the management of your software life-cycle. It contains a

description of your technical systems (that is, the software components currently installed) and a repository of

products and software components that can theoretically be installed in your landscape (such as the software

components available from SAP). As the landscape description is updated automatically once you have set-

up the systems self-registering, the SLD provides reliable and up-to-date information and functions as the

central information provider for SAP Solution Manager and Maintenance Optimizer.

The Maintenance Optimizer relies on up-to-date information about your system landscape. Therefore, it is

crucial that this data is correctly maintained in the SAP Solution Manager system landscape (transaction

SMSY).

The landscape verification tool helps you to detect and correct errors in the system landscape description of

SAP Solution Manager (transaction SMSY).

The following figure shows how the process of maintaining system landscape data in SAP Solution Manager

works:






Page 5

Task Description

0: Set Up Automatic Data Suppliers Add a new SLD on the Administration → Data Suppliers

page on the central SLD.

Java systems are registered with the Visual Administrator

or, as of SAP NetWeaver 7.1, the NetWeaver

Administrator.

AS ABAP systems are registered with transaction RZ70.

TREX is registered by generating SLD configuration files

and copying them to the Global SLD Directory.

1: Forward Data from Central SLD to Local

SLD in SAP Solution Manager

Typically, all systems address either directly or indirectly a

central SLD in your system landscape, which transferssystem data to the local SLD in your SAP Solution Manager

system.

2: Transfer data from SLD to the SAP

Solution Manager system landscape (SMSY)

To ensure that the data is transferred, you have to check

that the LANDSCAPE_FETCH background job is

scheduled in SAP Solution Manager (transaction sm37).

3: System Landscape Verification You have to run the background job in transaction

LVSM_LOAD before you start transaction LVSM in SAP

Solution Manager to check the description of the system

landscape in SMSY.

4: Starting a Maintenance Transaction – Selecting and Downloading Software

Packages

Use verified system description to create an XML stack filein the Maintenance Optimizer




Page 6

3.1 Setup the System Landscape Directory (SLD)

3.1.1 Set Up Automatic Data Suppliers

Depending on your system landscape setup, data can be sent automatically to the SLD from the followingsystems:

Application Server (AS) ABAP systems are registered with transaction RZ70.

AS Java systems are registered with the Visual Administrator or, as of SAP NetWeaver 7.1, theNetWeaver Administrator.

Dual-stack system can be registered automatically when the related AS ABAP and the AS Java havebeen registered.

TREX systems are registered by generating SLD configuration files and copying them to the GlobalSLD Directory.

Selected technical systems used by SAP, for example ATC Server, Unspecific Cluster System, MSIIS Instance, use predefined data suppliers.

For third-party systems, you can setup generic data suppliers like sldreg.How exactly the technical systems can be registered in the SLD is described in the Planning Guide - System

Landscape Directory in the SAP Community Network at http://scn.sap.com/docs/DOC-14151.

3.1.2 Forward Data from Central SLD to Local SLD in SAP

Solution Manager

If you maintain your system landscape data in a central SLD (outside SAP Solution Manager), you need to

setup the system data transfer to the local SLD (inside SAP Solution Manager):

If you are not using SAP NetWeaver Process Integration or any Web Dynpro Java applications, you can use

only the local SLD inside SAP Solution Manager as the central SLD:

If you are using a central SLD and a local SLD, you have to setup a bridge forwarding process from the

central SLD to local SLD. This ensures that, every time a system updates its information in the SLD, the

information update is automatically forwarded to all other SLDs that are maintained in the central SLD as

bridge forwarding partners.Perform the following steps to add the Solution Manager local SLD to the central SLD:








Page 7

1. Log onto the central SLD.

2. The URL for the central SLD is http://<sld host name>:<sld port>. In a standard installation, the portis: 5<SLD system Java instance number>00.

3. Open the Administration page.

4. Open the Data Suppliers link.

5. Choose Add SLD.

6. Enter the appropriate values in the following fields:

7. In the URL field, enter http://<solman host>:<solman port>. <solman host> is a SAP Solution Managerhost name and <solman port> is usually 5<SAP Solution Manager instance number>00 in a standardinstallation.

8. In the User field, specify SLDDSUSER.

9. In the Password field, enter the user password.

10. Save your changes.

For more information about the SLD, see:

System Landscape Directory in the SAP Community Network at http://scn.sap.com/docs/DOC-8042. Planning Guide - System Landscape Directory in the SAP Community Network at

http://scn.sap.com/docs/DOC-14151.

3.2 Transfer Data from SLD to SAP Solution Manager

System Landscape (SMSY)

After setting up the automatic system registration in the SLD, you can synchronize this system information

from the SLD with the SAP Solution Manager system landscape (SMSY). This transfer is performed by the

LANDSCAPE_FETCH background job that is scheduled during the initial configuration of the SAP Solution

Manager system (see Complete SAP Solution Manager Basic Configuration).

Check if the LANDSCAPE_FETCH job has been scheduled in transaction sm37.

If the job has not yet been scheduled, proceed as follows:

1. In the SAP Solution Manager system, start transaction SMSY_SETUP.

2. In the Automatic Data Transfer area, choose System and Landscape Directory (SLD).

3. Choose Schedule Automatic Data Transfer to schedule the LANDSCAPE_FETCH job.

4. Enter the start date.

5. Choose whether the job runs once or periodically (if you wish to run it once, do not set the PeriodicJob indicator).


The SAP Solution Manager system collects the system data automatically at the specified time, or

periodically, and displays it in the Solution Manager System Landscape (SMSY). After the data collection, the

automatically identifiable systems and servers are visible in the Solution Manager system landscape.

The system logs each data transfer. You can call the logs in the transactions SMSY_setup and SMSY

in the main menus under Logs → Update Logs → Display .

Check if the system data from the SLD was transferred to the Solution Manager system landscape

(transaction SMSY) by performing the following steps:

1. Start transaction SMSY in the SAP Solution Manager system.

2. Choose Landscape Components → Product Systems or Technical Systems and ensure that yoursystems are in the list.

If your servers are not in the list, set up the LANDSCAPE_FETCH job as described above.











Page 8

For more information, see http://help.sap.com → Application Lifecycle Management → SAP Solution Manager

→ SAP Solution Manager 7.0 → Basic Settings → Solution Manager System Landscape → Set Up Automatic

Data Capture for System Landscape.

3.3 Overview: System Landscape Modeling in SAP SolutionManager

With the technical system information as a basis, you can now start to model the logical system landscape

description in the SAP Solution Manager.

This section explains how to model your system landscape in SAP Solution Manager. First of all, it is very

helpful to understand the basic terminology used in this context:

Product SAP Products are the applications SAP ships and group sets of functions to solve business

requirements. The complete product catalog is shipped as SAP Software Catalog (or “CR

Content” in the SLD). The availability of products is published in the Product Availability

Matrix (PAM. Under http://service.sap.com/pam). The product model defines the product

structure with its product instances, software components, version, and technical

dependencies between product and its components. Products typically have a name

starting with 'SAP...' and are characterized by a version period and a maintenance cycle.

A product can be installed on one or more technical systems. All technical systems that are

involved in the installation of one product form the product system.

Examples: SAP ERP, SAP NetWeaver, and SAP Solution Manager.

One product consists of one or more product versions.

Product

version

Each SAP product is installed in a product version, which is a concrete release of a product,available at a particular time for a specific scope of functionality. It bundles productinstances and the included software component versions.

Like products, information on product versions is shipped in the SAP Software Catalog.They are the basis for the compatibility of closely coupled systems and the maintenance ofproduct systems. For each product version, a maintenance period is defined.

Example: SAP ERP 6.0, which is a product version of the product SAP ERP.

There are standalone product versions (for example, SAP ERP 6.0) and add-on

http://help.sap.com/



http://service.sap.com/pam








Page 9

product versions that require another product version as foundation for their installationand operation (for example, EHP5 for SAP ERP 6.0). For more information about add-onproduct versions, see Assigning and Checking Product Versions.

Technical

system

Installing a product version on hardware, on one or several physical or virtual hosts, createsone or more technical systems. Technical systems can either be distributed on one or more

application servers or on a database system on the same or a different host, webdispatcher, etc. or can run everything on one host.

A technical system is installed and administered as a whole. Often, e.g. in AS ABAP and AS Java, it is identified by a system ID (SID) or extended SID, a host, and an installationnumber. There are different technical system types, for example Application Server (AS)

ABAP, AS Java, or TREX.Technical systems are central elements when it comes to maintenance and operationalactivities, such as monitoring and alerting.

Product

system

A group of technical systems on which a product version is installed. Product systems areused to maintain and plan products in the system landscape.Most product versions can be installed in different ways on one or more technical systems,therefore knowing only the product version is not enough for maintenance. You also need to

define the associated product systems to maintain SAP products.On the technical systems of a product system, one standalone product version and eitherzero, one, or several add-on product versions are installed. One product system can consistof only one ABAP-based technical system and zero, one or several non-ABAP technicalsystems.

Software

component

version

Product versions bundle software component versions that are made available at the sametime for implementing a specific scope of functionality. A software component is the

smallest entity that can be installed on a technical system. It is a reusable component of theproduct. A software component version can be part of several product instances. It canrequire other software component versions to be installed as well.

Examples: SAP_HR, SAP_BASIS, BBPCRM.

Productinstance

Technically dependent software component versions are grouped in product instances(formerly known as main instances, instance or software units in transaction SMSY) which

are the smallest elements in a system landscape described in SAP Solution Manager. Oneproduct instance must be installed and updated as a whole on a single technical system.(ABAP-Java dual stack systems are considered one technical system.) Patches can still beinstalled for individual software components.

The various product instances of a product version can be installed on one or severaltechnical systems.

There are some exceptions to this rule. Some product instances (for example in SAPNetWeaver PI) are installed on both the AS ABAP and AS Java technical systems. Insuch cases you have a mandatory dual stack and in this case both stacks are treated asone technical system, even though for a dual stack system technical systems of the

types AS ABAP and AS Java need to be registered separately in the System LandscapeDirectory (SLD).

Examples: SAP ECC Server, SAP XSS (Self-Services), TREX.

Synonyms: main instance (in SAP Solution Manager transaction SMSY), software unit (inSystem Landscape Directory [SLD])

Technical

usage

Technical usage is a further qualification describing a specific configuration of a productversion. It bundles product instances for a distinct usage. It can be spread over multipletechnical systems and technology types. Not all product versions have this additionalgrouping. There is a mapping between business functions and technical usages for ERPenhancement packages.

For more information about products and their elements, see Understanding Landscape Descriptions - Part I:the Simple Approach to Explaining Products, Product Instances, and Software Components in the SAP

Community Network.

http://scn.sap.com/people/wolf.hengevoss/blog/2011/07/21/understanding-landscape-descriptions--part-i-the-simple-approach-to-explaining-products-product-instances-and-software-components









Page 10

For more information about technical usages and business functions, see the Master Guide for SAP ERP 6.0Enhancement Package 6 at http://service.sap.com/erp-ehp6-inst, section Enhancement Packages andSoftware Components: Architecture Overview .

In the following, the rules to model a landscape description in SAP Solution Manager are listed:

1. A product system usually has one active standalone product version. The standalone product

version must be installed on all technical systems belonging to the product system.

(The dual-stack upgrade to SAP NetWeaver 7.30 with SEM-BW is an exception to this rule. In this case,see SAP Note 1539356 for a description of the correct product system configuration.)

2. If additional add-ons or enhancement packages (EHPs) are deployed on the system, these alsomust be maintained as active product versions in the product system.There are two kinds of EHP product versions: add-on EHPs and standalone EHPs. For example, SAPERP 6.0 EHP 6 is an add-on product version that requires its standalone SAP ERP 6.0 product version;SAP EHP3 FOR SAP NETWEAVER 7.0 is a standalone product version.

3. All installed product instances of a product version must be assigned to the product system.

Some product instances contain both ABAP and Java components (for example, SAP NetWeaverMobile Infrastructure or SAP NetWeaver Process Integration). If such a product instance is installed,you have to link it to the relevant Java technical system.

4. Landscape patterns must be assigned to technical systems.

A landscape pattern defines whether a technical system is assigned to one (sidecar) or more (hub)product systems. For more information, see Assign Landscape Patterns.

SAP NetWeaver ERECRUIT, LSOFE, SEM-BW, and FINBASIS are stand-alone Add-Onsinstallable on SAP NetWeaver systems, but in SAP PPMS they are modeled within the ERP product.

Therefore, the system must be configured as ERP system and the corresponding instance must bemarked as installed.For more information, see SAP Note 1326576 and SAP Note 1531022.

We recommend that you use the landscape verification tool (see System Landscape Verification) for the system landscape modeling.

It sends a notification when incorrect product versions are assigned to the product systems andenables you to correct product version assignments.

It calculates a list of product instances that can be assigned to the product systems, based on thesoftware component versions of all technical systems assigned to the product system.

It sends notifications if, for example, the landscape pattern is not correctly set or if wrong productinstances are assigned to a product system.

If you have not installed the Landscape Verification add-on and do not use it to check the systemlandscape description, see Assign and Check Product Versions for a description how to assign a productversion to a product system in transaction SMSY.

If you model a product system for a SAP CRM, SAP SRM, or SAP SCM product with an SAPNetWeaver Java component (for example, SAP Enterprise Portal), create a separate product systemfor the SAP NetWeaver product. All installed SAP NetWeaver product instances have to beassigned to this product system.This note is relevant for the following product versions:

SAP CRM 7.0

SAP CRM 7.0 / NW7.01

SAP SRM 7.0

SAP SRM 7.0 / NW7.01

SAP SCM 7.0

When you maintain an add-on product version, you always also have to maintain the underlying (required)standalone product.

http://service.sap.com/erp-ehp6-inst



















Page 11

There are different kinds of enhancement package (EHP) product versions: an add-on EHP and a standaloneEHP. For example, SAP ERP 6.0 EHP 5 is an add-on product version, which requires its stand-alone productversion SAP ERP 6.0. SAP Solution Manager 7.0 EHP1 is shipped as Support Package.

For the product ERP 6.0 (2005) and corresponding enhancement packages, use the product SAP ERP andnot the product SAP ECC. If the product SAP ECC was assigned as the product system you need to change it

to SAP ERP, as described below.

3.4 System Landscape Description in Solution Manager

System Landscape (SMSY)

SAP Solution Manager 7.0 SAP Solution Manager 7.1

SP01-04

SAP Solution Manager 7.1

SP05

Product and technical system

information is maintained in

SMSY.

Product system information is

maintained in transaction SMSY.

Technical system information is

maintained in the new LandscapeManagement Database

(transaction LMDB).

Product and technical system

information is maintained in the

LMDB.

Note that an updatedversion of the Maintenance

Planning Guide will be

published for SP05 at

http://service.sap.com/mopz.

If you do not use the landscape verification tool, you need to model your system landscape manually in SAP

Solution Manager System Landscape (transaction SMSY) in accordance with the Basic System Landscape

Modeling in SAP Solution Manager . The following sections describe how to model systems manually in SMSY.

3.4.1 Create and Check Product SystemsTechnical systems are created in the SAP Solution Manager system landscape (transaction SMSY) during the

system data transfer from the System Landscape Directory (SLD). For AS ABAP technical systems, a product

system with the same name is created automatically.

To find a product system:

1. Start transaction SMSY in SAP Solution Manager.

2. Go to Landscape Components → Server .

3. Right-click on a server for your system and select the Where-Used List .

4. The table Use as Server in Product Systems provides you with an overview of the product systemscreated for your server (with product instances).

SMSY landscape components (product and technical systems, databases, servers) with nameslike <SID>_<number>, <SID><number> or <SID>_NABP (for dual-stack systems) are created in

SMSY if <SID> is the same in the SLD and in transaction SMSY, but any one of the following data

types may be inconsistent: message server, database server, installation number. To correctinconsistencies, see SAP Note 1507548.

If no product system was created for your technical system (because it is no AS ABAP), you can manually

create it:

1. Choose Landscape Components → Product Systems.

2. Right-click your product and choose Create New System with Assistant (for example SAP ERP).

The Create System wizard starts.

See also Assigning and Checking Product Versions for information on how to define a product.










Page 12

Figure: Create New System with Assistant

3. Choose Continue.

4. At the step Specify System ID and Product enter the following data:

a. Product System: Your SID plus optional 5 characters to clearly identify your system.

b. Short Description: Free text.

c. SAP Product : Already filled with default data.

d. Product Version: Choose the correct product version of your source system.

e. Enter the Installation Number .

5. Choose Continue and confirm the warning about a long system name if it appears.

6. Keep choosing Continue without entering any data until you reach the Complete pushbutton.

7. Choose Complete.

The product system is created under the specified product version.

8. Check whether the correct product version of your source system is displayed in the area ActiveProduct Versions on the Header Data tab.

3.4.2 Assign and Check Product Versions

You can check which of your products are add-ons and which are standalone products in the following way:

1. Start transaction SMSY in your SAP Solution Manager system.

2. Choose Product Definitions and select a product.

3. Open the Product Versions tab. If the Add-On Product Version checkbox is selected, the product isan add-on and has to be assigned to the product system together with a standalone product.

Examples of add-on product versions:




Page 13

Examples of standalone product versions:

A double-click on a product version calls up additional information about software component versions,

product instances, and required standalone products (for add-on product versions).

Example of a standalone product version for an add-on product version:




Page 14

Start with assigning a standalone product version to the product system. For example, an SAP CRM product

system is SAP CRM 7.0/NW 7.01. If you have also installed an SAP CRM enhancement package, assign

EHP1 FOR SAP CRM 7.0 as the add-on product version to this product system.

Figure: Example of a product version and add-on product version assigned to the product system.

You can check which product versions are assigned to the product system in the following way:

1. Start transaction SMSY in SAP Solution Manager.

2. Choose Landscape Components → Product System → <System>.

3. Open the Header Data tab.

4. Assigned product versions are displayed in the Active Product Versions section.

If your product version is not displayed correctly, you have to adapt it as follows:

1. Switch to the edit mode.

2. Choose Change Product Assignment .

3. Select your Product and Product Version and choose Copy .

4. If you do not find the correct version, select the checkbox Free Product/Select Production Version anddefine your product version.

5. Set the installed product version as Active.

6. If you need to delete an installed product version, select the product version in the list and chooseDelete Product Version.

7. Choose Continue.

The active product version is displayed.




Page 15

3.4.3 Select Product Instances

When the correct product versions have been assigned to the product system, you have to switch to the

Product Instance Selection tab to check the product instances.

Product instances can be either of the type ABAP or non-ABAP:

For ABAP installed product instances, only one can be set to Relevant , the others have to be set to Also Installed in Relevant ABAP Product Instance.

The Relevant and Also Relevant flags have the same meaning. One of the product instances isset to Relevant , the others are set to Also Relevant . There is no semantic difference between productinstances marked as Relevant and Also Installed in Relevant ABAP Product Instance.

Non-ABAP installed product instances have to be set to Relevant . For relevant non-ABAP productinstances, also maintain Technical System and System Type columns. For Java product instances,set the system type to Java; for TREX product instances, set the type to TREX ; for other non-ABAPproduct instances, select the type Java and link them to a Java technical system.

For Dual-Stack product instances, the flag needs to be set to Relevant/Also Installed for ABAP andJava product instances. For the relevant Java product instances the Technical Systems Assignment

needs to be set and the System Type and Technical System columns have to be maintained.

For detailed information about technical usages, see the following SAP notes:

1642789 Enhancement Package 2 for SAP CRM 7.0: Required SWC

1473026 Enhancement package 1 for SAP SCM: Required SWC

1585806 Enhancement package 2 for SAP SCM 7.0: Required SWC

1083576 SAP enhancement package 3 for SAP ERP 6.0 - required SWC

1324838 Enhancement package 5 for SAP ERP 6.0: Required SWC

1165438 Enhancement package 4 for SAP ERP: Required SWC

1566412 Enhancement package 6 for SAP ERP 6.0: Required SWC

1359215 Technical prerequisites for using enterprise services

1595753 Enhancement packages for SAP CRM 7.0: Required SWC 1052470 SAP ERP 6.0 EhP 2 - Business functions and SW components

3.4.4 Assign Landscape Patterns

If you have implemented SAP NetWeaver applications (for example SAP NetWeaver Portal) with one or more

SAP Business Suite applications as a hub or sidecar system, as is described in the Planning Guide - SAP

Business Suite Landscape Implementation, you have to specify a landscape pattern for the system in the SAP

Solution Manager system landscape.

This section describes how to assign landscape patterns for technical systems and illustrates the usage of

landscape patterns.

To specify a landscape pattern for a technical system, perform the following steps:

SAP Solution Manager 7.0 SAP Solution Manager 7.1

1. Start transaction SMSY in SAP Solution

Manager.

2. Select the technical system in the list ofLandscape Components.

3. Open the Other Attributes tab.

4. Switch to the edit mode.

5. Select a value (HUB or SIDECAR) for theattribute Landscape Pattern in the Attribute Value field.


1. Start transaction LMDB in SAP Solution

Manager.

2. Select the technical system and chooseEdit .

3. On the Overview , set the LandscapePattern parameter to Hub or Sidecar .



































Page 16

3.4.5 Example: SAP CRM with a Sidecar Deployment

This section shows an example of a sidecar deployment: An SAP Customer Relationship Management (SAP

CRM 7.0) application uses SAP Interactive Forms by Adobe.

For the maintenance of the SAP CRM 7.0 application with Adobe Document Services (SAP NetWeaver 7.3),

one product system for SAP CRM (in this example, product system LGD) will be created. It uses the CRM AS

Java product instance from the technical system for SAP NetWeaver (in this example: A96).

In SMSY, the product system LGD, with its product instances and A96 as sidecar technical system, looks like

this:




Page 17

Since A96 is not used by any other product systems, it is a “sidecar” technical system:

The landscape pattern sidecar effects the most restricted variation of the connected technical systems in the

product system – the calculated target technical SAP NetWeaver layer of the technical system A96 is kept asconsistent with the LGD system as possible.

During the update of the system LGD, the technical SAP NetWeaver stack and the product stack of CRM 7.0

are both updated synchronously. As a result, both systems are on the same technology level as well as on the

same SP stack level.

3.4.6 Example: SAP ERP 6.0 EHP 5 with a Hub Deployment

In this example, an HCM application of SAP ERP (EHP5 FOR SAP ERP 6.0) is running on an AS ABAP-

based backend system (product system F6W) and a separate SAP NetWeaver Portal system (SAP EHP2

FOR SAP NETWEAVER 7.0) that provides the Employee Self-Services (product system F6X). Additionally,

the Portal system is used by an SAP SRM 7.0 system (product system F7A).




Page 18

The following product systems have to be maintained in SAP Solution Manager system landscape in

transaction SMSY:

Product System F6W

Product system F6W is created for the maintenance of the HCM application and contains thetechnical systems F6W and F6X. The product version EHP5 FOR SAP ERP 6.0 is installed on bothtechnical systems.

According to the product definition data in transaction SMSY, EHP5 FOR SAP ERP 6.0 is an add-on

product version that requires the standalone product version SAP ERP 6.0 (see also Assign and

Check Product Versions). Therefore one standalone product version (SAP ERP 6.0) and one add-on

product version have to be assigned to the product system F6W and set to active.

The product instances Central Applications, Portal Content , Portal Content Self Services, SAP XSS

(Self-Services), are set to Relevant for the product system F6W:




Page 19

Product System F7A

The product systems F7A and F6X are created for the maintenance of the SRM application.

The product system F7A contains the technical systems F7A and F6X. The product version SAP SRM

7.0 is installed on both technical systems.

For the product version SAP SRM 7.0 you also need to create a separate product system for the SAP

NetWeaver Portal, as described above in the important note.

According to the product definition data in transaction SMSY, EHP1 FOR SAP SRM 7.0 is an add-on

product version that requires a standalone product version SAP SRM 7.0 (see Assign and Check

Product Versions):




Page 20

The product instances SRM Server and Portal Content Supplier are set to Relevant for the product

system:

Product system F6X

For the product version SAP SRM 7.0 you also need to create a separate product system for the SAP

NetWeaver Portal (SAP EHP2 FOR SAP NETWEAVER 7.0).

The same product system for the SAP NetWeaver Portal (SAP EHP2 FOR SAP NETWEAVER 7.0)

can be used, if you want to implement new SAP NetWeaver Portal functionality available with a new




Page 21

enhancement package version for SAP NetWeaver 7.0 with the SAP ERP product system, and the

SAP SRM product system remains unchanged.

According to the product definition data in transaction SMSY, SAP EHP2 FOR SAP NETWEAVER 7.0

is a standalone product version (see Assign and Check Product Versions):

The product instance Enterprise Portal is set to Relevant for the product system:

The same technical system F6X is assigned to the Enterprise Portal product instance of the product

system F6X (SAP Enterprise Portal) and to the Portal Content Supplier product instance of the

product system F7A (SAP SRM). Therefore, the product system F6X (SAP Enterprise Portal) will be

taken into consideration during the update of the product system F7A (SAP SRM).

The technical system F6X is used by multiple product systems, therefore it needs to be maintained as

a hub in transaction SMSY:




Page 22

3.5 System Landscape Verification

When Transfer Data from SLD to the SAP Solution Manager System Landscape has successfully been

completed, you need to ensure that system landscape in SAP Solution Manager system landscape

(transaction SMSY) is described as explained in System Landscape Modeling in SAP Solution Manager .

The landscape verification tool can analyze the landscape description in your SAP Solution Manager system

landscape, identify inconsistencies or errors, and display information about how to solve them. You can also

correct any detected problems with the landscape verification tool itself.

The use of the Landscape Verification is recommended.

For known restrictions regarding the landscape verification function in LMDB, see SAP Note

1704937.

3.5.1 Prerequisites for Landscape Verification

To be able to use all functions of the landscape verification tool, your user in the SAP Solution Manager

system must have the role SAP_SMSY_LV_ALL.

The add-on ST-LV is needed to perform landscape verification, see Install the LandscapeVerification Add-On.

To enable all the functions of the landscape verification tool, you first need to run a job that checks the entire

system landscape available through the system landscape of SAP Solution Manager (transaction SMSY) for

possible errors, gaps, or inconsistencies.

The job can have a runtime of several hours. Therefore start this job in good time before your firstuse of the landscape verification tool.

To start this job, proceed as follows:

1. Start transaction LVSM_LOAD.

2. In the Notification group box, you can activate the indicator for sending an e-mail to inform you when

the job is done.If a valid e-mail address is not maintained for your user, you will receive a message in your SAP

Solution Manager inbox (transaction SBWP).

To receive a notification e-mail, check that the SMTP node for SAP Connect (transaction scot) in

SAP Solution Manager is configured and a valid e-mail address is specified for your user in the usermaintenance (transaction su01).

For additional information about the configuration of e-mail using SMTP, see SAP Note 455140.

3. Choose Program → Execute in background .



Documentation of Landscape Verification at http://scn.sap.com/docs/DOC-8793.

For a detailed list of restrictions that are valid until 7.1 SP3, see SAP Note 1704937.

3.5.2 Run Landscape Verification

To start landscape verification, start transaction LVSM . The application opens in a new window. If the

LVSM_LOAD job has not been run when you start transaction LVSM , the system displays a message.

If you receive an error message about a missing s-user, check whether an s-user was assigned toyour system user in SAP Solution Manager transaction aisuser.

On the Home tab of the landscape verification tool, you see an overview of the most important landscape

verification details: The Task List contains a brief summary on how to work with the landscape verification tool.























Page 23

The Technical Systems Summary provides details on the status of your landscape descriptions in

transaction SMSY.

The SAP Landscape Model explains the terminology used for the landscape description within theSAP Solution Manager and that is relevant for the landscape verification check (for example, productsystem, technical system, product version, product instance).

You can switch to two displays of detected errors and inconsistencies by selecting the corresponding tabs

System Landscape and Errors – Warnings. In both views, you can see the errors and problems that

landscape verification has detected in your SAP Solution Manager System Landscape.

The System Landscape tab displays an overview of your system landscape. If errors have beendetected, these are displayed for each landscape element (product versions, product systems, andtechnical systems).

Figure: System Landscape tab

The Errors - Warnings tab shows a list of all errors and warnings detected in your system landscape.

To display more detailed information for one of these messages, choose the relevant message. A

separate window appears, containing a detailed long text that contains the cause for the problem and

also information about how to correct it.

You can correct inconsistencies directly within the tool. To do so, choose the activity related to the

relevant problem under Error Correction. The system displays a screen on which you can correct the

error.




Page 24



Documentation of Landscape Verification at http://scn.sap.com/docs/DOC-8793.

For a list of restrictions that are valid until 7.1 SP3, see SAP Note 1704937.

3.5.3 Check Product Systems

To check the status of product systems with the landscape verification tool, do the following steps:

1. Start transaction LVSM in SAP Solution Manager.

2. Go to the tab System Landscape.

3. Choose All Systems in the Product Systems list.

A list of all technical systems and product systems is displayed.

4. Find your system by using filters (for example name or database).

5. If the status of a technical system is red or yellow, switch to the tab Errors – Warnings for moreinformation and to correct any errors.

Follow the instructions described in the error message text to correct the error. To start the error

correction wizard, choose the pushbutton for a detected problem in the Error Correction column.
















Page 25

If you get an error message that the technical system is not assigned to a product system, you have

to assign it to an existing product system (using the Technical System wizard, see Using the

Technical System Wizard) or to a new product system (which you can create using the Product

System wizard, see Using the Product System Wizard).

6. If the technical systems have a green status, check the product systems to which the technicalsystems are assigned. A list of product systems for the technical systems is available on the ProductInstances tab of the technical system.

7. To find a product system, enter name of the product system in the Filter Product System field andchoose Filter Product System.

8. The specified product system appears in the Product Systems list.

9. Check the status of the product system.

If status of the product system is red or yellow, then switch to the Errors and Warnings tab and follow

the instructions described in the error message text to correct the errors. To start the error correction

wizard, choose the pushbutton for a detected problem in the Error Correction column.

If status of the product system is green, it is described correctly in the SAP Solution Manager system

landscape.

3.5.4 Using the Product System Wizard

The wizard enables you to create and edit properties of product systems.

There are several ways to start the wizard in the landscape verification tool:

To create a new system, choose Add Product System. In this case, you have to carry out all four of

the wizard's steps.

To correct errors, choose the pushbutton for a detected problem in the Error Correction column on theError - Warnings tab. In this case, the wizard starts with the relevant product system, if the detectedproblem concerns the properties of a product system. The wizard starts at the precise step where youcan edit the system properties that caused the problem.

To edit a product system, select it from a list and choose Change Product System in the contextmenu.

The user interface of the wizard also contains information about its usage.

For more information, see Documentation on landscape verification in the SAP Community Network at








Page 26

3.5.5 Using the Technical System Wizard

The wizard enables you to edit the properties of technical systems.

To start the wizard, choose the pushbutton for a detected problem in the Error Correction column on the Error

- Warnings tab. In this case, the wizard starts with the relevant technical system, if the detected problem

concerns the properties of a technical system. The wizard starts at the precise step where you can edit the

system properties that caused the problem.

The user interface of the wizard also contains information about its usage.

For more information, see Documentation on landscape verification in the SAP Community Network at


3.5.6 Typical Errors

For more information, see chapter 7.1 Messages in the Documentation on landscape verification in the SAP

Community Network at http://scn.sap.com/docs/DOC-8793.

The current version of landscape verification tool has the following restrictions:

Only ABAP, Java, TREX and Dual Stack systems can be verified with landscape verification tool. Thismeans that, for example the tool currently does not support SAP Business Objects products.

The tool currently does not support multiple standalone product version assignment, see SAP Note1546286. Therefore, do not change the system descriptions of systems with multiple standalone productversions with the Product System Wizard, see SAP Note 1538652.

For a detailed list of restrictions, see SAP Note 1704937.

4. Start a Maintenance Transaction – Select and

Download Software PackagesThe Maintenance Optimizer tool in SAP Solution Manager is used for the calculation of the required

enhancement package files and for the creation of the stack configuration file. The following sections describe

the procedure in detail.

In the SAP Solution Manager system, start transaction SOLMAN_WORKCENTER and choose the Change

Management Common Tasks New Maintenance Transaction.



















Page 27

In case of authorization issues, see User Maintenance for Maintenance Optimizer .

For the selected product version, a Maintenance Optimizer transaction with a unique identifier is created. Theprocess consists of five steps, which are described in the following sections.

4.1 Plan MaintenanceTo complete this work step of the Maintenance Optimizer transaction, proceed as follows:

1. Select the solution/product version for which you want to download the software packages.

For any enhancement packages for SAP ERP, select product version SAP ERP.

2. The related product systems are displayed. Select one or several product systems to be updated.

We recommend that you create a single stack configuration file for all product systems of atrack (development system, quality assurance system, and production system). In addition, runyour Maintenance Optimizer transactions for every affected system at the same time, in the samemaintenance transaction. This way you ensure that all systems are upgraded with exactly thesame software.If you run the same Maintenance Optimizer transaction at different points in time, it can includeslightly different software because SAP changes support package stacks whenever a fix isavailable for a critical issue in the software.

If you get the system message „There is already a transaction for the systems of this productversion‟, check SAP Note 1296589 and perform the manual steps described in the note.

3. Choose Continue.

The system checks the instances installed in your product system and determines the update options.This check is based on the product system settings that you made in the Landscape ManagementDatabase (LMDB).








Page 28

4.2 Select FilesTo complete this work step of the Maintenance Optimizer Transaction, proceed as follows:

1. Choose Calculate Files Automatically as the file selection mode.

Check the Log tab regularly, to see if any issues have occurred. In addition, the Systems tabprovides helpful information about the systems to be updated or upgraded.

2. Choose Continue. Decide which update option you want to pursue.

Select the Enhancement Package Installation update option if you want to install a new enhancementpackage. If you want to upgrade to an enhancement package, select the upgrade option UpgradeEnhancement Package Installation.

3. Choose Continue to proceed with the Choose Stack sub-step.4. Select the Target enhancement package product version and Target enhancement package stack

level .

Choose Stack Details to display a summary of the contents of the selected target stack.




Page 29

5. Select the technical usages.

A technical usage provides a set of business functions. Therefore, the decision which technicalusages are to be installed depends on the business requirements. From a technical point of view, atechnical usage consists of product instances that consist of software components.If you need help with the decision about technical usages, see the Business Function Prediction for

SAP ERP on the SAP Service Marketplace at http://service.sap.com/bfp.

Technical usages already installed in the system are automatically selected. You can select additionaltechnical usages.

The technical usages are grouped by their relevant product instances. For example, the instance

group Portal Content comprises all technical usages which contain the instance Portal Content . So atechnical usage can be part of several instance groups.

You can display detailed information about technical usages by clicking on the link with the name ofthe technical usage. This shows you product instances of the selected enhancement packagerelease, required product instances, product versions, and product systems.

You can only select technical usages for which required product instances are flagged as installed inthe LMDB. Product instances for unavailable technical usages are highlighted in red.

You cannot select a technical usage if it includes software components that must run on anSAP NetWeaver Portal that is not installed in your system.

For details about the mappings between technical usages, business functions, product instancesand the software components check following SAP Notes:SAP Note 1165438 (for SAP ERP 6.04)SAP Note 1324838 (for SAP ERP 6.05)SAP Note 1566412 (for SAP ERP 6.06)

6. If you have assigned Java technical systems to your maintenance transaction, the MaintenanceOptimizer also shows all installable Java instances in the section Additionally Installable JavaInstances. Java instances that are relevant for the selected version of the target stack are pre-selected.

http://service.sap.com/bfp



















Page 30

If you select additional Java-based product instances, you can choose from a bigger selection oftechnical usages in the upper section Technical Usages.

7. Choose Continue to proceed with the Confirm Target sub-step.

8. Check and confirm the major target constellation of your system.

If at this step a connected SAP NetWeaver system (for example an SAP NetWeaverPortal, or an SAP Business Warehouse system) is supposed to be updated to a release thatyou did not expect, check if you have correctly maintained the landscape pattern of thetechnical system. See Assign Landscape Patterns.

9. Choose Continue to proceed with the Choose Add-on Products.

10. The Maintenance Optimizer lists the following selection options if add-ons are affected by theinstallation, upgrade, or update:

Add-ons already installed that you can update with the update, upgrade, or installation of theenhancement package

Add-ons that you can install with the update, upgrade, or installation of the enhancement package

Select the add-ons and the stack level hat you want to install. Previously installed add-ons arepreselected.

Choose the add-on links to display the add-on instances and installable alternative (that is,the compatible software component versions).

The Maintenance Optimizer provides the option to include add-ons directly into your maintenanceoperation, so that you use the same downtime window instead of installing the add-ons separatelyafterwards.

Add-ons are part of the stack XML file for target releases based on NW 7.0 EHP2 or

higher, that is, add-ons are included as of SAP ERP 6.05 or higher.




Page 31

11. Choose Continue to proceed with the Select OS/DB-dependent files sub-step.

12. Select the files that correspond with the combination of your operating system and database.

Also select the files for SAP IGS and SAP HOST AGENT and for the Software Update Manager(SUM) if they are provided for selection. For more information about the SUM option, see SAP Note

1626435. If you run application servers on different operating systems, make sure that you also include theirkernel files. Sliding the mouse pointer on the kernel files displays a quick info that explains for whichsystem the kernel files were calculated.

13. Choose Continue to proceed with the Select Stack-Independent files sub-step.

14. Select the stack-independent files and files for the add-on upgrade or add-on installation. In mostcases, the stack-independent files include a SPAM/SAINT update for the target release. If youdecided to install new add-ons, the corresponding files are displayed.

A red asterisk indicates that there is no delivery package on the SAP Service Marketplacefor a support package.

You can also select files from the download basket for this maintenance transaction manually by

choosing Include/Exclude Files in Download Basket .The Maintenance Optimizer downloads these files, but does not automatically import them.

You have to import them manually.

15. Choose Continue to proceed with the Select Stack-Dependent files sub-step.

16. Decide how to deal with the stack-dependent files.

These files directly correspond to the technical usages that you have selected.

The support packages for the basis release are also displayed, the Maintenance Optimizer calculatedthem for the software components that you do not want to update with the enhancement package.

We recommend that you keep the selection. However, you can deselect any supportpackage that you do not want to apply to your system. Components of an SP stack that arenot in productive use do not need to be patched during the implementation of the SP stack,

unless there is a technical or logical dependency to the productive components.If deselection of support packages of a software component is disabled, the previously selectedtechnical usages and the target support package level indirectly determine that these supportpackages are required.

Do not deselect the files for the software components SAP_BS_FND and WEBCUIF asthey are required for the enhancement package.

17. To include current patches for Java support packages in your maintenance transaction, choose AddJava Patches.

The Maintenance Optimizer downloads these files, but does not automatically import them.You have to import them manually.

18. To add HR Support Packages or Country Legal Change Packages (CLC Packages) for an HR system

selected as a product system to your maintenance transaction, choose Add HR Packages.19. Choose Continue to proceed with the Confirm Selection sub-step.







Page 32

20. To download the files, choose whether you want to download them with the Download Basket or withthe Software Lifecycle Manager (only available if configured).

21. Choose Continue.

4.3 Download FilesTo complete this work step of the Maintenance Optimizer Transaction, proceed as follows:

1. A package configuration file containing your selections, based on your entries, is generated. Onceyou confirm the selection in the step Confirm Selection, this file is stored in the database in the SAPSolution Manager and at operating system level in the Electronic Parcel Service Inbox (EPS Inbox) ofthe transport directory.

Download the XML stack file. The text file is only needed for an upgrade with source release SAP R/34.6C (see SAP Note 1022704).

2. Download the files as soon as you have completed the Maintenance Optimizer transaction.

If you get a system message “ Adjustment of stack delta XML done with error: check application log ” atthis step, either your SAP Solution Manager system does not have the latest SPAM level, or you have

insufficient user authorizations to write the XML in theEPS/IN

directory (see User Maintenance for

Maintenance Optimizer ).

3. Choose Continue.

4.4 ImplementTo complete this work step of the Maintenance Optimizer transaction, proceed as follows:

1. Download the files according to the Maintenance Optimizer calculation.

2. Use the appropriate update tool, like the Software Update Manager (SUM), SAP EnhancementPackage Installer (SAPehpi), SAP upgrade tools (SAPup and SAPJup) to implement the downloadeditems.For more information, see www.service.sap.com/sltoolset.

3. After you have implemented the changes for the product system(s), change the Status ofImplementation for Product System(s) to Completed .

4. Choose Continue.

4.5 End MaintenanceTo complete this work step of the Maintenance Optimizer transaction, proceed as follows:

1. Choose Complete Transaction.

After you have completed the Maintenance Optimizer transaction, you can no longer make anychanges to it.

2. Choose Close.

5. Maintaining System Tracks with Maintenance

OptimizerTo update a single system, the Maintenance Optimizer provides all the files and the stack configuration file,

which can be handed over to the installation tool to apply the files. This works for a single system. But a

system track consists of individual systems for development, quality assurance, production etc. Thereby, the

following issues arise:

Different stack levels of the systems in a track

The productive system probably is on the lowest stack level because it is not updated that often. The

quality assurance system could be the same or higher as the productive system, and thedevelopment system most likely has the highest stack level of the track because it is regularly patched



http://www.service.sap.com/sltoolset








and updated. Therefore the stack configuration files generated by Maintenance Optimizer can be

different if they are generated separately from each other.

Different number of activated business functions on systems in a track

Most likely, the smallest number of activated business functions can be found on the productive

system, a higher number on the quality assurance system, and an even higher number on the

development system. Therefore, the generated stack configuration file for the development system is

not necessarily relevant for the other systems.

Do not generate a separate stack configuration file for every single system of a system track if you

plan to patch or upgrade the whole track.

To maintain a system track consistently, include all systems of one track in one Maintenance

Optimizer transaction to produce a single stack configuration file for the whole track. This ensures the

consistency of the patch or upgrade.

You can assign technical usages separately for each system of the track during the maintenance transaction.

Do not implement Legal Change Packages during the patch phase of a system track. This can cause

inconsistencies between the different systems of a track and invalidate the generated stack configuration

file for the whole system track. Information about upcoming Legal Change Packages is provided using

SAP Notes (“planned legal changes”).

See also SCN: Maintenance of system tracks with Maintenance Optimizer .

6. Copying Stack Configuration Files for Identical

SystemsTo reproduce a calculated target constellation on another system, use a copy report. To create exactly the

same constellation of one system on a second system, the stack configuration file for one system can becopied to use it for another system.

The copy report only works if both systems have the same Service Pack level as the system where the report

originally has been created for. Otherwise, create an individual maintenance transaction for the second

system. For more information, see SAP Note 1600302.

http://scn.sap.com/community/it-management/alm/blog/2012/10/26/maintenance-of-system-tracks-with-maintenance-optimizer








Date post:	02-Mar-2016
Category:	Documents
Upload:	samwwt
View:	8 times
Download:	0 times

MaintPlan Guide

Documents