solman

Maintenance Optimizer

The Maintenance Optimizer leads you through the planning, download and implementation of new software versons in existing systems. This includes the following actions:

Implementing support package stacks, which contain a set of support packages for your systems.

Implementing enhancement packages and upgrades, for which the Maintenance Optimizer provides the required files.

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

Integration

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

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

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

You must logon with your S-user. The S-user is your SAP Service Marketplace user ID. For more information see S-Users in the Maintenance Optimizer.

o It reads the download basket of your S-user.o This is a prerequisite for the approval of selected items in the download basket for

download. For further information, see Approve and Download Files in Download Basket.

o It gets the confirmed items in the maintenance transaction.o To specify maintenance transactions, the Maintenance Optimizer needs landscape

data. This is collected, by default, in the System Landscape Directory, and passed to the Landscape Management Database (LMDB) in SAP Solution Manager, for further processing. It is then available to the Maintenance Optimizer.

You can download the maintenance files provided by the Maintenance Optimizer, with the Download Manager.

The functional scope of the Maintenance Optimizer can be extended by the Software Lifecycle Manager automatic download functions.

You can use the following SAP upgrade tools to import the maintenance files provided:o SAP Add-On Installation Tool (SAINT)o Support Package Manager (SPAM)o Java Support Package Manager (JSPM)o Software Update Manager (SUM)

o ABAP Upgrade Program (SAPup)o SAP Java Upgrade Program (SAPJup)

Features

The Maintenance Optimizer helps you to maintain the implementation status when scheduling and performing maintenance. For more information, see Maintenance Transaction Overview, Maintenance Transaction Steps and Maintenance Transaction Scenarios.

To start a new maintenance transaction, choose a product version. The Maintenance Optimizer proposes product systems for the maintenance, based on the information obtained. You can simulate maintenance transactions.

Product systems are groups of technical systems which belong to one or more products. In the Maintenance Optimizer, you create a maintenance transaction for one product. For more information, see Manage Logical Landscape Information.

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

Scenario More Information

Manual selection of maintenance filesApprove and Download Files in Download Basket

Maintenance:

With installation of support package stacks With installation of support package stacks

for enhancement packages

Maintenance Transaction with Installation of a Support Package Stack

Installation of enhancement packages:

Without technical usages With technical usages

Maintenance Transaction with Installation of an Enhancement Package

Upgrade UpgradeInclude enhancement packages in an upgrade Upgrade with an Enhancement Package

Get Maintenance Files

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

Manual selectiono 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, see Approve and Download Files in Download Basket. Automatic calculation

o The Maintenance Optimizer determines the files to maintain the selected product system landscape, or the components to install an enhancement package. For further information, see Get Download Files Automatically, under Maintenance Transaction Steps.

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

o It simplifies the automatic installation of the files calculated for product maintenance 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 system/product combination, to be maintained or installed, the technical systems, and the assigned support package stacks.

It manages the downloaded files, in a central directory. You can create an XML-based simulation file, which simulates your start constellation

with the current status of the product systems. You start a maintenance transaction in simulation mode, or a regular maintenance transaction, from this simulation file. For more information, see Simulation-Data-Based Maintenance Transyction.

The Change Management work center shows an overview of all open and completed maintenance transactions for the user.

In the Queries view, you can also specify complex queries for all maintenance transactions. For more information, see Complex Product Maintenance Transaction Queries.

Please rate this topic:

Please send us your feedback about this topic. It will help us improve the quality of the documentation.

Answers

1. What is the Maintenance Optimizer? Maintenance Optimizer is a new function of SAP Solution Manager. It offers significant enhancements for maintenance processes and activities, such as:

o End-to-end and fully pre-configured maintenance management process o Planning and deployment dashboard for all maintenance-related activities

Back to Top

2. What are the benefits of Maintenance Optimizer? Maintenance Optimizer simplifies the management of patches for the customer's SAP support staff and helps to reduce maintenance costs. In addition, it provides transparency and enables you to govern your maintenance processes end-to-end. This step re-affirms SAP's overall service and support strategy with SAP Solution Manager as the key customer-facing support tool aiming to provide maximum benefit to SAP customers every day."

Back to Top

3. Is Maintenance Optimizer part of SAP Solution Manager? Yes, Maintenance Optimizer is part of SAP Solution Manager.

Back to Top

4. Which Release of SAP Solution Manager is recommended for Maintenance Optimizer? SAP recommends always using the latest Support Package of SAP Solution Manager.

Back to Top

5. For which applications is Maintenance Optimizer required? Maintenance Optimizer is required to download Support Packages, released after April 2nd, 2007 for all SAP applications based on SAP NetWeaver 2004s. This includes e.g. mySAP ERP 2005 and mySAP CRM 2005. In addition, it is also required for SAP NetWeaver 2004s standalone. However, you can download kernel updates without Maintenance Optimizer.

Back to Top

6. Can I also use Maintenance Optimizer for other SAP applications? Yes, the benefits of Maintenance Optimizer can be used for all SAP applications. This includes e.g. mySAP ERP 2004 and SAP R/3 Enterprise

Back to Top

7. Is the download of Support Packages and Stacks for Industry Solutions affected by Maintenance Optimizer? Yes, if they are based on NetWeaver2004s of mySAP Business Suite 2005.

Back to Top

8. How can I download SPAM/SAINT and JSPM updates? Those updates can be included in maintenance transactions in Maintenance Optimizer.

Back to Top

9. Does Maintenance Optimizer support Java support packages? Yes, Maintenance Optimizer manages all support packages for all instances of an SAP application, covering ABAP and Java.

Back to Top

10. Will the delivery of Support Packages and Stacks change for lower releases (e.g. mySAP ERP 2004 or SAP R/3 Enterprise)? The procedure for lower releases is not changed. However, the Maintenance Optimizer can be used for those products as well.

Back to Top

11. How can I find out, whether my SAP Application requires Maintenance Optimizer starting?

SAP Applications that require Maintenance Optimizer:

o All SAP Applications based on SAP Netweaver 7.0 and higher.

SAP Applications that do not require Maintenance Optimizer:

o SAP APO 3.1 o SAP BW 3.0B o SAP BW 3.1 Content o SAP CRM 3.0 o SAP CRM 3.1 o SAP CRM 4.0 o SAP ERP 2004 o SAP NetWeaver'04 o SAP R/3 4.6C o SAP R/3 4.6C (HR) o SAP R/3 4.7x110 o SAP R/3 4.7x110 (HR) o SAP R/3 4.7x200 o SAP R/3 4.7x200 (HR) o SAP SCM 4.0 o SAP SCM 4.1 o SAP Solution Manager 3.2 o SAP SRM 2.0 o SAP SRM 3.0 o SAP SRM 4.0

Hint: to verify if a dedicated SAP application will require the Maintenance Optimizer for delivery of updates, please go to the SAP Software Distribution Center (SWDC) 'Download' 'Support Packages and Patches'. On the level of Software Components it is indicated, if Maintenance Optimizer will be required. The same information is available for Support Package Stacks.

Back to Top

12. What about Support Package and Stacks released before April 2nd, 2007? Support Package and Stacks released before April 2nd, 2007 will not require Maintenance Optimizer. Maintenance Optimizer is required for packages release after April 2nd , 2007.

Back to Top

13. How do I configure Maintenance Optimizer? Please refer to the Implementation Guide (IMG, can be called via transaction SPRO) ⇒ SAP Solution Manager ⇒ Advanced configuration ⇒ Basic settings ⇒ SAP Solution Manager system ⇒ Change Management ⇒ Set-Up Maintenance Optimizer

Back to Top

14. Do I need to configure the complete Change Request Management for Maintenance Optimizer? No, Change Request Management is not required for Maintenance Optimizer.

Back to Top

15. How do I start Maintenance Optimizer? The Maintenance Optimizer can be found in the Work Center "Change Management" in SAP Solution Manager.

Back to Top

16. How does Maintenance Optimizer approval step work in detail? To work with Maintenance Optimizer, it needs to be connected via secure RFC connection to SAP. The Download Basket offers the additional category "Approval List". All packages that require approval are initially added to this new section of the Download Basket. Items on the "Approval List" can not be downloaded directly, but have to be approved. The approval step (integrated in Maintenance Optimizer) moves the packages to the actual Download Basket, from where they can be downloaded via Download Manager or directly to the local PC or network.

Back to Top

17. Does the technical download of Support Packages and Stacks change? No, selected packages are still put into the user's Download Basket in SAP Service Marketplace first. All packages for applications based on SAP NetWeaver 2004s require an approval step by SAP Solution Manager. This approval step is integrated in Maintenance Optimizer.

Back to Top

18. Once a Support Package is downloaded for a certain system, can it be imported in other systems as well or do I need to perform the download several times? Once a package is downloaded it can be imported in other systems as well. (E.g. Support

Packages for SAP_BASIS and SAP_ABA need to be downloaded once and can be imported into several systems (DEV, QAS, PRD) or products (SAP ERP, SAP CRM, SAP NetWeaver))

Back to Top

19. Do I still need the SAP Download Manager to download Support Packages and Stacks? Yes, these are still downloaded by SAP Download Manager. SAP will adapt the Download Basket, so that third party "download managers" can be used in the future as well.

Back to Top

20. Are Support Packages imported by Maintenance Optimizer? No, the import of Support Packages and Stacks is not effected by Maintenance Optimizer. They are still imported by the existing SAP tools like SPAM, SAINT,…

Back to Top

21. What happens if my SAP Solution Manager system is temporarily unavailable? SAP provides a fallback scenario. If urgently required, customers can create a message at component SV-SMG-MAI-APR and SAP will release the required download basket in SAP Service Marketplace.

Back to Top

22. Can I use Maintenance Optimizer if the SAP Solution Manager is not connected permanently to SAP? Yes, SAP Solution Manager does not need to be connected to SAP permanently. The connection to SAP is only required during the delta calculation phase and for confirmation of the downloads. All other steps of the Maintenance Optimizer can be done even if SAP Solution Manager is not connected to SAP.

Back to Top

23. How can customers with strong security policies use Maintenance Optimizer? To work with Maintenance Optimizer, it needs to be connected via secure RFC connection to SAP. Without this, it is impossible to use Maintenance Optimizer as collaboration platform. However, there are customers with high security requirements. Their procedure can be as follows: 1. Customer logs on to SAP Service Marketplace from a PC. This may be done in an environment even without connection to SAP Solution Manager. 2. Customer adds all required files to the download basket. 3. Customer then changes to a PC with connection to SAP Solution Manager and confirms the download of the data. For more information about secure RFC connection please refer to IMG in SAP Solution Manager. 4. The files are available for download and can be downloaded from the PC with a connection to the SAP Service Marketplace.

Back to Top

24. How can Value Added Resellers provide access to Maintenance Optimizer to their customers? Find details in SAP Note 1021275.

Back to Top

25. Where do I find additional technical information on Maintenance Optimizer? Please refer to SAP Note 1024932.

Back to Top

26. When using Maintenance Optimizer, why are there Technical Usages preselected and the selection cannot be changed? If Technical Usages or Business Functions are preselected, this means that these functions are already activated in the system. To ensure a consistent system state, Maintenance Optimizer automatically preselectes these Technical Usages or Business Functions and does not allow the user to deselect them.

Back to Top

inShare

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

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

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

Contents

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

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

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

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

1. Identify your technical systems and product systems

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

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

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

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

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

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

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

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

linkage and landscape pattern data, MOpz gives most precise calculation for your update – MOpz calculates for the constellation of inter-dependent technical systems altogether other than one by one separately.

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

2. Assign product versions to the product system

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

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

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

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

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

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

Example of assigned product versions for a product system:

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

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

Here are 3 examples of system maintenance:

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

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

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

Figure: Legend of illustration below

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

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

Figure: Product system CCD before update

The mapping of the above reality in SMSY.

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

Figure: Technical system CCD

Figure: Technical system DCD

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

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

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

Figure: Choose target

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

Figure: Selected and calculated targets

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

Figure: Product system CCD after update

You have selected a new product instance Finbasis in the above maintenance, which is not defined in CRM 7.0/NW7.01 product version. Assign a new product version EhP1 for SAP CRM

7.0 to CCD, and point the new installed product instance Finbasis to the technical system on which it’s installed.

Figure: Assign active product versions

Figure: Assign active product versions

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

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

Suppose you want to update ERP_0007 with new SAP innovations.

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

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

Figure: Product system ERP_0007 (a)

Figure: Product system ERP_0007 (b)

Figure: Product system CRM_0002

Figure: NW7 landscape pattern

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

Figure: Select target stack and technical usages

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

Figure: Selected and calculated targets

3. After the update, the system landscape is:

Figure: Product system ERP_0007 and CRM_0002 after update

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

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

Figure: Product system ERP_0002

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

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

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

Figure: Choose target stack

The targets are calculated for the product system ERP_0002:

Figure: Selected and calculated targets

Updgrade technical system ERP.

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

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

Figure: product system ERP_0002 after upgrade

6061 Views Average User Rating(4 ratings)My Rating: inShare

Comments

1 Comment

Jansi Rani Murugesan Mar 13, 2012 3:42 AM

Indeed Useful one!

Thanks for the sharing!

Like (0)

SAP TechEd 2012 SessionsExplore over 1,000 hours of educational content by track, sub-track, products and hot topics. View sessions for Las Vegas, Madrid and Bangalore. Learn More

Filter Blog

By date:

January 2011

Recent Posts

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

Incoming Links

Re: Stack for BW 7.0 Ehp3 Re: Hello Gurus Top 15 Most Popular SAP SCN Blogs of 2011

Follow SCN

Site Index Contact Us SAP Help Portal

Privacy Terms of Use Legal Disclosure Cop