mopz sp22 final en

8/2/2019 Mopz Sp22 Final En

1/46

Maintenance Optimizer

Release 7 .0 SP 22

SA

P

SO

LUTIO

N

M

A

N

AG

ER


2/46

SAP Online Help 29.01.2010

Maintenance Optimizer 7001 2

Copyright

Copyright 2009 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 bechanged without prior notice.Some software products marketed by SAP AG and its distributors contain proprietarysoftware components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of MicrosoftCorporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x,System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM,z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM,Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower,PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2

Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner,WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBMCorporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registeredtrademarks 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, WorldWide 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 fortechnology invented and implemented by Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, andother SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, CrystalDecisions, Web Intelligence, Xcelsius, and other Business Objects products and servicesmentioned herein as well as their respective logos are trademarks or registered trademarks ofBusiness Objects S.A. in the United States and in other countries. Business Objects is anSAP company.

All other product and service names mentioned are the trademarks of their respectivecompanies. Data contained in this document serves informational purposes only. Nationalproduct specifications may vary.

These materials are subject to change without notice. These materials are provided by SAPAG and its affiliated companies ("SAP Group") for informational purposes only, withoutrepresentation or warranty of any kind, and SAP Group shall not be liable for errors oromissions with respect to the materials. The only warranties for SAP Group products and


3/46



services are those that are set forth in the express warranty statements accompanying suchproducts and services, if any. Nothing herein should be construed as constituting anadditional warranty.


4/46



Icons in Body Text

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Additional icons are used in SAP Library documentation to help you identify different types ofinformation at a glance. For more information, see Help on Help General InformationClasses and Information Classes for Business Information Warehouseon the first page of anyversion of SAP Library.

Typographic Conventions

Type Style Description

Example text Words or characters quoted from the screen. These include fieldnames, 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 tabletitles.

EXAMPLE TEXT Technical names of system objects. These include report names,program names, transaction codes, table names, and key concepts of aprogramming language when they are surrounded by body text, forexample, SELECT and INCLUDE.

Example text Output on the screen. This includes file and directory names and theirpaths, messages, names of variables and parameters, source text, andnames of installation, upgrade and database tools.

Example text Exact user entry. These are words or characters that you enter in thesystem exactly as they appear in the documentation.

Variable user entry. Angle brackets indicate that you replace thesewords and characters with appropriate entries to make entries in thesystem.

EXAMPLE TEXT Keys on the keyboard, for example, F2 or ENTER.


5/46



Table of Contents

Maintenance Optimizer .......................................................................................................... 6System Landscapes and System Data ............................................................................... 9Prerequisites.................................................................................................................... 10

S-User in Maintenance Optimizer ................................................................................. 12Landscape Pattern ....................................................................................................... 13

Maintenance Transaction Overview ................................................................................. 16Steps in a Maintenance Transaction ................................................................................ 17Download Files ................................................................................................................ 19Maintenance Procedure Scenarios................................................................................... 20

Approve and Download Files in Download Basket ........................................................ 22Maintenance Transaction with Installation of a Support Package Stack ......................... 25Maintenance Transaction with Installation of an Enhancement Package ....................... 30Upgrade ....................................................................................................................... 35Upgrade with an Enhancement Package ...................................................................... 39

Finding Error Messages in the Maintenance Optimizer ..................................................... 44Product Maintenance Reporting ....................................................................................... 45


6/46



Maintenance Optimizer

The Maintenance Optimizer leads you through the planning, download and implementation ofsupport package stacks, which contain a set of support packages for your systems. You canalso install enhancement packages, perform an upgrade, or include enhancement packages

in an upgrade, with the Maintenance Optimizer.

The Maintenance Optimizer gives you an overview of all maintenance activities in yoursystem landscape.

For current information about implementing the Maintenance Optimizer, see SAP Note1024932.

Integration

This section explains the applications to which the Maintenance Optimizer is connected, andthe functions resulting from this integration.

The Maintenance Optimizer is connected to the SAP Support Portal of the SAPGlobal Support Backbone. It supports you as follows:

o It takes you directly to the area of the SAP Software Distribution Center forthe product that you have selected for maintenance, in the SAP ServiceMarketplace.

You must logon with your S-user. The S-user is your user ID for the SAPService Marketplace. For more information seeS-User in MaintenanceOptimizer[Page 12].

o It reads the download basket of your S-user.

o You can approve selected items in the download basket for download. Forfurther information, seeApprove and Download Files into Download Basket[Page 22].

o It gets the confirmed items in the maintenance transaction.

The Maintenance Optimizer is integrated with Software Lifecycle Manager (SLM). Itsupports automatic download of files which you have selected, or were calculatedautomatically, which can then be imported with the following SAP upgrade tools.

o SAP Add-On Installation Tool (SAINT)

o Support Package Manager (SPAM)

o Java Support Package Manager (JSPM)

o Enhancement Package Installer (EHPI)

o ABAP Upgrade Program (SAPup)

o SAP Java Upgrade Program (SAPJup)

The functional scope of the Maintenance Optimizer can be extended by the functionsfor automatic download via the Software Lifecycle Manager.
http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1024932&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1024932&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1024932&_NLANG=en&_NVERS=0


7/46



Features

The Maintenance Optimizer helps you to plan and carry out maintenance. For moreinformation, seeMaintenance Transaction Overview[Page 16],Maintenance TransactionSteps[Page 17] andMaintenance Transaction Scenarios[Page 20].

When you start a new product maintenance transaction, the Maintenance Optimizer reads thedata from the specified product version, and suggests files and product systems formaintenance.

Product systems are groups of technical systems which belong to one or more products. Inthe Maintenance Optimizer, you create a maintenance transaction for one product.

It leads you through the following scenarios, in guided procedures:

Scenario More Information

Manual selection of maintenance filesApprove and Download Files in DownloadBasket[Page 22]

Maintenance:

With installation of support packagestacks

With installation of support packagestacks for enhancement packages

Maintenance Transaction with Installationof a Support Package Stack[Page 25]

Installation of enhancement packages:

Without technical usages

With technical usages

Maintenance Transaction with Installationof an Enhancement Package[Page 30]

Upgrade Upgrade[Page 35]

Include enhancement packages in an upgradeUpgrade with an Enhancement Package[Page 39]

Get Maintenance Files

You can get maintenance files in the following ways, with the Maintenance Optimizer:

Manual selection

o The Maintenance Optimizer goes directly to the download area of the SAP

Software Distribution Center for the product that you want to maintain.

o It approves items in the SAP Software Distribution Center download basket.For further information, seeApprove and Download Files into DownloadBasket[Page 22].

Automatic calculation

o The Maintenance Optimizer determines the files to maintain the selectedproduct system landscape, or the components to install an enhancementpackage. For further information, see Get Download Files Automatically,underMaintenance Transaction Steps[Page 17].

o It supports the automatic download of automatically calculated files forproduct maintenance in your product system.


8/46



o It simplifies the automatic installation of the files calculated for productmaintenance in your product system.

General Functions

The Maintenance Optimizer collects all the necessary information in all scenarios,

into one transaction. This includes the users, the product to be maintained orinstalled, the technical systems, and the assigned support package stacks.

It manages the files downloaded by the Maintenance Optimizer, in a central directory.

The Change Managementwork center shows an overview of all open and completedmaintenance transactions for the user.

It provides a report function so that you can search for and display all maintenancetransactions in the SAP Solution Manager. Further information can be found underProduct Maintenance Reporting [Page 45].


9/46



System Landscapes and System Data

System Landscape Settings

You assign products to your product systems in the transaction Solution Manager SystemLandscape(SMSY). A product system can comprise various product versions:

Product versions which require other product versions.

Independent product versions, which do not require any other other product versions.

Independent product versions comprise operating system and database files, and kernel,basis and application components. Other product versions can be installed in theseindependent product versions, in technical systems. These installed product versions areusually application components.

You can see whether the selected product versionrequires another product version in itsDetail view knnen in the Solution Manager System Landscape. For example, the productversion EHP1 FOR SAP CRM 7.0 requires that you use the main instance CRM AMT withproduct version SAP CRM 7.0.

The main instances for a product system are often distributed among sevreal technicalsystems. The resulting dependencies are relevant for the update and maintenance of a role,if, for example, several main instances of various product systems are installed in a technicalsystem, and they use one main instance in parallel. The active product version of a productsystem determines the handling of the associated technical systems. You assign the attributeLandscape Patternto technical systems. It indicates their relationship to product systems, anddetermines their handling in maintenance transactions. For more information, seeLandscape

Patterns[Page 13].

Business Process-Specific Settings

Not all possible main instances of a product in a product system are necessarily active andinstalled. An independent product version provides a lot of business processes fromheterogeneous business areas. Choose the relevant main instances, depending on thebusiness processes used. Only the main instances relevant to your applications aremaintained. For further information about relevant main instances, see see SAP Help Portalat http://help.sap.comSAP Solution ManagerSAP Enhancement Package 1 forSAP Solution Manager 7.0EnglishBasic SettingsSolution Manager SystemLandscapeCreate Systems . For more information about system landscapes in theSAP Solution Manager, see SAP Help Portal athttp://help.sap.comSAP Solution

ManagerSAP Enhancement Package 1 for SAP Solution Manager 7.0EnglishBasic SettingsSolution Manager System Landscape .

System Data for Product Maintenance with the Maintenance Optimizer

The Maintenance Optimizer gets its system data from the SAP Solution Manager systemlandscape. It takes account of the relevant product version main instances in the productsystem to be maintained, in the maintenance procedures. It also handles the landscapepatterns into which you have classified the technical systems.

The sources of the system information in the SAP Solution Manager system landscape canbe configured, and depend, for example, on the system type. For example, to get Javatechnical system information in the SAP Solution Manager you must connect to the System

Landscape Directory (SLD).
http://help.sap.com/http://help.sap.com/http://help.sap.com/http://help.sap.com/http://help.sap.com/http://help.sap.com/http://help.sap.com/


10/46



Prerequisites

The Maintenance Optimizer contains a lot of scenarios for maintenence procedures. Thescenarios have different prerequisites.

Basic Prerequisites

1. You have performed the basic configuration of the SAP Solution Manager.

For more information, see SAP Help Portal at http://help.sap.comSAPSolution ManagerSAP Enhancement Package 1 for SAP Solution Manager 7.0EnglishBasic SettingsSAP Solution Manager Basic Configuration .

2. You have configured the Maintenance Optimizer in the SAP Solution Managercustomizing.

You must perform the following customizing activities for the Maintenance Optimizer:

o Assign S-users for SAP Support Portal functions.

This activity specifies the S users (user ID for the SAP Service Marketplace)assigned to user IDs for the SAP Solution Manager.

For more information seeS-User in Maintenance Optimizer[Page 12].

o Enter user for communication with SAP Service and Support systems

This activity specifies the RFC connection SAP-OSS and the correspondingRFC user.

3. You have satisfied the following prerequisites in the Solution Manager System

Landscape(SMSY) transaction:

o Assigned product versions to the technical systems to be maintained.

o You have assigned the technical systems to be maintained, to a logicalcomponent.

If you want to use a solution, you must assign the technical systems to bemaintained, to the solution landscape. For more information, see SAPHelp Portal at http://help.sap.comSAP Solution ManagerSAPEnhancement Package 1 for SAP Solution Manager 7.0English

Basic SettingsSolution Manager System Landscape .

o Sie haben classified your technical systems by landscape pattern. For moreinformation, seeLandscape Patterns[Page 13].

4. You have installed the Download Manager locally in your workplace. The DownloadManager is in the SAP Software Distribution Center in the SAP Support Portal.

You can use the Software Lifecycle Manager instead of the Download Manager.For more information, see below.
http://help.sap.com/http://help.sap.com/http://help.sap.com/http://help.sap.com/http://help.sap.com/http://help.sap.com/


11/46



Prerequisites for Automatic Calculation of Maintenance Files

For automatic calculation of the maintenance files, the following prerequisites must besatisfied in the Solution Manager System Landscapetransaction (SMSY):

1. You have assigned active product versions to the product systems to be maintained,

in the system landscape.

2. You have specified the relevant main instances for each product system to bemaintained, on the Selecting Main Instancestab, in the system landscape.

Flag the following main instances as relevant because the Maintenance Optimizeronly considers relevant main instances when determining the maintenance files:

o All business main instances in a product system.

o All ABAP business instances installed in addition to the ABAP main instance.

These main instances can be assigned to a technical system. You cancreate technical systems for a product system, in the Solution ManagerSystem Landscapetransaction (SMSY). For more information aboutmanaging the system landscape, see SAP Help Portal at

http://help.sap.comSAP Solution ManagerSAPEnhancement Package 1 for SAP Solution Manager 7.0EnglishBasic SettingsSolution Manager System Landscape .

3. You have assigned a message server and database host to each product system forwhich a maintenance transaction is to be performed, in the system landscape. TheMaintenance Optimizer can only identify the product system uniquely.

4. You can use the Software Lifecycle Manager instead of the Download Manager. Toconfigure it:

o Set-up an RFC connection

SAP recommends an HTTPS connection. For further information, see thesecurity guide in the SAP Service Marketplace, under

http://service.sap.com/instguides SAP Components SAP SolutionManager SAP Solution Manager Security Guide .

o Set-up a logical port

For further information, see the security guide in the SAP ServiceMarketplace, under http://service.sap.com/instguides SAP Components

SAP Solution Manager SAP Solution ManagerSecurity Guide .

o Set-up the Download Directory Assistant

o Set-up the Software Lifecycle Manager

Call the Central Download Directory Assistant with transaction/TMWFLOW/MOPZCD. You can view or delete files in the Central DownloadDirectory with the Central Download Directory Assistant.

Call the Configuration Assistant for the Software Lifecycle Manager withtransaction /TMWFLOW/MOPZCA in the SAP Solution Manager.
http://help.sap.com/http://help.sap.com/http://service.sap.com/instguideshttp://service.sap.com/instguideshttp://service.sap.com/instguideshttp://service.sap.com/instguideshttp://service.sap.com/instguideshttp://service.sap.com/instguideshttp://help.sap.com/


12/46



S-User in Maintenance Optimizer

Your S-user is the user ID which SAP gave you, to logon to the SAP Support Portal.

Always logon to the SAP Support Portal with your S-user, to which your SAP SolutionManager user ID is assigned.

If you do not do so, the Maintenance Optimizer cannot confirm and authorize the fileswhich you put in the download basket for this S-user.

Prerequisites

Your system administration has performed the following activities in Customizing for SAPSolution Manager under Basic Settings:

Maintain RFC/user for communication with SAP service and support systems

Assign S-user for SAP Support Portal Functionality, or an S-user assigned intransaction AISUSER

Your S-user must be assigned to the same customer or company number as theS-user which your system administration put in the destination SAP-OSS RFC. Ifthis is not so, the Maintenance Optimizer cannot read your download basket.

Integration

The Maintenance Optimizer is connected to the SAP Support Portal of the SAP GlobalSupport Backbone, and provides the following functions:

It takes you directly to the area of the SAP Software Distribution Center for theproduct that you have selected for maintenance. (Log on with your S-user.)

It reads the download basket of your S-user.

It authorizes selected items in the download basket so that they can be downloaded.

It gets the selected items in the maintenance transaction.


13/46



Landscape Pattern

A landscape pattern represents the relationship of a technical system to one or more productsystems. When you classify technical systems by landscape pattern, you specify the how thayare maintained in the product system.

The landscape pattern indicates dependencies between main instances in technical systems,resulting from how products are combined into business processes in your solutionlandscapes. This allows you to restrict maintenance transactions to one selected productversion, without creating additional maintenance requirements due to dependencies on otherproduct versions.

Sidecar

Technical systems with the landscape pattern Sidecar, are used by one product system withone active product version.

The target status of a Sidecartechnical system in a maintenance transaction, is determined

by the active product version of the product system. A synchronized combination of therelease statuses of the software components used, is determined, as the target status.

In this example, the product system has the active product version SAP ERP 6.0.The relevant main instances (SAP ECC Server, ERP Business Packages, SAP XSS andSAP FSCM - Biller Direct) are installed in two separate technical systems. In the secondtechnical system the main instance SAP NW - EP Core, which is only used locally by themain instances of an active product version (SAP ERP 6.0), is also installiert.

So you assign the landscape pattern Sidecarto the second technical system.

Updates or maintenance of this technical system depend on the active product version ofthe product system. The Maintenance Optimizer determines a synchronized target statusfor the various software components, depending on this.


14/46



Product system:

SAP ERP 6.0

contains the following main instances

in separate technical systems

SAP ECC ServerSAP ECC Server

ABAP Application Server

ERP Business Packages (Content)ERP Business Packages (Content)

SAP XSSSAP XSS

SAP NW EP CoreSAP NW EP Core

JAVA Application Server

SAP FSCM

Biller Direct

SAP FSCM

Biller Direct

Landscape pattern: SidecarLandscape pattern: Sidecar

Hub

Technical systems with the landscape pattern Hub, are used by more than one productsystem. You can perform separate maintenance transactions for each of these product

systems, independently. The Hubtechnical system is part of each of these maintenancetransactions.

When determining a consistent target status for the Hubtechnical system, as few softwarecomponents as possible are changed. This avoids additional dependencies between thetechnical system and the product systems which use it.

In this example, the product system has the active product version SAPNetWeaver 7.0. The main instance SAP NW - EP Core, which is used in parallel by twomain instances of other product systems: SAP XSS and ERP Business Packages(product system ) and SAP SRM Content (product system ), is installed on

the associated technical system.

So you assign the landscape pattern Hubto this technical system.

Updates or maintenance of this technical system depend on the active product version(SAP NetWeaver 7.00) of the product system.

In the other technical systems, update or maintenance also depend on the active productversion (SAP ERP 6.0 EHP4, SAP SRM 7.0 EHP1) of the product system. So you cansart maintenance for each product system independently.


15/46



Product system:

SAP NetWeaver 7.00


in the following technical system

ERP Business

Packages

(Content)

ERP Business

Packages

(Content)

SAP NW EP CoreSAP NW EP Core

JAVA Application Server

SAP SRM ContentSAP SRM Content

Product system:

SAP ERP 6.0 EHP4



SAP ECC ServerSAP ECC Server


Product system:

SAP SRM 7.0 EHP1



SAP SRM ServerSAP SRM Server


SAP XSSSAP XSS

Landscape pattern: HubLandscape pattern: Hub


16/46



Maintenance Transaction Overview

The Change Managementwork center (transaction SOLMAN_WORKCENTER) gives you anoverview of the maintenance transactions in the Maintenance Optimizer. It tells you how

many maintenance transactions with a specified status have been created or changed.

You can go to the selected display via links, e.g. to all maintenance transactions which havealready been implemented.

Features

The Change Managementwork center Maintenance Optimizerview lists the maintenancetransactions. You can display and filter them by certain criteria.

To open a maintenance transaction, choose its ID or description.

When you select a maintenance transaction in the list, detailed information about it is

displayed below it. This includes the priority, status, short text and the productversion.

There is also information about system status, the source component, and downloadfiles found and confirmed.

Activities

You can start a product maintenance transaction in SAP Solution Manager either withtransaction SOLUTION_MANAGER , or in the Change Managementwork center (transactionSOLMAN_WORKCENTER).

Access with transaction SOLUTION_MANAGER:

You must select a solution at the start of the maintenance transaction:

1. Enter the transaction SOLUTION_MANAGER in the SAP Easy Accessscreen.

2. Select a solution in the Solution Overview.

3. Choose Change Management Maintenance Optimizer Create NewMaintenance Transaction .

Access from Change Managementwork center:

You can start a maintenance transaction with or without assigning a solution:

Choose New Maintenance Transactionunder Common Tasks.


17/46



Steps in a Maintenance Transaction

Steps Common to Different Scenarios

The Maintenance Optimizer contains several scenarios. There are some steps common to allscenarios:

PlanMainten

ance

1

SelectFiles

2

Download Files

3

Implementation

4

Maintenance

Finish

5

Depending on the scenario selected, the Maintenance Optimizer automatically adds furthersteps to the standard procedure.

The system assigns a status to each step you perform. You can repeat previous steps untilthe transaction has the status Completed. Then you can no longer change the maintenancetransaction.

Automatic Calculation of Download Files

The Maintenance Optimizer can automatically calculate the download files required,

independently of the scenario which you select for the maintenance transaction.

The Maintenance Optimizer automatically calculates the files required for the maintenancetransaction, based on the defined system landscape, in the following additional steps:

ChooseStack

SelectOS-/DB-

DependentFiles

Select Stack-Independent

Files

Select Stack-Dependent

Files

ConfirmSelection

2.1 2.3 2.4 2.5 2.6

ConfirmTarget

2.2

A detailed description of these steps is in the descriptions of the maintenance transactionscenarios. For more information, seeMaintenance Transaction Scenarios[Page 20].

The Maintenance Optimzer selects download files for maintenance transactions for theselected product systems, which you have flagged as relevant main instances in thetransaction Solution Manager System Landscape(SMSY).


18/46



Tabs

You perform all steps in the maintenance transaction, during both manual selection andautomatic determination of the maintenance files, in the Operationstab.

You can also use the following tabs:

Systems

Shows the current start and target constellation of your maintenance transaction ineach step.

The Systemstab is only shown when you have selected a product version andproduct systems, in step 1. The target constellation is only shown after you haveperformed step 2.1.

Log

Shows all Maintenance Optimizer system messages during your maintenancetransaction.

Stack Files

Shows all XML files generated during your maintenance transaction.

The Stack Filestab is only shown after you have performed step 2.

Documentation

Links to frther information about the Maintenance Optimizer and enhancementpackages.


19/46



Download Files

You can download files for maintenance procedures as follows:

Download f iles directly from the download basket. The files are saved locally onyour hard disk.

You can download with the Download Manager. You must download and install theDownload Manager, and configure the connection to the SAP Service Marketplace.

The Download Manager connects to the SAP Service Marketplace and downloads allfiles in the download basket, to your local PC.

Download files with the Software Lifecycle Manager. This is the most convenientoption.

The Software Lifecycle Manager is part of the SAP Solution Manager installation.

When you download files with the Software Lifecycle Manager, they are saved in acentral download directory. They can be installed quickly from there.

You must configure the Software Lifecycle Manager. For more information, seePrerequisites[Page 10].


20/46



Maintenance Procedure Scenarios

The Maintenance Optimizer provides a lot of scenarios for performing maintenanceprocedures. You can, for example, approve and download files in the download basket,

locally to your PC. The Maintenance Optimizer also leads you through the proceduresrequired to plan maintenance transactions and download and implement support packagestacks, enhancement packages and patches.

The Maintenance Optimizer provides a guided procedure for all available scenarios.

Prerequisites

Information about the prerequisites for the scenarios is underPrerequisites[Page 10].

Procedure

Maintenance Procedure Scenarios

The Maintenance Optimizer contains a lot of scenarios for maintenence transactions.

Information about steps which are common to all procedures is under Steps in a MaintenanceTransaction[Page 17].

Which scenario you can perform depends on the product version which you specify when youcreate the maintenance procedure. The Maintenance Optimizer offers the following scenarios:

Scenario 1: Approve and Download Files in Download Basket

Use this scenario if you want to approve and download files in your download basket,for a product version. You can put files either in the SAP Service Marketplace, or

directly in the download basket in the Maintenance Optimizer.

For further information, seeApprove and Download Files into Download Basket[Page 22].

Scenario 2: Maintenance Procedure with Installation of a Support Package Stack

Use this scenario if

o you want to perform a maintenance transaction for a product version forwhich a support package stack is to be installed

o you want to perform a maintenance transaction for a product version forwhich a support package stack is to be installed for an installed enhancement

package

In this transaction, an SAP support package stack is installed. Support packagestacks are sets of support packages which have been tested together by SAP.

For further information, seeMaintenance Procedure with Installation of a SupportPackage Stack[Page 25].

Scenario 3: Maintenance Transaction with Installation of an Enhancement Package

Use this scenario to install one of the following enhancement packages for a productversion:

o Enhancement package without technical usages

o Enhancement package with technical usages


21/46



For further information, seeMaintenance Procedure with Installation of anEnhancement Package[Page 30].

Scenario 4: Upgrade

You can upgrade your product version in this scenario, with the Maintenance

Optimizer.

For more information seeUpgrade[Page 35].

Scenario 5: Upgrade with Installation of an Enhancement Package

In this scenario, the Maintenance Optimizer can combine the upgrade of your productversion with the installation of an enhancement package.

For further information, seeUpgrade with Installation of an Enhancement Package[Page 39].

If you selected product version SAP NetWeaver 7.0 in the first step, you canchoose between the following options:

o Maintenance (install a support package stack)

o Installation of an enhancement package (with technical usages)

o Upgrade


22/46



Approve and Download Files in Download Basket

To download only specified files from the download basket in a transaction:

PrerequisitesFor the prerequisites for this scenario, see Basic Prerequisites, underPrerequisites[Page10].

Procedure

Step 1: Plan Maintenance

1. Enter the required transaction information. The following fields require input:

o Priority

Enter the priority of the transaction.

o Description

The text New Maintenance Optimizer Procedureis the default. You can put ashort description in the text.

o Product Version

Select the product version for which you want to perform the transaction.

o Product System

Select the product systems for which you want to perform the transaction.

A product system is a group of technical systems which belong to one ormore products. In the Maintenance Optimizer, you create a maintenancetransaction for one product.

2. Entries are not compulsory in the following fields:

o Solution

If you use solutions when you enter the maintenance optimizer with thetransaction SOLUTION_MANAGER, you must specify a solution at the

beginning of the transaction.

o Other Fields...

You can specify the processor and the requester. You can also display thedocuments assigned to the transaction, or upload documents yourself.

3. Choose Continue. The system checks the instances installed in your product system,and determines the update options.

Step 2: Select Files

1. Choose Select Files Manually.

2. You can go to the download area, in which you can put files in the download basketmanually, with the following links:


23/46



o Select Files for Product Version Directly

You go to the download area for the specified product version in the SAPService Marketplace. For more information, see the application help in thedownload area.

o Go to the SAP Software Distribution Center

You go to the SAP Software Distribution Center.

3. You can also make the selection previously, in the SAP Service Marketplace. If youhave already selected files for the download basket, they are shown in the next step.

4. When you have selected all files for the download basket, choose Continue.

Step 3: Download files

Before downloading files with the download basket, you must confirm the selection in themaintenance optimizer.

Confirm

1. Choose Confirm Files in Download Basket. You go to the dialog box ConfirmFiles in Download Basket.

2. Set the checkboxes for the fields that you want to download.

3. Choose OK. When you confirm your selection, the files are assigned to theprocedure and released for download.

The Maintenance Optimizer logs all confirmed entries in the download basket, in

the table /TMWFLOW/MOBKLOG .

Download

1. You cannot download until you have confirmed the files. The quickest andeasiest way is to download the files directly. Choose Download Files inDownload Basket. You go to the dialog box Download Files from DownloadBasket.

2. Click on the names of the files consecutively, to download them to you harddisk.

3. When you have finished, choose Close.

4. Choose Continue.

Step 4: Implementation

You go to a list of copied and confirmed download files. You can display detailed information,such as package attributes, about each file, or call a side-effect report, before implementing.

If you selected product systems in step 1, they are shown here. When the data has beendownloaded, you must now import it into the selected product systems.

1. Use the maintenance optimizer to document the implementation. You can specify astart and end date, and the implemention status. You only go to the next step whenyou have selected the status Completed for all product systems.

2. Choose Save, and Continue.


24/46



Step 5: End maintenance

When you have implemented the files in the desired product systems, you can complete themaintenance transaction. Choose Complete Transaction.

You can then make no more changes.


25/46



Maintenance Transaction with Installation of aSupport Package Stack

In a maintenance transaction, you can import a support package stack for a product version,

or install a support package stack for an existing enhancement package. Support packagestacks are a combination of support packages for ABAP and patches for Java instances (notkernel patches), which were tested together by SAP, and whose implementation SAPreccomends, or possibly even requires.

Prerequisites

You have:

o a product version for which SAP offers a support package stack.

o a product version with an enhancement package for which SAP offers asupport package stack

You want the maintenance optimizer to determine the download files.

For information about the technical prerequisites, seePrerequisites[Page 10].

Procedure



o Priority


o Description


o Product Version

Select the product version for which you want to install a support packagestack. The Maintenance Optimizer displays all the product systems assignedto the product version.

o Product System

Set the checkboxes for the product systems for which you want to call andinstall a support package stack.



o Solution


26/46



If you use solutions when you enter the maintenance optimizer with thetransaction SOLUTION_MANAGER, you must specify a solution at thebeginning of the transaction.

o Other Fields...




1. Choose Calculate Files Automaticallyand then Continue.

2. Choose Maintenance, and then Continue. The maintenance option is only available ifthere are support package stacks for the product version specified in step 1.

The maintenance optimizer shows the following additional steps to determine the download

files automatically.

Step 2.1: Choose stack

To install a support package stack for your product version:

The maintenance optimizer shows all target stacks which are currently available inthe SAP Service Marketplace, for the specified product version, in a drop-down list.The current target stack is the default.

1. Select the target stack.

You can display a summary of the contents of the selected target stack, with

Stack Details.

2. Choose Continue.

To install a support package stack for an installed enhancement package:

The Maintenance Optimizer lists all enhancement package releases for which supportpackage stacks can be installed, for the product version specified in step 1, in a drop-down list.

1. Choose an enhancement package release.

2. As well as specifying the enhancement package release, the MaintenanceOptimizer proposes a target stack, in a drop-down list. A compatible support

package stack is usually installed when you install an enhancement package.

Choose the version of the target stack.

You can display a summary of the contents of the selected target stack, withStack Details.

3. If you have assigned Java systems to your maintenance transaction, theMaintenance Optimizer also shows all installable Java instances. Javainstances which are relevant for the selected version of the target stack, arepre-selected.

Select other Java instances to be installed during your maintenance

transaction.

4. Choose Continue.


27/46



Step 2.2: Confirm target

The Maintenance Optimizer lists the target constellation for the selected product systems andother technical systems, which are affected by the installation of the support package stack.

Confirm the target constellation with Continue.

Step 2.3: Select Add-On Products

1. If add-ons are affected by the installation of the support package stacks, theMaintenance Optimizer lists:

o Add-ons which you have already installed, which you can update with theinstallation of the support package stack

o Add-ons which you can install with the support package stack

2. Select the checkboxes of the add-on to be installed, and select the stack level. Add-ons which you have already installed are already selected.

You can display the add-on instances and installable alternatives, with the links inthe list, i.e show compatible software component versions.

3. Choose Continue.

Step 2.4: Select OS/DB-dependent files

The maintenance optimizer shows a list of files. It is sorted by operating system anddatabase.

1. Choose files in this list for your processing system/database combination.

The Maintenance Optimizer selects the database-independent files for the filesfor a database and operating system which you have selected.

2. Choose Continue.

Step 2.5: Select stack-independent files

If your selection contains files which are not assigned to a stack, the maintenance optimizernow shows these stack-independent files.

The maintenance optimizer proposes the highest currently available support package fordownload, for system components with no support package stack.

Support packages for which there is no delivery package in the SAP Service Marketplace,are flagged in the lists with a red star.

1. Check the selection. Deselect files which you do not need.

2. If the selection you made in the previous step contains add-ons, the MaintenanceOptimizer shows them.

Check the selection. Deselect files which you do not need.


28/46



3. You can also select files from the download basket which are also to be downloadedfor this maintenance transaction, manually.

Choose Include/Exclude Files in Download Basket.

The Maintenance Optimizer downloads these files, but does not automaticallyimport them. You must import them yourself, later.

4. Choose Continue.

Step 2.6: Select stack-dependent files

1. Check the automatic maintenance optimizer selection. All displayed files are in aselected stack.

2. If you want to put current patches for Java support packages, in your maintenancetransaction, choose Add Java Patches. You go to a dialog box.

Select files and choose OK.


3. Choose Continue.

Step 2.7: Confirm selection

1. Specify how the selected files are to be downloaded:

o You can download with the download basket.

The files are first put in the download basket, and then downloaded to yourlocal computer. For further information, seeApprove and Download Files intoDownload Basket[Page 22].

o You can download with the Software Lifecycle Manager.

It loads the files into a central directory, from which they can be installedquickly. Continue by downloading the files with the download manager or thesoftware lifecycle manager. For more information, seeDownloading Files[Page 19].

2. To download from the download basket, continue as decribed inApprove andDownload Files in Download Basket[Page 22] in Step 3: Download FilesunderDownload.

To download with the Software Lifecycle Manager, choose Continue.

A package configuration file containing your selections, based on your entries, isgenerated. Once you confirm the selection, this file is stored in the database in the SAPSolution Manager, and, at operating system level, in the Electronic Parcel Service inboxof the transport directory.

For further information, see the SAP Solution Manager security guide in the SAP ServiceMarketplace, under http://service.sap.com/instguides SAP Components SAP
http://service.sap.com/instguideshttp://service.sap.com/instguideshttp://service.sap.com/instguides


29/46



Solution Manager . The SAP upgrade tools read this configuration file and create theinstances.

The following steps are only relevant for download with the Software Lifecycle Manager.

Step 3: Download files

1. Choose Download.

2. Choose Continue.

Step 4: Implementation

If you selected product systems in step 1, they are shown here. When the data has beendownloaded, you must now import it into the selected product systems.

1. Use the maintenance optimizer to document the implementation. You can specify astart and end date, and the implemention status. You can only continue when youhave selected the status Completedfor all listed product systems.

The copied and confirmed download files are listed. You can display detailedinformation about each file, or call a side-effect report, before implementing.

2. When you have checked all files, and documented the implementation transaction,choose Continue.

Step 5: End maintenance

When you have implemented the files in the desired product systems, you can complete themaintenance transaction. Choose Complete Transaction.

You can then make no more changes.


30/46



Maintenance Transaction with Installation of anEnhancement Package

The Maintenance Optimizer installs the following enhancement packages for product

versions:

Without Technical Usages

With technical usages

Enhancement packages provide new functions and updates of product versions. They areprovided by SAP at regular intervals.

Prerequisites

You have a product version for which SAP offers an enhancement package, with orwithout technical usages.


For information about the technical prerequisites, seePrerequisites[Page 10].

Procedure



o Priority


o Description


o Product Version

Select the product version for which you want to install an enhancementpackage. The Maintenance Optimizer displays all the product systemsassigned to the product version.

o Product System

Set the checkboxes for the product systems for which you want to call andinstall an enhancement package.



o Solution


31/46




o Other Fields...





2. Choose EHP Installationand Continue.

The Maintenance Optimizer shows the following additional steps, in which you can select thefiles to download.


The Maintenance Optimizer lists all enhancement package releases which can be installed forthe product version specified in step 1, in a drop-down list.


2. As well as specifying the enhancement package release, the Maintenance Optimizerproposes a target stack, in a drop-down list. A compatible support package stack isusually installed when you install an enhancement package.


You can display a summary of the contents of the selected target stack, with StackDetails.

3. If you want to install an enhancement package with technical usages, theMaintenance Optimizer lists the technical usages.

You can only select the technical usages in the list for whose installation theprerequisites are fulfilled. Technical usages whose required system instances are notflagged as relevant in the SAP Solution Manager system administration, cannot beselected for the enhancement package release, and are not highlighted.

The technical usages are grouped by instance. For example, the instance groupPortal Contentcomprises all technical usages which contain the instance Portal

Content. So a technical usage can be in several instance groups.

If you expand the instance groups, you can display their details with the technicalusages links. This comprises the instances assigned, the required main instancesand product versions, and the product systems.

If you select the link of a technical usage which is not available, the main instanceswhich are not flagged as relevant in the system landscape, are colored red. For moreinformation, seePrerequisites[Page 10].

Set the checkboxes of the desired technical usages.

4. If you have assigned Java technical systems to your maintenance transaction, the

Maintenance Optimizer also shows all installable Java instances. Java instanceswhich are relevant for the selected version of the target stack, are pre-selected.


32/46



Select other Java instances to be installed during your maintenance transaction.

5. Choose Continue.


The Maintenance Optimizer lists the target constellation for the selected product systems andother technical systems, which are affected by the installation of the enhancement packagerelease.



1. If add-ons are affected by the installation of the enhancement package, theMaintenance Optimizer lists:

o Add-ons which you have already installed, which you can update with theinstallation of the enhancement package

o Add-ons which you can install with the enhancement package



3. Choose Continue.



1. Choose files in this list for your processing system/database combination.


2. Choose Continue.




Support packages for which there is no delivery package in the SAP Service Marketplace,are flagged in the lists with a red star.



33/46





3. You can also select files from the download basket which are also to be downloaded

for this maintenance transaction, manually.



4. Choose Continue.


1. Check the automatic maintenance optimizer selection. All displayed files are in theselected stack.




3. Choose Continue.









A package configuration file containing your selections, based on your entries, isgenerated. Once you confirm the selection, this file is stored in the database in the SAP


34/46



Solution Manager, and, at operating system level, in the Electronic Parcel Service inboxof the transport directory.

For further information, see the SAP Solution Manager security guide in the SAP ServiceMarketplace, under http://service.sap.com/instguides SAP Components SAPSolution Manager . The SAP upgrade tools read this configuration file and create the

instances.


Steps 3-5 Download Files, Implement, and End Maintenance

Information about steps 3, 4 and 5 start at Step 3: Download FilesunderMaintenanceTransaction with Installation of a Support Package Stack[Page 25].


35/46



Upgrade

The Maintenance Optimizer helps you to upgrade a product version. It calculates all the filesthat you have to download from SAP Service Marketplace, in addition to the files delivered onthe upgrade DVD. It leads you through the implementation of these files.

Prerequisites

You have a product version for which SAP offers an upgrade.


For information about prerequisites, seePrerequisites[Page 10].

Procedure



o Priority


o Description


o Product Version

Select the product version for which you want to perform the upgrade. TheMaintenance Optimizer displays all the product systems assigned to theproduct version.

o Product System

Select the checkboxes of the product systems for which you want to performthe upgrade.

A product system is a group of technical systems which belong to one ormore products. In the Maintenance Optimizer, you create a maintenance

transaction for one product.


o Solution


o Other Fields...



36/46






2. Choose Upgrade. This option is only available when you have selected a productversion in step 1, for which an upgrade is possible.



The maintenance optimizer shows all target stacks which are currently available in the SAPService Marketplace, for the specified product version, in a drop-down list. The current targetstack is the default.

1. Choose a target stack from the drop-down list.


2. Choose Continue.


The Maintenance Optimizer lists the target constellation for the selected product and othertechnical systems, which are affected by the upgrade.


Step 2.3: Select OS/DB-dependent filesThe maintenance optimizer shows a list of files. It is sorted by operating system anddatabase.

1. Choose files for your operating system/database combination.


2. Choose Continue.




Support packages for which there is no delivery package in the SAP Service Marketplace,are flagged with a red star.



37/46



2. You can also select files from the download basket which are also to be downloadedfor this maintenance transaction, manually.



3. Choose Continue.


1. Check the automatic maintenance optimizer selection. All displayed files are in one ormore selected stacks.




3. Choose Continue.









A package configuration file containing your selections, based on your entries, isgenerated. Once you confirm the selection in step 2.5, this file is stored in the database inthe SAP Solution Manager and at operating system level in the Electronic Parcel ServiceInbox of the transport directory.

For further information, see the SAP Solution Manager security guide in the SAP ServiceMarketplace, under http://service.sap.com/instguides SAP Components SAP


38/46



Solution Manager . The SAP upgrade tools read this package configuration file andcreate the instances.





39/46



Upgrade with an Enhancement Package

When you upgrade a product version, the Maintenance Optimizer can find and implement itsenhancement packages as well. The Maintenance Optimizer calculates all the files that youhave to download and the files delivered on the upgrade DVD from SAP Service Marketplace.It leads you through the implementation of these files.

Prerequisites

You have a product version for which SAP offers an upgrade, and you want toinstallieren an enhancement package at the same time.


For information about prerequisites, seePrerequisites[Page 10].

Procedure



o Priority


o Description


o Product Version

Select the product version for which you want to determine and install theenhancement package release for the upgrade. The Maintenance Optimizerdisplays all the product systems assigned to the product version.

o Product System

Set the checkboxes for the product systems for which you want to install theenhancement package.



o Solution


o Other Fields...



40/46






2. Choose Upgrade with EHP Installation. This option is only available when you haveselected a product version in step 1, for which an upgrade with the installation of anenhancement package is possible.



The Maintenance Optimizer lists all enhancement package releases which can be installed forthe product version specified in step 1, in a drop-down list.


2. As well as specifying the enhancement package release, the Maintenance Optimizerproposes a target stack, in a drop-down list. A compatible support package stack isusually installed when you install an enhancement package.



3. The Maintenance Optimizer lists the Technical Usageswith their Java Instances.

o Technical Usages

You can only select the Technical Usages in the list for whose installation theprerequisites are fulfilled. Technical usages whose required system instancesare not flagged as relevant in the SAP Solution Manager systemadministration, cannot be selected for the enhancement package release,and are not highlighted.

The technical usages are grouped by instance. For example, the instancegroup Portal Contentcomprises all technical usages which contain theinstance Portal Content. So a technical usage can be in several instancegroups.

If you expand the instance groups, you can display their details with thetechnical usages links. This comprises the instances assigned, the requiredmain instances and product versions, and the product systems.

If you select the link of a technical usage which is not available, the maininstances which are not flagged as relevant in the system landscape, arecolored red. For more information, seePrerequisites[Page 10].

Set the checkboxes of the desired technical usages.

o Java Instances

If you have assigned Java technical systems to your maintenancetransaction, the system also shows all installable Java instances. Javainstances which are relevant for the selected version of the target stack, are

pre-selected.


41/46



Select other Java instances to be installed during your maintenancetransaction.

4. Choose Continue.


The Maintenance Optimizer lists the target constellation for the selected product and othertechnical systems, which are affected by the upgrade.



1. If add-ons are affected by the upgrade, the Maintenance Optimizer lists:

o Add-ons which you have already installed, which you can update with theupgrade

o Add-ons which you can install with the upgrade



3. Choose Continue.



1. Choose files for your operating system/database combination.


2. Choose Continue.




Support packages for which there is no delivery package in the SAP Service Marketplace,are flagged with a red star.



42/46





3. You can also select files from the download basket which are also to be downloaded

for this maintenance transaction, manually.



4. Choose Continue.


1. Check the automatic maintenance optimizer selection. All displayed files are in one ormore selected stacks.




3. Choose Continue.









A package configuration file containing your selections, based on your entries, isgenerated. Once you confirm the selection in step 2.5, this file is stored in the database in


43/46



the SAP Solution Manager and at operating system level in the Electronic Parcel ServiceInbox of the transport directory.

For further information, see the SAP Solution Manager security guide in the SAP ServiceMarketplace, under http://service.sap.com/instguides SAP Components SAPSolution Manager . The SAP upgrade tools read this package configuration file and

create the instances.





44/46



Finding Error Messages in the MaintenanceOptimizer

If problems occur in the product maintenance transaction, you can find detailed information asfollows:

on the Logtab

The tab lists all messages, exceptions and errors, and is directly in the MaintenanceOptimizer.

in the application log

The application log is a tool which captures messages, exceptions and errors. Thisinformation is put in a log and displayed.

Procedure1. To see the entries in the application log, call the transaction SLG1.

2. To see the entries for the Maintenance Optimizer in the application log, enter:

o Object: SOLAR

o Subobject: SAP_BACKEND for the SAP Service Marketplace; or

SAP_BACKEND_MOPZ for the Maintenance Optimizer

o Time Restriction: Enter an appropriate time period, e.g. the previous day, orlast week.

o User: of the SAP Solution Manager user

The Display Logsscreen appears.

3. Open an entry in the log entry list, by clicking on it. The message text is displayed atthe bottom of the screen.

4. To get further details of the message, double-click on it. You go to a dialog box whichcontains the information required for the error handling, e.g. to create an errormessage:

o Application

oAction

o Version

o Destination (for the download basket)


45/46



Product Maintenance Reporting

Product maintenance reporting gives an overview of all product maintenance transactions inyour SAP Solution Manager system. You can also display transactions from different

solutions at the same time. You can also display completed or cancelled transactions.

The reporting function can:

create an overview of product maintenance transactions by specified criteria, e.g.status or priority

go to the corresponding step in an open product maintenance transaction in theMaintenance Optimizer

create an overview of product maintenance transactions, and save it in a local file forfurther processing

IntegrationThe roporting function is in SAP CRM, and lists the selected product maintenancetransactions in the Maintenance Optimizer.

Prerequisites

SAP Solution Manager users have created at least one product maintenance transaction.

Features

The results can be passed to an external application for further processing. These include:

Microsoft Excel

Rich Text format

HTML

The system displays a list of product maintenance transactions which satisy your selectioncriteria. You can die sort the information by columns, and save the list as a local file for furtherprocessing.

Double-click on an entry in the list, to get further details of it. The system goes to thecorresponding step in the Maintenance Optimizer, as last saved by the user.

ActivitiesTo display an overview of the product maintenance transactions performed with theMaintenance Optimizer, call the transaction /TMWFLOW/MAINTENANCE.

Select product maintenance transactions by the following criteria:

System Status:

o Open

o Completed

Priority: The transaction priority selected by the user

User Status: corresponds to the current transaction step


46/46


Created/Changed on: Date on which the transaction was created or last changed

Created/Changed by: User who created or last changed the transaction

Solution: SAP Solution Manager solution in which the transaction was created

SAP Product: Product version selected in step Plan Maintenance

System: a system in the transaction

System Status: Implementation status of the systems in the transaction. If at leastone system in the transaction satisfies the status criteria which you selected, thereport performs this transaction.

Choose Execute.

mopz sp22 final en

Documents