Maintenance Management

An Overview of Maintenance Optimizer and Maintenance Certificate

Solution Management
Application Lifecycle Management
 Disclaimer

This presentation is a preliminary version and not subject to your license agreement
or any other agreement with SAP. This document contains only intended strategies,
developments, and functionalities of the SAP product and services and does not bind
SAP to any particular course of business, product strategy, and/or development. This
document is subject to change and may be changed by SAP at any time, without
notice.

SAP assumes no responsibility for errors or omissions in this document.

© SAP 2008 / Page 2

 Contents

1. Overview of Maintenance Process

2. Basic Concept of Maintenance Optimizer
3. Maintenance Optimizer in Action
3.1. Overview of enhancements (SP 18)
3.2. Single system update
3.3. Track update
3.4. Maintenance Optimizer and enhancement packages
4. Summary Maintenance Optimizer
5. Maintenance Certificate

© SAP 2008 / Page 3

 Maintenance of an SAP Landscape

Customer pain points

1 Maintenance activities are Customer has no overview over required maintenance

not transparent activities in the system landscape

Various types of changes have to be applied to maintain a

2 Maintenance activities
landscape, e.g.
require considerable
manual effort OS & DB patches, SAP kernel patches
Support packages / enhancement packages / Legal
Changes
Transport requests
Different objects have different deployment mechanisms
The activities need to be synchronized manually

No control of maintenance No central procedure to control maintenance activities

3
activities No standardized way to perform maintenance activities

© SAP 2008 / Page 4

 Maintenance of an SAP Landscape – The
Challenge
Current situation:
Typical customer landscape comprises a development, a consolidation, and a production
environment.
Changes are made in development environments and are applied and tested in the
consolidation environment before being applied to the production landscape and used by
the business.
Changes in SAP landscapes comprise:
Operating system and database patches as well as SAP kernel patches
SAP support packages and patches for software components
Custom development and code changes that are included in SAP Notes
Deployment mechanisms:
OS/DB patches, SAP kernel patches & SAP Support packages & patches have to be
deployed manually to the dedicated servers, and imported with the appropriate tools
SAP Transport Management System (TMS) to transport ABAP-based custom
development and code changes. With One Transport Order (OTO) enhancements, TMS
can transport non-ABAP changes as well

Maintenance Optimizer has been enhanced to control the entire

maintenance process in a customer landscape
© SAP 2008 / Page 5
 Maintenance of an SAP Landscape – The
Solution

Development Landscape Test Landscape Productive Landscape

DEV TST PRD

OS / DB patches

SAP kernel patches

Service*

SAP Support SPAM /

SLM

packages & patches JSPM /

EHPs, LCPs, … SAPehpi

Custom Development
/ Customizing ABAP CTS
TMS

(Single) SAP Notes

Custom Development CTS+

JAVA,.NET, C++ Maintenance Optimizer Governance – as of SP 18
* SAP kernel patches planned for 2010

© SAP 2008 / Page 6

 Contents

1. Overview of Maintenance Process

2. Basic Concept of Maintenance Optimizer
3. Maintenance Optimizer in Action
3.1. Overview of enhancements (SP 18)
3.2. Single system update
3.3. Track update
3.4. Maintenance Optimizer and enhancement packages
4. Summary Maintenance Optimizer
5. Maintenance Certificate

© SAP 2008 / Page 7

 Application Management Processes
Maintenance of SAP Solutions with Maintenance Optimizer

Plan Perform End

Select Files Download Files
Activity Implementation Maintenance

Select the system Select maintenance Select download type Deploy Packages to Maintenance
that requires type the related servers/ transaction is
Software Lifecycle
maintenance systems and import closed when
Maintenance Manager (SLM)
the packages implementation is
Create a service downloads
Upgrade (EHPs) finished in all
maintenance files automatically to a
systems
activity central download Transport Manage-
directory ment System (TMS)
Assign the relevant SAP Solution
ensures the correct
system / solution Manager connects to Put files in SAP
deployment of
Support Backbone Service Marketplace
transport orders
and displays possible download basket and
throughout the
options for the download via SAP
landscape
customer Download Manager
CTS+ (OTO)
functionality can be
Customer finalizes used to include non-
the selection ABAP changes

© SAP 2008 / Page 8

 Maintenance Optimizer Global Support
Backbone Interaction

SAP Solution Manager Global Support

User in SolMan S-User in SMP Backbone
MAYERF S000011111
MUELLERK S000021112 Available
SCHULZS S000088115 SP Stacks
3
… SPS 13

Display
1 SPS 14

SPS 15
Create SPS 16
Maintenance Activity

Download Selection
4
2
5
Assign Solution /
System
Solution
DEV TST PRD

© SAP 2008 / Page 9

 Perform Implementation – process view
Deployment of changes throughout the landscape

1 Download packages into central

Legal
SP Stack Change
OS / DB
directory
EHP Automatically using SLM Service
Kernel
Manually using SAP Download Manager

2 Import packages using 4

installation tools Import packages 11 Import packages using
using installation installation tools
tools

DEV TST PRD

3 Adapt changed objects 5 Import transport request 12 Import transport request

Apply side-effect Notes
Add changes to transport request 6 Conduct tests 13 Go-Live
Release transport request

7 Fix reported errors

Add fixes to transport request
Release transport request
8 Import transport request

9 Conduct tests

10 Release transport request

© SAP 2008 / Page 10
 Contents

1. Overview of Maintenance Process

2. Basic Concept of Maintenance Optimizer
3. Maintenance Optimizer in Action
3.1. Basic capabilities
3.2. Single system update
3.3. Track update
3.4. Maintenance Optimizer and enhancement packages
4. Summary Maintenance Optimizer
5. Maintenance Certificate

© SAP 2008 / Page 11

 Maintenance Optimizer – Capabilities

Customer creates a maintenance transaction

Maintenance Optimizer connects to the SAP Global Service Backbone,
specifies required option (e.g. target stack,..) and calculates the files required in
your solution
Maintenance files are selected and downloaded automatically to a local
download directory SLM service is required*
Maintenance files are deployed to required systems, import tools are started
(e.g. SPAM, SAINT, JSPM, SAPehpi), status is recorded, SLM Service is
required*
Deployment of changes (captured in Transport Orders) is controlled by
Maintenance Optimizer with extended navigation**
Maintenance procedure can be run from Change Management work center
Maintenance procedure can be related to solutions and/or systems*

* enhanced capabilities as of SP 18 ** available as of SP 21

© SAP 2008 / Page 12
 Contents

1. Overview of Maintenance Process

2. Basic Concept of Maintenance Optimizer
3. Maintenance Optimizer in Action
3.1. Basic capabilities
3.2. Single system update
3.3. Track update
3.4. Maintenance Optimizer and enhancement packages
4. Summary Maintenance Optimizer
5. Maintenance Certificate

© SAP 2008 / Page 13

 Use case: “Single system update”

Scope:
Apply the recent support package (stack) to a single system (e.g. set-up a new development
system for a future landscape)
A system that was installed initially is given the last support package level

Capabilities:
Maintenance Optimizer calculates required support packages
The packages are downloaded to a local directory by the SLM service
SLM service checks for required import tools and applies support packages in the target
system
Maintenance Optimizer controls the complete process and provides an overview of current
status

Requirements:
SLM service is configured

See demo for the scenario “Single system update”

© SAP 2008 / Page 14

 Use case: “Single system update”:
Automatic Download via SLM service

© SAP 2008 / Page 15

 Use case: “Single system update”:
Automatic Download via SLM service

© SAP 2008 / Page 16

 Use case: “Single system update”:
Automatic Deployment via SLM service

© SAP 2008 / Page 17

 Contents

1. Overview of Maintenance Process

2. Basic Concept of Maintenance Optimizer
3. Maintenance Optimizer in Action
3.1. Basic capabilities
3.2. Single system update
3.3. Track update
3.4. Maintenance Optimizer and enhancement packages
4. Summary Maintenance Optimizer
5. Maintenance Certificate

© SAP 2008 / Page 18

 Use case: “Track update”

Scope:
Maintain a landscape (development, test and productive systems) and bring it up to a required
support package level
Changes captured in transports are controlled, as well as support packages

Capabilities:
Maintenance Optimizer calculates required support packages
The packages are downloaded to a local directory using the SLM service
SLM service checks for required import tools
Transport requests can be created via Maintenance Optimizer
All changes (support packages and transport requests) are deployed and applied in the
landscape; Maintenance Optimizer provides a procedure (Step 4 Implementation is expanded into
sub-steps)
Maintenance Optimizer controls the complete process and provides an overview of current status

Requirements:
Available as of SP 21, SLM service is configured

See demo for the scenario “Track update”

© SAP 2008 / Page 19

 Use case: “Track update”:
Expanded Navigation – Step 4 Implementation

© SAP 2008 / Page 20

 Contents

1. Overview of Maintenance Process

2. Basic Concept of Maintenance Optimizer
3. Maintenance Optimizer in Action
3.1. Basic capabilities
3.2. Single system update
3.3. Track update
3.4. Maintenance Optimizer and enhancement packages
4. Summary Maintenance Optimizer
5. Maintenance Certificate

© SAP 2008 / Page 21

 Details of usage scenario for SAP ERP
Enhancement Packages

Enhancement Packages in a nutshell

Offer new functional enhancements to SAP ERP
Do not require upgrading your systems to take advantage of the newest technology and business process innovations
For more information about ERP enhancement packages, see: http://service.sap.com/erp-ehp

Maintenance Optimizer and EHPs

Additional capabilities of Maintenance Optimizer – related to EHPs
MOPZ can detect and download enhancement packages, just like support packages and patches (as
of SP 12)
MOPZ provides a configuration file (XML-based) that includes all selected packages
Configuration file is then used by SAINT (import tool for Add-Ons) or SAPehpi to ensure the application
of all required packages in the correct sequence
Use cases for EHPs
Maintenance – Apply support package without any other use
Installation – Use cases
– Install additional technical usage of the installed Enhancement Package Level
– Install a higher enhancement package level (and an additional technical usage)
Upgrade – Upgrade to SAP ERP 6.0 (as of Release 4.0B): Calculate and apply files required in
addition to the files from upgrade DVD

© SAP 2008 / Page 22

 SAP EhP Installation using SAPehpi an
Maintenance Optimizer – the Big Picture

Steps in EhP installation SAPinst / SAP SolMan

Prepare the system – application server: 1 2 3

1. Install the system
2. Configure the system
System data are input for SAP Solution Manger
3. Make the system known Maintenance Optimizer
in the SAP Solution Manager
Prepare the stack for the EhP SAP SolMan MOPZ
installation – SAP Solution Manager:
1 2 3 4 5
1. Plan Maintenance
2. Select Files
3. Download files
SAP Solution Manger Maintenance Optimizer
4. Perform Implementation
defines the download stack to apply with SAPehpi
5. End Maintenance
Apply the stack of EhP and SPS SAPehpi
to the systems – SAPehpi:
1 2 3 4 5 6 7 8
1. Initialization
2. Extraction
3. Configuration
4. Checks
5. Preprocessing
6. Downtime
7. Post processing
8. Finalization

© SAP 2008 / Page 23

 XML stack file to control the import tools

© SAP 2008 / Page 24

 Contents

1. Overview of Maintenance Process

2. Basic Concept of Maintenance Optimizer
3. Maintenance Optimizer in Action
3.1. Overview of enhancements (SP 18)
3.2. Single system update
3.3. Track update
3.4. Maintenance Optimizer and enhancement packages
4. Summary Maintenance Optimizer
5. Maintenance Certificate

© SAP 2008 / Page 25

 Maintenance Optimizer – Benefits

Customer Benefits

Transparency
The SAP Solution Manager provides an overview and monitors the complete maintenance
procedure for your entire SAP solution

Efficiency
Standardization: Maintenance Optimizer is a central access point for activities to plan and
download software updates. It governs the complete maintenance process
Maintenance Optimizer provides an easy-to-use interface, and guides the user through the
required steps

Control
The Maintenance Optimizer is a central access point for activities to plan and download
software updates.
SAP Solution Manager controls the complete process and the entire SAP solution

© SAP 2008 / Page 26

 How to Set-Up Maintenance Optimizer

Maintenance Optimizer is part of the basic configuration of SAP Solution Manager.

Maintenance Optimizer configuration steps are, e.g.
Configure Remote Connection to SAP Global Support Backbone
Assign S-user to SAP Solution Manager users
Connect systems to SAP Solution Manager ( Define system landscape)

Configure usage of extended functions:

Scenario-Specific Settings Change Control

Find more information in SAP Service Marketplace at

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

© SAP 2008 / Page 27

 Contents

1. Overview of Maintenance Process

2. Basic Concept of Maintenance Optimizer
3. Maintenance Optimizer in Action
3.1. Overview of enhancements (SP 18)
3.2. Single system update
3.3. Track update
3.4. Maintenance Optimizer and enhancement packages
4. Summary Maintenance Optimizer
5. Maintenance Certificate

© SAP 2008 / Page 28

 Maintenance Certificate in Detail

The Maintenance Certificate ensures that only customers with a valid maintenance
contract can apply support packages. It prevents unauthorized use.

Coverage:
All SAP products based on SAP NetWeaver 7.0 and beyond (including SAP Business
Suite 2005)

Deployment of Maintenance Certificates:

Automatically to all systems by SAP Solution Manager
Self-service to request a Maintenance Certificate will be offered in SAP Support Portal

Validity:
A Maintenance Certificate has a validity of 3 months

Procedure:
Maintenance Certificate is stored in SAP system license store (transaction: SLICENSE)
SAP import tools (e.g. SPAM, SAINT, JSPM,…) check for valid Maintenance Certificate
Import is stopped if no Maintenance Certificate is available

© SAP 2008 / Page 29

 Example – Maintenance Certificate File

----- Begin SAP Maintenance Certificate -----

SAPSYSTEM=MAR
HARDWARE-KEY=P1719877629
INSTNO=0020224520
BEGIN=20080115
EXPIRATION=20080415
LKEY=MIIBOgYJKoZIhvcNAQcCoIIBKzCCAScCAQExCzAJBgUrDgMCGgUAM
AsGCSqGSIb3DQEHATGCAQYwggECAgEBMFgwUjELMAkGA1UEBhMCREUxHDA
aBgNVBAoTE215U0FQLmNvbSBXb3JrcGxhY2UxJTAjBgNVBAMTHG15U0FQL
mNvbSBXb3JrcGxhY2UgQ0EgKGRzYSkCAgGhMAkGBSsOAwIaBQCgXTAYBgk
qhkiG9w0BCQMxCwYJKoZIhv
SWPRODUCTNAME=Maintenance_DB6
SWPRODUCTLIMIT=2147483647
SYSTEM-NR=000000000310537041

© SAP 2008 / Page 30

 Distribution of Maintenance Certificate –
Automatic vs. Manual

Distribution by SAP Solution Manual

Manager (recommended) distribution
Master Data
Data Customer Data
Exchange ---- Inst 00001234 Exchange via
---- Inst 00001245
---- Inst 00001256 SAP Service
Automatic
Regular Automatic Marketplace
ofKey
Update Updates
Maintenance SELF-SERVICE:
Request
on Certificate
regular basis Certificate

SAP Solution Maintenance

Manager Certificate is
distributes installed
Maintenance manually on
Certificate to every system
system

SAINT
SAINT
SPAM
SPAM
JSPM
JSPM

© SAP 2008 / Page 31

 Automatic Distribution of Maintenance
Certificates – Process Flow
Customer Global Support
Backbone
SAP Solution Manager

SolMan requests 1 Maintenance

Maintenance Certificates Certificates are
generated

2
Managed system
3 SolMan receives
Maintenance Certificates
4

System receives
Maintenance Certificate

1 SAP Solution Manager requests Maintenance Certificates for all managed systems
2 Maintenance Certificates are generated in Global Support Backbone
3 SAP Solution Manager receives Maintenance Certificates upon next connection
4 Managed system pulls Maintenance Certificate from SAP Solution Manager
End-to-end process may take up to 48 hours (SAP Solution Manager connects to Global
Support Backbone once a day)
© SAP 2008 / Page 32
 License Management Cockpit (as of SP 18)

Scope of License Management Cockpit:

License Management Cockpit provides a central overview on available Licenses and
Maintenance Certificate for all systems that are known by the SAP Solution Manager system

Basic capabilities:
Central overview
Receive Maintenance Certificate and SAP Licenses of SAP’s Global Service Backbone
Distribute items to the systems connected to SAP Solution Manager
Manage automatic distribution of Maintenance Certificate and licenses per system
Download received Maintenance Certificate and SAP Licenses in bulk
Multi-customer support

© SAP 2008 / Page 33

 License Management Cockpit

Manage automatic
distribution
Multi-customer support
Download in bulk

Filter

© SAP 2008 / Page 34

 Maintenance Certificate – Additional
Information

General information about Maintenance Certificates is in SAP Support Portal at

http://service.sap.com/maintenancecertificate

This includes:
FAQ Section on Maintenance Certificates
How to request a Maintenance Certificate in SAP Support Portal
SAP Solution Manager 7.0 Set-up Guide “Automatic Distribution of Maintenance
Certificates by SAP Solution Manager”

© SAP 2008 / Page 35

 Thank you!

© SAP 2008 / Page 36

 Copyright 2008 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.
SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, SAP Business ByDesign, ByDesign, PartnerEdge 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 and associated logos displayed
are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.
The information in this document is proprietary to SAP. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document
contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy,
and/or development. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or
other items contained within this material. This document is provided 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 have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation
shall not apply in cases of intent or gross negligence.
The statutory liability for personal injury and defective products is not affected. 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

Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durch
SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden.
Einige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte können Softwarekomponenten umfassen, die Eigentum anderer Softwarehersteller sind.
SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, SAP Business ByDesign, ByDesign, PartnerEdge und andere in diesem Dokument erwähnte SAP-Produkte und Services sowie die
dazugehörigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Ländern weltweit. Alle anderen in diesem Dokument erwähnten Namen
von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich und dienen lediglich zu
Informationszwecken. Produkte können länderspezifische Unterschiede aufweisen.
Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP. Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderen
Vereinbarung mit SAP. Dieses Dokument enthält nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP®-Produkts und ist für SAP nicht bindend, einen bestimmten
Geschäftsweg, eine Produktstrategie bzw. -entwicklung einzuschlagen. SAP übernimmt keine Verantwortung für Fehler oder Auslassungen in diesen Materialien. SAP garantiert nicht die
Richtigkeit oder Vollständigkeit der Informationen, Texte, Grafiken, Links oder anderer in diesen Materialien enthaltenen Elemente. Diese Publikation wird ohne jegliche Gewähr, weder
ausdrücklich noch stillschweigend, bereitgestellt. Dies gilt u. a., aber nicht ausschließlich, hinsichtlich der Gewährleistung der Marktgängigkeit und der Eignung für einen bestimmten Zweck
sowie für die Gewährleistung der Nichtverletzung geltenden Rechts.
SAP übernimmt keine Haftung für Schäden jeglicher Art, einschließlich und ohne Einschränkung für direkte, spezielle, indirekte oder Folgeschäden im Zusammenhang mit der Verwendung
dieser Unterlagen. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit.
Die gesetzliche Haftung bei Personenschäden oder die Produkthaftung bleibt unberührt. Die Informationen, auf die Sie möglicherweise über die in diesem Material enthaltenen Hotlinks
zugreifen, unterliegen nicht dem Einfluss von SAP, und SAP unterstützt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewährleistungen oder Zusagen über
Internetseiten Dritter ab.
Alle Rechte vorbehalten.

© SAP 2008 / Page 37