SAP Enterprise Support Book Intro

Gerhard Oswald, Uwe Hommel
SAP Enterprise Support

ASAP to Run SAP
Bonn Boston
Contents at a Glance
1 2 Introduction ....................................................................... Establishing SAP Solution Manager as a Consolidated Data Source in Your Enterprise .......................................... 3 4 5 6 7 8 9 10 11 Introducing the Measurement Platform ............................ Customer Center of Expertise ............................................ 35 89 99 17
Preserving Business Continuity ......................................... 131 Accelerated Innovation ...................................................... 163 Improving Business Processes ........................................... 197 Protection of the IT Investment ........................................ 219 Innovating Without Risking Disruptions .......................... 257 SAP MaxAttention and SAP Safeguarding ........................ 271 Mission-Critical Support for Partner Applications and Technologies ...................................................................... 289
12 Run SAP Programs for SAP Partners ................................. 311 13 Overview of Training and Certification Offerings .............. 323
Contents
Preface ............................................................................................. 15
Introduction .................................................................
1.1 1.2 1.3 1.4 What SAP Enterprise Support Can Do for You ................ SAP Standards for Solution Operations ........................... Creating the Foundation for a Single Source of Truth ...... About This Book .............................................................
17
18 20 23 30
Establishing SAP Solution Manager as a Consolidated Data Source in Your Enterprise ..............
2.1 Basic Concepts ............................................................... 2.1.1 Application Management Lifecycle ..................... 2.1.2 Projects in SAP Solution Manager ...................... 2.1.3 Solutions in SAP Solution Manager .................... 2.1.4 Processes for Application Lifecycle Management ..................................................... 2.1.5 Quality Gates in SAP Solution Manager .............. Implementing SAP Solution Manager as a Standardized Platform for Application Lifecycle Management .............. 2.2.1 Planning ............................................................ 2.2.2 Installation and Configuration of SAP Solution Manager ............................................................ Business Configuration .................................................... 2.3.1 Requirements Phase ........................................... 2.3.2 Design Phase ..................................................... 2.3.3 Build and Test Phase .......................................... 2.3.4 Deploy Phase ..................................................... Business Continuity ........................................................ 2.4.1 Operate Phase ................................................... 2.4.2 Optimize Phase ..................................................
35
35 36 37 38 40 44 45 46 46 49 50 52 54 60 63 63 78
2.2
2.3
2.4
Contents
Introducing the Measurement Platform ......................

3.1 3.2 3.3 3.4 SAP Solution Manager as SAPs Measurement Platform ... Architecture and Definition of the Measurement Platform .......................................................................... Continuous Assessment and Improvement ...................... Outlook on Upcoming Enhancements to the Measurement Platform ...................................................
89
90 91 94 96
Customer Center of Expertise ......................................

4.1 Challenges for the CIO .................................................... 4.1.1 Ensure Business Continuity ................................. 4.1.2 Reduce Costs ...................................................... 4.1.3 Improving Business Processes ............................. 4.1.4 Accelerate Innovation ........................................ Organizational Model for Company Solution Operations ...................................................................... 4.2.1 Optimizing Internal Collaboration in Two Ways ... 4.2.2 Outtasking and Outsourcing ............................... From Customer Competence Center to Customer Center of Expertise ......................................................... 4.3.1 The Customer COE Charter ................................. 4.3.2 The Reactive IT Box ............................................ 4.3.3 Set up, Manage, and Coordinate the Situation Room .................................................. 4.3.4 Quality Manager Roles in the Customer COE ...... 4.3.5 Customer COE Certification ................................
99
101 102 104 105 105 106 109 109 110 111 113 114 117 127
4.2
4.3
Preserving Business Continuity ................................... 131

5.1 5.2 Highest Availability of Mission-Critical Business Processes ........................................................................ The Necessity of Business Continuity ............................... 5.2.1 Ensuring Continuous Business Availability .......... 5.2.2 Operate More Systems with Fewer Resources .... 5.2.3 Reduce License and Project Costs with SAP Solution Manager Enterprise Edition ........... 5.2.4 Reduce Cost of Resources ................................... 132 134 134 134 135 136
Contents
5.3
5.4
5.5 5.6
5.2.5 Reduce Infrastructure Requirements .................. 5.2.6 Increase Business Value of IT .............................. Managing Business Continuity from the QMs Perspective ..................................................................... 5.3.1 Close Cooperation Between QM and Teams ...... 5.3.2 SAP Technical Operations .................................. 5.3.3 Business Process Operations .............................. 5.3.4 Application Management Team ......................... Quality Management for Business Continuity: How You Can Measure Your Success .............................. 5.4.1 Technical Operations ......................................... 5.4.2 Business Process Operations .............................. 5.4.3 Application Management ................................... Services Available from SAP Active Global Support, Training, and Certification ............................................... Case Study: Ensuring Stable Operations .......................... 5.6.1 The Case-Study Scenario .................................... 5.6.2 Setting Up Standard-Compliant Operations ........ 5.6.3 Application Management and SAP Technical Operations Strategy ........................................... 5.6.4 Business Process Operations Strategy .................
136 136 136 137 139 140 146 148 148 148 149 150 150 151 153 154 157
Accelerated Innovation ................................................ 163

6.1 Integration Testing ......................................................... 6.1.1 Test Strategy ...................................................... 6.1.2 Test Project Preparation ..................................... 6.1.3 Test Scope Identification .................................... 6.1.4 Business Process Change Analyzer and EHP Business Functions ...................................... 6.1.5 Test Planning and Test-System Preparation ........ 6.1.6 Test Execution ................................................... 6.1.7 Final Activities and Deployment of Changes in Production Systems ........................................ Technical Integration Validation ..................................... 6.2.1 Method ............................................................. 6.2.2 Assessment ........................................................ 6.2.3 Technical Analysis .............................................. 6.2.4 Optimization ...................................................... 163 165 166 167 168 170 171 173 173 173 175 175 177
6.2
Contents
6.2.5 6.2.6 6.3 6.4
Verification ........................................................ Case Study: Added Value from Integration Validation .......................................................... Services Available from SAP Active Global Support ......... Case Study ...................................................................... 6.4.1 Step 1: Identify the Situation Prior to Integration Testing ............................................. 6.4.2 Step 2: Understand the Solution Using Minimum Documentation .................................. 6.4.3 Step 3: Integration Test and Detection of Issues ............................................................. 6.4.4 Step 4: Identify Root Causes ............................... 6.4.5 Step 5: Recommendations to Resolve Issues ....... 6.4.6 Step 6: Implement the Recommendations .......... 6.4.7 Step 7: Verification and Validation of Successful Integration .........................................................
178 179 182 183 184 184 189 189 190 194 195
Improving Business Processes ..................................... 197

7.1 7.2 Roles and Objectives of the QM ..................................... Methodology and Tools .................................................. 7.2.1 Determining the Business Process Requirements ..................................................... 7.2.2 Appraisal of the Solution Landscape ................... 7.2.3 Checking the Technical Implementation of Business Processes ............................................. 7.2.4 Recording Process-Related Problems and Possible Optimization Potential .......................... 7.2.5 Analyzing Interfaces ........................................... 7.2.6 Summarizing the Results .................................... 7.2.7 Follow-Up Activities After an SAP Solution Management Assessment ................................... Prerequisites for Business Process Improvements ............ Business Process Monitoring ........................................... Related Services Available from SAP Active Global Support .......................................................................... Success Factors ............................................................... 198 199 201 202 203 204 205 206 206 207 208 209 210
7.3 7.4 7.5 7.6
10
Contents
7.7 7.8
Skills and Training ........................................................... 212 Case Study: Improving the Order-to-Cash Business Process ........................................................................... 213
Protection of the IT Investment ................................... 219

8.1 Extended Maintenance in the Context of SAP Enterprise Support .......................................................................... 8.1.1 Special Rules for the Extended Maintenance for Customers with SAP Enterprise Support ............. 8.1.2 Benefits and Advantages of Extended Maintenance ...................................................... Quality Management ...................................................... Harmonized IT Landscape ............................................... 8.3.1 Keep the Software Landscape Up to Date .......... 8.3.2 Document and Minimize Custom Code .............. 8.3.3 Evaluation of Custom Developments .................. 8.3.4 Keep the Master Release Plan Up to Date .......... Methodology and Tools .................................................. 8.4.1 SAP Solution Manager Maintenance Optimizer .......................................................... 8.4.2 SAP Solution Manager Methodology and Tools Ease Upgrades .......................................... 8.4.3 Solution Documentation Assistant ..................... 8.4.4 Custom-Development Management Cockpit ...... 8.4.5 Upgrade Dependency Analyzer .......................... 8.4.6 SAP Standard for Solution Documentation for Custom Development ........................................ 8.4.7 SAP Standard for Custom Code Management ..... 8.4.8 SAP Standard for Incident Management ............. 8.4.9 SAP Standards for Change Management ............. 8.4.10 Report Issued by SAP Enterprise Support ........... Related Services Available from SAP Active Global Support .......................................................................... 8.5.1 SAP Solution Transition Assessment ................... 8.5.2 Modification Justification Check ......................... 8.5.3 Custom Code Maintainability Check ................... 8.5.4 Accelerated Innovation Enablement ................... 221 223 225 225 229 229 231 232 237 238 239 239 240 241 242 243 244 245 246 246 247 247 248 249 250
8.2 8.3
8.4
8.5
11
Contents
8.5.5
8.6 8.7 8.8
SAP Business Process Performance Optimization ...................................................... 8.5.6 SAP Upgrade Assessment ................................... 8.5.7 SAP Downtime Assessment ................................ 8.5.8 Continuous Quality Checks ................................. Success Factors and Related Standards ............................ Skills and Training ........................................................... Case Study: Planning Requests for Innovation .................
251 251 252 252 253 254 254
Innovating Without Risking Disruptions .................... 257

9.1 9.2 9.3 Service-Oriented Architecture: The Evolutionary Approach ........................................................................ The Maintenance Strategy: Stable Core and Access to Innovations ..................................................................... SAP Enhancement Packages ............................................ 9.3.1 Selective Use of New Functions .......................... 9.3.2 Separation of Maintenance and Further Development ..................................................... 9.3.3 Available Innovations Information Sources ......... Tools for Deploying SAP Enhancement Packages ............. 9.4.1 Maintenance Optimizer for Enhancement Packages ............................................................ 9.4.2 SAP Enhancement Package Installer ................... 9.4.3 Near-Zero Downtime ......................................... Switch Framework and Activation ................................... Case Study: Experiences of SAP's IT Department ............. 258 259 260 262 263 264 265 265 265 267 268 269
9.4
9.5 9.6
10 SAP MaxAttention and SAP Safeguarding .................. 271

10.1 10.2 10.3 10.4 10.5 10.6 The Holistic Approach of SAP MaxAttention ................... The Engagement and Governance Model ........................ A Standardized Approach ............................................... Safeguarding for Implementations, Upgrades, Migrations, and Operations ............................................ Continuous Improvement Through SAP MaxAttention .... Optimizing Architecture and System Landscape .............. 10.6.1 Architecture Services .......................................... 10.6.2 Support Services for System Landscape Optimization ...................................................... 273 276 277 282 283 284 285 286
12
Contents
10.7 10.8
High Security Standards .................................................. 287 Sustainability Aspect ....................................................... 287
11 Mission-Critical Support for Partner Applications and Technologies .......................................................... 289

11.1 Support Processes with Partners ..................................... 11.1.1 The Problem-Solving Process in Detail ............... 11.1.2 Remote Connections to Customer Systems ......... 11.1.3 Note Creation for Partners ................................. 11.1.4 Integration with the SAP Global Support Backbone ........................................................... 11.1.5 Service Level Agreement .................................... Support for Partner Solutions by Software Partners ......... The Value of Partner Integration for SAP Customers ....... Integrating Value Added Resellers into the SAP Ecosystem ............................................................... 11.4.1 Incorporating VARs into the Support Delivery Model .................................................. 11.4.2 Elements of SAP Enterprise Support from the VAR Perspective .......................................... 11.4.3 Establishing an SAP Enterprise SupportCapable Support Organization ........................... 291 292 293 294 294 295 296 299 301 302 304 308
11.2 11.3 11.4
12 Run SAP Programs for SAP Partners ............................ 311

12.1 12.2 12.3 12.4 The Run SAP Methodology ............................................. The Run SAP Implementation Partner Program for SAP Service Partners ....................................................... The SAP Support Partner Program .................................. The SAP Training and Certification Program for Running End-to-End Solutions ........................................ 311 315 318 320
13 Overview of Training and Certification Offerings ........ 323

13.1 13.2 Training Classes .............................................................. 324 Certification .................................................................... 326
13
Contents
Appendices ......................................................................... 327

A Additional Information and Offerings ........................................ A.1 Expert Guided Implementation ....................................... A.1.1 Basic Training Offering ....................................... A.1.2 Target Group and General Requirements ............ A.1.3 Delivery ............................................................. A.2 Continuous Quality Checks ............................................. A.2.1 Continuous Quality Check for SAP Solution Manager ............................................................ A.2.2 Continuous Quality Checks for Implementation ... A.2.3 Continuous Quality Checks for Operations ......... A.2.4 Continuous Quality Checks for Upgrade Projects .............................................................. A.3 Services from SAP Active Global Support ........................ A.3.1 SAP Business Process Management .................... A.3.2 Data Volume Management ................................ A.3.3 SAP EarlyWatch Alert ......................................... A.3.4 Preparation Session for SAP Solution Manager ... A.3.5 SAP GoingLive Check ......................................... A.3.6 Optimization Sessions ........................................ A.3.7 SAP Technical Integration Check ........................ A.3.8 SAP Business Process Performance Optimization ...................................................... A.3.9 SAP Interface Management ................................ A.3.10 SAP Solution Management Assessment .............. A.3.11 Modification Justification Check ......................... A.3.12 Solution Architect Services ................................. A.3.13 Other Services from SAP AGS ............................. A.4 SAP Product Standards ................................................... A.4.1 SAP Product Standard: Business Configuration ... A.4.2 SAP Product Standard: IT Service and Application Management ................................... Bibliography .............................................................................. Editors ...................................................................................... Authors and Editorial Office ...................................................... D.1 Editorial Office ................................................................ D.2 Authors .......................................................................... 329 329 330 331 332 335 335 336 336 338 340 340 340 340 341 341 342 343 344 345 345 346 347 347 348 348 352 359 361 363 363 363
B C D
Index ................................................................................................ 367
14
With its holistic approach to application lifecycle management (ALM), SAP Enterprise Support services enable you to drive innovation faster, improve business continuity, and, at the same time, reduce both risk and total cost of operations.
Introduction
Single source of truth
Management of an SAP solution requires comprehensive and up-to-date knowledge of the solution. SAP calls this knowledge, contained in one system, a single source of truth. It is a structured, comprehensive, and reliable collection of information about the state of all of your current projects and productive SAP-based processes that serves as the foundation of well-grounded and fact-based decisions and actions along the entire application lifecycle. SAP Enterprise Support is a holistic offering that supports your business processes comprehensively, thus protecting your IT investment and sustaining your IT solution throughout the entire application lifecycle. The mission statement ASAP to Run SAP reflects this claim: All of the phases of the application lifecycle are covered, allowing you to quickly implement and deploy business processes into productive use, to support their long-term operation, and to flexibly adapt and continuously optimize them from the implementation methodology to the end-to-end solution operations. In this context, SAP Enterprise Support covers not only SAP applications and technology but also the complete platform, including complementary partner software and customer-specific solutions. By combining the components outlined in Figure 1.1, SAP Enterprise Support facilitates managing highly integrated IT solutions and value networks with an end-to-end quality-assurance process.
ASAP to Run SAP
17
Introduction
SAP Enterprise Support Manages innovation and integration in SAP solution landscapes Value Proposition: Innovation and Protection of Investment Delivered via: Run SAP Methodology Enabled by: End-to-End Solution Operations
Delivered via: Mission-Critical Support
Delivered via: SAP Global Support Backbone
In Collaboration with SAP Ecosystem
Holistic service solution for todays business world with SOA and value networks Support for complete customer landscape Realization via Run SAP methodology
Figure 1.1 SAP Enterprise Support
1.1
Value proposition
What SAP Enterprise Support Can Do for You
SAP Enterprise Support enables accelerated innovation by making continuous improvements and masking complexity. Emphasis is placed on protecting investments. With this offering, SAP aims to support you in reducing your total cost of ownership (TCO) and risks in relation to the operation of SAP-centric solutions. The fact that SAP Enterprise Support can reduce TCO has clearly been shown by the results of the SAP User Group Executive Network (SUGEN) Key Performance Indicator (KPI) program, which was conducted in 2009 and continues in 2010, in the framework of the SAP Enterprise Support advisory customer program. Details on the underlying measurement platform are described in Chapter 3, Introducing the Measurement Platform. The holistic value of SAP Enterprise Support is not a theory or a marketing campaign; it is a reality that can easily be verified by the customer proof points that have been collected by SAP Active Global Support (SAP AGS) in the Customer Quotes Program. The quotes highlight the quantifi-
18
What SAP Enterprise Support Can Do for You
1.1
able value created by SAP support engagements. SAP customers have submitted more than 1,000 quotes for external publication on the SAP Service Marketplace to share with their peers. These quotes, describing the value of SAP Enterprise Support during all phases of the application lifecycle, can be found at http://service.sap.com/customerquotes. These quotes clearly show the confidence and trust inspired by SAP Enterprise Support in SAPs customer base. SAP Enterprise Support achieves these objectives by applying SAP standards for solution operations to tasks such as monitoring business processes, managing custom developments, ensuring remote supportability, and using sophisticated diagnostic functions (see Section 1.2, SAP Standards for Solution Operations). Each of the standards provides best practices for individual tasks, recommendations for using the various capabilities and processes in SAP Solution Manager, and information on training courses and services that help you implement the standards to unlock SAP Enterprise Supports full potential. Implementing these standardized processes in the context of SAP Enterprise Support is leveraged by Run SAP, which is the implementation methodology for end-to-end solution operations. The Run SAP methodology (see Section 12.1, The Run SAP Methodology) contains standards for end-to-end solution operations based on SAP Solution Manager. These standards cover the demands of both business process experts and IT specialists. The methodology was developed jointly by SAP Consulting and SAP Active Global Support. Another component for implementing SAP Enterprise Support handles the task of supporting mission-critical processes. This offering provides continuous quality checks (CQCs), explicit service-level agreements (SLAs), clearly defined contact persons (support advisory center), and root cause analyses including custom development on a 24/7 basis. The SAP Enterprise Support report is also a valuable instrument for planning future investments because it gives a clear overview on achievements and areas with improvement potential. The task of supporting mission-critical processes requires among other things rapid support, remote diagnostics, advice, and knowledge transfer from experienced SAP experts as well as services to ensure
End-to-end solution operations
Run SAP
Mission-critical support
19
Introduction
continuous optimization and quality assurance. All of this is organized using the functions for collaboration in SAP Solution Manager.
SAP global support backbone
The SAP global support backbone is made up of SAP Solution Manager, enterprise edition; SAP Service Marketplace; and the SAP service and support backbone infrastructure. It constitutes the technical foundation of SAP Enterprise Support. The 24-hour availability of SAP partners that are integrated into the SAP global support backbone enables you to obtain fast solutions from SAP or its partners for all problem messages through a single point of contact.
1.2
Definition of processes
SAP Standards for Solution Operations
A key prerequisite for a single source of truth is the clear definition of processes, responsibilities, service-level agreements (SLAs), and key performance indicators (KPIs) to measure the fulfillment of service levels. SAP has defined standards and best practices that help customers set up and run end-to-end solution operations for their SAP-centric solutions. These cover not only applications from SAP or resold by SAP (vendorbranded reselling products, VBRs) but also applications from independent software vendors (ISVs), original equipment manufacturers (OEMs), and custom-code applications integrated into customers solution landscapes. The SAP standards complement commonly agreed upon standards such as the IT Infrastructure Library (ITIL). You can reproduce in detail how the processes for lifecycle management can be integrated into your SAP solution. The SAP standards contain the following components:
Incident management The process of incident resolution. Exception handling and business process and interface monitoring How to define a model and procedures to manage exceptions and error situations during daily business operations. It also defines the monitoring and supervision of mission-critical business processes. Data integrity and transactional consistency Helps avoid data inconsistencies in end-to-end solution landscapes
20
SAP Standards for Solution Operations
1.2
and safeguards data synchronization across applications in distributed system landscapes.
Change management Enables efficient and timely implementation of changes with minimal risk. Upgrade Guides customers and technology partners through upgrade projects. Root cause analysis Defines how to perform end-to-end root cause analysis across different support levels and different technologies. Custom code management Details how to effectively manage customer-specific development and functional enhancements. Solution documentation and solution documentation for custom development Defines the required level of documentation and the reporting capabilities needed for customer solutions. Security Provides best practices for the secure operation of SAP-centric solutions. Remote supportability Contains five basic requirements that have to be met to optimize the supportability of customer solutions. Data volume management Describes how to manage data growth. Job scheduling management Explains how to manage the planning, scheduling, and monitoring of background jobs. System administration Describes how to administer SAP technology to run a customer solution efficiently. System monitoring Covers monitoring and reporting of the technical status of IT solutions.
21
Introduction
Test management Explains methods for test management, as well as approaches for functional, scenario-specific-, integrative-, and technical testing of SAP-centric solutions.
Each standard contains best-practice procedures for performing the individual tasks, descriptions of which tools should be used, and information regarding the assignment of tasks to roles, available training offerings, and available services that support the adoption of the standard.
Roles and standards
Although multiple roles may be involved in a standard process, one role acts as the owner of the standard. Table 1.1 shows how the mapping is handled in this book. However, the assignments may vary depending on an individual customers situation.
Owner End user, key user Business process champion Key Standards and Practices Incident management Exception handling Data integrity Application management Root cause analysis Remote supportability Business process operations Business process and interface monitoring Data volume management Job scheduling management Transactional consistency Technical operations System administration System monitoring
Table 1.1 Matrix of Owners Mapped to Key Standards
Customer Center of Expertise
To mature your IT, migration from the traditional SAP Customer Competence Center (SAP CCC) to the new Customer Center of Expertise (Customer COE) is required, along with establishing four quality managers that can drive improvement in the following areas:
22
Creating the Foundation for a Single Source of Truth
1.3
Safeguarding integration validation Business continuity Business process improvement Investment protection
Information about the new Customer COE model, as well as detailed documentation of the four quality managers, is available in Chapter 4, Customer Center of Expertise.
1.3
Application lifecycle management (ALM) should lead to a radical reduction of TCI (total cost of implementation), TCO (total cost of ownership), and risk for your IT organization. The key elements of lifecycle management are as follows:
The ASAP methodology (for implementation) and the Run SAP methodology (for operations) The concept of a single source of truth as implemented in SAP Solution Manager The organizational aspects of Customer COE and the critical quality management roles The SAP Enterprise Support services portfolio
SAP Solution Manager, enterprise edition, under SAP Enterprise Support
The SAP Solution Manager, enterprise edition, under SAP Enterprise Support, is available to customers with an SAP Enterprise Support contract1. With SAP Enterprise Support, you can use the SAP Solution Manager for the complete customer solution, which includes SAP software and all horizontal and vertical IT assets and software components that
1 The functions and processes of SAP Solution Manager described in this book always refer to the SAP Solution Manager, enterprise edition, under SAP Enterprise Support, unless explicitly stated otherwise (SAP Solution Manager, enterprise edition, under SAP Standard Support). Customers who have a Product Support for Large Enterprises (PSLE) contract can also use the SAP Solution Manager, enterprise edition, under SAP Enterprise Support.
23
Introduction
are required to complete the customers business processes as documented in the solution documentation in SAP Solution Manager.
An example: Application Incident Management
This important extension of the usage rights of SAP Solution Manager within SAP Enterprise Support can be illustrated by a simple example. A company has a productive business process, which is documented in the solution documentation in SAP Solution Manager, enterprise edition. Within this process, a printer needs to print out a receipt or a paycheck. If the printer does not work properly, the business process cannot be completed. A user can create an incident for this printer, regardless of whether the root cause of the incident is an empty toner or cartridge, a hardware error, an incorrect printer configuration in the SAP system, or a network error. This incident can be processed end to end using SAP Solution Manager application incident management. This emphasizes the holistic understanding of SAP Enterprise Support for the customers business processes: Any incident in the customer solution can be raised, analyzed, processed, and solved completely. SAP Standard Support continues to allow customers to adopt SAP technologies and innovation, technology updates, and legal changes, and it provides the platform for reactive support capabilities and proactive remote services, for example, SAP GoingLive Check and SAP EarlyWatch Check. SAP Solution Manager, enterprise edition, under SAP Standard Support, provides capabilities to enable the value realization of SAP Standard Support. In a nutshell, this means the following:
SAP Solution Manager, enterprise edition, under SAP Standard Support
SAP Solution Manager, enterprise edition, under SAP Standard Support, enables the adoption of SAP innovation supporting the installation, maintenance, and upgrade within SAP Solution Manager. The platform supports the adoption of SAP technologies with maintenance management for corrective software updates (SAP support packages, SAP enhancement packages, and SAP legal change packages). Reactive support offerings such as the service desk for SAP software components, SAP NetWeaver-based System Monitoring (e.g., CCMS), and root cause analysis tools for SAP technology continue to be available. The proactive remote services SAP EarlyWatch Check and SAP GoingLive Check are also part of SAP Standard Support.
24
1.3
Customers with an SAP Standard Support engagement may use SAP Solution Manager, enterprise edition, only for SAP software, that is, not for the previously mentioned vertical and horizontal IT assets and software components. In SAP Standard Support, the usage rights of SAP Solution Manager are restricted to maintenance tasks as well as the installation, upgrade, and break-fix services of SAP applications and technologies, including all tools for remote root cause analysis. The intent of this book is to explain SAP Enterprise Support from a customers point of view rather than from the SAP perspective. Rather than a functional explanation of the individual components of SAP Enterprise Support, this book tries to describe how the support offering can actually be used to enable ALM in your enterprise, allowing you to leave the limitations of SAP Standard Support far behind you. Therefore, Chapters 3 to 13 presume an SAP Enterprise Support engagement without going into the delta between SAP Standard Support and SAP Enterprise Support in detail. If you are interested in functional scope descriptions, you can visit the SAP Enterprise Support home page at http://service.sap.com/enterprisesupport. By working through this book, you can get started with ALM and explore the value and scope of establishing a single source of truth for SAP solutions within your company (see Figure 1.2). The step that logically follows is defining a roadmap for a Run SAP implementation. In this step, you should identify your implementation and operations pain points, and map them to procedures and tools suggested by the Run SAP roadmap. This can help you mature your IT. A clear business case with expectations for return on investment should be developed so that you can measure the economic results of your IT maturity improvement. This assessment may, for example, uncover that the current change request management is already optimal in your organization, but using incident management in SAP Solution Manager, enterprise edition, could provide significant value. Such an assessment through the Run SAP methodology is provided by the SAP Consulting organization or by certified SAP partners (see Chapter 12, Run SAP Programs for SAP Partners). Certain aspects of the Run SAP roadmap are
Functional Limitations of SAP Solution Manager under SAP Standard Support
Definition of a roadmap
25
Introduction
mandatory for collaboration with SAP Consulting and SAP partners. They are explained later in Section 5.2, The Necessity of Business Continuity, in Chapter 5, and in Chapter 12.
Establish the Foundation for SAP Application Lifecycle Management

Explore the value and scope of establishing a single source of truth for SAP solutions
Define a roadmap for Run SAP implementation

Identify pain points Investigate ROI for improving IT maturity
Optimize IT processes
Assign quality managers
Implement SAP Solution Manager, enterprise edition

Assistant for basic configuration of SAP Solution Manager
Empower IT organization
Run SAP Customer COE E2E Solution Operations SAP Solution Manager
Figure 1.2 Steps to Take After Reading This Book SAP Solution Manager, enterprise edition
SAP Solution Manager, enterprise edition, is the foundation of holistic ALM. Each SAP Solution Manager implementation requires a technical foundation (see Figure 1.3). To implement this foundation, you plan your SAP Solution Manager implementation, install or extend it, and perform the basic configuration of SAP Solution Manager, which comprises connecting your system landscape to SAP Solution Manager. When this foundation is in place, you can already benefit from end-toend root cause analysis for efficient troubleshooting across technology
26
1.3
stacks, maintenance optimization; and SAP EarlyWatch Alert services, as well as collaboration with SAP Services, for example, in incident management. Also, the technical prerequisites for CQCs and mission-critical support with SLAs are available after the basic configuration. Scenarios such as system administration or system monitoring can be added to the foundation with a minimum of additional configuration.
Establishing the Foundation for SAP Application Lifecycle Management

Plan
SAP Soluon Manager Master Guide
Install, Upgrade, Extend

Installaon Guide
Basic Conguraon
Work Center SAP Solution Manager Administration
Connect systems
Work Center SAP Solution Manager Administration
E2E Solution Operations for the Entire Lifecycle Projects Solutions Systems
Document Business Processes

Supported by Solution Documentation Assistant
Change Control Management

Quality Gate Management Change Request Management Synchronized Deploymentof Updates
Business Process Operations

Business Process Monitoring Job Management Data Consistency Cockpit Data Volume Management
Technical Operations
System Monitoring System Administration IT-Reporting
Application Incident Management
Figure 1.3 SAP Solution Manager Implementation Overview
In addition, you can document your business processes in SAP Solution Manager. Ideally this happens as part of an implementation project, but you can also document your existing processes with the help of the solution documentation assistant. After you have documented your business processes in SAP Solution Manager, you can carry out test management in SAP Solution Manager, for example, by using the new business pro-
27
Introduction
cess change analyzer (BPCA), which can calculate test recommendations based on planned transports to production. Finally, you can define your automated business process operations based on the business-process documentation in SAP Solution Manager.
Value of solution documentation
Depending on the kind of documentation you create in SAP Solution Manager, you can benefit from a wide range of use cases for the implementation, operation, and continuous optimization of your software. Figure 1.4 shows the three fundamental types of documentation and the functions they enable.
SAP Solution Manager Key Capabilities and Scenarios SAP Solution Manager Scenarios and functions can be configured and implemented based on customer-specific priorities and roadmaps. Individual services and guided expert session for desired configuration are available.
Four steps to fully exploit the value of SAP Solution Manager, enterprise edition To achieve IT transparency with a single source of truth To get access to specific SAP Enterprise Support and SAP Solution Manager capabilities
Accelerated Innovation Enablement for SAP Enterprise Support Upgrade ASAP Additional Template Custom Code Management CQCs* Maintainability Check Quality Gate Business Process Management Test Content Monitoring System Monitoring Configuration Content 4 SAP Enterprise Technical SLA & IT Reporting Support SLA Modification 3 Service Desk Change Request Documentation Management Business Process Root Cause Documentation Analysis Run SAP Selected CQCs* for Technology Modification Justification Check Solution Documentation Assistant 1 Install and Connect to SAP Technical Landscape Documentation 2 System Administration Custom Development Mgt. Cockpit
* Continuous Quality Checks
Root Cause Analysis for Custom Code
Test Workbench & Regression Testing
Run SAP for Industries
Figure 1.4 Key Capabilities and Prerequisites for SAP Solution Manager, Enterprise Edition Technical landscape documentation
The technical landscape documentation (Figure 1.4, item 2) is already covered by the basic configuration of SAP Solution Manager at its minimum required level (Figure 1.4, item 1). The documentation comprises the following:
28
1.3
The availability of system data of all productive systems in the system landscape directory (SLD) The availability of one or more solution landscapes that contain the productive systems as logical components
During the basic configuration, you also implement the communication capabilities between the managed systems and SAP Solution Manager, as well as the connection between SAP Solution Manager and the central SAP support system. After these communication channels are established, you can activate the automated data exchange of the most important technical data (system data and SAP EarlyWatch Alert). If you are using non-ABAP programs, you also configure the end-to-end root cause analysis because these functions are indispensable for error analysis. Additional information on the basic configuration of SAP Solution Manager and the functions it enables are detailed in Section 2.2.2, Installation and Configuration of SAP Solution Manager. To use incident management for the entire enterprise and thus support your IT team, additional configuration is required to bring your service desk processes and organization into SAP Solution Manager. Basic incident management for SAP software, however, requires only the basic configuration. Incidents (service desk messages) can be sent to SAP AGS after the basic configuration has been completed. If you document your core business processes (Figure 1.4, item 3) in a business blueprint, you can use this information not only when support is needed but also throughout the entire software lifecycle. This increases the value of internal communication because there is always a relation to core business processes; that is, the relevance of a requirement or problem is always visible. You can reuse the documentation of business processes with the following SAP Solution Manager processes, for example:

Business process documentation
Test management Business process monitoring and interface monitoring Job scheduling management Upgrade and maintenance projects Issue and top issue management
29
Introduction
The minimum requirements for the documentation of core business processes are a complete list of all process steps, the assignment of individual process steps to the systems on which they are executed, a list of the transactions (or other entry points as URLs or background jobs) that are called via actions, and the interfaces used. You can document additional information about business processes in SAP Solution Manager, but this is not a prerequisite for SAP Enterprise Support. Change management is less dependent on the business-process documentation than on the projects and system landscape defined in SAP Solution Manager (maintenance projects). You can benefit from clearly documented quality gates (q-gates) with standard check content for each q-gate. In addition, synchronized deployment of updates across transport tracks can be automated with change management.
Modification documentation
Documentation of SAP software modifications (item 4 in Figure 1.4) is particularly important: 1. Modifications are not subject to SAP CQCs. 2. They can be lost in an upgrade when implemented improperly. 3. After some time, actual usage is often no longer checked, and modifications cause unnecessary maintenance cost and performance losses as dead coding. The documentation comprises a short description of the development and its related development objects, for example, programs in the customer name space. Based on this documentation, you can easily control your coding using the custom development management cockpit (CDMC) in SAP Solution Manager. You can initiate the deletion of obsolete files, folders, reports, and jobs on a regular basis. You also can use the SAP services offered with SAP Enterprise Support (modification justification check and custom code maintainability check) and the end-toend root cause analysis for custom code.
1.4
About This Book
This book describes the steps required to establish a single source of truth and continuously keep it up to date. It defines the standard for
30
About This Book
1.4
achieving the knowledge base for a solution centered on SAP software throughout the entire lifecycle. The book describes the vital principles and big picture of application lifecycle management and explains how you can benefit from SAPs experience to do the following:

Reduce risk and cost. Ensure business continuity. Accelerate improvements and innovation.
Supporting an SAP solution for the entire lifecycle based on sound and up-to-date knowledge is the starting point for the optimal use of SAP Enterprise Support services. Take the example of a complex problem analysis. A problem can affect various stakeholders: the IT department, business units, possibly outsourcing or out-tasking partners, application and technology partners, as well as SAP. To ensure that all stakeholders can cooperate in an efficient problem-solving process and thus are able to quickly resolve disruptions, they all need to be able to access certain information, such as the customers core business processes, the required applications, the latest changes made, and any incidents or problems that were logged and solved in the past. Establishing a single source of truth is not only imperative for effective management of an SAP solution by in-house experts but also for leveraging the SAP expert network and the collective knowledge and experience these experts have gathered during more than 35 years of supporting SAPs customers. With SAP Enterprise Support, SAP provides a management application that allows customers to store, retrieve, manage, and analyze all information that makes up each customers single source of truth. SAP Solution Manager, enterprise edition, provides the knowledge repository to maintain the single source of truth, as well as the functionality to maintain, update, and use this data in all operations during the solution lifecycle. This book provides an outline and an overview of the standard procedures customers should carry out during the complete solution lifecycle to reap the benefits of SAP Enterprise Support. The main focus is on activities that are required to configure and operate business-driven changes, that is, the implementation or improvement of business proSAP Solution Manager, enterprise edition
Standardized approach
31
Introduction
cesses supported by an SAP solution. Its purpose is to establish a business configuration and operation standard that defines how to best proceed from the conception of a business process to its consumption, including its improvement. This standard explicitly includes IT-related aspects, such as the automation of processes and the documentation, testing, and technical monitoring of interfaces for mission-critical business processes. In Chapter 2, Establishing SAP Solution Manager as a Consolidated Data Source in Your Enterprise, we introduce the essential concepts of application lifecycle management (ALM) the definition of the lifecycle itself and an explanation of the basic SAP Solution Manager models that help you realize holistic and standardized ALM. In addition, we describe the integrated quality management process that covers the entire lifecycle. We also cover how to create the prerequisites for ALM, outline the methodologies available, and shed light on how to install and configure SAP Solution Manager.
Chapter 3, Introducing the Measurement Platform, introduces the measurement platform for ALM, originally defined and successfully executed for the SAP User Group Executive Network (SUGEN) Key Performance Indicator (KPI) program. The ultimate goal of the measurement platform, which is implemented on SAP Solution Manager, is to provide complete, reliable, and comparable benchmark data. The KPIs and metrics must be measurable and represent a particular TCO driver properly, respond to SAP Enterprise Support offering (tools, services), reflect the status regarding the SAP Enterprise Support report, and manifest the achieved benefits. It is important to emphasize that the entire value of SAP Enterprise Support is not measured directly by these KPIs. The underlying concept of ALM goes far beyond the set of KPIs measured.
The Customer Center of Expertise (Customer COE), SAPs new model for the organization and scope of a customers support organization, is the topic of Chapter 4, Customer Center of Expertise. Whereas a classical SAP CCC focused mainly on reactive support tasks and was deeply embedded in a customers IT organization, a Customer COE is focused on actively driving accelerated innovation for the customers business units; that is, the Customer COE focuses on upgrades, the implementa-
32
About This Book
1.4
tion of new software, and the use of SAP enhancement packages (EHPs). This presupposes that a single source of truth has been established in the customers SAP Solution Manager. Based on the organizational model outlined in Chapter 4, Chapter 5, Preserving Business Continuity, describes the role of the quality manager for business continuity. It explains the methods and tools available with SAP Enterprise Support in detail, for example, data volume management, root cause analysis, and the Run SAP methodology.
Chapter 6, Accelerated Innovation, is dedicated to the tasks of the quality manager for integration validation. Here, the focus is placed on how test management and integration validation can contribute to faster innovation in highly integrated IT solutions.
In Chapter 7, Improving Business Processes, we describe how you can explore the potential for optimization. By leveraging the role of the quality manager for business process improvement and using tools such as business-process monitoring, you can unlock this potential. The protection of your IT investment is the main topic of Chapter 8, Protection of the IT Investment, with particular attention being paid to managing custom code. The tasks and goals of the quality manager for protecting the IT investment are described step by step using a real-life example, which covers items such as avoiding or reducing custom development, and creating an IT master plan.
Chapter 9, Innovating without Risking Disruptions, explains how you can avoid downtime using the SAP release strategy, and how you can drive innovation without upgrades using SAP EHPs. Tools such as the maintenance optimizer and the SAP EHP installer, as well as optimized upgrade procedures, are introduced.
Under the umbrella of SAP Enterprise Support, SAP offers support models such as SAP MaxAttention and SAP Safeguarding, which are explained in context in Chapter 10, SAP MaxAttention and SAP Safeguarding. SAP Enterprise Support incorporates SAP partner offerings. Chapter 11, Mission-Critical Support for Partner Applications and Technologies, explains central concepts for collaboration in the SAP global support
33
Introduction
backbone and how mission-critical support for partner applications and technologies is enabled. The chapter also details how value-added resellers are integrated into the SAP ecosystem.
Chapter 12, Run SAP Programs for SAP Partners, describes the Run SAP implementation and operations initiatives for partners. These initiatives provide knowledge transfer to partners and enable them through comprehensive training and certifications to deliver premium strategic services to their customers.
A short overview of the training courses available for SAP Enterprise Support is provided in Chapter 13, Overview of Training and Certification Offerings. The appendix provides additional information, for example, about the expert-guided implementation for SAP Solution Manager, or a detailed description of the CQCs offered by SAP AGS. You will also find information on SAP internal standards and learn how you can profit from these standards in SAP Enterprise Support.
34
SAP Enterprise Support provides a broad portfolio of services with which you can run your IT solutions end to end, at minimum cost. This concept is based on a unique central database (single source of truth) that is accepted by all stakeholders.
Establishing SAP Solution Manager as a Consolidated Data Source in Your Enterprise
To create a single source of truth that enables all stakeholders to cooperate efficiently and effectively throughout all phases of the application lifecycle, you need to be familiar with the basic concepts of application lifecycle management (ALM). Establishing these concepts in your enterprise is a crucial step toward effective and efficient ALM, which, in turn, enables you to reap the full benefit from SAP Enterprise Support.
2.1
Basic Concepts
The SAP Solution Manager is the standard platform for ALM. It is one of the central components of SAP Enterprise Support. The book SAP Solution Manager Enterprise Edition1, also published by SAP PRESS, contains a detailed description of the SAP solution for application management and administration. The most important concepts for creating a single source of truth are presented in the following sections.
1 Marc O. Schfer, and Matthias Melich, SAP Solution Manager Enterprise Edition, 2nd ed. (Boston: SAP PRESS, 2009).
35
2.1.1
Application Management Lifecycle
Application management can best be described as being based on a lifecycle. This book is based on the application management lifecycle described in version 3 of the IT Infrastructure Library (ITIL). Application management is a comprehensive support approach in the application environment that spans the entire lifecycle of IT solutions, from concept to phase-out. The lifecycle has six phases (see Figure 2.1), as follows:
Phases
Requirements Collect requirements for new applications or for adapting existing applications. Design Convert requirements into detailed specifications. Build and test Configure the application, and create an operating model according to specifications. Deploy Transfer changes and the operating model into the existing live IT landscape. Operate Provide IT services for ongoing operations. Optimize Analyze service-level fulfillment, and perform any activities required to improve results.
This book describes the key tasks during this lifecycle. Sections 2.3, Business Configuration, and 2.4, Business Continuity,2 explain how to perform these tasks.
2 In the literature, the term business continuity is often used for disaster recovery. In that context, business continuity describes the continued operation in outsourced computing centers after a complete destruction of the primary computing center due to natural disasters, attacks, and so on. We use the term in a slightly different manner based on SAPs experience that system downtime results more frequently from defective transports, data inconsistencies, or system administration mistakes than from natural disasters. It is the task of the quality manager for business continuity to assess and avoid these risks, and to ensure continued business operations.
36
Basic Concepts
2.1
Requirements Opmize Applicaon Management Operate Build & Test Deploy

Figure 2.1 ITIL Application Management Lifecycle
Design
2.1.2
Projects in SAP Solution Manager
A project in SAP Solution Manager describes the grouping and organization of business, technical, and organizational tasks during the implementation of SAP software in an enterprise. In an implementation project, the project team performs tasks that are structured according to a common project plan and roadmap. In SAP Solution Manager, projects follow the ASAP methodology, starting with project preparation and completing the project in the go-live phase. From the lifecycle perspective, a project covers the application management phases from requirements gathering through building and testing. All information you have accumulated during the project is cut over into a solution at the end of the deploy phase, including knowledge transfer to end users via e-learning, implementation of the support organization, and so on. Using SAP Solution Manager for projects has many advantages, including the following:

A structured, systematic procedure throughout the project. Strict adherence to a process-oriented approach that is separate from individual applications and components. This provides a more comprehensive view of process flows in heterogeneous system landscapes.
Benefits of SAP Solution Manager project administration
37
Centralized metadata repository for solutions, including documentation, test cases, and configuration information. No information loss between project phases. Once created, content is reused throughout the software lifecycle, preventing integration gaps.
A Solution Manager project covers the business configuration in the application management lifecycle, that is, all phases from the requirements phase through the preparation of production processing (deploy phase).
2.1.3
Information about systems, software components, and business processes
Solutions in SAP Solution Manager
After you have successfully completed a project, the challenges during operations are preserving the knowledge gained during the project and keeping it up to date. The SAP Solution Manager solution concept helps you do so. During the deployment into productive use, all of the information accumulated in your project is transferred into a solution. An SAP Solution Manager solution contains all of the information about systems, software components, and business processes (scenarios) needed in the operation and continuous optimization of your IT solution. This ensures that all information remains accessible and can be consolidated when a project is over. A solution covers a longer period of time than a project, providing all of the information needed for operations and the preparation of optimization projects. The integrity of your solution is the key to successful ALM. The solution is also crucial as an information source for ALM in two dimensions:
Horizontally, any software component required to complete the customers business processes as documented in the solution documentation can be managed using the ALM processes. Vertically, every layer of the solution can also use these processes, including database, and IT assets.
38
Basic Concepts
2.1
You manage solutions in the solution directory, which offers the following advantages:
The Solution Directory
All assignments are in the SAP Solution Manager project
Scenario and business process structures are transferred to the solution. Configuration object assignments are readily available. Test cases in the structure can be used to test changes that have been made. E-learning materials from projects in the solution can be reused. The solution has the same system landscape as the project; therefore, you can reuse the structure when you upgrade.
Standard presentation of solution components such as servers, systems, business processes, and scenarios

The display of graphics and diagrams is enhanced. You can export graphics to Microsoft Office or HTML.
The solution completely covers business continuity in the application management lifecycle in SAP Solution Manager, that is, from deployment to optimization. Fulfilling the minimum recommendations for SAP Enterprise Support means that you have documented your core business processes. Usually, there are very few according to SAPs experience: one to five core business processes within a company. Core business processes are the most important processes, which, when disrupted, lead to a severe impact on the companys business. Critical business processes are new or technically challenging business processes, for example, processes with custom development or non-SAP components needing high awareness or monitoring. Documentation in SAP Solution Manager is not designed to model every process step variant and detail. It is intended to provide an understandable structure, with information relevant to other teams and other application lifecycle capabilities.
What are core and critical business processes?
39
Example
Manufacturing Industries Example: Material Supply of the Production The material supply process is a critical core process because the company loses money if material outages occur:
If this process is disrupted, and material outages arise, the production of finished parts will be impossible. If this happens, the company has to change production plans, causing higher total production cost. Customer orders will not be delivered in time, so that customer satisfaction decreases.
2.1.4
Processes for Application Lifecycle Management
SAP provides 10 processes to support both projects and solutions (business configuration and business continuity) throughout the lifecycle (see Figure 2.2), as follows:
Business Continuity
Solution Documentation
Requirements
Upgrade Management Maintenance Management

Optimize
Application Management
Design
Solution Implementation
Operate
Technical Operations Business Process Operations Application Incident Management

Deploy
Build & Test
Template Management Test Management
Change Control Management
Business Configuration
Figure 2.2 Application Lifecycle Management (ALM) Processes
40
Basic Concepts
2.1
Solution Documentation Consisting of technical landscape documentation and business process documentation, solution documentation is the basis for all other SAP Solution Manager capabilities. It describes a customers SAP and non-SAP technical components, core business processes, and interfaces. The documentation also includes custom code and modification documentation, as well as links to supporting technical objects, such as transactions and programs.
The correct use of implementation projects automatically leads to sufficient solution documentation in the operations and optimization phase. If you start with the documentation in the operations phase, you should re-document your core business processes in SAP Solution Manager. In relation to a complete implementation project, only a subset of information is then needed. Solution documentation can be continuously enriched along the ALM life-cycle phases (see Figure 2.3):
Focus Re-Documentation
Requirements
Focus Initial Documentation
Upgrades verify documentation
Opmize Applicaon Management Operate
Design
Template Management create global documentation Implementation create or locally adjust documentation Configuration extend documentation
Operations re-document
Build & Test Deploy
Figure 2.3 The Solution Documentation Lifecycle
Design: Create global business process templates and specifications for later rollout of regional implementation projects. Design/Build: Create or locally adjust the business process structure during your regional implementation project.
41
Build/Test: Extend business process documentation during solution configuration with custom code documentation, configuration information, and test cases. Operate: Re-document or adjust your business process documentation during operations with system information, and adjust process documentation after go-live. Optimize: Verify your business process documentation before upgrades; for example, delete obsolete information and not used custom code.
Solution documentation is the basis for the whole application management lifecycle. It ensures that customers achieve transparency of their IT solution landscape and business processes. It also fully exploits the potential of SAP Enterprise Support.
Solution Implementation Involves the identification, adaptation, and implementation of new and enhanced future-oriented business and technical scenarios. It is designed to decouple technical installation from business innovation and uses SAP Solution Manager to implement innovation within the system landscape. Template Management Allows customers with multi-site SAP installations to efficiently manage their business processes across geographical distances, such as part of a global rollout approach: from initial template definition to template implementation and template optimization. Test Management Allows you to define the integration testing requirements and test scope based on a change impact analysis, develop automatic and manual test cases, manage testers, and report on the test progress and test results. Change Control Management Provides workflow-based management of business-driven and technology-driven solution improvement changes with integrated project management, quality management, and synchronized deployment
42
Basic Concepts
2.1
capabilities, to best manage the risks associated with the implementation of the solution, ensuring technical and functional robustness.
Technical Operations Represents all capabilities for monitoring, alerting, analyzing, and administering SAP solutions, and allows customers to reduce TCO by using predefined content and centralized tools for all aspects of SAP Solution Manager operations. It provides end-to-end reporting functionality either out of the box, or individually created by customers. Business Process Operations Comprises the most important application-related operations topics necessary to ensure the smooth and reliable flow of the core business processes to meet a companys business requirements. Application Incident Management Enables centralized and common incident and issue message processing on multiple organization levels and offers a communication channel with all relevant stakeholders of an incident. The process includes business users, SAP experts at the customer site, SAP Active Global Support (SAP AGS), and partner support employees. It is integrated in all ALM processes of SAP Solution Manager and in any SAP Business suite solution, can be connected to a non-SAP help-desk application, and includes follow-up activities such as knowledge research, root cause analysis, or change management. Upgrade Management Represents the identification, adaptation, and implementation of new and enhanced business and technical scenarios, and uses SAP Solution Manager to holistically and effectively manage the upgrade project end to end. It allows SAP customers to better understand and manage the major technical risks and challenges within an upgrade project, and to make the upgrade project a non-event for the business. Maintenance Management Covers software correction packages: from discovery and retrieval to test-scope optimization, possibly including optional automatic deployment into the production environment.
43
2.1.5
Quality-assured change-management process
Quality Gates in SAP Solution Manager
Highly integrated solution landscapes require a controlled and qualityassured change-management process for solutions to be reliable and highly available. Most changes and extensions in the application lifecycle of SAP-centered solutions are motivated by changes in the application layer. Custom developments and customizing changes are managed in projects and transported from the development system via the test system to production systems. These types of changes require a formal quality management process covering all phases of the application management lifecycle (see Figure 2.4) until they are transported into the production landscape.
Quality Gate open
Quality Gate passed
Build
Quality Gate
Test
Quality Gate Document

Quality Manager
Document Upload documentation Q-Gate rating
Tester
Developer
Quality Steering Board
the results
Confirm/ reject Quality Manager recommendation
Operator
SAP Solution Manager Project using Quality Gate Management

Figure 2.4 Quality Gate Management Process Q-Gate
A quality gate (q-gate) is a type of milestone in SAP Solution Manager project management. It controls the import of project data into subsequent systems. Data can be propagated into subsequent systems only if a q-gate has the status passed.
44
Implementing SAP Solution Manager as a Platform for ALM
2.2
All activities in the q-gate management process are supported by for SAP Solution Manager 7.0 EHP 1. In addition to the existing functionality, such as change request management, test management, and incident management, several new functions are available, as follows:
Q-gate management Provides complete transparency of changes and enables formal transitions between phases via q-gates. Synchronized transport management Collects changes and transport requests from all development workbenches and for all SAP-supported development environments (ABAP, Java, Microsoft .NET, and C/C++). Transports from various systems can be synchronized to guarantee availability of all dependent developments and changes in subsequent target system landscapes. Work center change management Lists views and calendar views for all q-gates, changes, and transports.
New test management functions, such as BPCA, are described in Section 6.1, Integration Testing. At all major q-gates (typically at the transition point from one lifecycle phase to another or to sign off critical custom developments or custom configurations), the SAP AGS organization empowers and supports you with feedback and formal sign-off procedures to help ensure that solutions work properly.
Q-gates with integrated feedback from SAP
2.2
Implementing SAP Solution Manager as a Standardized Platform for Application Lifecycle Management
SAP Solution Manager supports planning, setup, implementation, training, and operations throughout the entire application lifecycle. This section outlines how to approach the installation and configuration of SAP Solution Manager. It also describes which tools and methods are embed-
45
ded within the platform to quickly come to concrete results and what functions are available after completing an individual step.
2.2.1
Run SAP roadmap
Planning
The SAP Solution Manager Run SAP roadmap function provides the Run SAP roadmap as reference material. You can read how certain end-toend standards are implemented, and you can access best practices information provided via accelerators in the roadmap. The roadmap in the Run SAP methodology provides content for SAP industry solutions mainly business process operations. You can use filters and selections to restrict the roadmap content. The Run SAP roadmap can be used together with project management functionality to define and manage a Run SAP project to implement or optimize operation processes.
SAP Solution Manager master guide
The SAP Solution Manager master guide supports you in all relevant planning steps for an SAP Solution Manager implementation, such as SAP Solution Manager architecture, sizing, and agent deployment strategy to the managed systems.
2.2.2
Installation and Configuration of SAP Solution Manager
The configuration effort depends heavily on the use of the SAP Solution Manager and the number and type of systems connected to it.
Basic configuration
Through a guided procedure, the basic configuration is now very comfortable and takes only a short time, after which you can already use most of the SAP Solution Manager scenarios, including all functions for SAP Enterprise Support. Three main ways of using SAP Solution Manager are supported depending on the customers situation:

In an implementation and upgrade project To support core business processes in operational processing For the administration, maintenance, and monitoring of your system landscape, and for technical service-level reporting
46
Implementing SAP Solution Manager as a Platform for ALM
2.2
If additional configuration effort is required, it is usually only necessary to select and implement content, not technically configure a function. The effort required can be considerable, particularly for system monitoring and service desk and job management. Organizational arrangements are typically significant in change request management and business process monitoring. The following explains and underscores the significant potential already available to you after the basic configuration of SAP Solution Manager. SAP Solution Manager is installed using a standard procedure that is supported primarily for troubleshooting by the SAP Solution Manager installation guide for the combination of system and database. You can prepare SAP Solution Manager and connect managed systems in the development, quality assurance, and production layers using the basic configuration assistant (Transaction: SOLMAN_SETUP; see Figure 2.5 and Figure 2.6). The assistant considerably simplifies and accelerates both the initial installation and future upgrades of SAP Solution Manager; thus, an average system landscape containing only a few systems can be configured within a few days.
Extended configuration
Figure 2.5 Guided Procedure for the Basic Configuration of SAP Solution Manager
After basic configuration has been completed, and managed systems are connected to SAP Solution Manager, you can create projects and solutions within solutions.
47
Figure 2.6 Guided Procedure for Connecting Managed Systems to SAP Solution Manager Managing connected systems
You can do the following with all connected systems:
Display all connected systems in a standard solution called SAP solution. Create solution documentation with an assistant. Process SAP EarlyWatch Alert weekly (automatically scheduled). Download SAP software with the maintenance optimizer. Perform end-to-end root cause analysis. Collaborate with the SAP Services organization to do the following:

Plan service delivery and engagement. Receive continuous quality checks (CQCs). Create incidents (service desk messages) or issues and send them to SAP AGS. Open a connection for remote support by SAP Services or SAP partners.
Administer systems using preconfigured standard tasks, including reporting. Perform technical service level and IT reporting. Perform real-time system monitoring with automatic alerting. Use self-services, such as data volume optimization.
If you have created a maintenance project, you can manage q-gates along the project lifecycle. You can document the business process and custom code, perform business configuration, manage tests, and, with
48
2.3
additional configuration, transport synchronously across stacks according to the business process structure blueprint in projects. If you have more formal documentation requirements, you can benefit from change request management (again, with additional configuration). You can model business processes and map business process steps and interfaces to the connected systems in projects and solutions. SAP recommends that you document mission-critical core business processes, including custom code, in SAP Solution Manager, to benefit from the following:
Document core business processes
The modification justification check and custom-code maintenance check (see Sections 8.4.6, SAP Standard for Solution Documentation for Custom Development, and 8.4.7, SAP Standard for Custom Code Management) Business process operations (with additional configuration):

Business process and interface monitoring Job request management Data volume management Data consistency cockpit
SAP offers a comprehensive training curriculum and services such as expert guided implementation for SAP Solution Manager, as well as CQCs to help you with these tasks. For further details, see Chapter 13, Overview of Training and Certification Offerings, and Appendix A, Additional Information and Offerings.
2.3
As explained in the previous sections, business configuration covers the application management lifecycle phases: requirements, build and test, and deploy. In the deploy phase, a project is passed to the operations organization. Therefore, this phase is the changeover from project to solution environment in SAP Solution Manager and affects both business configuration and business continuity.
49
2.3.1
Evaluate scenarios
Requirements Phase
During the requirements phase, your primary concern is to evaluate scenarios and their business processes, and check their viability for your project. Planned change requests emerge during the operate and optimize phases, followed by assessment and technical feasibility checks to prepare the subsequent decision-making milestone. In SAP Solution Manager, you can use SAP Business Maps and Engagement tools for knowledge transfer and more detailed process analysis. This content is contained in the business process repository (BPR), a content library that includes content designed specifically for implementation purposes, which you can use in your projects (see Figure 2.7). You can access the BPR via SAP Solution Manager or use its online version at https://implementationcontent.sap.com/bpr.
Figure 2.7 Online Version of the Business Process Repository
50
2.3
In a project, you can benefit directly from SAPs internal business-configuration standard, which provides you with software and content from SAP. This gives you a head start in implementation projects because you do not have to start from scratch. You, therefore, benefit from best practices and end-to-end processes that you can adapt to your own business requirements. In many projects, you need to first analyze which transactions and processes are currently in use so that you can define the project scope. SAP Solution Manager provides a function to automatically analyze systems and business processes: the solution documentation assistant.
Requirements Phase: What SAP Enterprise Support Offers for You Benefit Case: Next Best Practice Included Continuous improvement is at the heart of SAP Enterprise Support in this phase. The ultimate goal is to get the most out of the innovation provided by SAP; the first steps toward this goal are taken here. SAP Enterprise Support explicitly facilitates the adoption from an end-to-end perspective: You can pick the software that covers your requirements and install only the scope that helps you maximize the value of your IT solution.

Solution documentation assistant
Benefits for customers: Increased business satisfaction Benefits for partners: Built-in continuous improvement and standardization increases customer satisfaction
Core Assets Core assets of SAP Enterprise Support for the requirements phase include the following:

SAP Business Maps and Engagement tools BPR and configuration guidelines
SAP Enterprise Support Services
Accelerated innovation enablement: Five days of remote support from solution/technology architects (from solution management) to support the deployment of the latest enhancement package (EHP) and to help you identify what innovation helps you improve your business processes.
51
2.3.2
Design Phase
To deal with potential bottlenecks quickly and efficiently, you need professional, visible project management procedures and a clearly defined project scope. With these in place, you can safeguard your companys investments, deploy resources for specific objectives, set priorities, and ensure that everyone involved in a project communicates clearly.
Project management procedure
The role of SAP Solution Manager during this phase is to provide roadmaps proven procedures for project management and to structure project management activities clearly, using tools such as the project administration functions. SAP Solution Manager helps you draw up a well-defined, comprehensive conceptual design a business blueprint for your project. The purpose of the business blueprint is to outline the current situation as identified during workshops to document the target state for the solution being implemented and the resulting requirements. The conceptual design drawn up by the project team describes how your enterprise plans to map its business processes using both SAP software and non-SAP software. This phase comprises the following steps:

Business blueprint
Refining the original project goals and objectives Finalizing the overall project schedule Implementing organizational and change management Defining and documenting functional standards for custom developments Defining the requirements for the authorization concept, security policy, and end-user training Planning the system environment for operations
In SAP Solution Manager, you can draw up your conceptual design in the business-blueprint transaction (SOLAR01). It provides valuable support, especially for mapping and documenting the processes for implementation. The project structure maps business processes to technical objects (see Figure 2.8).
52
2.3
Figure 2.8 Detail Mapping of a Project Structure in SAP Solution Manager
The decision whether planned changes can be carried over into the build phase is assigned to the members of the q-gate design to build team. During the q-gate meeting, members discuss all relevant aspects, including reasons for the requirements, priorities, risks involved, mission-critical business processes impacted, and budget availability. The decision is documented and signed by decision-makers. SAP Enterprise Support also offers a fit/gap-analysis and a sign-off by SAP for the blueprint in this phase based on the q-gate design to build.
Relevant SAP Solution Operations Work Center in SAP Solution Manager Standard Solution Documentation Solution Documentation for Custom Development Implementation/Upgrade Solution Documentation Assistant
G-gate design to build
53
Design Phase: What SAP Enterprise Support Offers for You Benefit Case: Configuration Content Is Maintained Like Code In this phase, SAP Enterprise Support offers capabilities that lead to less work for business process design, and integration as well as interface design. By the phased implementation approach and the preconfigured content, fewer issues occur and less specifications work is required, which leads to rapid prototyping.

Benefits for customers: Up to 30 % lower design costs Benefits for partners: Less risk of design failure by sign-off by SAP
Core Assets Core assets of SAP Enterprise Support for the design phase include the following:

SAP Business Maps and Engagement tools BPR and configuration guidelines Issue management Best practices (including improvement guides with each EHP) Fit/gap analysis sign-off by SAP (Q-gate design to build)
Accelerated innovation enablement: Five days of remote support from solution/technology architects (from solution management) to support the deployment of the latest EHP
2.3.3
Build and Test Phase
The goals of the build and test phase are to develop the software, test it comprehensively, and release it in preparation for production operation.
Solution Implementation To implement the scenarios and processes you defined in the design phase in the build phase, you must set up the system landscape that will support your scenarios and business processes. You can then adopt the structure used in the business blueprint, which helps you configure your solution around your business processes, and also during subsequent testing activities.
54
2.3
Configuration implementation comprises the following steps:
Continuous monitoring of project targets, especially costs, deadlines, and resources Active implementation of organizational and change management Elaboration of training materials and end-user documentation Creation of end-user roles, and implementation of your authorization and security concept Elaboration and implementation of realization specifications for custom developments
Configuration implementation steps
SAP Solution Manager serves as the central repository for the entire project documentation, which includes the business blueprint, technical specifications, and test cases. Documentation is uploaded to the process structure. An approval process also exists for documentation in SAP Solution Manager. SAP Solution Manager assists you in configuring your systems around your processes. You can navigate directly to the SAP implementation guide (IMG) in the development component systems and set up these systems centrally from within SAP Solution Manager. You can also document configuration settings centrally. All relevant customizing objects are tracked in SAP Solution Manager at the project level and can be accessed directly from SAP Solution Manager using the link to the IMG. SAP Solution Manager supports you in organizing and documenting the results of a range of test activities from unit testing to integration testing with its integrated test tool, the test organizer. SAP Solution Manager also has an authoring environment for creating customer-specific learning maps, where you can prepare and distribute training materials for roles. Changes such as solution extensions with custom development activities, customizing changes, interface changes, or integration of a partner or third-party application are implemented during the build phase. Developers perform unit tests, and the quality-assurance department prepares functional and user-acceptance tests for the next phase. A change-impact analysis should be performed to check whether mission-
Project documentation repository
Test organizer
55
critical processes are affected by the changes. You should also document solution operations.
Q-gate build to test
During the build-to-test q-gate meeting, members decide whether the development and other change activities are mature enough to be transported from the development to the test-system landscape. The decision and reasons are documented and signed by the q-gate members involved. Only after the q-gate has been passed successfully can data be imported into the following systems.
Change Control Management Contemporary software solutions involve multiple development workbenches and create various file types or transport objects. Many business processes also require multiple applications and components. For example, trade promotion management in the consumer products industry requires SAP NetWeaver Portal, SAP ERP, and SAP CRM. Transports from the development workbenches into the development systems with user interface (UI) and business logic changes can be synchronized with standard procedures to guarantee smooth testing in the subsequent testing landscape. Individual transports could cause errors in subsequent systems due to non-synchronized transport of incompatible UI or business logic changes.
Relevant SAP Solution Operations Standard Change Management Work Center in SAP Solution Manager Change Management
Test Management All relevant types of tests are performed during the test phase, as follows:

Regression tests Integration tests Scenario tests
56
2.3
User-acceptance tests Performance tests
During business-logic processing, you should perform tests that proactively check data consistency, response times, and exceptions (see Chapter 5, Preserving Business Continuity). Testers, or automatic test tools, document problems and errors in the incident management process. Root cause analysis can assess complex problems. Problems that need to be fixed require additional activities in the development system, with subsequent transports into the test system landscape. Test coordinators monitor test activities, the status of open high-priority problems, and retesting activities after problems are fixed. At a minimum, test-exit criteria must be in place to verify the following:
Documentation of problems and errors
User-acceptance tests confirm that business departments agree with planned changes. Integration tests verify that transactions with several instances run correctly. Regression tests validate that all core business processes can be executed with correct system behavior and results. Performance tests demonstrate that changed solutions have acceptable response times.
Final activities at the end of this phase include updates to end-user documentation prior to going live. The test management process comprises the following steps:

Create a test plan. Create test packages. Assign test packages to testers. Run tests, and log results. Review results.
Test management process
You can start to generate test plans and test packages from the SAP Solution Manager project structure. Test packages may include manual and
57
automatic test cases. You can use the SAP Solution Manager automatic test tool extended computer aided test tool (eCATT) to automate the test process and create test data for user-acceptance tests. You can also assign test packages to testers and track the progress of your test activities with SAP Solution Manager.
Business process change analyzer
After a planned change has been approved, a risk assessment sheds light on the effects the change will have on critical business processes. This type of assessment allows the test coverage to be determined on a risk basis: Test activities will focus on changes impacting critical business processes. This reduces the potential amount of effort associated with testing and enables test resources to target risk areas more precisely. You can use the business process change analyzer (BPCA) for general changeimpact analysis of software changes on business processes (see Sections 6.1.3, Test Scope Identification, and 6.1.4, Business Process Change Analyzer and EHP Business Functions). During testing, you can manage collaboration between users and the development team by creating internal messages, logging tests, and monitoring test status. At the end of a test cycle, you can also review the results.
Q-gate test to deploy
The most important q-gate takes place at the end of the test phase, when decision makers discuss the maturity of all tested changes. This includes test status reports, achievement of predefined quality goals, and test-exit criteria, which are all used to decide whether a change may be transported into the production system landscape. As with the other q-gates, the final decision must be documented, including the information available at the time.
Relevant SAP Solution Operations Standard Test Management Work Center in SAP Solution Manager Test Management
Integration Validation
Monitor central business processes
You should monitor core business processes such as creating a sales order in single-user mode after the functional quality assurance has
58
2.3
been completed. This identifies problems in performance, data consistency, and technical compliance, before they appear in load tests or in productive operations. An end-to-end trace analysis can anticipate possible performance problems in a multi-user environment. Data-consistency problems can also be avoided by analyzing the commit behavior in an end-to-end trace (SQL behavior). You can also prevent technical exceptions that are not visible in the UI of an application but that can still cause significant problems in production. By closely monitoring the program flow with an end-to-end trace analysis, you can even reduce or eliminate load tests and improve process continuity after changes. Simulating parallel execution in load tests requires a lot of effort for script management and provision of test data. Each reduction of effort for load tests has a significant impact on TCO. If load tests are still necessary, they can be monitored and statistically analyzed with end-to-end workload analysis and end-to-end exception analysis. Instead of logging on to each system, you can analyze load tests from a single point of access, SAP Solution Manager. This procedure to analyze performance, data consistency, and technical compliance systematically after the functional integration test is called integration validation. SAP extends quality management with best practices and with validation of integrated, cross-technology, and cross-component solutions.
Build and Test Phase: What SAP Enterprise Support Offers for You Benefit Case: Configuration Content Is Maintained Like Code The focus of SAP Enterprise Support in this phase is on the reduction of configuration and testing efforts for the customer solution, that is, SAP software as well as horizontal and vertical software and IT assets. The goal is to reduce the cost of labor for configuration and testing as much as possible. This also comprises a reduction of unnecessary modifications resulting in fewer conflicts with SAP support packages and EHPs.

Detailed end-toend trace analysis
Benefits for customers: Up to 30 % lower configuration costs Benefits for partners: Less implementation costs, and support by SAP
59
Core Assets Core assets of SAP Enterprise Support for the build and test phase include the following:
Configuration content and configuration guidelines, user exits, and services (SOA) Test workbench BPCA Test automation support

Modification justification check Modification maintainability check Accelerated innovation enablement: Five days of remote support from solution/technology architects (from solution management) to support the deployment of the latest EHP
2.3.4
Deploy Phase
Final preparation (deploy phase) involves transferring the results from the build and test phase to the live solution. In this phase, you clarify any open go-live issues, and when this phase has been completed, your production business processes are ready to run in your solution. As with the build and test phase, test management in SAP Solution Manager is extremely useful during the deploy phase. In this phase, you use the same resources and tools to conduct and document a wide range of system tests on aspects such as performance, load, and interfaces. This phase is also when you distribute the learning maps created in SAP Solution Manager to end users. Users can use the maps to learn about new functions relevant to their tasks and provide feedback on individual learning units or the learning map as a whole. You can evaluate feedback and use it to improve your training materials.
Going live
The deployment phase is the transition from a pre-production to production-operation environment. It is important to establish support structures for end users that will be available in the long term, not just
60
2.3
during the critical period immediately after going live. You can use the integrated service desk in SAP Solution Manager for this purpose. One prerequisite for going live is that data verified in the build and test phase has been transferred (cut over) from the legacy system to the production system. Tested configuration settings, modifications, and customer developments are also transported to the production system. You should engage the SAP GoingLive Check service about two months before you plan to go live. It reduces the risks involved in implementation by identifying potential performance, availability, and maintenance problems, so that you can take corrective measures in plenty of time. During the go-live and support phase, users gain practical experience working with a solution. This phase requires a well-organized user-support structure that all employees can easily access. This phase also entails monitoring system transactions and optimizing overall system performance. SAP Solution Manager offers a wide range of resources and tools to help you run the solution. For instance, you can monitor the implemented processes across all systems. Especially when a system has not been in operation for long, you should proactively analyze it to identify potential problems, prevent bottlenecks, and monitor system performance regularly and automatically. You accomplish this by setting up the SAP EarlyWatch Alert service in SAP Solution Manager. This tool is also very effective for checking your core business processes and systems. The SAP EarlyWatch Check service proactively analyzes your operating system, database, and SAP software to optimize performance and provides recommendations and proposals for further action. After passing the test-to-deploy q-gate, the transport lock may be released, and the final synchronized transport can take place. The project ends when the changed solution can be handed over to the support organization.
SAP EarlyWatch Check SAP GoingLive Check
61
Relevant SAP Solution Operations Standards Solution Documentation Solution Documentation for Custom Development Change Management
Work Centers in SAP Solution Manager Implementation/Upgrade Solution Documentation Assistant Change Management
SAP also provides CQCs for the implementation. For further information, see Appendix A, Additional Information and Offerings.
Deploy Phase: What SAP Enterprise Support Offers for You Benefit Case: Go Live on Time and on Budget SAP Enterprise Support provides a reduction of test efforts for integration and volume testing and at an increased quality management during deployment, resulting in improved business process availability. Q-gate management reduces the stabilization effort, and the suite of root cause analysis capabilities optimizes performance and workload distribution. SAP supports this phase by dedicated CQCs.

Benefits for customers: Up to 30 % lower integration test costs Benefits for partners: Less risk of failure as go-live is signed-off by SAP
Core Assets Core assets of SAP Enterprise Support for the deploy phase include the following:
Root cause analysis tools, including end-to-end trace, SQL trace, and usage and performance statistics Best practices and tools for integration validation, performance, and data consistency per business process Best practices and tools for sizing and workload distribution, Quick Sizer Migration workbench Modification justification check
SAP CQCs for implementation (GoingLive Check for Solutions, Integration Validation, Support Going Live) System sizing and configuration content
62
Business Continuity
2.4
2.4
Business Continuity
By introducing SAP NetWeaver and service-oriented architecture (SOA), SAP significantly increased the ability of IT to satisfy business demands. However, our customers system landscapes have also become significantly more sophisticated. On the customer side, keeping the IT solution available, stable, integrated in the software landscape, and performing optimally is the main challenge of IT service and application management. The number of systems IT has to operate is growing continuously, while IT staffing remains stable. In addition, IT staff needs to acquire new skills to support an increasing variety of technologies and software that can result from acquisitions, as well as from implementing thirdparty solutions provided by resellers and OEMs. The task of IT service and application management is to ensure business continuity, while reducing TCO in distributed, heterogeneous environments. Most IT organizations can survive this challenge only by managing their operations by exception. In this approach, routine tasks must be automated as much as possible. Instead of sitting in front of a monitoring system, IT staff should be alerted when a system reaches a critical state, a business process is affected, or business continuity is at risk. Reporting used to prove business continuity and the value of IT to the business should be automated as much as possible.
Exception principle
2.4.1
Operate Phase
SAP Solution Manager enables processes to be handled automatically in many different areas, such as system monitoring and error notification, the collection of technical data, report summaries based on SAP EarlyWatch Alert, and service-level reporting. Current know-how, as well as task and workflow documentation, is integrated in many areas where administrative responsibilities and other tasks occur, for example, central system administration, solution reporting, and business process monitoring. Automation and the efficient transfer of knowledge provide experts with the time they need to concentrate on their core competences. This, in turn, allows small teams to monitor and manage complex system landscapes, while making the services they offer visible to end users. As a result, SAP Solution Manager makes it possible for you
63
to keep IT know-how inside your company or outsource it and monitor the services provided. A key process in solution operations is application incident management, as outlined in Section 5.3.1, Close Cooperation Between QM and Teams.
Action plan
For each incident and problem, an action plan is formulated, together with the problem message. Its implementation must be monitored, which may involve system administration activities, such as implementing a patch or changing a configuration. Two customer IT teams are involved in solution monitoring:

Business process operations team for business process monitoring Technical-operations team for system monitoring
Solution monitoring process
The solution-monitoring process runs on both business process and technical system levels:

The solution monitoring tools in SAP Solution Manager generate alerts. The alert solution includes the processes business process operations or technical operations. Each alert has a description that explains the alert processing. If the solution is not clear, the alert is given the status of a problem and must be subjected to root cause analysis.
The following sections describe the scope of technical operations, business processes, and application management.
Technical Operations Technical operations include system and end-user experience monitoring (see Section 5.3, Managing Business Continuity from the QMs Perspective) and the routine tasks of system administration.
System and End-User Experience Monitoring Business units expect that performance problems and errors will be detected proactively and resolved before they affect business continuity. SAP NetWeaver, the operating system, and the database are subject to system monitoring to ensure smooth technical operation. During opera-
64
Business Continuity
2.4
tions, exceptions may arise from SAP NetWeaver or the underlying technology. Effective and efficient handling of these exceptions is a crucial factor for stable technical operations. Whereas root cause analysis aims at problem resolution, system monitoring detects incidents automatically. When agents report diagnostics data that exceeds thresholds specified in a central alert definition, alerts are created, and the IT experts responsible are notified so they can take corrective action. If the required corrective action is not obvious, root cause analysis is performed to resolve the incident. SAP Solution Manager provides both real-time and historical monitoring. Real-time monitoring goes down to a granularity of 15 seconds; historical monitoring starts at an hourly level and can be aggregated in SAP Solution Manager to daily, weekly, and annual levels using the SAP NetWeaver Business Warehouse (SAP NetWeaver BW) component. Real-time monitoring is provided with the dashboard technology in CA Wily Introscope. All dashboards are shipped preconfigured by SAP and are part of SAP Solution Manager. If you want to create your own dashboards, for example, for custom code or legacy applications, you can purchase the SAP Extended Diagnostics application by CA Wily (a reseller product on the SAP price list). This entitles you to use the full version, including all preconfigured instrumentation and dashboards for non-SAP applications. From the triage view of the SAP NetWeaver Portal component, your IT staff can dive more deeply into monitoring detailed metrics, which are updated every 15 seconds. To help your IT staff analyze performance and exception development trends, SAP Solution Manager offers end-to-end workload and exception analysis. Both are based on SAP NetWeaver BW in SAP Solution Manager. All required extractors and agents are provided with SAP Solution Manager; you do not have to develop them yourself. From a user perspective, a well-running server environment does not necessarily guarantee appropriate response times and availability because exceptions can occur on clients, or in the network from the client to the server environment. End-user experience monitoring meaWorkload and exception analysis Types of monitoring
Dashboards
65
sures true response times from a client to a server periodically based on scripts simulating end-user click sequences. Figure 2.9 shows a self-service timesheet application for which a customer wants to see performance and availability in eight locations. At each location, the customer has implemented agents that continuously monitor end-user experience. In contrast to other end-user experiencemonitoring infrastructures on the market, not only does SAP Solution Manager measure behavior on the client, but it also collects statistics and traces that analyze the correlation to the server environment.
WALLDORFWDFD00987654
2770/5000 ms
WALLDORFWDFD00123456
SINGAPOREPHLN00123456
2755/5000 ms
2772/5000 ms
SINGAPOREPHLN00987654
2767/5000 ms
Live
2775/5000 ms
ESS TIME SHEET
2775/5000 ms
PHILADELPHIAPHLN00987654
2749/5000 ms
NICE NCEN00987654
2775/5000 ms
NICENCEN00123456
PHILADELPHIAPHLN00123456
Locations
SINGAPORE-PHLN0098 NICE-NCEN00987654 PHILADELPHIA-PHLN00 SINGAPORE-SINN0012 WALLDORF-WDFD0098
Response
2770/5000 ms
2775/5000 ms
Figure 2.9 End-User Experience Monitoring of a Self-Service Time Sheet Application End-to-end alerting
System monitoring and user-level monitoring can be automated with end-to-end alerting. Thresholds are defined for key metrics, and alerts are raised automatically by the alerting infrastructure. By automating
66
Business Continuity
2.4
monitoring through end-to-end alerting, the same operations staff can run more systems. The new alerting infrastructure provides open, configurable consumption of alerts, such as exposure to third-party application management, emailing, or SMS text messaging through SAP NetWeaver, and a unified alert inbox that is part of the System Monitoring work center in SAP Solution Manager.
Relevant SAP Solution Operations Standard System Monitoring Work Center in SAP Solution Manager System Monitoring
System Administration Regular routine tasks are part of a customers technical-operations manual and include performing backups and restarts, managing printers, and carrying out identity management tasks.
Relevant SAP Solution Operations Standard SAP System Administration Work Center in SAP Solution Manager System Administration
Business-Process Operations You need to consider and address four basic aspects to maintain a sustainable concept for business process operations:

Business process and interface monitoring Job scheduling management Data consistency management Data volume management
The following sections describe these aspects in more detail and refer to SAP standards for solution operations. These standards describe the operational processes and the supporting tools used to set up, support, and execute operational processes.
67
Business Process and Interface Monitoring The monitoring of business processes and related interfaces is one of the main aspects for a business-operations concept (see Figure 2.10). The goal is to ensure smooth operation and a stable flow of information, according to defined business requirements. During operations, exceptions may arise from within business applications. Effective and efficient handling of these exceptions is a crucial factor for both an optimized TCO and smooth business execution.
Figure 2.10 Business Process Monitoring
68
Business Continuity
2.4
Relevant SAP Solution Operations Standard
Work Center in SAP Solution Manager
Exception Handling and Business Pro- Business Process Operations cess and Interface Monitoring
Additional sources of input for monitoring processes are best practice documents for business process operations. Based on standard processes, the documents describe typical monitoring aspects or error situations, provide relevant information about the execution of business process steps, and refer to typical background processing or critical integration scenarios and their interfaces with the software components involved. These documents are available via SAP Solution Manager.
Job Scheduling Management for Successful Automation Management
Within a highly comprehensive and distributed landscape, job scheduling management is important to data management and data processing. Even in todays real-time processing environment, the need to run jobs in the background is significant. Jobs are concatenated into long job chains, usually containing many jobsequence dependencies. If one, or several jobs abort and cancel, the alert mechanism has to inform the appropriate support level or has to be able to start an automatic error-handling procedure and restart the jobs. Another aspect of job scheduling management is the efficient use of available system resources, such as CPU and memory. A typical requirement is the coordination of activities of concurrent online users and background jobs that need the same time window and system environment. This requirement needs to be managed to avoid system bottlenecks, performance bottlenecks, or delays in data processing.
Relevant SAP Solution Operations Standard Job Scheduling Management Work Center in SAP Solution Manager Business Process Operations
Job chains
Data Consistency Management Across the IT Landscape
Transactional correctness and data consistency are crucial factors for the success of each SAP solution. Your daily business operations from
69
end-user transactions to management decisions rely on correct and up-to-date data being available at the right time. As a result, data inconsistencies can have a severe cost impact, resulting, for example, from lost business deals or non-availability of your solution. Transactional correctness is a solution-configuration requirement it relates mainly to software functionality and the underlying technical infrastructure. Checks for transactional correctness have to be part of integration testing before a new solution or changes to an existing solution can be used in production. Transactional correctness corresponds to data consistency.
Reason for data inconsistency
The cause of data inconsistencies in a solution landscape is usually one of the following:
End users or key users are not aware of manual activities they have to perform to guarantee data consistency. For example, a key user changes master data in one component and sends this update to other systems manually. An interface that does not function properly. This is recorded in an error log on one side of the interface and may or may not trigger a workflow item being sent to a person to resolve the issue. Jobs are not running correctly or, due to insufficient time, were not started in the first place. If these jobs, for example, load data into a data warehousing solution, business reports are not accurate and may lead to incorrect business decisions.
Data consistency is an important aspect in business process operations. It is vital for the operation to create 100 % transparency of all aspects of data consistency.
Relevant SAP Solution Operations Standard Data Integrity and Transactional Consistency Work Center in SAP Solution Manager View Data Consistency Management in the Business Process Operations work center
70
Business Continuity
2.4
Data Volume Management to Manage the Growth of Business Data Optimal management of business data is another important aspect of business process operations. Data volume management requires technical considerations for optimal storage management for business data. Simply adding additional disks to storage area networks (SANs) and storage subsystems over time may actually make the situation worse. For example, system management can become more and more difficult or performance may degrade.
On the other hand, your business and business-application requirements have an impact on the management of business data. For example, business and legal requirements define the data retention period of critical financial data. Data volume management consists of the following phases:
Data volume scoping This is the starting point of data volume management. When implementing a data volume management strategy, a detailed look at the solution landscape identifies the major pain points and provides an overview of the most beneficial measures to take, such as data deletion or archiving. Data volume management strategy The focus is on the implementation of the methodologies of avoidance, summarization, data deletion, and data archiving (depending on the kind and type of data), and on considering business and external requirements, such as compliance with legal requirements. Data volume reporting Data volume reporting lists archiving activities already being performed and identifies additional reduction potential that may be realized by changes in business processes. Scheduling this activity on a regular basis can show the growth of the database at the businessobject level and identify how growth can be minimized.
Reaching a steady state that is, the balance between additional new data and archived data is an SAP standard required to run SAP solutions within given service-level agreements (SLAs) through future time periods.
71
Relevant SAP Solution Operations Standard Data Volume Management
Work Center in SAP Solution Manager View Data Volume Management in the Business Process Operations work center
Application Incident Management Application incident management is used during the testing phase to collect all errors. It is also used after going live as the central incidentmanagement function. Messages can be forwarded to SAP, if necessary, and tracked with SAP Solution Manager until the problem is fixed.
Service desk
The service desk in SAP Solution Manager is a trouble-ticket tool that is integrated into all important functions of SAP Solution Manager and the connected managed systems. Whenever problems arise during operation, end users create service-desk messages. The service desk then directs these messages automatically to the correct place within the customers support organization. Here, or in close collaboration with SAP AGS, the message is processed and resolved. The service desk provides everyone involved in the incident management process with central access at all times to the information relevant to them, including system information. The service desk simplifies the process of managing error messages and considerably reduces the time required to process incident and problem management. The following scenarios can be mapped using the service desk:

A global group and a global support organization Multiple segments of a group, and a common support organization A service provider that manages several companies
Root cause analysis is tightly integrated into incident management; it is triggered by either incident management (user interaction) or solution monitoring (system monitoring or business process monitoring).
Trigger by incident management
When an IT problem occurs, it can be recorded, categorized, and prioritized in the service desk of SAP Solution Manager, either by an end user or an IT employee. The service desk message is sent to first-level sup-
72
Business Continuity
2.4
port, which attempts to clarify the problem, and searches both the customers solution database and the SAP Notes service database. If a solution is not found, application management (second-level customer support) begins by carrying out a root cause analysis. SAP provides monitoring for both the technical operations team (described in the system monitoring standard) and the business process operations team (described in the business process and interface monitoring standard). The teams sole aim is to proactively detect errors and performance bottlenecks before they affect business continuity. Alerts are triggered based on thresholds and notify the responsible IT team. The goal of solution monitoring is the proactive detection of incidents; the goal of root cause analysis is incident resolution. For example, a memory-intensive activity on a specific system triggers an alert in the system monitor. The cause of this unusual memory growth is not clear; root cause analysis may point to a memory leak in custom-developed software.
Relevant SAP Solution Operations Standard Incident Management Work Center in SAP Solution Manager Incident Management Business Process Operations
Trigger by solution monitoring
End-to-End Root Cause Analysis
If an end user experiences a performance problem in a browser, the performance hit may be in the client, the network, or somewhere in the server environment, which itself comprises different instances of different technologies. Server-side processing may take place in SAP NetWeaver Portal (based on Java technology), then continue on to SAP ERP on the backend (based on ABAP), and finally call the database and storage subsystem for data retrieval. A performance problem or functional defect may occur at one or all stages of this roundtrip activity launched by an end user from a browser. End-to-end root cause analysis helps identify the specific components that cause a performance bottleneck.
73
When the service desk within the business unit cannot solve an incident, the application management team performs end-to-end root cause analysis to isolate the component responsible for a functional defect, or a performance problem: client, network, various SAP applications (such as SAP NetWeaver Portal, SAP CRM, and SAP ERP), database, or storage.
Root cause analysis
SAP Solution Manager supports end-to-end root cause analysis to identify the component that is responsible for the error. This top-down approach helps you systematically target the cause of the error; you no longer have to perform an untargeted, intuition-based approach using various component experts. The latter method involves much more time and expense. You can envision the end-to-end root cause analysis approach as a type of crime scene investigation, systematically leading to the solution. End-to-end root cause analysis is supported by the following:
End-to-end change analysis Provides transparency on changes (code, business configuration, and content) that were applied recently to a production application. This analysis is particularly important if a few ad hoc changes result in disruptions after they were applied. End-to-end workload analysis Provides unified access to server-side workload statistics. End-to-end exception analysis Provides unified access to exceptions reflected in high-severity log entries and dumps. Component-specific log and dump viewers can be accessed directly from this analysis. End-to-end trace analysis Records performance and functional defects in a single activity of a single user or process, from browser to disk. The measurement is started at the UI of the end user, and the trace level for the roundtrip is selected. When the request gets to downstream servers, all components switch their traces on or change the log level according to the selected trace level.
The example in Figure 2.11 shows an end-to-end trace analysis. Within this analysis, a complete flow trace of the end-user activity is recorded,
74
Business Continuity
2.4
starting at the browser and ending at the disk. In this case, the request leaves the browser, passes the SAP NetWeaver Composition Environment (SAP NetWeaver CE), and goes to a backend application. In this example, most of the time was spent in SAP NetWeaver CE. The end-toend trace analysis allows drilling down to the code level that is responsible for the performance bottleneck.
Figure 2.11 End-to-End Trace Analysis in Root Cause Analysis Work Center
Component Root Cause Analysis After the application management team has performed an end-to-end root cause analysis and has identified the problematic component, incident management enables the issue to be forwarded to the correct expert in custom development, business process operations, technical operations, or IT infrastructure.
Various tools are needed to complete the different tasks in component root cause analysis. In a distributed customer solution, these tools may
75
be located on different systems. SAP Solution Manager provides a central access point to the system landscapes and simplifies access to the required tools.
Analysis by SAP or SAP Partner
Even though every customer should perform preparatory work and endto-end root cause analysis of an issue, many IT organizations are not able to resolve all problems themselves because this requires in-depth knowledge of specific SAP components. SAP, or its partners, may have to get involved as needed. For experts to be able to provide efficient support, they need access to the customers IT solution landscape.
Remote supportability
The remote-supportability standard describes how customers can provide remote access to the required tools and how SAP reduces the risk involved in this activity. By giving external experts access to the tools and related data required to solve an issue, customers can accelerate the delivery of support services and reduce costs. SAP provides all tools required to perform endto-end root cause analysis to customers, partners, ISVs, and SAP consultants, who can then access these tools remotely and safely through a secured connection to the customer. How does SAP reduce the risk of uncontrolled, or even inadvertent, changes to the productive environment? This is achieved by read-only authorization policies of the individual root cause analysis applications. Access to productive servers at the operating-system level should be given only in exceptional situations. Such system access can be avoided by continuously collecting operating system statistics in SAP Solution Manager, as well as by using the command console of the operating system, which allows read-only execution of operating system commands. These tools are also instrumental to a customers application-management team, as the IT infrastructure team often does not allow operating system access to their production servers.
Relevant SAP Solution Operations Standard Root Cause Analysis Work Center in SAP Solution Manager Root Cause Analysis
76
Business Continuity
2.4
IT Reporting To demonstrate the value of IT to the business, SLAs are aligned between business units and IT. To confirm that the service levels agreed upon between IT and business are met, SAP provides IT reports that you can adapt to meet your specific needs by tailoring them to the relevant SLA. After you have configured these reports, they can be generated and broadcast automatically to defined recipients in your business or IT organization. SAP EarlyWatch Alert is a standardized IT benchmark that customers cannot change; therefore, the flexibility in SAP-provided service-level reports to compile IT reports based on SAP EarlyWatch Alert reporting content in a more customizable form is limited. If you require full flexibility for IT report compilation and broadcasting, SAP recommends you use customer-specific reporting. Technically, the diagnostics-data collection consists of gathering and exporting relevant KPIs, on a continuous basis, into the SAP NetWeaver BW layer of SAP Solution Manager. This happens after the basic setup of SAP Solution Manager has been completed. This data is used already by end-to-end root cause analysis and end-toend monitoring, but it can also be used for automated, highly customized IT reporting. With SAP NetWeaver BW, systematic aggregation from hour cubes to day cubes, to more coarsely granulated cubes, is performed continuously. This enables you to create your own Web templates and embedded queries, resulting in completely customized IT reports and broadcasting features. You do not have to create the data collection and extraction infrastructure and content on your own. Furthermore, no programming is required to compile customized IT reports. The IT reports, and their broadcasting, can be modeled with a graphical report builder in the SAP NetWeaver BW layer of SAP Solution Manager; cube content is already populated by the end-to-end diagnostics infrastructure. SAP also offers CQCs for this phase. You will find a detailed description in Appendix A, Additional Information and Offerings.
SAP EarlyWatch Alert
Customer-specific reporting
77
Operate Phase: What SAP Enterprise Support Offers for You Benefit Case: Operation Content Is Maintained Like Code Because the operations phase is the longest phase in the lifecycle, SAP Enterprise Support offers processes and services to reduced planned and unplanned downtime. To ensure business continuity, the support engagement provides protection of investment by innovation without upgrade, built-in business process monitoring, and system and interface monitoring processes, as well as capabilities for data consistency and data volume management.

Benefits for customers: 99.x% business process availability Benefits for partners: Less risk of failure by mission-critical support by SAP
Core Assets Core assets of SAP Enterprise Support for the operate phase include the following:

Business process monitoring best practices System monitoring best practices Application incident management for the customer solution and incident knowledge base (SAP Notes) Best practice for creating and maintaining the operation handbook Dedicated production down support (7x24)
SAP CQCs (e.g., EarlyWatch Check, Remote Performance Optimization, Business Process Performance Optimization, Data Volume Management, Security Optimization Check, Business Process Management, Business Process Analysis, Solution Transition Assessment) Prio 1 and Prio 2 SLAs for root cause analysis and issue resolution recommendations
2.4.2
Optimize Phase
The optimize phase is a time for making sure that software changes are planned and implemented consistently, after your software is in operation. SAP Solution Manager supports you in this task with its functions for managing change requests. If you need to make significant changes, such as upgrading a software component in your solution, the tool lets you take a professional approach using tried-and-tested procedures.
78
Business Continuity
2.4
Another challenge you may face during the optimize phase is distributing a template defined at the head office to your organizations subsidiaries. SAP Solution Managers answer to this challenge is the global rollout function. To keep your software landscape up to date, you must consider three types of software changes:

Types of software changes
Support package updates Software upgrades SAP EHPs
Support Package Updates Installing support package updates is an ongoing task. Support package implementation is planned on a yearly basis, and SAP strongly recommends that you implement the latest support packages. By doing so, you ensure that your companys software is at the latest status of a certain release. This means it has all of the available corrections and improvements, and this helps your, as well as SAPs support and development. Knowing the exact status of your software can dramatically reduce the time it takes SAP to support your software. As a result, software stability and availability can increase significantly. With the maintenance optimizer, SAP Solution Manager enables a holistic update process. The maintenance optimizer provides the following functions:

Maintenance optimizer
Lists available support packages for all installed SAP applications Allows direct download and installation of patches Checks compatibility of patches by considering dependencies among different systems
Upgrade management functionality provides you with an overview of the support package level of all SAP applications from one central tool. It checks for new patches for your installed SAP landscape, taking into account possible dependencies among different systems.
79
Relevant SAP Solution Operations Standard Change Management
Work Center in SAP Solution Manager Change Management
Software Upgrades Changing business conditions lead to changing IT solutions, and every evolving organization needs to adapt its IT environment accordingly. In many cases, this drives the need to upgrade your SAP software. Upgrades allow you to benefit from the latest available functionality, leverage new technologies that foster innovation, and get long-term protection of IT investments. Details of upgrade-related tasks and the technical upgrade itself may vary depending on product, release, platform, and interface constellation. However, you should give your full attention to the following tasks:

Align the upgrade program with corporate business and IT strategies. Plan the IT infrastructure. Adapt applications and custom developments. Manage parallel changes during the upgrade project. Manage Unicode conversions and other data changes. Minimize business downtime. Ensure business continuity.
Align the Upgrade Program Large enterprises usually maintain a number of complex solutions that consist of software from different vendors, include multiple releases of the same software product; or incorporate same-release software at multiple support package levels. In addition, organizational factors, such ITprovider concept, data-center concept, or server architecture, drive complexity.
Dependencies between systems
Within these environments, mutual dependencies among the systems always exist. Therefore, an SAP release upgrade almost always triggers changes in all levels of the solution landscape and may require addi-
80
Business Continuity
2.4
tional hardware resources. When planning an individual upgrade, you have to consider such changes, and you may decide to make IT changes in combination with the upgrade. This could save effort and costs for the individual project. Thus, it is very important to update your corporate global IT program definition in the specific context of an upgrade, before starting the first individual project. As the basis for an update of your corporate strategy, you need to have full transparency of the current situation. Thus, complete and reliable documentation of all solution components in the solution directory of SAP Solution Manager and an overview of every IT project documented in SAP Solution Manager are crucial for the planning and execution of an upgrade project.
Plan the IT Infrastructure Proper infrastructure planning is a prerequisite for a successful upgrade, as well as for a reliable and well-performing target solution. Two major challenges exist: ensuring the compatibility of all connected software components, and correctly sizing the hardware needed for the future solution.
In general, you need to consider two dimensions of compatibility for complex solutions. First, the vertical stack consisting of SAP software components: the SAP kernel, operating system, and database have to be checked for compatible combinations and restrictions of the upgraded versions. SAP publishes its product availability matrix (PAM) on the SAP Service Marketplace (http://service.sap.com/pam); here you can retrieve the released combinations. For add-ons, you should also check the respective release restriction and add-on release strategy notes. To find this information, enter the add-on name and the search string release strategy into the SAP Notes search box on the SAP Service Marketplace. The compatibility or interoperability among different SAP and non-SAP applications has to be verified when one of them is upgraded. The upgrade dependency analyzer (UDA) helps you analyze known dependencies when upgrading technical components in your landscape. Accessible from the SAP Service Marketplace under http://service.sap.com/uda,
Software compatibility
81
this tool provides dependency information to support the planning of upgrade projects. The tool can compare two applications at a time: the application being upgraded, and one other application in the solution landscape. The output is an online dependency statement, and an optional reference to SAP Notes. The UDA is a high-level planning tool for upgrades but does not cover all dependencies relevant for planning an upgrade. For more detailed information, especially with respect to process or scenario information, refer to the scenario and process component lists located at http://service.sap.com/scl. In all cases, you should consult the SAP master guide and upgrade guide. These guides refer to specific standard SAP Notes that always reflect the most current status regarding release restrictions.
Capacity planning
Determining the correct size of all relevant system resources is a crucial aspect of an upgrade. This lets you achieve good performance without bottlenecks, while spending an appropriate portion of the upgrade budget. It all starts with a clear picture of the current situation, which can be obtained easily by using the SAP EarlyWatch Alert scenario of SAP Solution Manager. This lets you find the current load of key system resources, as well as available buffers for future growth. Checking the Quick Sizer tool on the SAP Service Marketplace can provide an initial estimate of additional hardware requirements. Your hardware partner can then work with you to refine the actual size of all major system components in the target scenario. In addition, SAP provides the SAP GoingLive Functional Upgrade Check service to conduct a plausibility check of the planned capacity of the target system. This may include upgrade sizing, as well as Unicode sizing.
Adapt Applications A significant cost driver during software upgrades is custom code and modifications made to standard software. The custom development management cockpit (CDMC, see Section 8.4.4, Custom Development Management Cockpit) is the approach SAP promotes to analyze the custom
Custom development management cockpit
82
Business Continuity
2.4
code in your software landscape and to optimize upgrades to these developments. In addition to custom developments, application adjustments need to be performed to match your solution to changed SAP standard functionality. SAP Solution Manager helps with this task by automatically presenting upgrade and delta views of the IMG for each component to be upgraded.
Manage Parallel Changes
It is very important to not compromise any aspect of your change-management process in the course of an upgrade. You might be tempted to allow mass exceptions to the existing set of rules. You usually have to implement many changes in a short period of time and might feel that you do not have enough time for a thorough evaluation to determine if a change is really required. However, such practices introduce a lot of risks. You should, therefore, make the reliability of the change-management process your first priority. SAP Solution Manager provides powerful tools to implement change request management. Do not reassign roles, change the sequence, or implement new tools, if these steps are not urgently required. If this has to be done perhaps to facilitate the upgrade you should try to adapt the process as early as possible in the upgrade and let the new scenario be established well before the upgrade in day-to-day business. To maintain the current production environment, we strongly recommend setting up a maintenance landscape in parallel to the project landscape for implementing corrections in the old release. During this phase, urgent corrections to the production system have to be applied twice: in the development systems of both the maintenance and upgrade landscapes (dual maintenance). To minimize project efforts for dual maintenance, you should implement a strict code-freeze period immediately after upgrading the development system.
Convert Data
Reliable change management process
SAP always attempts to create downward-compatible software, so that you can still execute old functions and software in the new release.
83
However, continuous product enhancements may require data conversions. Such conversions can mean considerable preparation and execution effort. The most prominent example is the conversion to the Unicode standard. Although this activity is technically not required to be executed with an upgrade, many upgrades to products based on SAP NetWeaver 7.0 (particularly SAP ERP 6.0) require Unicode conversion because SAP does not support more than one installed codepage in these releases. Single codepage systems do not have to convert to Unicode, but SAPs product strategy is committed to Unicode. Therefore, a conversion cannot be avoided in the long term.
ASU toolbox
In addition to Unicode conversion, other application-specific data conversions may be triggered by changes in applications data models. You can use the SAP Application-Specific Upgrade (ASU) toolbox to analyze changes in the application areas. The ASU toolbox enables you to recognize additional application-specific steps before and after the upgrade, in addition to the actual technical upgrade. The analysis covers the following main areas of application changes:
Checks for the existence and usability of certain customer-specific data, such as report and display variants Information on necessary customizing settings for new functionalities Starting of reports that are not part of Execution of Programs after Import (XPRA) reports (which are started automatically during the upgrade) to adjust your data to the new release
The ASU toolbox can be integrated into standard upgrade procedures through automatically generated task lists and provides all required tasks in their optimal sequence. The ASU toolbox is also integrated with upgrade project management in SAP Solution Manager to guide you through manual activities before and after the upgrade, including, for example, the direct display of related SAP Notes.
Minimize Business Downtime
For customers with extremely high system availability requirements, SAP offers the near zero downtime method. This method enables you to reduce business downtime to three or four hours for a release upgrade. Business downtime is defined as total system outage for business users,
84
Business Continuity
2.4
including downtime for the technical upgrade, as well as required data conversions, the implementation of customer transports, and system validation, with sign-off by business users. More detailed process information can be found in Section 8.4.3, Solution Documentation Assistant.
Ensure Business Continuity
One major challenge of any upgrade project is to ensure maximum business continuity after the completion of the technical upgrade, which means making sure that the availability, stability, and performance of the software can be provided at the same level as before the upgrade. Important measures to minimize the risk and impact of business disruption include efficient testing of core business processes, sufficient training of end users, and an appropriate update of solution operation procedures. After delta changes and adjustments have been executed, the test workbench functionality in SAP Solution Manager helps you plan, execute, and monitor your integrated testing based on your business process documentation and the delta changes you selected to be implemented (see the Section Application Incident Management in this chapter for more information). The learning map builder in SAP Solution Manager helps you create role-specific learning maps based on documents generated during the upgrade project, which are relevant to end-user training. Finally, operating procedures must be reviewed for their currentness and updated as required, and the operations staff has to be trained accordingly. This may include the following tasks:
Test workbench
Learning maps
If new business processes, application components, or technologies are implemented in the course of a functional upgrade project, the new parts of the solution need to be integrated into the existing operations concept. If the hardware, operating system, or database software is being migrated to a different platform, system administration and monitoring procedures must be analyzed and updated.
85
If interface technologies are changed, or new interfaces are added, the interface-management concepts and handling procedures need to be reviewed and adapted to ensure performance and stability of business processes. A revision of the general security policy is usually required.
Work Center in SAP Solution Manager Implementation/Upgrade Change Management View Data Volume Management in the Business Process Operations work center
Relevant SAP Solution Operations Standards Upgrade Change Management Data Volume Management
SAP Enhancement Packages As of SAP Business Suite 2005, SAP bases its release strategy on optional EHPs. The concept was first available with SAP ERP 6.0; however, it is, or will be, extended to all SAP Business Suite applications and SAP NetWeaver. EHPs deliver new functionality and key innovations for SAP applications on top of a software release, eliminating the need for you to upgrade to the current release of an SAP product. EHPs include functional enhancements, industry-specific enhancements, and simplifications; they have the same maintenance duration as the underlying core application. The switch framework enables you to activate new business functions in an EHP when desired. Until then, the technical installation of an EHP has no impact on your existing business processes or UIs.
SAP EHP installer
Through the SAP Service Marketplace, you may discover new enhancements and evaluate their business relevance for your company. The technical installation is separate from business innovation; it has no effect on any UI or existing business process. The technical installation is supported by the maintenance optimizer and the SAP EHP installer through guided procedures. A detailed description of this procedure can be found in Section 9.4, Tools for Deploying SAP Enhancement Packages.
86
Business Continuity
2.4
The main advantages of the SAP EHP installer include the following:

Improved user experience due to an intuitive guided procedure Streamlined installation process Reduced downtime Easier addition of support packages Mitigated risk due to an isolated shadow system
Work Center in SAP Solution Manager Implementation/Upgrade Change Management
Relevant SAP Solution Operations Standards Upgrade Change Management
SAP also offers continuous quality checks (CQCs) for upgrade projects. You will find a detailed list of available CQCs in Appendix A, Additional Information and Offerings.
Optimize Phase: What SAP Enterprise Support Offers for You Benefit Case: Built-In Protection of Investment To protect your investment, SAP Enterprise Support offers technology upgrades (SAP support packages, SAP legal change packages) and maximal time for return on investment and deployments by the 7-2 maintenance strategy. A set of dedicated services and capabilities is available to keep planned downtimes and thereby minimize upgrade costs and risks. It also supports the virtualization of system resources and provides holistic quality management during the optimize phase, as well as overall protection of investment by innovation without upgrade.

Benefits for customers: Up to 20 % less cost of operations Benefits for partners: Less operation costs by SAP support, and less than 30 % data growth; compliance guaranteed by SAP
Core Assets Core assets of SAP Enterprise Support for the operate phase include the following:

Maintenance optimizer Solution management assessment best practices
87
Data growth management and archiving best practices Built-in archiving SAP Notes with code changes and SAP Notes Assistant SAP support packages, SAP legal change packages Technology updates Best practices for tuning 7-2 support strategy

SAP Enterprise Support status report review Modification justification check Modification maintainability check SAP CQCs (Downtime Assessment, Upgrade Assessment, GoingLive Functional Upgrade Check)
Summary
SAP Enterprise Support provides a proactive rather than reactive approach to solution support and enables ALM. This is accomplished with integrated quality management throughout the lifecycle of solutions. The engagement goes the extra mile and covers SAP software and all horizontal and vertical IT assets and software components that are required to complete the customers business processes as documented in the solution documentation in SAP Solution Manager.
88
Index
A
Action plan 132, 138 Alert management 63, 137 Alerts 140 Americas SAP Users Group (ASUG) 290 Analysis tools 175 Application lifecycle 132 Application lifecycle management 35 Application management 36, 63, 74, 107, 111, 221 Application management lifecycle 44, 49, 241, 243 Application management team 75, 107, 136, 146 Application-specific upgrade 84 Application-specific upgrade toolbox 240 Architecture services 284 ASAP methodology 37 Business process improvement 91, 102, 207, 208, 210, 212, 238, 246 Business process improvement plan 132 Business process integration 120 Business process monitoring 63, 68 Business process operations 43, 67, 107, 121, 140, 148 Business process operations team 136, 140 Business process repository 50, 243 Business process requirements 131, 201, 213, 232, 238 Business processes 140, 141, 142, 150 Business processes monitoring 142, 144, 146
C
CA Wily Introscope 65 CA Wily Introscope Enterprise Manager 155 Certification 127, 316, 320 Run SAP implementation program for SAP service partners 317 Change analysis 74, 155 Change control 120, 122 Change impact analysis 168 Change management 56, 83, 102, 246 Change request management 47 Change-impact analysis 168 Clearing analysis 241 Clearing project 241 Code freeze 83 Company network 311 Composite application development 231 Continuous quality checks 178, 252 Core business processes 122, 173, 263 Cost of innovation 228 Critical path 173
B
Back office 281 Background processing 69 Balanced scorecard 278, 279 Blueprint 240 Build 241, 244 Build and test 36, 54, 55 Business blueprint 52 Business configuration 38, 49 Business continuity 39, 63, 64, 85, 91, 102, 120, 131, 134, 138, 142, 147, 207, 238 Business function 268 Business process 38, 114, 120, 131 Business process champion 107, 123, 124, 137, 138, 141, 157, 198, 200, 201, 213, 230, 243, 246, 255 Business process change analyzer 45, 164, 167, 168
367
Index
Custom code 41, 48, 55, 61, 65, 73, 75, 82, 163, 226, 231, 232, 233, 234, 247, 248 Custom code maintainability check 126, 249 Custom development 107, 141 Custom development management cockpit 82, 236, 241 Custom development team 107, 136, 141, 156, 228, 255 Custom software 226 Customer COE 99, 100, 102, 110, 117, 127, 173, 211, 219, 226, 272 Customer-specific maintenance 223
F
Front office 281
G
Go-live 61, 311 Governance 276
H
Hybrid model 258
I
Incident 135, 138 Incident management 43, 64, 72, 75, 121, 137, 245 Incremental upgrade and Unicode conversion (IUUC) 267 Innovation 86, 102, 112, 163, 207, 219, 231, 257, 260 Innovation and protection of investment 91 Integration testing 57, 118, 163 Integration validation 58, 150, 172, 173, 238, 272 Interface monitoring 68, 142, 144 Interfaces 203, 205, 227, 236, 240 Issue management 177 IT infrastructure 70, 76, 81, 121, 137, 260, 289 IT Infrastructure Library (ITIL) 36, 315 IT infrastructure team 107 IT reporting 77, 147 IT transformation 272
D
Data aggregation 136 Data consistency 112, 143, 144, 177 Data consistency management 69 Data conversion 83 Data integrity and transactional consistency 144 Data volume management 71, 145, 146 Deploy 36, 37, 60 Design 36, 52, 241, 244 Design operations 313 Development 229 DMAIC 94 Downtime 84, 87, 148
E
eCATT 58 EHP business function 168 End-to-end analysis 174 End-to-end solution operations 101, 102, 121, 272 Engagement architect 276 Enhancement package 207, 239 Exception analysis 74, 155, 176 Exception handling and business process and interface monitoring 142 Extended Maintenance 221
J
Java log viewer 155 Job chains 69 Job management 142, 143 Job scheduling management 69, 143, 149 Job sequences 142
368
Index
K
Key user 70, 107, 137, 144 KPI 201, 208, 211, 253
P
Partner 109, 311 Performance test 57 Planning reliability 259 Problem management 72 Product availability matrix 81, 240 Program management office 107, 109, 117, 136, 228, 246, 256 Protection of investment 102, 112, 150, 207, 226, 242, 246, 251
L
Legal change packages 222 Lifecycle 37, 44, 318 Lifecycle management 38, 40 Load tests 172
M
Mainstream maintenance 222 Maintenance 263 Maintenance costs 242 Maintenance management 43 Maintenance optimizer 79, 86, 239, 265 Maintenance project 48 Maintenance strategy 222, 259 Master release plan 228, 229, 256 Measurement platform 89, 90, 96 Minimum documentation 184 Modification justification check 124, 126, 248, 255
Q
QM for accelerated innovation 112 QM for business continuity 112, 120 QM for business process improvement 112, 123 QM for protection of investment 112, 125 Quality gate 44, 45, 48, 53, 56, 58, 61 Quality management 44, 45, 59, 111, 221 Quality manager 117, 219 Quality standards 243 Quality-gate management 45 Quick Sizer 82
N
Near-zero downtime 267
R
Reduce operational costs 173 Regression test 57 Release strategy 86, 225, 229 Release upgrade 260, 264 Remote connection 293 Remote supportability 76 Requirements 36, 50 Root cause analysis 59, 72, 73, 75, 76, 77, 120, 121, 134, 135, 146, 147, 155 Run SAP 46, 101, 103 Run SAP Implementation Partner Initiative Guide 317 Run SAP Implementation Program 311 Run SAP methodology 121, 132, 134, 159, 311
O
Operate 36, 50, 63 Operations processes 253 Optimization 174 Optimization of business processes 199, 209 Optimize 36, 50, 78, 241 Organizational model 106 Outsourcing 109, 110, 114, 133, 134, 272 Outtasking 109, 110, 114, 133, 134, 272
369
Index
Run SAP roadmap 46, 312 Assessment and scoping 313 Handover into production 314 Operation and optimization 315
S
SAP Active Global Support 273 SAP Business Process Performance Optimization 251 SAP Business Suite 86, 207, 259, 260 SAP CCC 110 SAP Central Process Scheduling by Redwood 143 SAP Downtime Assessment 252 SAP EarlyWatch Alert 61, 77, 123, 147 SAP EarlyWatch Check 61 SAP ECC 6.0 261 SAP enhancement package 86, 100, 106, 126, 173, 229, 260, 262, 263, 264, 265 SAP enhancement package installer 86, 265, 266, 267 SAP Enterprise Support 35, 178 SAP global support backbone 20, 294 SAP GoingLive Check 61 SAP GoingLive Functional Upgrade Check 82 SAP master guide 82 SAP MaxAttention 271 SAP NetWeaver 63, 86, 139, 155, 237 SAP NetWeaver BW 77, 147 SAP NetWeaver Composition Environment 75 SAP Notes 294 SAP Partner 76 SAP R/3 4.6C 259 SAP R/3 Enterprise 259 SAP Safeguarding 271, 272, 282 SAP Safeguarding for Integration Validation 117, 119, 120, 173, 182, 274 SAP Safeguarding for Operations 274 SAP Safeguarding for Upgrade 274 SAP Service Marketplace 86, 264 SAP service partner 316 SAP Solution Management Assessment 123, 124, 198, 200
SAP Solution Manager 35, 37, 38, 46, 47, 51, 52, 55, 60, 63, 65, 72, 74, 76, 77, 78, 82, 83, 90, 100, 109, 118, 120, 135, 140, 141, 146, 154, 173, 184, 201, 202, 211, 236, 238, 243, 282, 316 Basic configuration 47 SAP Solution Manager installation guide 47 SAP Solution Manager master guide 46 SAP Solution Transition Assessment 237, 247 SAP standards for solution operations 110, 137 SAP Support package 79, 87, 173, 222, 228, 230, 239, 241, 260 SAP technical operations team 107, 135, 136, 139 SAP Upgrade Assessment 251 SAP upgrade guides 82 SAP Upgrade Road Map 240 Secure area 294 Security 287 Service desk 61, 72, 74, 110, 113, 239, 245, 292 Bidirectional interface 245 Service desk message 72, 137, 292 Service plan 278, 281, 283 Service-level reporting 135 Single point of contact 20, 294 Single source of truth 102, 112, 113, 141, 150 Situation report 92 Situation room 102, 114, 115, 116, 135, 137 Six Sigma 94 SOA 63, 100, 132, 231, 258, 317 Solution architect 276 Solution directory 39 Solution documentation 133 Solution documentation assistant 240 Solution documentation for custom development 243 Solution implementation 54 Solution Manager project 37, 39 Solution monitoring 64, 73 Solution operations 210, 236
370
Index
Solution operations standards 133 Standards for solution operations 109, 318 Support advisory center 19 Support services 183 Sustainability 287 Switch framework 126, 263, 264, 268 Switch framework cockpit 268 System administration 67, 120, 122, 140 System landscape optimization services 284 System monitoring 64, 73, 139, 146
Test strategy 165 Test workbench 177, 240 Thread dump analyzer 155 Top issue 115, 118, 132 Total cost of operation 91 Trace analysis 74, 119, 155, 176, 177 Training 320 Transactional consistency 114 Transactional correctness 143 Transparency 116 Transport management 56 Trend analysis 142
T
Technical analysis 174, 175 Technical integration validation 117, 118, 172, 173 Technical operations 43, 64, 121, 122, 148 Technical quality manager 276, 281 Technology updates 222 Test case 42, 170 Test documentation 172 Test management 42, 45, 55, 56, 164 Test organizer 55 Test package 57 Test plan 57, 170 Test project preparation 166 Test scope identification 167
U
Unicode 82, 84 Upgrade 43, 80, 82, 83, 85, 163, 164, 226, 238, 239, 241, 242, 251, 267 Upgrade costs 229 Upgrade dependency analyzer 81, 242 Upgrade/change impact analysis 241 User-acceptance test 57
V
Verification 174, 178
W
Work center 53, 72, 139, 146 Workload analysis 74, 155
371

SAP Enterprise Support Book Intro

Uploaded by

Copyright:

Available Formats

SAP Enterprise Support Book Intro

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SAP Enterprise Support Book Intro

Uploaded by

Copyright:

Available Formats

Gerhard Oswald, Uwe Hommel

SAP Enterprise Support

Introducing the Measurement Platform ......................

Customer Center of Expertise ......................................

Preserving Business Continuity ................................... 131

Accelerated Innovation ................................................ 163

6.2.5 6.2.6 6.3 6.4

Improving Business Processes ..................................... 197

7.3 7.4 7.5 7.6

Protection of the IT Investment ................................... 219

8.6 8.7 8.8

251 251 252 252 253 254 254

Innovating Without Risking Disruptions .................... 257

10 SAP MaxAttention and SAP Safeguarding .................. 271

High Security Standards .................................................. 287 Sustainability Aspect ....................................................... 287

11 Mission-Critical Support for Partner Applications and Technologies .......................................................... 289

11.2 11.3 11.4

12 Run SAP Programs for SAP Partners ............................ 311

13 Overview of Training and Certification Offerings ........ 323

Appendices ......................................................................... 327

Index ................................................................................................ 367

ASAP to Run SAP

Delivered via: Mission-Critical Support

Delivered via: SAP Global Support Backbone

In Collaboration with SAP Ecosystem

Figure 1.1 SAP Enterprise Support

What SAP Enterprise Support Can Do for You

What SAP Enterprise Support Can Do for You

SAP Standards for Solution Operations

SAP Standards for Solution Operations

and safeguards data synchronization across applications in distributed system landscapes.

Customer Center of Expertise

Creating the Foundation for a Single Source of Truth

Creating the Foundation for a Single Source of Truth

SAP Solution Manager, enterprise edition, under SAP Standard Support

Creating the Foundation for a Single Source of Truth

Functional Limitations of SAP Solution Manager under SAP Standard Support

Establish the Foundation for SAP Application Lifecycle Management

Define a roadmap for Run SAP implementation

Implement SAP Solution Manager, enterprise edition

Creating the Foundation for a Single Source of Truth

Establishing the Foundation for SAP Application Lifecycle Management

Install, Upgrade, Extend

Document Business Processes

Change Control Management

Business Process Operations

Application Incident Management

Figure 1.3 SAP Solution Manager Implementation Overview

Root Cause Analysis for Custom Code

Test Workbench & Regression Testing

Run SAP for Industries

Creating the Foundation for a Single Source of Truth

Business process documentation

About This Book

About This Book

About This Book

Establishing SAP Solution Manager as a Consolidated Data Source in Your Enterprise

Establishing SAP Solution Manager as a Consolidated Data Source in Your Enterprise

Application Management Lifecycle

Requirements Opmize Applicaon Management Operate Build & Test Deploy