Maintenance Optimizer Features and key improvements for the SAP Business Suite 7 Innovations 2010 based on SAP Solution Manager 7.0 EHP1 SP23 TECHNOLOGY & INNOVATION PLATFORM CORE Lifecycle Management August 2011
Goal of the Maintenance Optimizer: Plan, manage and carry out all maintenance activities Central point of access in SAP Solution Manager for all maintenance-related activities to manage the installation of Support Packages, Support Package stacks and Enhancement Packages (EHPs) for the SAP Business Suite and to support upgrades. Maintenance Optimizer gives an overview of all maintenance activities in your system landscape Maintenance Optimizer leads you through the planning, download and implementation of the above mentioned maintenance activities. Guided Procedure in a Maintenance Optimizer Transaction 2011 SAP AG. All rights reserved. 2
Maintenance Optimizer for the Business Suite 7i2010 Prerequisites SAP Solution Manager 7.0 EHP1 SP23 (or higher) is required to install SAP Business Suite 7i2010. SAP recommends to apply the latest SP to the Solution Manager system. Take SAP Note 1488450 into account if the Business Suite 7i2010 product version data is missing in the Maintenance Optimizer. Accuracy of system data and the correctness of landscape data in Solution Manager System Landscape (SMSY) is the key for a successful installation of SAP Business Suite 7i2010. Recommendation To ensure consistency in your system landscape SAP strongly recommends to use the Landscape Verification 1.0 SP1 Add-on for SAP Solution Manager. This is especially recommended for customers planning to install or upgrade to the Business Suite 7i2010. 2011 SAP AG. All rights reserved. 3
Maintenance Optimizer Transaction: Select Target State Technical Usage: predefined, installable subsets of an SAP enhancement package for SAP ERP SAP Note 1324838 (ERP EHP5) maps identified Business Functions to Technical Usages Enter the Technical Usages in the Maintenance Optimizer and it automatically calculates the relevant download files and the stack xml-file Example: ERP EHP 5 including Technical Usage HCM Self Services 2011 SAP AG. All rights reserved. 4
Key improvements of the Maintenance Optimizer for the SAP Business Suite 7 Innovations 2010 1 2 3 4 5 All New Frontend Design Browser based Frontend Simplified Navigation through Guided Procedure Minimal impact on customer system landscape Landscape Awareness Landscape Pattern Different Innovation Speeds Support of SAP Add-On products Identify installed Add-On Products Install additional Add-On Products Additional Java Patch Download Java Patch Selection Java Patch Download Better Supportability Application Logs Traces Stack File 6 Legal Change Packages for SAP ERP HCM solutions 2011 SAP AG. All rights reserved. 5
1) All New Frontend Design Complete New Frontend Entire frontend has been replaced by a redesigned WebDynpro UI Integration in Solution Manager Work Center Change Management New Guided Procedure Guided procedure has been optimized to reduce superfluous noise on the UI and to improve the user experience Navigation in the guided procedure is always explicit and non-ambiguous Presentation of stack details and system impacts in the guided procedure Integration of application logs, Traces and stack files into the guided procedure Customer Benefit Better and nicer user interface Simplified and unique navigation Easier to use 2011 SAP AG. All rights reserved. 6
2) Minimal impact on customer system landscapes Minimum impact on landscape Often more than one SAP application is deployed on a technical system (see figure) Interdependencies of technical systems during maintenance activities and EHP implementation Avoid unnecessary updates of connected systems Landscape Pattern MOPZ interprets landscape pattern and calculates software updates for connected systems and hubs with minimum system impact Different innovation speeds Manage different innovation speeds in landscape For details: "Bring Innovations to Complex Landscapes, Quickly and Easily" ECC 6.0 EHP5 AS ABAP 7.02 SAP ERP System Product System SAP ERP ERP Content XSS 605 SRM Content NetWeaver EP-C software update AS JAVA 7.0 SAP NetWeaver Portal (Hub) SRM 7.0 AS ABAP 7.01 SAP SRM System Product System SAP SRM Product System SAP NetWeaver 2011 SAP AG. All rights reserved. 7
3) Support of SAP Add-Ons Automated Add-On handling in MOPZ MOPZ supports the installation, maintenance and upgrade of SAP Add-On product versions based on SAP NetWeaver 7.0 EHP2 as target product version: Installed SAP Add-On product versions on the source system are identified Additional installable SAP Add-On product versions on the target system are offered and can be included to the target stack also. Selected Add-On product versions are part of the calculated stack XML-file and included in the download files SAPup or SAPehpi will automatically deploy these Add-Ons without additional manual work Compatibility of Add-Ons in general Check SAP Note 1318299 if you re planning to run ERP EHP5 together with an Add-On on the same system 2011 SAP AG. All rights reserved. 8
3) Support of SAP Add-Ons Example Include the SAP Add-On EHP1 for SAP Event Management 7.0 in an ERP EHP5 stack xml-file calculation 2011 SAP AG. All rights reserved. 9
4) Additional Java Patch Download Automated download of Java Patches The Maintenance Optimizer offers the option to download latest patches for Java support packages in the maintenance transaction The Maintenance Optimizer downloads these files, but does not automatically import them. The selected Java patches have to be deployed separately. 2011 SAP AG. All rights reserved. 10
4) Additional Java Patch Download Example Download latest Java patches for XSS self services Support Packages for XSS Self Services 2011 SAP AG. All rights reserved. 11
5) Legal Change Packages for SAP ERP HCM solutions Installation of Legal Change Packages For an HR system you can add HR Support Packages or Country Legal Change Packages (CLC Packages) within a MOPZ maintenance transaction Demo on SAP Service Marketplace Demo Maintenance Optimizer and HR Legal Change Packages 2011 SAP AG. All rights reserved. 12