FAQs on Maintenance Optimizer

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:
• End-to-end and fully pre-configured maintenance management process
• Planning and deployment dashboard for all maintenance-related activities

 

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."

 

3. Is Maintenance Optimizer part of SAP Solution Manager?
   Yes, Maintenance Optimizer is part of SAP Solution Manager. It is included in the standard delivery of Support Package Stack 9 for SAP Solution Manager 7.0. A reduced version will also be available in Support Package Stack 15 for SAP Solution Manager 3.2.

 

4. Which Release of SAP Solution Manager is recommended for Maintenance Optimizer?
   SAP strongly recommends the use of SAP Solution Manager 7.0. Most benefits like planning, transparency and reporting are available only with SAP Solution Manager 7.0. In addition, further enhancements like the automated deployment of patches will only be available in SAP Solution Manager 7.0. Maintenance Optimizer in SAP Solution Manager 3.2 only allows the approval process. It does not support the planning and download process.

 

5. For which applications is Maintenance Optimizer required?
   Maintenance Optimizer is required to download Support Packages, released after April 2^nd, 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.

 

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

 

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.

 

8. How can I download SPAM/SAINT and JSPM updates in the future?
   Those updates will be available without Maintenance Optimizer. SAP is working on giving customers the option to include those into Maintenance Optimizer as well.

 

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.

 

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.

 

11. What exactly changed in Software Distribution Center (SWDC) on April 2, 2007?
    Only the direct download from the SAP Service Marketplace is disabled. That means you can continue to view the Software Distribution Center and add packages to the basket. Only the download itself requires the confirmation via SAP Solution Manager.

 

12. How can I find out, whether my SAP Application will require Maintenance Optimizer starting April 2^nd?
    
          SAP Applications that require Maintenance Optimizer:
• mySAP CRM 2005
• mySAP ERP 2005
• mySAP SCM 2005
• mySAP SRM 2005
• SAP Netweaver 2004s
• SAP Solution Manager 7.0

      SAP Applications that do not require Maintenance Optimizer:

• SAP APO 3.1
• SAP BW 3.0B
• SAP BW 3.1 Content
• SAP CRM 3.0
• SAP CRM 3.1
• SAP CRM 4.0
• SAP ERP 2004
• SAP NetWeaver'04
• SAP R/3 4.6C
• SAP R/3 4.6C (HR)
• SAP R/3 4.7x110
• SAP R/3 4.7x110 (HR)
• SAP R/3 4.7x200
• SAP R/3 4.7x200 (HR)
• SAP SCM 4.0
• SAP SCM 4.1
• SAP Solution Manager 3.2
• SAP SRM 2.0
• SAP SRM 3.0
• 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.

 

13. Which will be the first Support Package Stacks that require the Maintenance Optimizer?
    According to the current SAP Support Package Stack Schedule the first Support Package Stacks for SAP Solutions (based on Business Suite 2005) that will require Maintenance Optimizer are: mySAP CRM 2005 ' SP Stack 9, planned availability calendar week 23 mySAP ERP 2005 ' SP Stack 9, planned availability calendar week 20 mySAP SCM 2005 ' SP Stack 9, planned availability calendar week 23 mySAP SRM 2005 ' SP Stack 9, planned availability calendar week 24 SAP NetWeaver 2004s ' SP Stack 12, planned availability calendar week 19 SAP Solution Manager 7.0 ' SP Stack 12, planned availability calendar week 24.
    Disclaimer: Be aware, that the information contained in this schedule is subject to change. SAP does not guarantee the availability of an SP Stack on the specified date.

 

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

 

15. 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

 

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

 

17. How do I start Maintenance Optimizer?
    Start SAP Solution Manage using transaction "solution_manager". Maintenance Optimizer is available via "Change Management" ⇒ "Support Package Stacks"

 

18. 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.

 

19. 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.

 

20. 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))

 

21. 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.

 

22. 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,…

 

23. What happens if my SAP Solution Manager system is temporarily unavailable?
    SAP will provide 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.

 

24. 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 disconnected from the SAP.

 

25. 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.

 

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

 

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