e2e200 en Col93 Fv Inst a4

E2E200 E2E Change Control Management SAP Solution Manager

Date Training Center Instructors

Education Website

Instructor Handbook Course Version: 93 Course Duration: 5 Day(s) Material Number: 50111976 Owner: Sylke Graupner (D033660)

An SAP Compass course - use it to learn, reference it for work

Copyright Copyright © 2012 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Trademarks Microsoft, Windows, Excel, Outlook, PowerPoint, Silverlight, and Visual Studio are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, z10, z/VM, z/OS, OS/390, zEnterprise, PowerVM, Power Architecture, Power Systems, POWER7, POWER6+, POWER6, POWER, PowerHA, pureScale, PowerPC, BladeCenter, System Storage, Storwize, XIV, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX, Intelligent Miner, WebSphere, Tivoli, Informix, and Smarter Planet are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the United States and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countries. Oracle and Java are registered trademarks of Oracle and its affiliates. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems Inc. HTML, XML, XHTML, and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. Apple, App Store, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C, Retina, Safari, Siri, and Xcode are trademarks or registered trademarks of Apple Inc. IOS is a registered trademark of Cisco Systems Inc. RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry Torch, BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry App World are trademarks or registered trademarks of Research in Motion Limited. Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps, Google Mobile Ads, Google Mobile Updater, Google Mobile, Google Store, Google Sync, Google Updater, Google Voice, Google Mail, Gmail, YouTube, Dalvik and Android are trademarks or registered trademarks of Google Inc. INTERMEC is a registered trademark of Intermec Technologies Corporation. Wi-Fi is a registered trademark of Wi-Fi Alliance. Bluetooth is a registered trademark of Bluetooth SIG Inc. Motorola is a registered trademark of Motorola Trademark Holdings LLC. Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH.

g2012529105051

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAP HANA, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company. Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc. Sybase is an SAP company. Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are registered trademarks of Crossgate AG in Germany and other countries. Crossgate is an SAP company. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

Disclaimer These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies (“SAP Group”) for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

g2012529105051

g2012529105051

About This Handbook This handbook is intended to complement the instructor-led presentation of this course, and serve as a source of reference. It is not suitable for self-study.

Typographic Conventions American English is the standard used in this handbook. The following typographic conventions are also used. Type Style

Description

Example text

Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths, and options. Also used for cross-references to other documentation both internal and external.

2012

Example text

Emphasized words or phrases in body text, titles of graphics, and tables

EXAMPLE TEXT

Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example SELECT and INCLUDE.

Example text

Screen output. This includes file and directory names and their paths, messages, names of variables and parameters, and passages of the source text of a program.

Example text

Exact user entry. These are words and characters that you enter in the system exactly as they appear in the documentation.

Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.

© 2012 SAP AG. All rights reserved.

v

About This Handbook

E2E200

Icons in Body Text The following icons are used in this handbook. Icon

Meaning For more information, tips, or background

Note or further explanation of previous point Exception or caution Procedures

Indicates that the item is displayed in the instructor’s presentation.

vi


2012

Contents Course Overview .......................................................... ix Course Goals ........................................................... ix Course Objectives .....................................................xii

Unit 1: How To Get Started .............................................. 1 How To Get Started.....................................................2

Unit 2: Introduction to E2E Change Control Management ......11 Application Lifecycle Management ................................. 12 E2E Change Control Management ................................. 23

Unit 3: Solution Documentation in SAP Solution Manager .... 41 Introduction ............................................................ 43 Technical Landscape Management with LMDB................... 51 Managing Projects with SAP Solution Manager .................. 70 Managing Solutions with SAP Solution Manager ................. 87 Reverse Business Process Documentation and Modelling Tools ...............................................................105 Business Process Change Analyzer ..............................122

Unit 4: Enhanced Change and Transport Management ........ 161 SAP Change and Transport System for ABAP...................163 Enhanced Change and Transport System CTS+ Overview ....174 Working with CTS+ ..................................................194 Enterprise Portal and CTS + .......................................209 (Appendix) CTS+ Configuration For Other Scenarios...........242 (Appendix) Transport Parameters for CTS+......................265

Unit 5: Reporting And Analysis Tools.............................. 271 Configuration Validation .............................................273 Software Change Strategies........................................338 Custom Development Management Cockpit (CDMC) - Change and Transport System (CTS) Analysis ........................372 Guided Self-Services/ Transport Execution Analysis ...........418

Unit 6: Transport Management with SAP Solution Manager.. 431 Introduction ...........................................................433 Infrastructure for Change Control Tools...........................438 Task List ...............................................................453

2012


vii

Contents

E2E200

Critical Object.........................................................462 Cross System Object Lock .........................................466 Retrofit.................................................................471 Transport of Copy ....................................................480

Unit 7: Quality Gate Management .................................. 485 Overview of Quality Gate Management...........................487 Setup of Quality Gate Management ...............................493 Project Phases and Quality Gates................................. 511 Central Transport Management ....................................527 (Appendix) Prerequisites to Set Up Quality Gate Management 555

Unit 8: Change Request Management ............................. 563 Overview ..............................................................565 Project and Release Management ................................573 Request for Change .................................................581 Project and Process Types .........................................606 ALM Integration ......................................................642 Tools ...................................................................654 (Appendix) Change Request Management.......................677

Unit 9: Maintenance Management .................................. 683 SAP Maintenance Strategy .........................................685 Types of Maintenance ...............................................697 SAP Enhancement Packages ......................................713 Maintenance Optimizer..............................................729 System Recommendations .........................................742 Upgrade / Change Impact Analysis................................760

viii


2012

Course Overview Target Audience This course is intended for the following audiences: • • • • • • •

Change Managers: Responsible for approval and change processes System Landscape Architects: Responsible for the design of the transport landscape topology System Administrators: Responsible for executing transports Development Managers: Responsible for performing development changes Test and QA Managers: Responsible for software quality and testing Persons responsible for a module / Application Manager: Responsible for approving and performing changes in an application module Support Manager and members of the Customer Competence Center (CCC) Partners and System Integrators for the Run phase

• Note: –

–

These training materials are not a teach-yourself program. They complement the explanations provided by your course instructor. Space is provided on each page for you to note down additional information. There may not be sufficient time during the course to complete all the exercises. The exercises provide additional examples that are covered during the course. You can also work through these examples in your own time to increase your understanding of the topics.

Course Prerequisites Required Knowledge • •

Fundamentals of Software Change Management. Basics of SAP Solution Manager.

Recommended Knowledge • •

End-to-End Solution Support (E2E040). Software Logistics for AS ABAP (ADM325).

Course Duration Details Unit 1: How To Get Started

2012


ix

Course Overview

E2E200

How To Get Started

20 Minutes

Unit 2: Introduction to E2E Change Control Management 20 Minutes Application Lifecycle Management 25 Minutes E2E Change Control Management Unit 3: Solution Documentation in SAP Solution Manager 15 Minutes Introduction 25 Minutes Technical Landscape Management with LMDB 10 Minutes Exercise 1: Technical Landscape Description 15 Minutes Managing Projects with SAP Solution Manager 15 Minutes Exercise 2: Create a Project 15 Minutes Managing Solutions with SAP Solution Manager 15 Minutes Exercise 3: Business Processes Exercise 4: (Optional) Transfer Project 10 Minutes Documentation to Solution Reverse Business Process Documentation and 20 Minutes Modelling Tools 30 Minutes Business Process Change Analyzer 20 Minutes Exercise 5: Business Process Change Analyzer Unit 4: Enhanced Change and Transport Management 20 Minutes SAP Change and Transport System for ABAP Enhanced Change and Transport System CTS+ 20 Minutes Overview 20 Minutes Working with CTS+ 30 Minutes Enterprise Portal and CTS + 15 Minutes Exercise 6: Portal Content Studio 10 Minutes Exercise 7: Transport Package Editor 10 Minutes Exercise 8: Transport Organizer Web UI 15 Minutes (Appendix) CTS+ Configuration For Other Scenarios 10 Minutes (Appendix) Transport Parameters for CTS+ Unit 5: Reporting And Analysis Tools Configuration Validation Exercise 9: (Optional) Change Diagnostics Exercise 10: Configuration Validation Exercise 11: Configuration Validation – Report Directory Software Change Strategies Exercise 12: Software Change Strategies Custom Development Management Cockpit (CDMC) - Change and Transport System (CTS) Analysis Exercise 13: CDMC Change and Transport System Analysis Guided Self-Services/ Transport Execution Analysis

40 Minutes 10 Minutes 15 Minutes 10 Minutes 45 Minutes 15 Minutes

45 Minutes 25 Minutes 35 Minutes

Unit 6: Transport Management with SAP Solution Manager

x


2012

E2E200

Course Overview

Introduction Infrastructure for Change Control Tools Task List Critical Object Cross System Object Lock Retrofit Transport of Copy Unit 7: Quality Gate Management Overview of Quality Gate Management Setup of Quality Gate Management Exercise 14: Setup of Quality Gate Management Project Phases and Quality Gates Exercise 15: Project Phases and Quality Gates Central Transport Management Exercise 16: Transport Management in Quality Gate Management (Appendix) Prerequisites to Set Up Quality Gate Management

2012

15 Minutes 15 Minutes 20 Minutes 15 Minutes 15 Minutes 25 Minutes 15 Minutes 15 Minutes 20 Minutes 15 Minutes 20 Minutes 15 Minutes 30 Minutes 15 Minutes 20 Minutes

Unit 8: Change Request Management Overview Project and Release Management Request for Change Exercise 17: Request for Change Project and Process Types Exercise 18: Normal Change ALM Integration Tools Exercise 19: Reporting (Appendix) Change Request Management

30 Minutes 30 Minutes 30 Minutes 15 Minutes 35 Minutes 30 Minutes 25 Minutes 30 Minutes 20 Minutes 20 Minutes

Unit 9: Maintenance Management SAP Maintenance Strategy Types of Maintenance SAP Enhancement Packages Maintenance Optimizer System Recommendations Exercise 20: System Recommendations Upgrade / Change Impact Analysis

15 Minutes 20 Minutes 25 Minutes 20 Minutes 25 Minutes 15 Minutes 25 Minutes


xi

Course Overview

E2E200

Course Goals This course will prepare you to: • • •

Understand the value of E2E Change Control Management. Describe the concept and methods of E2E Change Control Management. Leverage the SAP Solution Manager as an application platform for E2E Change Control Management.

Course Objectives After completing this course, you will be able to: •

Know to use the capabilities SAP offers to manage Change Control Management.

Important Information It is strongly recommended to check necessary information published on the SAP Service Market Place. All information essential for course preparation like instructor guides, system setup guides, trouble shooting guides, logon information, and so on, you will find under the alias /curr-info (http://service.sap.com/curr-info). In case you cannot access this site please ask the responsible education coordinator (the sender of this document) to make the relevant information available to you.

xii


2012

Unit 1 How To Get Started

1

Unit Overview The SAP Solution Manager is an integrated customer platform that provides the procedures, capabilities and content needed to successfully and efficiently implement, operate and optimize SAP and non-SAP solutions. The purpose of this course is to introduce you to the SAP Solution Manager Change Control Management capabilities delivered with this lifecycle platform in order to understand their usage.

Unit Objectives After completing this unit, you will be able to: • •

Know the training system landscape Understand the SAP Solution Manager portfolio

Unit Contents Lesson: How To Get Started .....................................................2

2012


1

Unit 1: How To Get Started

E2E200

Lesson:

How To Get Started

2

Lesson Duration: 20 Minutes

Lesson Overview Within this chapter we will focus on the environment of the course and the usage rights for the SAP Solution Manager. Furthermore we will look into the education portfolio for the SAP Solution Manager.

Lesson Objectives After completing this lesson, you will be able to: • •

Know the training system landscape Understand the SAP Solution Manager portfolio

Business Example

Figure 1: SAP Solution Manager Functional Baseline for SAP Standard Support Customers

2


2012

E2E200

Lesson: How To Get Started

SAP Solution Manager under SAP Standard Support can be used exclusively for SAP software components. SAP Standard Support Customers receive continuous improvements for the functional baseline (shown on graphic above), including error correction and functions supporting the SAP product strategy. Custom Development Management Cockpit, Business Process Change Analyzer and Quality Gate and many more new scenarios with SAP Solution Manager 7.1, are only available under SAP Enterprise Support.

Figure 2: ALM Capabilities for SAP Enterprise Support Customers

2012


3


E2E200

Figure 3: Run SAP Capabilities for SAP Enterprise Support Customers

Figure 4: End-to-End Change Control Management Certification

4


2012

E2E200


Figure 5: Training Landscape and Architecture

The SMD agents are installed in all managed systems and on the SAP Solution Manager itself. The system RWE serves also as back end for the ESS scenario.

Figure 6: Training Landscape: How to Connect

2012


5


E2E200

Figure 7: Motivation & Benefit of SAP Enterprise Support Academy

SAP Enterprise Support helps customers: Implement Better

Integrated E2E Application Lifecycle Management

Operate Better

Run SAP Like a Factory

Innovate Better

Accelerated Innovation

Academy Value to Customers • • •

6

Deployment best practices training lets customers run most effective, lowest cost operations Proactive implementation of best practices reduces downtime and failure rates Distance learning model reduces customer cost to implement best practices (and SAP Solution Manager)


2012

E2E200


Figure 8: Updated Portfolio of Expert Guided Implementations: SAP Solution Manager 7.1 - Planned EGIs until Q2 2012

This presentations and SAP’s strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.

Figure 9: Available Trainings in Area of ALM & Run SAP like a Factory

2012


7


E2E200

More information you could find in the service market place. Please use the following links: • • • •

8

http://service.sap.com/solutionmanager http://service.sap.com/esacademy http://service.sap.com/changecontrol http://service.sap.com/rkt-solman


2012

E2E200


Lesson Summary You should now be able to: • Know the training system landscape • Understand the SAP Solution Manager portfolio

2012


9

Unit Summary

E2E200

Unit Summary You should now be able to: • Know the training system landscape • Understand the SAP Solution Manager portfolio

10


2012

Unit 2 Introduction to E2E Change Control Management

11

Unit Overview This unit introduces SAP Solution Manager as a platform to support the whole life cycle of SAP and non-SAP applications in your solution landscape. This concept is extended to the idea of application lifecycle management, which SAP Solution Manager supports with a dedicated portfolio of tools, services and methods. The Part of this portfolio, that is relevant for E2E Change Control Management, we will focus on in this course. Within this unit we will give an short overview about the content and goal of this course.

Unit Objectives After completing this unit, you will be able to: •

• • •

Understand the basic principals of Application Lifecycle Management (ALM) and the role of SAP Solution Manager as the central ALM platform of SAP. Understand the E2E Change Control Management roles. Explain the scope of End-to-End Change Control Management. Explain the role of SAP Solution Manager to manage changes in your solution landscapes.

Unit Contents Lesson: Application Lifecycle Management .................................. 12 Lesson: E2E Change Control Management.................................. 23

2012


11

Unit 2: Introduction to E2E Change Control Management

Lesson: 12

E2E200

Application Lifecycle Management Lesson Duration: 20 Minutes

Lesson Overview This chapter will give you an introduction into the challenges within Change Control Management. It explains the different roles and shows how Application Lifecycle Management (ALM) can support you on daily basis.

Lesson Objectives After completing this lesson, you will be able to: •

•

Understand the basic principals of Application Lifecycle Management (ALM) and the role of SAP Solution Manager as the central ALM platform of SAP. Understand the E2E Change Control Management roles.

Business Example You are searching for an integrated platform that provides the procedures, tools and content needed to successfully and efficiently implement, operate and optimize your SAP and non-SAP solutions.

12


2012

E2E200

Lesson: Application Lifecycle Management

Figure 10: Analogy to suboptimal Application Management

This slide should highlight what may happen if Application Lifecycle Management isnt setup properly. It could be treated as a humorous worse case scenario. 1. 2. 3. 4. 5. 6.

7.

Picture 1 shows the initial expectation on business side to get a high end solution for minimum costs Picture 2 shows the result of a meeting where business tried to explain the expected solution to the implementation team Picture 3 shows the designed solution based on their understanding and in addition reflecting some stability aspects Picture 4 shows the solution built by the developer based on his understanding and in addition reflecting functional and stability aspects Picture 5 shows the situation that due to short timeframe there was not enough time to completely document and test the built solution Picture 6 shows the result of mismatch between change management and change execution (transports), so some components/objects hasn’t been deployed Picture 7 shows the result of a missing handover from implementation to operation and missing documentation

Development and support of large and complex software applications can be a nightmare for companies of any size with budget overruns and delivery delays. Also, as potential outsourcing’s risks grow ever greater, the need for control by in-depth monitoring of disruptions and deviations is critical. If corporate data, intellectual property, and business processes are to remain stable, transparency in real time, becomes a necessity. The stability of a company’s outsourcing practice depend on it. Ensure that everything gets done. Efficient Application Lifecycle Management should utilize the capabilities of SAP Solution Manager. Solution Implementation using Application Lifecycle Management with integrated functions: • • • • • •

2012

Use optimized implementation, updates tools and methods Usage of methodology concept and accelerators speed project organization Usage of integrated test scenarios reduce test and training effort Use integrated comprehensive (project) documentation Implement a solution based on SAP best practices and according to SAP implementation methods Ensure smooth and secure go-live


13


E2E200

Figure 11: The Change Management Dilemma

On one hand we have: • • •

The business which expects fast reaction on their demands – new functionality or bug fixes need to be implemented as fast as possible New development has to reach production systems fast Time for testing is limited

On the other side we want: • •

Stable systems which require dedicated processes to control all software related changes Dedicated testing phases

The change management processes must balance both sides – so we are able to deliver changes for the business in time AND in parallel keep the systems stable.

14


2012

E2E200


Figure 12: General Change Management Process: How is the focus set for IT?

The best transport strategy depends on the customer focus. This can be safety, flexibility or cost. There is no single best practice that fits all criteria equally well. If one criterion is very important, then the other two cannot be achieved at the same time.

Figure 13: E2E Change Control Management Roles and Responsibilities

PROVA 2012


15


E2E200

The program management office is the central group in the customer business unit that is responsible for the overall planning, implementation, and continuous improvement of the business processes in the solution landscape. All requests for changes, including Solution Design and Solution Maintenance flow through this office and need to be integrated into a schedule of landscape changes. As such, change request management is a large part of the program management offices activities. This office is responsible for managing everything from day-to-day changes and adoptions to all release planning and major infrastructure technology shifts. In addition, these activities must be aligned with all stakeholders. The key interface between business and IT is the application management organization. End users, key users and the program management office use the services of IT for a wide variety of tasks; from solution landscape planning to implementation, from business unit request handling to execution, from documentation standards, training and certification to management level reporting. Being such a central component, several of the introduced roles use the application management platform as their central working application. It is essential that changes to the solution landscape are managed carefully to ensure transparency. The Change Request Management standard ensures that standardized methods and procedures are used for the efficient and prompt handling of all changes. In addition to Change Request Management, the deployment and the analysis of changes need to be addressed to ensure that changes are executed without disrupting ongoing business. This is the focus of the Change Control Management standard. The standard covers two major areas of change control: Change Deployment and Change Diagnostics for Application and System Changes. Customers need a robust, flexible and comprehensive management solution for both SAP and non-SAP components.

16


2012

E2E200


Figure 14: Most typical challenges of software solution change management

In order to implement, change and run non-SAP components (often based on 3rd party application infrastructure such as Microsoft .net or IBM WebSphere) the same way as SAP components, SAP delivers the capabilities for it. Every customer has mission-critical applications along with integration needs. SAP landscapes become more sophisticated the more comprehensive & integrated they are. To run these landscapes a new set of capabilities is required.

Figure 15: Orchestrate Your Solution with SAP Solution Manager (1)

Optimized solution operations is the key success factor to manage speed of innovation and integration, risk and total cost of operations. This is enabled by SAP Solution Manager Enterprise Edition.

2012


17


E2E200

Figure 16: Orchestrate Your Solution with SAP Solution Manager (2)

•

•

18

At the center of SAP’s integrated ALM approach is SAP Solution Manager, an application management solution that helps you manage and reduce complexity e.g. by providing you with a “single source of truth”. This means you have structured, comprehensive, unified and reliable information about all projects in process, a transparent mapping of your solution landscape and business processes and a real-time view into your state of your productive solutions. By this, you can make informed, fact-based decisions and take actions throughout the application lifecycle. For example, a change manager should be able to tell whether all necessary tests have been successfully completed before approving a shipment for production.


2012

E2E200


Figure 17: Solution Documentation: Technical Landscape Documentation

In the last few years, the IT world of SAP customers has become much more complex. Instead of one single R/3 system there are now extensive system landscapes distributed over the entire globe and involving different SAP solutions. Therefore, it has become much more complicated to keep track of the whole system landscape. If something goes wrong within the solution landscape, it is much more difficult to judge the relevance for other activities. It is, therefore, much more important to have an operational concept for the customers solution landscape.

Figure 18: Solution Documentation in SAP Solution Manager

2012


19


E2E200

There is a business view and a technical view available in the SAP Solution Manager. Generally, many benefits of Solution Documentation could be found: • • •

Proven approach to structure projects according to business scenarios and processes as well as system landscapes Efficient knowledge management – all information of project / solution is saved in SAP Solution Manager Traceability through various types of documentation in the same context: –

• • • • • •

Business requirements, process description, configuration items, development objects, systems, transactions, test objects, test cases, training material, etc. Transparency during implementation, upgrade projects and for ongoing maintenance activities and change management Accelerated set-up of testing and process monitoring reusing the process structure and content Simplifies alignment of business and IT Accelerates internal IT support Allows fact-based decisions about innovation and business process operation Eases collaboration with SAP

Figure 19: Business Change Impact Analysis: Overview

20


2012

E2E200


The goal of the BPCA is to help customers to find out which business processes are affected by planned changes. SAP Solution updates occur frequently: • •

SAP triggered: Support Packages, Enhancement Packages Customer triggered: Customizing changes, Custom code development

The Business Process Change Analyzer requires an object list (TBOM) for the critical core business processes. These lists are determined by an initial trace. They can be compared against the object lists of transport requests in order to find out which core business process is affected by this change.

2012


21


E2E200

Lesson Summary You should now be able to: • Understand the basic principals of Application Lifecycle Management (ALM) and the role of SAP Solution Manager as the central ALM platform of SAP. • Understand the E2E Change Control Management roles.

Related Information • •

22

http://service.sap.com/supportstandards --> Media Library http://service.sap.com/ALM


2012

E2E200

Lesson: 23

Lesson: E2E Change Control Management

E2E Change Control Management Lesson Duration: 25 Minutes

Lesson Overview Highly integrated solution landscapes require a controlled and quality-approved change management process to enable solution operations to be reliable and highly available. Looking at the application lifecycle of SAP-centric solutions it becomes obvious most changes and extensions will be motivated by changes of the application layer. Custom developments and customizing changes are managed via projects and transported from development via test to production systems. These type of changes require a formal quality management process spanning all phases of the application management lifecycle up until the final transport into the production landscape.


Explain the scope of End-to-End Change Control Management. Explain the role of SAP Solution Manager to manage changes in your solution landscapes.

Business Example You are interested in getting an overview about the change control capabilities of the SAP Solution Manager platform.

2012


23


E2E200

E2E Change Control Management

Figure 20: Change Control Management - the whole is more than the sum of its parts

In the today’s distributed environments a spreading change control management plays a crucial role. With standardized processes, methods and tools it ensures throughout for a high transparency and a continuous quality of the change processes during the entire application lifecycle. Change control management coordinates how changes are introduced to a software landscape so that the changes do not conflict with each other and ensure that they are executed without disrupting the on-going business. This results in improved quality of the software landscape, higher availability of IT solutions, and lower total cost of ownership. Also important, change control management ensures that the changes performed remain transparent and traceable.

24


2012

E2E200


Figure 21: Change Control Management Change and Transport System (SAP/ Non-SAP)

The Scope is to establish one tool to transport SAP and Non-SAP objects to gain transparency of all changes.

Figure 22: Enhanced CTS - One Transport Tool for Multiple Content Types

There are boxes showing dots at the right hand side. This suggests that CTS+ can support more than the applications that are named explicitly in the other boxes. There were already additional options like SLD or MDM in the past. But now, CTS+ can do even more. You can get an impression how an integration could be done for those applications.

2012


25


E2E200

Figure 23: CTS+ Transport Landscape - Basic Example

A typical landscape consist of three systems for an application. One system where developments are done, one test system and one which is used productively by end-users. Your landscape might look different. This is just a typical example, not a restriction in CTS. You can also create landscapes consisting of just two or many more systems. To support transports for non-ABAP systems, one additional system is needed where CTS can be used. This system acts as Domain Controller and Communication System for the non-ABAP systems. The content is created or developed in the development system respective the corresponding development workbench. Within the workbench, the developer should find a mechanism to export what he did. During the export, he should have an option to choose a transport request and attach his files directly from within the workbench to this transport request. The availability of this option depends on the application. If it is not available, a manual attachment process might be supported to post the new content to CTS. This would mean that the file is downloaded from the workbench and manually attached to the transport request. After that, a Transport Request can be released and the import can be started. This is done within CTS. For the file types supported by now CTS calls the deployment tool of the application to deploy the new content to the next system in the route. After a successful import into e.g. the Q-system of the application, CTS forwards the transport request to the queue of next system – in this case the productive system. After a successful test, the administrator in CTS could start the import for the productive system. You can use options like schedulers that you might know if you are using CTS with ABAP.

26


2012

E2E200


Figure 24: Change Control Management: Transport Analytics / Configuration Validation

Figure 25: Change Diagnostics Capabilities

Configuration validation is a reporting to understand how homogeneous the configuration of systems is. It uses centrally stored configuration data in Solution Manager to do a validation of a large number of systems using a sub set of the collected configuration data. Setting up Diagnostic capabilities in SAP Solution Manager is a pre-requisite for the availability of this reporting.

2012


27


E2E200

PROVA

Figure 26: CDMC CTS Analysis: Transport Landscape and Typical Usage Scenario

Most SAP customers modify or enhance their SAP standard software in some way. These changes allow customers to tailor solutions to their individual requirements. There are usually a large number of custom development objects in customer systems. Change and Transport Analysis carries out a usage analysis of customer objects in transport requests before the go live of a business release. Change and Transport System Analysis helps the user performing quality checks by doing a usage analysis, environment analysis and remote comparison for a specified object set of requests in the analysis (QAS/Test) system. It gives the list of the objects that were used during the test phase. It also helps to check if the objects in the request are identical across the landscape.

28


2012

E2E200


Figure 27: Transport Analytics & Configuration Validation From Analysis to Reporting & Optimization

The Transport Execution Analysis Service is a wizard-based self service in SAP Solution Manager. Typical questions answered by the SAP Transport Execution Analysis: • • • •

2012

How many transport requests caused errors in the production environment? How many emergency changes have been executed? What are the transport backlogs in the development and production system? How consistent is my transport landscape?


29


E2E200

Figure 28: Change Control Management: Transport Management with SAP Solution Manager

The Scope of transport management with SAP Solution Manager is to establish one tool to manage transport via SAP Solution Manager and manage and control the transport activities via phases of your project.

Figure 29: Transport Management with SAP Solution Manager: Central access to Transport Information

By taking advantage of transport management with SAP Solution Manager you can manage all transport activities via SAP Solution Manager. You are hereby enabled to use the following features centrally: CTS+, transport of copies, reporting, critical objects, cross-system object lock and retrofit.

30


2012

E2E200


Figure 30: Transport Management with SAP Solution Manager: SAP Transport Best Practices

Figure 31: Change Control Management: Quality Gate Management

2012


31


E2E200

Figure 32: Introducing Quality Gate Management

Figure 33: Change Control Management: The whole is more than the sum of its parts

32


2012

E2E200


Figure 34: Introducing Change Request Management

Figure 35: Introducing Change Request Management

2012


33


E2E200

Introducing Change Request Management supports you within the following areas: • • • • • • •

Provides full control & transparency over change execution. Delivers predefined change management processes & workflows. Supports all types of changes: (SAP, non SAP, technical & non-technical). Incorporates SAP’s best practices regarding transport management. Provides the link between business requirements and the underlying technical implementation. Fully integrated transport mechanism and change control system to manage changes across technology stacks and application components. Is highly integrated in other SAP Solution Manager areas and processes.

Figure 36: Change Control Management: Maintenance Management

Maintenance Management supports the customer in planning and implementing the available SAP software updates. Tools and procedures are in place to eliminate known side-effects, estimate the impact on custom code and minimize the downtime. There is a clear differentiation between bug fixes and new functionality which is delivered in enhancement packages and support packages.

34


2012

E2E200


Figure 37: Maintenance Management: Process View

Maintenance Management supports the customer in planning and implementing the available SAP software updates. Tools and procedures are in place to eliminate known side-effects, estimate the impact on custom code and minimize the downtime. There is a clear differentiation between bug fixes and new functionality which is delivered in enhancement packages and business packages.

Figure 38: Maintenance Optimizer (MOPZ) Plan, Manage and Carry out all Maintenance Activities

The maintenance optimizer is the central application for all software maintenance activities in a system landscape.

2012


35


E2E200

maintenance optimizer supports all maintenance types: • • • • • • •

Enhancement Package (EHP) installation. Support Package installation. Upgrade. Legal Change Package installation for SAP ERP HCM Solutions. HR Support Packages. Support of SAP Add-ons. Support of Java Patches.

The maintenance optimizer provides a powerful automatic delta calculation feature to ensure all needed maintenance files will be downloaded as well as a user-friendly and easy-to-use guided procedure for the handling of all maintenance activities

PROVA

You can find further information about the Solution Manager Maintenance Optimizer at service.sap.com/solman-mopz, detailed documentation at help.sap.com –> SAP Solution Manager –> (select your preferred language) in the “Change Management” section.

Figure 39: Secure your System with System Recommendations

To keep your SAP systems up-to-date and secure you have to apply various types of notes and patches. System recommendations shows all relevant and patches for the selected systems and helps you to easily keep all of your systems up-to-date. It provides a detailed recommendation of SAP notes and non-SAP notes which should be implemented, based on the actual status of the system and already implemented notes and enables customers to validate there system landscape regarding the implementation status.

36


2012

E2E200


The course content will be: Day 1

Introduction to E2E Change Control Management

Day 1

Solution Documentation in SAP Solution Manager • • •

Day 2

Change and Transport System • •

Day 2/3

Configuration Validation Software Change Strategies CDMC CTS Analysis Transport Execution Analysis Self Service

Transport Management with SAP Solution Manager •

Task List, Cross System Object Locking and Retrofit

Day 3/4

Quality Gate Management

Day 4

Change Request Management

Day 5

Maintenance • • •

2012

CTS for ABAP CTS for Non ABAP

Reporting and Analysis Tools • • • •

Day 3

Landscape Maintenance Business Process Documentation BPCA analysis

Support Packages and Enhancement Packages Maintenance Optimizer System Recommendations


37


E2E200

Lesson Summary You should now be able to: • Explain the scope of End-to-End Change Control Management. • Explain the role of SAP Solution Manager to manage changes in your solution landscapes.

38


2012

E2E200

Unit Summary

Unit Summary You should now be able to: • Understand the basic principals of Application Lifecycle Management (ALM) and the role of SAP Solution Manager as the central ALM platform of SAP. • Understand the E2E Change Control Management roles. • Explain the scope of End-to-End Change Control Management. • Explain the role of SAP Solution Manager to manage changes in your solution landscapes.

2012


39

Unit Summary

40

E2E200


2012

Unit 3 Solution Documentation in SAP Solution Manager

41

Unit Overview Companies need to model their business processes and keep their system landscape up to date within SAP Solution Manager. The business process could have already been modeled with other modeling tools. Companies could also use the reverse engineering approach as basis for process modeling in SAP Solution Manager. This unit introduces how solution documentation standard with SAP Solution Manager 7.1 can support SAP customers to model their business processes and keep them up to date.

Unit Objectives After completing this unit, you will be able to: • • • • • • • • •

2012

Describe the Solution Documentation process. Describe the different types of documentation and what they are used for. Explain the Architecture and Use Cases of the Solution Manager System Landscape Documentation. Describe how to keep the Solution Landscape Documentation up to date. Define a project in SAP Solution Manager using transaction solar_project_admin. Assign the technical landscape to a Solution Manager project. Use the Business Process Repository (BPR) as template to document core business processes. Assign additional information to individual business process steps. Define a new solution in SAP Solution Manager and transfer business process documentation to it.


41

Unit 3: Solution Documentation in SAP Solution Manager

• • • • • •

E2E200

Describe best practices to tailor solutions in SAP Solution Manager. Describe Reverse Business Process Documentation (RBPD) with the Solution Documentation Assistant. Describe the different possibilities for modelling business processes using new offline tools with interfaces to SAP Solution Manager. Get an overview about SAP’s methodology for testing and how it is used in SAP Solution Manager. Determine the change impact with the Business Process Change Analyzer. Get known the Test Management Work center.

Unit Contents Lesson: Introduction ............................................................. 43 Lesson: Technical Landscape Management with LMDB ................... 51 Exercise 1: Technical Landscape Description ........................... 67 Lesson: Managing Projects with SAP Solution Manager ................... 70 Exercise 2: Create a Project ............................................... 83 Lesson: Managing Solutions with SAP Solution Manager ................. 87 Exercise 3: Business Processes .......................................... 95 Exercise 4: (Optional) Transfer Project Documentation to Solution .101 Lesson: Reverse Business Process Documentation and Modelling Tools ..............................................................................105 Lesson: Business Process Change Analyzer ...............................122 Exercise 5: Business Process Change Analyzer.......................147

42


2012

E2E200

Lesson: 43

Lesson: Introduction

Introduction Lesson Duration: 15 Minutes

Lesson Overview Within this lesson you will get an overview about the different areas of solution documentation and the possibilities of reusing it to leverage Application Lifecycle Management.


Describe the Solution Documentation process. Describe the different types of documentation and what they are used for.

Business Example You like to implement a new application, solution or business function and want to document all relevant information in SAP Solution Manager.

Motivation for Solution Documentation This ALM process addresses all challenges when you want to document your technical landsacpe and the business processes running on these systems.

2012


43


E2E200

Figure 40: Application Lifecycle Management: Requirement-to-Deploy Scenario with SAP Solution Manager

What are the main goals of Application Lifecycle Management? Business continuity, accelerating innovation, and reducing risk as well as total cost of operations while protecting your investment, is the key challenge for each CIO. Accelerated innovation •

Reduced cost of implementation projects and operations, plus higher stability – – – –

44

Advantages in project allocation and solution operations React flexibly to market requirements and competitive situations, tangible evaluation of improvement potential (benchmarking) Profit from new business processes of next release Maintain competitive advantage by surgical investments into target areas of improvement identified by benchmarking


2012

E2E200


What are the main challenges for IT organizations regarding ALM? •

•

•

A conflicting goal is to deploy required changes without disrupting the ongoing business processes. Therefore, Its not enough to focus on operations of your business. You have to focus on the entire Application Management Lifecycle. In addition, there is the wish of the business that you deploy the changes on the latest technology with a fast time to market (Accelerated Innovation) and with high quality (Integration Validation) – again two conflicting challenges. Safeguard the superior quality of the service provided by customers IT organization – –

•

main goals of With SAP Solution Manager nearly the entire process is supported by tools. – – – – – –

2012

Less problems by built-in best practices and proactive quality checks (avoid trial-and-error approaches) Standardization of customer implementation, quality management and operations (including diagnostics)

Application

Requirements and Change Management can be handled by ITSM Lifecycle functionality. Management Business Blueprints can be created from transaction SOLAR01 and the Configuration within the build phase will be reflected by transaction SOLAR02 Impacts of changes for semi-autonmated regression testing is supported by Business Process Change Analyzer (BPCA) Tests can be managed by Test Workbench in SAP Solution Manager. The deployment together with the end user trainings and hand-over into production is supported by Solution Directory (transaction SOLMAN_DIRECTORY)


45


E2E200

Figure 41: Solution Documentation Motivation

Why is Solution Documentation important? • • • • •

46

Get a common understanding on business processes Accelerate search for information Training of new employees and rollouts of new functionality Foundation for bugfixing and later process enhancements Basis for End to End Solution Operations


2012

E2E200


Solution Documentation contains 3 types of documentation: 1.

Technical Landscape Documentation • •

2.

System, server, database and software component documentation Maintenance done by:

– system administrators – technical SAP Solution Manager experts Business Process Documentation • •

Documentation of Core Business Processes and related interfaces Maintenance done by: – – –

3.

solution architects, e.g. for interface specifications business process experts, e.g. to document (core) process flow project members, e.g. to document test cases and project specific customizing – functional SAP Solution Manager experts, e.g. for simple transfer if good process documentation is available Custom Code Documentation • •

Documentation of Custom Code objects and Modifications Maintenance done by: – –

2012

solution architects, e.g. for custom developments Project members, e.g. document custom developments in business scenarios


47


E2E200

Figure 42: Documentation Types How to get a Minimum Documentation and fully exploit the Value

48


2012

E2E200


Depending on which capabilities you want to use, different requirements exist regarding documentation. •

•

•

•

•

•

2012

The Figure shows the three fundamental kinds of documentation and the functions they enable. Technical Landscape Documentation, Business Process Documentation and Custom Code Documentation. The technical landscape documentation (sector 1) is already covered by the basic configuration of SAP Solution Manager in its minimum required level. The documentation comprises of the availability of system data of all productive systems in the System Landscape Directory and the availability of one or more solution landscapes which contain the productive systems as logical components. A complete technical landscape documentation is essential for using other SAP Solution Manager functions like System Monitoring, Diagnostics or Change Request Management. Business Process documentation (2) (including the documentation of interfaces) comprises of the availability of all your core business process in the Business Blueprint and imported into the Solution Directory. If you document your core business processes in a Business Blueprint you can use this information not only when support is needed but throughout the entire software Lifecycle. This increases the value of internal communication as there is always a relation to business processes, i.e. the relevance of a requirement or problem is always visible. You can re-use the documentation of business processes for example with the following SAP Solution Manager processes: Test Management, Business Process Monitoring and Interface Monitoring, Job Scheduling Management, Upgrade and Maintenance Projects and Issue and Top Issue Management 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 they are executed on, a list of the transactions or other entry points as URLs or background jobs which are called via actions, and used interfaces. The third kind of documentation is the documentation of custom developments. Custom Code documentation (3) comprises of a short description of the development and its related development objects, e.g. programs in the customer name space. This documentation is especially important for the following reasons. First of all, modifications are not subject to SAP quality checks. Secondly, they can be lost in an upgrade when implemented improperly. Thirdly, the actual usage is often not checked after some time but modifications cause unnecessary maintenance cost and performance losses as so called “dead coding”.


49


E2E200

Lesson Summary You should now be able to: • Describe the Solution Documentation process. • Describe the different types of documentation and what they are used for.

50


2012

E2E200

Lesson: 50

Lesson: Technical Landscape Management with LMDB

Technical Landscape Management with LMDB Lesson Duration: 25 Minutes

Lesson Overview This lesson will describe how to document your technical system landscape with the new LMDB in SAP Solution Manager 7.10


Explain the Architecture and Use Cases of the Solution Manager System Landscape Documentation. Describe how to keep the Solution Landscape Documentation up to date.

Business Example You want to document all technical systems belonging to your landscape and keep the information up to date automatically.

2012


51


E2E200

Technical Landscape Management with LMDB

Figure 43: Solution Documentation: Technical Landscape Documentation

In the last few years, the IT world of SAP customers has become much more complex. Instead of one single R/3 system there are now extensive system landscapes distributed over the entire globe and involving different SAP and non-SAP solutions. Therefore, it has become much more complicated to keep track of the whole system landscape. If something goes wrong within the solution landscape, it is much more difficult to judge the relevance for other activities. It is, therefore, much more important to have an operational concept for the customers solution landscape.

52


2012

E2E200


Figure 44: Landscape Data Distribution in a Typical Landscape: Topology in Detail

2012


53


E2E200

General Topology Details •

LMDB gathers landscape data from SLD systems in productive and non-productive landscape areas. –

• •

•

In Solution Manager 7.1, LMDB leads: It retrieves & enhances SLD data, providing it to client applications – In SAP Solution Manager a better synchronization mechanism with the SLD is provided; a local SLD is not needed in most scenarios – SMSY also reads LMDB, getting data incrementally when changes happen, providing it to its client applications All data suppliers report to the central SLD (note that in a dual stack system both AS need to report separately). From the SLD used in the design time area (if for example PI is used) development data (such as business systems, Products and SCs) are exported and transported in to the central runtime SLD preferably using CTS+ Central SLD provides data for other SLDs and LMDB: – – –

By forwarding technical systems data to all other SLDs By an unidirectional full automatic sync to LMDB Optionally, by a bidirectional full automatic sync to hot-backup SLD (for this scenario, a virtual IP address is used to access the SLD) Note: Note that to set up a full automatic sync connection the target SLD needs to be on SAP NetWeaver 7.1 or higher; LMDB behaves as such an SLD and can therefore read data from an SLD as of SAP NetWeaver 7.0 SP12 (recommended: SLD of SAP NetWeaver 7.1 or higher for quicker updates in case of changes providing notifications)

Data Flow from SLD & SMSY to LMDB – Data Sync from LMDB to SMSY: •

LMDB stores data from SLD and SMSY (automatically or manually created) and allows manual creation of Technical Systems, which are then synced into SMSY –

“New” Technical Systems data: – – – –

All data delivered by data suppliers to the SLD or created there are stored in LMDB. New technical systems that need to be created manually, are created in LMDB. SAP Solution Manager System Landscape (SMSY) does not directly access SLD data but gets LMDB only. Reading system data via RFC: Only recommended if no data supplier is available.

54


2012

E2E200


The system needs to be created manually in LMDB, to be synced into SMSY and completed with data remotely. –

“Legacy” Technical Systems data (data migration): –

–

LMDB reads system data that is not handled by the SLD or manually created in LMDB from SMSY. – Migration of SMSY data is typically done once after the installation. – SMSY gets all technical system’s data from LMDB and allows creation of product systems. Product Systems: Created in SMSY or in wizard-based landscape verification tool. – –

•

All product system types can be maintained in SMSY. Product systems for technical system types AS ABAP and AS Java can be verified later or directly created in landscape verification product system editor. SID and extended SID are used to identify systems in the landscape In the SLD technical systems with identical SID are distinguished by their DB Host . – In the SAP Solution Manager (SMSY) the extended SID was used for that purpose. – LMDB extends SIDs sent by SLD when needed, and offers ExtSIDs at system creation. Extended SID = SID + 5 char suffix (optional, only used if needed)

–

•

– – –

Allowed characters in the SID: A-Z, 0-9 in any sequence Allowed characters in the Suffix: A-Z, 0-9, “_” Automatically generated prefixes consist of 5 digits including leading zeros (e.g. ABC00001) Hint: To find managed systems in the SAP Solution Manger, you need to use wildcards

Special cases: – – – –

ABAP and JAVA: The Extended SID must begin with the SID TREX System: If no SID is found in the caption, the SID defaults to “TRX” Introscope Standalone Enterprise Manager & Introscope Enterprise Manager Cluster: The Extended SID always starts with “WLY”

There is no valid case for a system in LMDB to have no extended SID.

2012


55


E2E200

Data Synchronization from LMDB into SMSY: •

Data synchronization from LMDB into SMSY is done automatically –

Prerequisites: – –

•

LMDB basis configuration has been performed A SOLMAN-Batch-user is used (e.g. SOLMAN_BTC), created in SOLMAN_SETUP

Functions: –

Synchronization from LMDB to transaction SMSY is automatic and unidirectional if : –

–

Automatic synchronization of changes, which come via the SLD: If changes from SLD are written into LMDB, this goes to LMDB change log. Changes for all data are written into SMSY after 5 minutes. Automatic synchronization of changes, done manually in the Technical System Editor in the LMDB.

Data Migration from SMSY into LMDB: •

Data migration from SMSY into LMDB should only be done for Technical Systems without data supplier, and only once after the initial configuration –

Prerequisites: – –

–

LMDB basis configuration has been performed Automatic synchronization of changes, done manually in the Technical System Editor in the LMDB Functions: –

–

Migrates Technical Systems from SMSY into LMDB for system types AS ABAP, AS Java, MDM, and Unspecific – Available via SOLMAN_SETUP → System Preparation → Prepare Landscape/Setup LMDB – Migration is done on a single system basis Best Practices: – – –

If possible, use SLD Data Suppliers if available. We recommend that you select only those Technical Systems that are still used Filter for manually created systems (all other should be sent to LMDB via the SLD)

Manual Creation and Editing Technical Systems in LMDB: •

Prerequisites: –

56

LMDB has been set up


2012

E2E200


– •

User with change permissions in LMDB: SAP_SYSTEM_REPOSITORY_ALL Best Practices: Avoid manual creation and editing whenever possible

–

–

If systems need to be created manually, do it in LMDB, which supports more system types than the SLD (SMSY does not allow Technical System creation any longer) If a Technical System is changed, all attributes of the affected CIM Class are locked for automatic updates from the SLD – this requires detailed model knowledge, so: – – – –

• •

•

•

• • •

•

2012

We recommend to avoid changes of Technical System data Host data are handled the same way as Technical Systems’ data Product System assignment should not be done in the SLD – use SMSY or landscape verification tool (accessible via the LMDB). Also see Note 1291187 - Products installed in SMSY and SLD

The content of the SLD must be updated regularly. At SAP site, a Master Component Repository mirrors the data from the SAP Product and Production Management System (PPMS). Therefore, the Master Component Repository contains up-to-date information about all available SAP products and their dependencies. The content of the Master Component Repository is published in the SAP Service Marketplace, so that customers can update their individual component information. The content updates are available as delta files (see note 669669 for details) Customers can add additional information, about 3rd-party products that they are using and their own development activities, to their individual component information in their own System Landscape Directories. The landscape description contains information about all systems and installed products or components at the customer’s site. Applications and tools (installation, administration etc.) use information from the System Landscape Directory as a central information provider. Based on proven industry standards of the Distributed Management Task Force (DMTF): – Common Information Model (CIM) – Web-Based Enterprise Management (WBEM) You can access SLD by directing a browser to http://:/sld (where is the SLD server and is the J2EE HTTP port). You will be prompted for a user name and password.


57


E2E200

Figure 45: Information Stored in the SLD

The SLD is part of the J2EE Engine and can be reached using: http://:/sld. It contains the following parts: •

Landscape descriptions – – –

Technical Systems Landscapes Business Systems

Business systems are logical systems that act as senders or receivers within the SAP NetWeaver Exchange Infrastructure. A Business System is always associated with a technical system. • •

Component Information Name Reservation – –

58

Namespaces (done only by administrators) Single names (done only by administrators – developers perform this task in the SAP NetWeaver Developer Studio)


2012

E2E200


Figure 46: How Does SLD Get Landscape Description Data?

• • • •

•

2012

Each SLD server contains an SLD data bridge, which is capable of sending system data received from the Data Supplies to multiple SLD servers. The system information is reported periodically as well as at system startup. The data supplier within an ABAP-based system periodically delivers collected system information to SAP Gateway (additionally required). Data suppliers are available for ABAP-based systems as of release 4.0B (SAP_BASIS/SAP_ABA). A SAP Gateway routes information to SLD bridge (part of SLD) and a SLD bridge transfers this information (as CIM-compliant data) to SLD. The SLD can collect automatically data from ABAP, J2EE, C++ and .NET based installations


59


E2E200

During the basis configuration of a new SAP Solution Manager the SMSY will be connected to the LMDB. The following connections have to be established: •

SLD Clients –

•

Configure the SLD Data Supplier (in an ABAP system) by calling transaction RZ70 and maintain the gateway server host and the name of the gateway service. – Configure the SLD Data Supplier (in a J2EE system) Start the J2EE Engine Visual Administrator and navigate to Administration → Server → Services → SLD Data Supplier. SAP Solution Manager –

•

Connect LMDB to Solution Manager (Covered by Basic Setup of Solution Manager). SLD Server

–

• •

Activate the SLD Server Call up the SLD initial page http://:/sld and choose Administration → Server Settings. Enter a name for the Object Server. Import the SAP Master Component information Choose Administration → Import and select the file CR_content.zip Specify Service for Communication (JCo RFC Provider) From the J2EE side, /usr/sap/JCXX/J2EE/admin/go or go.bat, Visual adminServer → Services → Jco RFC Provider.

Figure 47: Access Landscape Management Database (LMDB)

60


2012

E2E200


With SAP Solution Manager 7.1 handling of landscape data is changed: •

•

In the center of all applications handling such data is the newly created Landscape Management Database (LMDB) running as a part of the SAP Solution Manager LMDB integrates with the System Landscape Directory (SLD) in productive and non-productive landscape and SMSY and landscape verification tool to gather landscape data and provide it to client applications in the SAP Solution Manager

The Landscape Management Database (LMDB) shall provide an infrastructure for centralized landscape data management in the SAP Solution Manager. The Landscape Management Data Base (LMDB) can be access via the workcenter: Solution Manager Administration -> Landscape. You can browse the technical information for a single product system or display the status information of the last data collection. The Technical System Editor can also be accessed via the transaction LMDB.

Figure 48: LMDB: Technical System Editor

For the current LMDB setup guide please go to:

2012


61


E2E200

http://service.sap.com/solutionmanager → Media Library → Technical Information. •

The LMDB is the central tool to handle landscape data in the SAP Solution Manager. The LMDB retrieves data from the SLD by full automatic synchronization. The content retrieved includes all SLD data (CIM/CR content, technical systems data, and manually created data such as business systems, manually created products, software components, etc.).

• Note: Exactly one SLD needs to be assigned to the LMDB for this content. •

Both SLD and LMDB are based on CIM* standard. They store: –

The CIM-based data model – –

–

–

–

Basis for interpretation of all data Provided and updated by SAP on SMP * Common Information Model, as defined by DMTF (Distributed Management Task Force) The software catalog (all installable software) based on CIM Data – Basis for interpretation of software state of technical systems – Provided and updated by SAP on SMP – Enriched by customers & partners of SAP The technical systems (available systems in an IT landscape – host data and software state) based on the Software Catalogue – Basis for business processes – Systems registered at the SLD (in some cases created manually) Data entered manually (business systems, landscapes) –

•

62

Systems’ data used in system communication (SAP NetWeaver PI and Web Dynpro Java) – System groups for administration purposes – Product / product system assignment is → done via LMDB calling SMSY and landscape verification Information about the SLD and corresponding documentation containing blogs discussing SLD related topics in detail, mostly showing system demos you will find under: http://sdn.sap.com/irj/sdn/nw-sld.


2012

E2E200


Figure 49: Solution Manager Data Model (CIM Model)

This slide shows the main data model object types used in SAP Solution Manager scenarios. Definitions: •

•

•

Product: Used in SAP solutions. Generally speaking, a product fulfills business requirements. A maintenance period is defined for a product. Examples: SAP NetWeaver, SAP ERP. SAP ERP has several usages such as HR or FI. Product Version: A concrete release of a given product. It bundles together software component versions made available at the same time for implementing a well defined scope of functionality. A product has versions (releases) consisting of Software Components. Examples: SAP ERP 6.0, SAP NetWeaver 7.0 Product System (formerly named System): A group of Technical Systems, on which one version of each contained product is installed. In one Product System there can be only one ABAP-based Technical System and zero or more non-ABAP Technical Systems – Example: SAP CRM 7.0 Technical System (formerly named System Component for non-ABAP Systems): Runtime environment, which executes SAP applications. Identified with a System Identifier (SID). Must be assigned to a Product System explicitly, manually. –

•

–

•

2012

A technical system could be running on one or more hardware boxes and has one database instance that is shared between the parts of the systems running on different boxes. Logical System: A specific client on an ABAP-based technical System


63


•

•

•

•

E2E200

Technical Usage: A grouping in PPMS, that is used to bundle together dependent product instances as part of a Product. Not all SAP products have this additional grouping. For ERP, technical usages are mapped to business functions and thus are used for translating business needs into technical entities. Examples: Strategic Enterprise Mgmt, HCM Self Services, Financials Contract Accounts and Leasing Product Instance (formerly called Main Instancein SMSY, Instance or Software Unit in SLD): A part of a product version and the smallest elements for designing system landscapes. It groups technically dependent software component versions, which have to be installed and operated on a single technical system. The different product instances of a product version could be installed on different or on the same technical system. One product instance is always installed on one technical system (it cannot span more than one technical system). Examples for Product Instances: AS ABAP, AS Java, SAP ECC Server, Trex, SAP NW Enterprise Portal. Software Component (SC): Reusable component of the product from a production view: Unit of product upgrade or update / support package (one or more SCs). A single SC may require other SCs. Examples: SAP_BASIS, SAP_HR Landscape Patterns: Describe the use of a technical system in product systems. –

•

64

Hub: Technical system used by more than one product systems (Example: a SAP NetWeaver Enterprise Portal (EP) used by the SAP HR and SAP CRM product systems) – Sidecar : Technical system used in only one product system, but not running on the ABAP stack. A Logical Component is an administration unit, which uniquely assigns logical systems to system roles for a Product Instance throughout the system landscape and across projects in SAP Solution Manager It is defined that process steps can only run on Logical Components. On the other hand, a business process step can be executed on implementation relevant Product Instances. Therefore, you can have one Logical Component for every implementation relevant Product Instance of a product. For example, we can have the Logical Component Z_ERP, defined for Product SAP ERP, with Product Version 6.0 and Product Instance ECC Server containing the three (logical) systems R3D client 100, R3Q client 200 and R3P client 300 with the roles of Development, Quality and Productive respectively.


2012

E2E200


Figure 50: Transaction SMSY: Software and Hardware Inventory

For definitions of Products, Product-Versions, Systems, Logical Components, Product Instances please find further info under: http://service.sap.com/supportstandards -> Media Library -> Solution Documentation.

2012


65


E2E200

Figure 51: Transaction SMSY: Software and Hardware Inventory

•

Data retrieved for ABAP systems:

•

– System name and number – Message server – Clients (information from client table T000) – Installed software components, releases, and patch levels – Instances of the system – Servers assigned to the instances – Server data – Databases of a system – Server of a database – License keys from system Data retrieved for JAVA systems: – – – – – – – – – –

66

System name and number. Message server. Installed software components, releases, and patch levels. Instances of the system. Server nodes. Servers assigned to the instances. Server data. Databases of a system. Server of a database. License keys from system.


2012

E2E200

65


Exercise 1: Technical Landscape Description Exercise Duration: 10 Minutes

Exercise Objectives After completing this exercise, you will be able to: • Find software version information about a customer landscape in SAP Solution Manager.

Business Example RWS is the Solution Manger system that contains all information about the system landscape. RWE is a managed system which is connected to RWS.

Task: Call transaction SMSY or LMDB to find information for the SAP ERP system RWE. 1.

What is the current Support Package Level for the software component SAP_APPL? Answer: _____________________________________________________

2012


67


E2E200

Solution 1: Technical Landscape Description Task: Call transaction SMSY or LMDB to find information for the SAP ERP system RWE. 1.

What is the current Support Package Level for the software component SAP_APPL? Answer: _____________________________________________________ a)

Transaction SMSY: In the tree structure on the left hand side of transaction SMSY, drill down into Landscape Components → Product Systems → SAP ERP → RWE → SAP ECC Server. On the right hand side, choose the tab Software Components. Search for the software component SAP_APPL and check the SP Level.

b)

Transaction LMDB: Call transaction LMDB → select Application Server ABAP (ABAP) and System ID RWE in tab Technical System. Afterwards select the button “Display”.

Figure 52: Technical System Editor- Entry Screen

In the tree structure on the left hand side drill down into Software. On the right hand side, choose the tab Software Component Versions. Search for the software component SAP_APPL and check the SP Level.

Figure 53: Technical System Editor- Display

68


2012

E2E200


Lesson Summary You should now be able to: • Explain the Architecture and Use Cases of the Solution Manager System Landscape Documentation. • Describe how to keep the Solution Landscape Documentation up to date.

2012


69


Lesson: 68

E2E200

Managing Projects with SAP Solution Manager Lesson Duration: 15 Minutes

Lesson Overview This lesson will describe how to document Business Processes in SAP Solution Manager for a new project. In the Project Administration, you can create a project by defining the system landscape for the individual project phases and specifying the project scope and standards. In the Business Blueprint, you create or enhance the project structure for your company-specific business processes. By separating your business scenarios, business processes, and process steps, you can assign transactions, business functions, and the relevant documentation to the structure items. A possible source of business scenarios is the Business Process Repository. Based on the process requirements from the project structure in the business blueprint, you configure the individual structure items for your business scenarios in the development systems and document these steps. Now you are able to reuse these processes e.g. during the different test phases.

Lesson Objectives After completing this lesson, you will be able to: • • • •

Define a project in SAP Solution Manager using transaction solar_project_admin. Assign the technical landscape to a Solution Manager project. Use the Business Process Repository (BPR) as template to document core business processes. Assign additional information to individual business process steps.

Business Example A new HCM business scenario should be implemented at customer side. The complete documentation for that project shall be done with SAP Solution Manager.

70


2012

E2E200

Lesson: Managing Projects with SAP Solution Manager

Managing Projects with SAP Solution Manager

Figure 54: Solution Documentation: Business Process Documentation

Main tools for Business Process Documentation delivered with SAP Solution Manager are: • • •

2012

Business Blueprint Solution Configuration Solution Documentation Assistant


71


E2E200

Figure 55: Solution Manager Projects

A project in the SAP Solution Manager serves like an umbrella to bundle information and functionality which are necessary for implementation, maintenance upgrade or rollout activities. You can create different types of projects and assign system landscapes to them.

72


2012

E2E200


Figure 56: Reuse of Solution Documentation: Reuse of processes and related information in SAP Solution Manager capabilities

•

• • •

•

•

The business scenario is a collection of business processes in regards to organization or other aspects. The definition of such scenarios have impact on the definition of templates. The template will be then used to populate the information to rollout projects. The business processes designed in the design phase will have impact on the configuration of those processes. The business process structure can be also taken as a basis structure for the testing purposes. Alternatively it can be changed in sequences. Also business process monitoring is relying on the business process design. Based on the threshold, the alerting will be presented in the monitoring graphical overview area. The business process step is the smallest granularity in the design will be re-used with all his assignments (transaction, documents, developments) to document the customization, building the testing (transaction as a test object; test documents as test cases) and in operate as a smallest granularity to specify alerts. Process Structure: It is recommended to assign all relevant documentation to the business process steps. Such a documentation could be: – – – –

Technical/Functional Specifications Process/Step Descriptions Configuration/Development descriptions Test Cases

Configuration/developments: It is recommended to document configuration and developments needed for a business process step. Assigning the information in SAP Solution Manager you create a central point of information for the business processes. The configuration objects can be assigned to person responsible. With this information the configuration and development of the managed system can be done by entering customizing/development objects from SAP Solution Manager centrally. •

2012

Interfaces: It is recommended to document all interfaces relevant to at least core business processes. This information of interfaces can be done already in project blueprint phase together with business process design.


73


E2E200

Figure 57: Scope of Projects

SAP Solution Manager supports all phases of an Implementation Project. In this example, the project works on the ERP and CRM system. The complete transport landscape is part of the project.

Figure 58: How to Document Your Solution in SAP Solution Manager?

74


2012

E2E200


Innovation Management involves the identification, adaptation and implementation of new and enhanced future-proof business and technical scenarios. With SAP Solution Manager you can document all information within an Implementation Project and later transfer this information to Solution •

Key features during the phases of Application Lifecycle Management are: – – – – – –

2012

REQUIREMENTS: Provide information regarding available possibilities DESIGN: Administer your implementation project DESIGN: Define your specifications (Business Blueprint) BUILD: Configure the application such that they realize the specification BUILD: Document custom developments The Phases TEST and DEPLOY are covered by separate ALM processes


75


E2E200

Figure 59: Step 1: Create a Project: (Transaction SOLAR_PROJECT_ADMIN)

• • •

76

Any existing projects are displayed in the project overview of Solution Manager. Additional functions are available to coordinate the project administration data of a project. Transaction SOLAR_PROJECT_ADMIN provides an overview of the active projects in the customer organization. Alternative: You can use Workcenter: Implementation/Upgrade → Plan → Create or Maintain Project


2012

E2E200


You can enter the following data on the General Data tab: •

•

Person responsible - The responsible person must exist in the project administration of the SAP System. You can use the possible entries help to change the responsible person. Project language –

• • •

When you choose a project language, all language-dependent information for this language (project documentation and status information) is made available to project members. This is independent of the logon language of the project member. – The project structure is created in the specified project language. – All content will be stored in the chosen project language. – Once the project language has been selected and saved, it can no longer be changed. Status - The default values for status are set on the Project Standards tab. Plan Data - This tab allows you to enter the dates for the planned project start and finish as well as the work required in man days (MD). Actual Data - This tab allows you to enter the dates of the actual project start and finish and the actual work carried out in man days (MD). –

2012

The planned data and the actual data represent the time plan for the entire project. Any dates entered for individual process steps in the Business Blueprint or Realization phases must lie within the time frame set on the General Data tab.


77


E2E200

Figure 60: Business Blueprint Structure Structure Levels - Example

•

•

Definition of the Business Blueprint allows you to document the business processes, in your enterprise, that you want to use in your SAP System. You create a project structure in which relevant business scenarios, business processes and process steps are organized in a hierarchical structure. You can also create project documentation to assign to individual scenarios, processes or process steps. To define how your business processes should run in your SAP Systems, you then assign transactions to each process step. Definition of the Business Blueprint provides you with a detailed description of your business processes and system requirements. You can also print out the Business Blueprint document. The project documentation and the project structure that you use during the Business Blueprint phase, can also be put to further use during configuration and test organization. –

– –

78

When you configure your business processes, the system displays the project structure you created for the Business Blueprint. You can use the Business Blueprint project structure as an orientation point during configuration. You can also display and edit the project documentation from the Business Blueprint phase during configuration. The project structure from the Business Blueprint forms the basis for all test plans that you create during test organization. The transactions that you assign to process steps in the Business Blueprint are put in test plans during test plan generation. The transactions can be processed as function tests to test the transactions.


2012

E2E200


Figure 61: Step 2: Model the Business Process (Transaction SOLAR01)

One example how SAP Solution Manager supports the solution implementation process is the implementation content. •

The Business Process Repository (BPR) in SAP Solution Manager provides predefined implementation content for all the applications and solutions in SAP Business Suite. –

–

– –

2012

It includes the business scenarios and processes supported by the respective application, relevant business descriptions, assignments to SAP functions in the form of transactions and URLs, for example, as well as settings for configuring the business processes. The implementation content portrays an SAP application or industry solution, allowing you to familiarize yourself with the details of a given solution. Building on this content in your project reduces the time and effort you spend on implementing and tailoring the solution as part of an upgrade project, for example. Therefore Business Process Repository (BPR) serves as starting point for business process documentation. Technically the BPR is delivered within SAP software component ST-ICO in SAP Solution Manager.


79


E2E200

Figure 62: Step 3: Assign Documentation- (Transactions SOLAR01 / SOLAR02)

For each element in the project hierarchy, there are multiple tabs for collecting documentation • • • • • • • • •

Transactions Development objects Configuration Project documentation Administration (Status, plan/actual data, team member, keywords) Test cases Issues / messages Training materials End user roles

SAP Solution Manager provides version control and compare and adjust functionality (transaction SA_PROJECT_UPGRADE).

80


2012

E2E200


Figure 63: Business Process Graphic

• •

2012

The Business Process Structure is the central documentation directory. It is available in a graphical view, that can be used to discuss the business processes.


81


82


E2E200

2012

E2E200

81


Exercise 2: Create a Project Exercise Duration: 15 Minutes

Exercise Objectives After completing this exercise, you will be able to: • Create a project in SAP Solution Manager. • Maintain project data.

Business Example This exercise has to be executed in the Solution Manager system RWS. The project consists of the SAP ERP system and an Enterprise Portal.

Task: Create a project 1.

What transaction in SAP Solution Manager do you use to create a project? Answer: _____________________________________________________

2.

Create a new project with the name E2E200_## of type Maintenance project (## = your group number). Do not assign a solution. Enter a title for the project and select the project language English.

3.

On the tabstrip System Landscape → Systems, enter the following logical components with the F4 Help: SAP ERP → SAP ECC Server → logical component Z_ERP_QGM SAP NetWeaver → Enterprise Portal → logical component Z_EP_CCM

4.

Create an IMG project for both logical components. When asked to create a transport request, immediately choose No, Later. Finally, both IMG projects should show a green light.

2012


83


E2E200

Solution 2: Create a Project Task: Create a project 1.

What transaction in SAP Solution Manager do you use to create a project? Answer: _____________________________________________________ a)

Answer: SOLAR_PROJECT_ADMIN Alternative: Call SM_WORKCENTER, go to tabstrip Implementation / Upgrade. Mark section Plan and click the link Create or Maintain Project

2.

Create a new project with the name E2E200_## of type Maintenance project (## = your group number). Do not assign a solution. Enter a title for the project and select the project language English. a)

3.

In transaction SOLAR_PROJECT_ADMIN, create a new project. Enter the project name E2E200_## and the project type Maintenance project. Do not assign a solution. In the next screen, enter a title for the project and below the tabstrip General data select the project language English.

On the tabstrip System Landscape → Systems, enter the following logical components with the F4 Help: SAP ERP → SAP ECC Server → logical component Z_ERP_QGM SAP NetWeaver → Enterprise Portal → logical component Z_EP_CCM a)

4.

Alternatively to the menu path you can select in the tabstrip System Landscape → Systems in the column Logical Component the F4-help button and enter in the next screen via the Search button the logical components Z_ERP_QGM and Z_EP_CCM. Finally save your selection and confirm the window Enhancements for documents.

Create an IMG project for both logical components. When asked to create a transport request, immediately choose No, Later.

Continued on next page

84


2012

E2E200


Finally, both IMG projects should show a green light.

2012

a)

Choose the tab IMG Projects. You should see a red light for your project.

b)

Mark your project and press button Create IMG Project( ). Choose No, Later on the dialog box that asks you to create a transport request immediately.

c)

Choose Yes when asked to give your IMG Project a new name.

d)

Name your IMG project E2E200_##I (where ## is your group number).

e)

Choose No, Later on the dialog box that asks you to create a transport request immediately.

f)

Repeat the steps for the second logical component.

g)

Choose Back.

h)

Save the project.


85


E2E200

Lesson Summary You should now be able to: • Define a project in SAP Solution Manager using transaction solar_project_admin. • Assign the technical landscape to a Solution Manager project. • Use the Business Process Repository (BPR) as template to document core business processes. • Assign additional information to individual business process steps.

86


2012

E2E200

Lesson: 85

Lesson: Managing Solutions with SAP Solution Manager

Managing Solutions with SAP Solution Manager Lesson Duration: 15 Minutes

Lesson Overview Solutions are the basis for the operation scenarios and are used when the projects are finished by the implementation team to hand over the needed information to the operation team. This lesson will describe the concepts and best practices for defining solutions in SAP Solution Manager.


Define a new solution in SAP Solution Manager and transfer business process documentation to it. Describe best practices to tailor solutions in SAP Solution Manager.

Business Example The project has been successfully finished and now all information regarding the business process structure should be transferred to a new solution to be used in operation scenarios in SAP Solution Manager.

2012


87


E2E200

Managing Solutions with SAP Solution Manager

Figure 64: Solution Directory in SAP Solution Manager

• •

•

A solution describes a collection of information about systems, software components, and business processes (scenarios). Solutions are the basis for the operation scenarios – Solution Monitoring – Technical Administration – Business Process Monitoring – Collaboration Solutions provide handover information from the project phase to the operations phase –

88

Any project change is copied to the solution directory after being set active


2012

E2E200


Figure 65: Criteria for Tailoring a Solution

From SAP’s point of view, the critical drivers for tailoring a solution are the size of the documented end-to end business processes, as well as the related number of systems involved, depending on use, for example, system monitoring.

Adequar

2012

For complex organizations, we recommend that you define several solutions in accordance with the organizational tailoring and the selection requirements of the individual organizational units. In this way, large and complex customers and corporate groups can be displayed more clearly in special sections and administrated more effectively. However, it is essential that all of the business objects for a business process are located within one solution. The process must not be divided among several solutions or sub processes.


89


E2E200

Figure 66: Solution Overview

The Solution Overview is the central point for maintaining business processes in SAP Solution Manager. Here, you can assign logical components to your solution landscape, create business processes and copy business processes from implementation projects or other sources. You can access the Solution Overview in the Workcenter: Solution Manager Administration Overview -> Solutions Note: The old transactions: DSWP and SOLUTION_MANAGER have been disabled with the new Solution Manager release 7.10. See SAP Note: 1541013 for further information. Al Solutions are stored in the Solution Directory as a central repository in the SAP Solution Manager. You can access the Solution Directory with the transaction SOLMAN_DIRECTORY.

90


2012

E2E200


Figure 67: Transfer Project to Solution

Business processes within a solution can be created manually, copied from the business process repository, from other solutions or from projects. The structure of business process documentation in a solution equals to the structure of a SAP Solution Manager project. Therefore all information will be transferred together with the business process from a project to a solution •

• • •

The data is displayed in a “swim-lane” graphic (as it is used also in the project maintenance) indicating on which logical component the business process step is executed. Business Processes are attached to either a project or a solution. Business Processes can be copied from a project to a solution when a project goes live. Set the status for the business process to “Production” if you want to monitor the business process. This is only possible if there is a production system assigned to the logical components that the business process is using.

SAP Solution Manager enables the documentation of SAP solutions. At least the following information should be documented for core business processes: • • • • •

2012

Involved systems Business process steps Used transactions/background jobs Interfaces Custom developments


91


E2E200

Solution Documentation is the foundation for proficient application management: • •

Transparency enables efficient collaboration Solution Documentation is foundation of support processes (incident management, root cause analysis, maintenance, delivery of support services, integration validation, implementation/upgrade of SAP solutions, …)

Main tools for Business Process Documentation in SAP Solution Manager 7.1: •

Business Blueprint (SOLAR01)

•

– Initial documentation during regular project work. – Upload via standardized interface possible. Solution Configuration (SOLAR02)

•

– Enriching the documentation , e.g. with configuration and test data. Solution (in the Solution Directory) – –

•

Reflection of the actual productive environment. Secured documentation with controlled maintenance (“check-in/check-out”). Solution Documentation Assistant

•

– Continous verification of the existing documentation. – Reverse documentation with predelivered content. Enhanced Business Process Blueprinting –

Graphical modeling of Business Processes

Figure 68: Changes in operation: Check In / Check Out mechanism

92


2012

E2E200


After check out the project into the maintenance cycle, old released information will be available in this solution for monitoring and support purposes while the same content can be changed within the maintenance project. After the check in, the content within the solution gets updated by changes done in maintenance project. Procedure: 1. 2. 3.

2012

Checking out business processes for maintenance purposes (request + check out) Adoptions on business process content After configuration, developments, and testing, the content can be checked in back into Solution


93


94


E2E200

2012

E2E200

93


Exercise 3: Business Processes Exercise Duration: 15 Minutes

Exercise Objectives After completing this exercise, you will be able to: • Transfer business processes from the business process repository. • Assign documentation and test cases to the business process.

Business Example This exercise has to be executed in the Solution Manager system RWS. The project consists of the SAP ECC system and an Enterprise Portal.

Task: Create a business process from the business process repository in the new maintenance project. 1.

Go to the business blueprint of the maintenance project that you have created in the exercise before. In which transaction do you find the blueprint? Answer: ___________________________________________________

2.

Switch to change mode. Create a new business scenario HCM in the process structure (Do NOT select a scenario from the business process repository!) and save it.

3.

Create a new business process. From the business process repository, select the Human Capital Management scenario and the process Managing Employee Time and Attendance. In the subsequent dialog box, deselect the proposed additional logical components. Save your selection.

4.

The business process steps can now be maintained. Navigate to the structure of the process. After the first step, add an additional manual step. Enter the step name: Record working times in backend and assign the logical component for the ABAP backend system. Save your definition. Delete the last business process step Analytical Reporting for Employee HR Data.

5.

Navigate to the first step Record working times and absences on the left side and assign the URL for accessing the Enterprise Portal. What is the URL? Answer: ___________________________________________________ Continued on next page

2012


95


6.

E2E200

Navigate to the newly created second step and assign the transaction CAT2. Test the transaction. In which system and client are you logged on? Answer: ____________________________________________________

7.

Display the graphic and documentation for the process.

8.

Assign customizing activities to the newly created business process step. Which is the transaction for this? Answer: ____________________________________________________ In this transaction, select the newly created step and assign a specific customizing activity from the F4 help in the tabstrip Configuration of type IMG Object. Choose the activity via the F4 help in the column Object and select the following IMG path in the Structure window: Cross Application Components → Time Sheet → Specific settings for CATS regular → CATS regular → Record Working Time → define field selection. Choose Copy selected nodes and save your settings. What is the technical name of the IMG activity? Answer: ____________________________________________________ You can navigate into the customizing activity by double-clicking on the technical name. In which client on which system is the reference IMG started? Answer: ____________________________________________________

9.

Assign an eCATT test case and a manually created test case to the newly created business process step within tab Test Cases. For the eCATT test case, use the F4 help (do NOT select a logical component) and search for the test case ZETIMERECORDING_HR. For the manual test case, select type Test Document. In the dialog box, select Copy of Solution Manger Document. Select project CHARM_MAIN and the test document ZDTIMERECORDING in the column Test Object assign transaction CAT2.

96


2012

E2E200


Solution 3: Business Processes Task: Create a business process from the business process repository in the new maintenance project. 1.

Go to the business blueprint of the maintenance project that you have created in the exercise before. In which transaction do you find the blueprint? Answer: ___________________________________________________

2.

a)

Answer: SOLAR01

b)

Alternative: Call SM_Workcenter and go to tabstrip Implementation / Upgrade. From the Overview, choose the section Plan and then click on the link Define Business Blueprint.

Switch to change mode. Create a new business scenario HCM in the process structure (Do NOT select a scenario from the business process repository!) and save it. a)

3.

Navigate in the Business Blueprint Structure to Business Scenarios, select tabstrip Structure and enter HCM as the Scenario Name. Save your settings

Create a new business process. From the business process repository, select the Human Capital Management scenario and the process Managing Employee Time and Attendance. In the subsequent dialog box, deselect the proposed additional logical components. Save your selection. a)

4.

In the Business Blueprint Structure, navigate to Business Processes, and select tabstrip Structure. Use the F4 help in the column Process Name and enter in the next screen via the Search button the process Managing Employee Time and Attendance. In the Business Process Repository choose the entry below this process and choose Continue. Deselect the logical component selection in the next screen and save your settings.

The business process steps can now be maintained. Navigate to the structure of the process. After the first step, add an additional manual step.


2012


97


E2E200

Enter the step name: Record working times in backend and assign the logical component for the ABAP backend system. Save your definition. Delete the last business process step Analytical Reporting for Employee HR Data.

5.

a)

In the Business Blueprint Structure, mark the newly created process Managing Employee Time and Attendance. Select the tabstrip Structure on the right and mark the second step Record and administrate time data. Select the icon Insert Line and enter Record working times in backend as the step name. Select logical component Z_ERP_CCM from the F4 help and save your settings.

b)

Now mark the last process step Analytical Reporting for Employee HR Data and press the button Delete Row. Confirm the next dialog box and save your settings.

Navigate to the first step Record working times and absences on the left side and assign the URL for accessing the Enterprise Portal. What is the URL? Answer: ___________________________________________________ a)

Navigate to the first step Record working times and absences. Select tabstrip Transactions. Use type web address or file, type in the text Portal Access and the URL for the Portal access: http://portal-rwe:50000/irj/portal

6.

Navigate to the newly created second step and assign the transaction CAT2. Test the transaction. In which system and client are you logged on? Answer: ____________________________________________________ a)

Navigate to the newly created step Record working times in backend in the Business Blueprint Structure on the left side. Select tabstrip Transactions on the right side. Use type: Transaction, enter CAT2 in the field Object and save your settings.

b)

Select the Execute button of the new business process step in the Business Blueprint Structure.

c)

The following screen will pop up: “No system for component Z_ERP_QGM and role ’Evaluation System’”. You have to assign your development system as evaluation system. Please choose Business Blueprint → System Role... and choose your development system to change the system role assignment. Press button Copy. When you select the Execute button of your new business process step in the Business Blueprint Structure you are logged on to client 801 in RWE now.


98


2012

E2E200


7.

Display the graphic and documentation for the process. a)

Navigate to the process Managing Employee Time and Attendance in the Business Blueprint Structure. Then choose the tabstrip Graphic. The documentation can be found under the tabstrip General Documentation. The graphic should look like this:

Figure 69: Project: E2E200_00 - Business Blueprint

8.

Assign customizing activities to the newly created business process step. Which is the transaction for this? Answer: ____________________________________________________ In this transaction, select the newly created step and assign a specific customizing activity from the F4 help in the tabstrip Configuration of type IMG Object. Choose the activity via the F4 help in the column Object and select the following IMG path in the Structure window: Cross Application Components → Time Sheet → Specific settings for CATS regular → CATS regular → Record Working Time → define field selection. Choose Copy selected nodes and save your settings. What is the technical name of the IMG activity? Answer: ____________________________________________________ You can navigate into the customizing activity by double-clicking on the technical name. In which client on which system is the reference IMG started?


2012


99


E2E200

Answer: ____________________________________________________ a)

Answer: SOLAR02 Alternative: Go to the Work Center Implementation/Upgrade. From the Overview, choose the section Build and then click the link Goto Business Process Configuration.

b)

Answer: The technical name of the IMG Activity is PCUI_ESS_CATS_004 The technical name can be found below the column Object of the related business step.

c) 9.

Answer: Client 801 in the ECC system RWE

Assign an eCATT test case and a manually created test case to the newly created business process step within tab Test Cases. For the eCATT test case, use the F4 help (do NOT select a logical component) and search for the test case ZETIMERECORDING_HR. For the manual test case, select type Test Document. In the dialog box, select Copy of Solution Manger Document. Select project CHARM_MAIN and the test document ZDTIMERECORDING in the column Test Object assign transaction CAT2. a)

For the eCATT test case: Navigate to your new step in the configuration structure on the left hand-side. Select tabstrip Test Cases. Below column Test Case Type, choose eCATT Test Configuration and do NOT select a logical component. Enter the name ZETIMERECORDING_HR in column Test Case via the F4 help in the field Test Configuration in the next window and save the settings.

b)

For the manual test case: Choose Test document as the type. In the next popup select Copy of a Solution Manager Document. In the next popup select the project CHARM_MAIN and Execute. Then mark ZDTIMERECORDING and press Enter, Save and Close. In the column Test Object assign transaction CAT2 by using the F4-help.

100


2012

E2E200

99


Exercise 4: (Optional) Transfer Project Documentation to Solution Exercise Duration: 10 Minutes

Exercise Objectives After completing this exercise, you will be able to: • Create a Solution in SAP Solution Manager. • Transfer a business process from a project to a Solution.

Business Example This exercise has to be executed in the Solution Manager system RWS. The project consists of the SAP ECC system and an Enterprise Portal.

Task: Create a solution and transfer the new business process to the solution.

2012

1.

Create a new solution with the name E2E200_SOL## (## = your group number)

2.

Transfer the newly created business process into the solution. Check if the assigned logical components, the transaction, and the URL are included.


101


E2E200

Solution 4: (Optional) Transfer Project Documentation to Solution Task: Create a solution and transfer the new business process to the solution. 1.

Create a new solution with the name E2E200_SOL## (## = your group number) a)

Execute transaction SM_Workcenter or open the Work Centers URL in your Favorites. Select the tab Solution Manager Administration and push Solution on the left navigation bar. In the Solution Overview, choose New. Enter the name of your solution. Leave all other fields unchanged and choose Save solution.

Figure 70: SAP Solution Manager- Transfer project data into a solution


102


2012

E2E200


2.

Transfer the newly created business process into the solution. Check if the assigned logical components, the transaction, and the URL are included. a)

Navigate into Solution Directory of your new solution. Switch to change . In the business process section, transfer the business process from your project (make sure that the source is set to project!). 1. 2. 3.

Press F4 in Scenario Name field Drilldown to your project E2E200_##, click Business Scenarios, then HCM and finish your entries with Copy. Save and Refresh. Confirm the assigned logical components.

Figure 71: Solution Directory- Change: SAP Solution Manager

Navigate to the first two process steps. Check under tabstrip Transactions if the URL and the transaction CAT2 have been assigned.

2012


103


E2E200

Lesson Summary You should now be able to: • Define a new solution in SAP Solution Manager and transfer business process documentation to it. • Describe best practices to tailor solutions in SAP Solution Manager.

104


2012

E2E200

Lesson: 103

Lesson: Reverse Business Process Documentation and Modelling Tools

Reverse Business Process Documentation and Modelling Tools Lesson Duration: 20 Minutes

Lesson Overview This lesson will describe how to (re-)document productive business scenarios in SAP Solution Manager with the Solution Documentation Assistant. It also contains a description of new available offline tools for modelling business processes and how they are connected to the SAP Solution Manager.


Describe Reverse Business Process Documentation (RBPD) with the Solution Documentation Assistant. Describe the different possibilities for modelling business processes using new offline tools with interfaces to SAP Solution Manager.

Business Example You want to use SAP Solution Manager for documenting already implemented core business processes. Automatic tools are needed to evaluate which steps are really executed in the production systems. Non SAP users are also involved in modelling and documentation of the business processes with no direct access to the SAP Solution Manager.

2012


105


E2E200

Reverse Business Process Documentation and Modelling Tools

Figure 72: Initial Documentation Challenges during Software Implementation

You could obtain a business process structure in SAP Solution Manager 7.1 as a starting point for your Solution Documentation. This is achieved by using Reverse Business Process Documentation (RBPD) with Solution Documentation Assistant in SAP Solution Manager 7.1.

Figure 73: What is Reverse Business Process Documentation?

106


2012

E2E200


How to start Reverse Business Process Documentation with predefined SAP Content: • • • •

Step 1: Step 2: Step 3: Step 4:

Content Upload into SoDocA Create Analysis based on Analysis Project Create Solution Manager Project Complete Business Blueprint

Figure 74: Reverse Business Process Documentation with Solution Documentation Assistant (SoDocA) - Data Flow

Before you can work with the RBPD content, you have to download it first from SAP Service Marketplace. Technically, the content is an XML file which is attached to SAP Note 1591505 - just open the note to download the content, and save the content file to your local PC. Related links: http://service.sap.com/rbpd - Page with presentations, demos and further useful information on Reverse Business Process Documentation

2012


107


E2E200

Figure 75: Solution Documentation Assistant- What does it do?

The Solution Documentation Assistant can be started via the Workcenter. There is a separate workcenter for the Solution Documentation Assistant. The Solution Documentation Assistant provides an overview of the current status of your analysis projects and analyses. The overview also gives you quick access to your current analysis, analysis projects, analyses, and analysis results.

108


2012

E2E200


Figure 76: Solution Documentation Assistant- Analysis Results

2012


109


E2E200

The following terms are important for the Solution Documentation Assistant: •

Analysis Project –

•

Project created from an existing SAP Solution Manager project. Existing structures and objects are copied to the Analysis Project. Results are mapped to the structures in the Analysis Project, and can then be copied back the underlying project to indicate what is in scope for the upgrade. Analysis Results –

•

Output of the Analysis, contains detailed consideration of analyzed objects such as transactions or reports. Results can also copied to the project or displayed in an HTML report. Check Steps –

•

The Analysis Result is based on check steps. You use Check Steps to determine what the Analysis should display. Check steps can be brought into the Analysis Project from the underlying Solution Manager project structure, or added from the Rule Database. Check Item –

•

Organization object in the Analysis Project so you can group Check Steps. Check Items rate Analysis Structure nodes during analysis. The rating is based on the results of Check Steps assigned to the Check Items. You can assign any number of Check Steps to a Check Item. You can assign any number of Check Items to a structure node. Rule Database –

110

Repository for Check Steps, can contain customer-specific transactions and report information from an analysis result. Check Steps detected during an analysis can be copied to the Rule Database for use in future analyses.


2012

E2E200


Figure 77: Solution Documentation Assistant- Update the Solution Manager Project

• •

•

The results of the Solution Documentation Assistant can be transferred back to the source project. Steps which were identified as active by the Solution Documentation Assistant can be set to “In Scope”. Steps which were identified as not active can be set to “Out of Scope”. Steps with no results are not changed. This could be used to create new business processes or to update already existing ones.

With SAP Solution Manager 7.10 SAP offers now new offline tools for modelling Business Processes outside the SAP Solution Manager. The information can be then uploaded again into the SAP Solution Manager. Tools integrated with the SAP Solution Manager: • • •

2012

Enhanced Business Process Blueprinting (BPB) ARIS Toolset (with an adapter provided by SAP) XLS Interface


111


E2E200

Figure 78: Sources for Structures- XLS Interface

The XLS interface serves for initial upload of blueprint structure and documents: Initial documentation is automatically being build up by using implementation projects in SAP Solution Manager. To speed up this process, a new upload interface has been built into the Business Blueprint. The following information can be uploaded from external sources: • • • • • • • • •

112

Business Blueprint Structure Business Blueprint Structure Attributes Project Documentation tab Transactions tab Business Functions tab Configuration tab Development tab Test Cases tab Training Material tab


2012

E2E200


Figure 79: Content/XLS Upload - Data Flow

How to work with the upload interface: •

•

•

2012

Export the structure, attributes and other tabs to template.txt files which contain content examples for your reference and can easily be edited, e.g. with Microsoft Excel. Create a Business Blueprint Structure first before you continue uploading additional content. Detailed information can be found in the SAP Solution Manager online help: http://help.sap.com/alm --> SAP Solution Manager --> SAP Solution Manager 7.1 --> Application help --> changes and new features in SAP Solution Manager 7.1 SP01 --> Implementing Solutions --> Download/Upload for Business Blueprint Projects. You could start the import by calling SOLAR_PROJECT_ADMIN --> choose your project and access it --> Edit --> Create Template File --> choose e.g. Structure. Upload the file for your business blueprint structure as txt file. The upload is only activated for an initial upload. Delta uploads are not supported.


113


E2E200

Figure 80: Sources for Structures - SAP Business Process Blueprinting

The new SAP Business Process Blueprinting (BPB) is a Rich Modeling Environment based on Eclipse RCP (Rich Client Platform): With a RCP, programmers can build their own applications on existing platforms.

Figure 81: SAP Solution Manager and Business Process Blueprinting - Integration

Without offline tools like the new Enhanced Business Blueprinting tool it was difficult to integrate non SAP-users in the process of documenting Business Process scenarios in SAP Solution Manager. Now the content can be downloaded

114


2012

E2E200


to the Business Blueprinting tool and processes can be modelled offline. With the help of a bidirectional interface it is then possible to map the structure to the structure in the Solution Manager and upload the content again. Blueprint Definition: A SAP Business Blueprint is a detailed technical plan containing all required documents that help better understand how the company intends to run its business within the SAP software system. Key Capabilities: • • • • •

Process Modeling using BPMN (Business Process Management Notation: standardized graphical modeling notation language) Deep Integration with Solution Manager Search and Adapt from SAP Best Practice content (BPR,..) Documentation of custom Business Processes Integration with SAP NetWeaver BPM (as of SAP NetWeaver 7.31)

Figure 82: Business Process Blueprinting with SAP Solution Manager 7.1

SAP Business BPB offers a lot of enhanced feature and functionalities for process modeling:

2012


115


E2E200

Features: • • • • • •

Exchange of business process structures Transfer of transactions assigned to business process structures (User Interfaces) Representation of business process documents by links Representation of tasks and decision- start- and end points Interlink between processes (Planned for SP05 for SAP Solution Manager 7.10) More documentation/graphical objects (Planned for SP05 for SAP Solution Manager 7.10)

Key Message: • • • •

Modeling capabilities based on Business Process Management Notation standards (BPMN) Significantly increased usability and graphical modeling Access to various modeling content sources such as BPR, Template, Project content Ability to deal with Composition and SOA content

How to work with the RCP client • • •

• •

Open existing SAP Solution Manager project in RCP (Rich Client Platform) client Enhance blueprint structure, e.g. create new process Edit process-related contents – Transactions / Reports – General/Project Documentation – Business Process Flow Diagrams – (SOA Services) Interactively model structure elements in RCP client based on BPMN notation Save and write back contents to SAP Solution Manager Note: Usage of new modeling capabilities require future editing in the RCP client

116


2012

E2E200


Figure 83: Sources for Structures - ARIS

SAP offers an adapter for the ARIS toolset with a bidirectional interface: Already existing process documentation can be downloaded to ARIS and can be modeled there. With the help of an ARIS script the ARIS 5-level process structure will be mapped to the 3-level structure of SAP Solution Manager. After this the Structure can be transferred back to the Solution Manager. If customer does not have already ARIS installed the complete product can also be ordered from SAP. Advantage: specific product version covering all necessary technical prerequisites. In Addition to that also the complete support is covered by SAP support contract. The product is called: SAP Business Designer by IDS Scheer

2012


117


E2E200

Figure 84: SAP Solution Manager and ARIS- Integration

Advantages of ARIS: • • •

Customer can modelize not only the SAP Systems but the complete Customer Landscape. ARIS UI is easy to use and state of the art for modeling Business Processes No limitation to the three step structure in SAP Solution Manager

Objects which can be synchronized between SAP Solution Manager and ARIS: • • • • •

118

SAP Scenarios SAP Processes SAP Process Steps Transactions / Master Data / Organization Units SAP System Landscape


2012

E2E200


Additional Training Opportunities: • •

SMI210: Solution Manager Implementation Methodology Overview 8 hours – – –

• •

SMI310: Implementation Projects with SAP Solution Manager 3 Days – –

• •

Understand the concept of SAP Solution Manager with the focus on supporting implementation (and upgrade) projects Explore tools, services, and methods in detail to successfully and efficiently implement complete software solutions and new enhancements

SMI410: Solution Manager (7.0) Implementation Tools in Detail 5 days – – –

2012

Introduce the ASAP Methodology for Implementations 7.0 and the ASAP Implementation Roadmap Understand how to use this methodology to implement SAP Solutions Introduce the SAP Solution Manager and the use of the Implementation Roadmap in Projects.

Understand the composition and functions of the SAP Solution Manager Use the tools provided to successfully and efficiently implement your SAP solution This course is the equivalent to SMI210 & SMI310


119


E2E200

Additional Information: •

Overview: Solution Documentation and Application Life-Cycle Management – –

http://service.sap.com/alm –> Processes –> Solution Documentation Technical Papers: SAP Solution Manager Media Library http://service.sap.com/alm –> SAP Solution Manager and Tools –>Media Library

–

•

Learning maps: Documentation of Core Business Processes and Solution Documentation Assistant http://service.sap.com/rkt-solman –> SAP Solution Manager 7.1 –> Solution Documentation – Onsite training: Implementation Projects with SAP Solution Manager http://service.sap.com/education –> Training Catalog –> Course Search –> SMI310 – Addional information: http://help.sap.com/landscape-description -> overview landscape description Landscape Management Database (LMDB):

•

– http://scn.sap.com/docs/DOC-8817 Business process blueprinting: – – – –

–

Online help: http://help.sap.com/bpb SDN Webinar: http://www.sdn.sap.com/irj/bpx/index?rid=/library/uuid/40b5b278-30bc-2e10-dd84-8e39ff052ce9 SDN Presentation: http://www.sdn.sap.com/irj/scn/events?rid=/library/uuid/308948dc-6abf-2e10-3fad-ae69a62555c0 E-Learning/ TechEd Session: http://www.sdn.sap.com/irj/scn/shop?rid=/media/uuid/708dfc59-5ab4-2e10-f396-a206c118c6e8 How-to guide regarding Integration BPB/SolMan: http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/000c23b9ce19-2f10-6b8d-cfa4591750ea

(system demo) Solution Documentation Assistant (SoDocA)

120


2012

E2E200


Lesson Summary You should now be able to: • Describe Reverse Business Process Documentation (RBPD) with the Solution Documentation Assistant. • Describe the different possibilities for modelling business processes using new offline tools with interfaces to SAP Solution Manager.

2012


121


Lesson: 120

E2E200

Business Process Change Analyzer Lesson Duration: 30 Minutes

Lesson Overview Business Process Change Analyzer provides precise impact analysis of software changes on business processes. Basic and advanced analysis functions are available to trace SAP objects used during business process execution, which are leveraged to analyze the effect of software changes applied via transport requests to SAP system landscapes. Risk-based test recommendations are provided to guide the user during scoping of regression test activities.

Lesson Objectives After completing this lesson, you will be able to: • • •

Get an overview about SAP’s methodology for testing and how it is used in SAP Solution Manager. Determine the change impact with the Business Process Change Analyzer. Get known the Test Management Work center.

Business Example You wish to know if the changed or new objects within your transports influence your business process. Your transport is available in the development system or in the sandbox system at this point in time. You are interested to know how the Business Process Analyzer works and how the test workbench in the SAP Solution Manager is integrated in case you detect that your business process has to be tested.

122


2012

E2E200

Lesson: Business Process Change Analyzer

Introduction into SAP´s Approach for Testing of planned changes Bringing changes into SAP Solutions might lead to increased effort for testing. Within SAP Solution Manager you can find capabilities to help you to organize and carry out necessary tests. Customer pain points have been collected via customer survey conducted in the US and Europe: 1.

2. 3.

4.

Tests in heterogeneous system landscapes: E2E Integration Tests of business processes in system environments interfacing SAP with non-SAP solutions Change Impact Analysis: Indentification of critical business processes affected by software changes, No risk-based test recommendations Test Data Management Test Systems with outdated test data, Productive System copy is too expensive and rework intensive, Creation of appropriate test data for manual / auto test cases Test Automation Creation of automated test cases is time consuming and expensive to maintain via skilled QA specialists, Automated test cases get damaged by change events and need time consuming repair by QA Specialist

SAP took action to help customers to fullfill their testing strategy by providing Adapters (e.g. HP quality center, IBM rational) to other vendors as well as by providing integration possibilities (e.g. Test workbench framework).

PROVA

Figure 85: Test Stages - Typical Test Stages in SAP Projects

2012


123


E2E200

Different tests could be carried out according to customer needs: •

Unit Test –

•

A functional test for individual transactions or function modules. It focuses primarily on internal functions rather than integration and interfaces. – Interaction with other activities is not tested, with the exception of interfaces within the tested unit. Scenario Test or String Test

–

•

Test of multiple related transactions, such as a series of transactions within a business area. – Test focus is on the interaction between individual transactions and their interfaces and checks the functional compliance. Integration Test: –

•

Integration tests cover complete end-to-end business processes including process variants that have changed. – Integration tests also include the integration of SAP solutions with non-SAP applications and system interfaces. – Customer business processes are mapped in the form of end-to-end scenarios; systems are tested in accordance with cross-module and cross-system scenarios. Regression Test: –

•

Regression tests ensure that solution functionality and business processes have not suffered adverse effects after a system change. Technical System Tests (primarily performance tests): –

•

Technical system tests evaluate the entire system, not only focusing on business processes but also on infrastructure such as database, application servers, front ends, networks, printers, etc. – Performance tests are one of the most important technical system tests. They test the runtime behavior (for example, to evaluate answer times, SLAs) of a solution and its infrastructure by simulating system load. User Acceptance Test: –

Final acceptance from project stakeholders/end users for an implementation/project.

SAP Solution Manager integrates application lifecycle management capabilities of SAP Solution Manager with test planning and test execution capabilities to cover the test process. You can benefit from enhanced control for test coordinators and improved communication and collaboration in test teams by built-in and preconfigured workflow.

124


2012

E2E200

2012



125


E2E200

Figure 86: SAP Test Management - Options for SAP Customers based on SAP Solution Manager 7.1

• • • •

• •

• • • • • • • • •

• • • •

126

Within the E2E200 we will show the usage of the business process change analyzer. First, we will identify the test scope for the newly created business process. The SAP Test Data Migration Server (TDMS) supports the automatic creation of test systems with low data volume. With the Business Process Change Analyzer, you can analyze business processes that are affected by a change and have to be tested again. You can base test plans on the analysis results. You can access the Test Workbench functions in the Test Management work center, or in the SAP menu under Tools ABAP Workbench Test Workbench . When you use the functions of the Test Workbench to create test plans for a project, all test cases and transactions which are assigned in the configuration structure of the project, are displayed by default. You can select test cases and transactions from this default selection, and then generate a test plan. The Test Automation Framework creates automatic test cases, with eCATT or third-party tools. You can summarize a selection of test cases to a test package and assign the test package to a tester. You can sort the test cases in a test package into test sequences. You can assign individual test cases of a test package to different testers. You can schedule automatic tests (e.g. overnight). For better test execution control, you base a workflow on a release status schema. Than the test is performed. The SAP Solution Manager Test Management work center is the central point of entry for performing and evaluating tests. In the Tester Worklist, the tester sees a list of all test packages assigned to him or her. For more information about executing the tests in the Test Workbench, see Testing. The tester can also call and process his work list directly via the link in the E-Mail notification, in the workflow. The status info system enables you to display, print and process test plan status analyses. The BI reporting functions display graphically formatted overviews of the status of the test plans or the processing history. Remark: Test Automation Framework is provided with SAP Solution Manager 7.1 to integrate smoothly 3rd party test automation tools with SAP Solution Manager. More detailed information could be found under http://service.sap.com/testing.


2012

E2E200


Figure 87: Using the BPCA for finding the right scope for testing

From change management perspective SAP Solution updates occur frequently. We can find the following change events: • •

SAP triggered: Support Packages, Enhancement Packages, SAP Notes Customer triggered: Customizing changes, Custom code development

Regression Testing and Test Automation - Best Practice Recommendations Regression Testing: •

• •

The most critical business processes need to be repeatedly tested after each change (for instance, transports, service pack implementation, process changes). Typically, a regression test set consists of a selection of integration test cases. It is recommended to use a risk-based test case selection for regression testing in combination with a technical change analysis (by using Business Process Change Analyzer).

Test Automation: •

• •

2012

Automated testing can significantly reduce cost and time effort. However, the initial planning of the automation approach as well as the qualification of the internal testing team can be time-consuming. Resources freed by test automation can be used to extend the scope of a regression test. The key criteria to determine an automated test case are business criticality as well as the number of times the test case will be executed in the future.


127


E2E200

Figure 88: Preparation: Business Process Documentation - How to create Business Process documentation

To carry out a BPCA we need a business structure where we can assign the technical bill of material to the executable entity.

Business Process Change Analyzer – Overview

Figure 89: Business Process Change Analyzer - use case for ESS scenario

128


2012

E2E200


This picture shows an overview about the use case for BPCA within the E2E200 course. We customized in the RWE backend our ESS scenario within the HCM project and now we would like to know whether changes to the process need to be tested. How to find out this?

Figure 90: SAP Solution Manager - Business Process Change Analyzer

You can use the Business Process Change Analyzer (BPCA) to check whether a process structure is affected by specific changes. You can precisely specify both the relevant parts of the process structure and the relevant changes. The result of the analysis is a list of the affected nodes in the process structure. You can use the result to create test plans to retest the affected scenarios, processes or process steps after the change.

2012


129


E2E200

Business Process Change Analyzer – Preparation

Figure 91: Technical Bill of Material (TBOM) - Concept

A TBOM (Technical Bill of Materials) contains all the objects involved in a transaction. The Business Process Change Analyzer uses TBOMs to determine whether a transaction is affected by a change or not. In order to be able to run the Business Process Change Analyzer usefully, you therefore have to create a TBOM for each transaction that you use in your scenarios, processes, and process steps.

130


2012

E2E200


The TBOM is an attribute of an executable entity in the Business Process Hierarchy. •

•

Static: In the static generation of a TBOM, the transaction is not called. The system uses an environment analysis to determine the objects involved in the transaction. If your user parameter AGS_BPCA_TBOM_EXPERT has a value of at least 3, you can specify the branching level during static generation. By default, the branching level is set to 3. Values from 1 to 4 are possible. Dynamic calls or generated objects are not found, so they are not in the TBOM. The result is not as precise as with dynamic generation. Dynamic TBOMs: In systems with kernel 620/640, the creation of dynamic TBOMs is only possible after status ST-PI 2008_01 SP03. In all other systems (kernel 46C or after 640), the creation of dynamic TBOMs is available. The associated executable entity is called via the corresponding RFC user in the managed system. You must be authorized to execute the executable entity in the managed system. Enter the data required for the executable entity there. All objects in the executable entity are captured in the background, and copied to the TBOM once the executable entity is complete. The dynamic creation also includes RFC connections and branched GUI user procedures within the same (primary) system, and RFC connections to other (secondary) systems. Further RFC connections to third-party systems are also recorded, but branched GUI processes in secondary or third-party systems are no longer recorded. You can create dynamic TBOM enhancements for the following types of executable entities:

•

•

2012

– BSP application – CRM WebClient application – SAP application URL (SAP_LONG_URL) – Program – SAP CRM people-centric UI application – Transaction Cross-system TBOMs: If an executable entity addresses other systems (e.g. by RFC), the objects in the other systems are also recorded. A separate TBOM enhancement is created for these objects per system. This function is available if all managed systems involved have a kernel status of at least 700. Web applications: To record TBOMs for web applications, the managed systems must have a kernel status of at least 700.


131


E2E200

The TBOM contains the following information about the individual objects involved in the executable entity (you can view this information in the TBOM content display): • •

Program ID: ID of the object, for example, R3TR for complex objects such as programs and all related elements or LIMU for subobjects Object type: Precise assignment of the object to a type, for example, REPS for Report Source, FUNC for functions, TABL for tables

There are several hundred different object types. • •

Object name: Technical name of the object, Program ID, object type, and object name together uniquely identify the object. Origin: Origin of the object D for dynamically generated objects S for statically generated objects

•

Classification type: Different object types are summarized to a classification type. The default assignment of classification types to object types is stored in the system.

The following classification types have been predefined: • • • • • • • • •

TABC = Table Class UI = User Interface TRAN = Business Transaction FUNC = Business Function DOKU = Technical Documentation Object DDIC = Data Dictionary AUTH = Authorization Object CUSX = Customer Extension Points (EnhSpots) MISC = other classification types

More Information could be found under: http://help.sap.com/saphelp_sm71_sp01/helpdata/en/fb/1ce5f08a14454eb7ead8193db2491b/content.htm

132


2012

E2E200


Figure 92: Preparation: Technical Bill of Material (TBOM) - Manual Creation from Business Blueprint (1)

You have to create TBOMs for all executable entities in your process structure. You have to ensure that the TBOMs are up-to-date. You only get correct and reliable analysis results if the TBOMs are up-to-date. The obsolescence check (AGS_BPCA_TBOM_OUTDATE_CHECKER2) compares the objects listed in the TBOM with the objects that actually exist in the system affected. You can update TBOMs in the following ways: You can re-record or recalibrate TBOMs. For more information, see the SAP Solution Manager help portal or go to the SAP Solution Manager release notes for SM7.1 under. http://service.sap.com/instguides → SAP Components --> SAP Solution Manager. You find the SAP Solution Manager release notes within the spotlight area.

2012


133


E2E200

Figure 93: Preparation: Technical Bill of Material (TBOM) - Manual Creation from Business Blueprint (2)

You can choose Display Contents in the Enhancements dialog, to display the contents of TBOM enhancements. The objects in the TBOM are displayed in a separate window. Statistical information, and a detailed list of all objects, are displayed. The graphical overview shows the statistical distribution of the objects over the TBOM classification types and software components. The tabular overview shows the absolute and percentage distribution of all objects in the TBOM over the classification types. Note: If the displayed objects are tables, the Key Exists column indicates whether table keys were recorded for the table entry.

134


2012

E2E200


Figure 94: Preparation: Technical Bill of Material (TBOM) - Alternatives for manual and automatic TBOM creation

With SAP Solution Manager 7.1 different options for creating/updating TBOMs are available. You can create TBOMs for executable entities which do not run in the classical SAP GUI. The following types of web applications are supported: • • • •

BSP application CRM WebClient application SAP CRM people-centric UI application SAP application URL (SAP_LONG_URL): With this type, you can, for example, specify the URL of a portal via which an SAP application in an ABAP application server is started.

Prerequisites: In the type SAP application URL, the URL must start an SAP application in an ABAP application server. The managed systems have at least kernel status 700 and ST-PI 2008_01 SP03. Customers have invested in creation of automated test scripts and want to reuse automated test scripts. Test scripts executing business processes steps can be reused with the new Test Automation framework for TBOM creation. To sum it up three steps are necessary: 1. 2. 3.

Assign Test Configurations Create Test Plan and Test Package Execute Test Package and create TBOMs automatically

For more information, see the Customizing for SAP Solution Manager →Capabilities → Business Process Change Analyzer.

2012


135


E2E200

TBOM work list For working with TBOM work lists the system checks whether you have specified a business process expert for each selected entry, whether the business process expert has an E-Mail address, and whether there is both a system user and a business partner for the business process expert. The E-Mail address, system user and business partner are also checked for the quality expert. After choosing Create Tasks the system creates a TBOM recording task for each entry selected. The business process expert and the quality expert are informed by E-Mail, and can access the recording task in the Test Management work center, in the view TBOM Worklist. They can access their TBOM work list via the links in the E-Mails. Please see the following picture regarding the process:

Figure 95: Preparation: TBOMs created by business experts (Work items)

The quality expert requests a business process expert to record a TBOM. He creates a recording request. The system informs the quality expert and the business process expert about the new recording request, by E-mail. The business process expert records the TBOM. The business process expert completes the recording task. The system informs the quality expert about the completion of the recording task, by E-mail. The quality expert checks the recorded TBOM, and confirms the recording request.

136


2012

E2E200


Pre-requisites: You have performed the Customizing activity Adjust Workflow for TBOM Work List, to activate the E-Mail notification for TBOM recording tasks. For more information, see the Customizing for SAP Solution Manager →Capabilities (Optional) Business Process Change Analyzer . You have set up SAPconnect. For more information, see the Customizing for SAP Solution Manager under Technical Settings →Set Up SAPconnect . Within the Test Management Work Center you could push the Evaluate button in the Test Preparation area. This will bring you to the reporting screen were you will find the TBOM Status and TBOM Type. You could create work items for TBOM recording for processes in scope by pushing the button Create TBOM Recording Work Items.

Business Process Change Analyzer – Analysis

Figure 96: Use Case for Change Impact Analysis with BPCA

2012


137


E2E200

Specify the changes relevant for the analysis. There are the following scope types: • • •

•

Transport Requests: You can select transport requests from a managed system. Delivery Transports: You can select delivery transports such as support packages, enhancement packages or add-on delivery requests. Maintenance Optimizer: Simplified SAP delivery transport selection. The delivery transports must have been installed in the managed system by the SAP Maintenance Optimizer. Planned Activation of a Business Function: You can select business functions, and check which parts of business processes will be affected, before activation. You can either select the business functions directly from the managed system, or use the business function scope of a project or solution, as source. Prerequisite for the use of this function is that the managed system has at least one of the following software statuses: – – – – –

SAP Netweaver Enhancement Package 1: Support Package Stack 06 SAP Netweaver Enhancement Package 2: Support Package Stack 02 SAP ERP 600 Enhancement Package 4: Support Package Stack 06 SAP ERP 600 Enhancement Package 5: Initial delivery SAP CRM 7.0 Enhancement Package 1: Initial delivery

Figure 97: Change Impact Analysis - Transport Requests containing Coding, Dictionary or Customizing objects

The detail to run the change impact analysis is described in the picture.

138


2012

E2E200


Figure 98: Analyze Change and identify impact on existing processes

You can use this analysis to check whether a process structure is affected by specific changes. You can precisely specify both the relevant parts of the process structure and the relevant changes.

Figure 99: Results of Change Impact Analysis

In the top detail table (Result ID ...), select the project or the solution to evaluate. You can choose Test Plan → Create Test Plan to generate a test plan from all test cases that exist for the affected executable entities.

2012


139


E2E200

You can use Test Plan → Extend Test Plan to add test cases from the affected executable entities to an existing test plan. The system allows you to extend all test plans that exist for the project you selected. Objects are often assigned to several nodes in the Business Process Hierarchy, and are in several test plans. With Optimize Test Scope, you can optimize the scope of the test plans to be created, to avoid redundancies and test as many objects as possible with as little test effort as possible.

Figure 100: Business Process Change Analyzer- Test Scope Optimization for non-critical processes

Optimization, i.g. identification of test cases based on number of changed SAP objects and test effort can be reached here. Each changed SAP objects should be tested at least once. Not all affected process steps have to be included in the regression test.

140


2012

E2E200


Figure 101: Analysis: Test Recommendation- Semi automatic test plan generation

You can use the test cases contained in the Business Process Hierarchy to create test plans that are tailored to the relevant changes. You can check scheduled changes as well as changes that have already been made.

Figure 102: Risk-based Test Recommendation - Automatically Create Test Plan

From the result of the Business Process Change Analyzer run you can automatically create a test plan. This test plan will contain all test cases of the affected business process steps.

2012


141


E2E200

(System Demo) Change Impact Analysis

Test Execution

Figure 103: Test Workbench - Overview

Test catalog, Project or Solution Directory structure serve as repository for the collection of test cases. Test plans: • •

View on one test catalog Contains all test cases for one test cycle

Test package: • •

Person and time-oriented view on a test plan Contains all test cases one tester has to work with

Test case: • •

Business process step / process chain Manual test case description or eCATT script

•

Standard approach: Several Testers (Tester Pool) are assigned to a collection of Test Packages. Sequence approach: In addition to standard approach you can assign each Test Case to a Tester and the sequence of test cases can be process as workflow (e-mail notification).

•

142


2012

E2E200


Figure 104: New User Interface for Test Execution- Tester Worklist in Test Management Work Center

Test case descriptions should be based on a unified document template which contain at least the following information: • • • • •

Test case title Short description of test case Preparation / prerequisite steps to conduct the test Execution / test steps Expected result

The quality and detail level of test cases should be defined in the test concept. A workflow should be in place to keep the test cases up-to-date when the business processes change.

When executing manual test cases, you can do the following: • • •

2012

Assign a status so that the test cases can be further processed. Measure the current effort Enter information which allows for reproducing errors, for example, the steps which led to a dump.


143


E2E200

Figure 105: Test Execution - Accessing Test Case

Working with the manual test case means you have documented the result of your test case. The test organizer has an overview of the status of all test cases in your test package.

Figure 106: Test reporting capabilities

144


2012

E2E200


During the test stages (e.g. sign off test scope, sign off test plans, test execution, sign off test execution) you are able to carry out test reports. Here the test reporting during execution is shown were you could see e.g. results regarding test status and progress, actual test effort, detected errors and related messages. This status reporting is necessary for the sign off phase. There are also the following functions to evaluate test plans: •

Status Analysis –

•

You get a detailed overview of the status of the test cases assigned to the selected test plan, in the Test Workbench. Status Info System –

•

The Status Info System gives you information about several test plans. The status overview shows the current status. Status Report (BW-based) –

The test plan status report is based on the last data extraction from the SAP Solution Manager system. Note: The number of test cases in a test plan, with a specified status, in this list, can differ from the number in the BW reports. The difference arises if a test case is performed by several testers. This list sums every test case by status value. The BW report takes repeats of the same test case by different testers, into account. The worst status value of the test case applies.

•

Progress Report –

•

The progress report is based on the last data extraction from the SAP Solution Manager system. Message Report

–

•

The message overview in the Test Workbench contains all messages created in a test plan. Test Effort Report –

This test effort report gives you an overview of the test effort and clarifies whether the planned test effort is sufficient or exceeded.

In the Test Management work center, go to the Test Evaluation view to start the report.

2012


145


E2E200

Figure 107: Use Cases for Testing - Mitigate Risk of Changes with Test Management, SoDocA and BPCA

Testing will be carried out at different stages within the application lifecycle management phases. The process is described within this picture.

Further information could be found under http://service.sap.com/rkt-solman → SAP Solution Manager 7.1: Test Management

146


2012

E2E200

145


Exercise 5: Business Process Change Analyzer Exercise Duration: 20 Minutes

Exercise Objectives After completing this exercise, you will be able to: • Record a technical bill of material for transaction CAT2. • Perform an impact analysis with the Business Process Change Analyzer. • Create a test plan out of the results of the Business Process Change Analyzer.

Business Example RWS is the SAP Solution Manger system that contains all information about the managed systems. RWE is a ERP system that is managed by RWS. You plan to bring changes into your system landscape and transport RWEK900205 is waiting in the development system to be imported. Before doing so you want to verify whether these changes influences your business processes.

Task 1: Record a technical bill of material (TBOM) for transaction CAT2. 1.

Log on to SAP Solution Manager with your user, E2E200-## (change ## to your group number). Navigate to the Test Management work center and choose Test Preparation.

2.

In the Test Preparation view, select the Solution Manager project E2E200_## (## = group number) that you created in the exercise for Solution Documentation. Navigate to the Business Blueprint. Which transaction is it?

3.

In your project, select the business process step Record working times in backend, which you added in the exercise for Solution Documentation, and select the attributes of the related transaction.

4.

In the attributes of transaction CAT2, chose the TBOM tab. Start to create a technical bill of material for this transaction. Choose Create Option Dynamic. This means that a trace is executed to record all objects that are used in this transaction.

5.

Enter some working time in transaction CAT2 and finalize the creation of the TBOM. Make the following entries in transaction CAT2.


2012


147


E2E200

Figure 108: Time Sheet: Initial Screen

Do not change the default values for Data Entry Profile and Personnel Number. Enter some working time entries and save it. After that, a TBOM with name and date will be created.

Figure 109: Time Sheet: Data Entry View

6.

Display the object list of the newly created TBOM.

Task 2: Perform an impact analysis run with the Business Process Change Analyzer. 1.

Navigate to the Test Management work center and select the BP Change Analyzer menu. Enter all relevant data in the Business Process Change Analyzer. Please use transport request RWEK900205 that was already created on system RWE:801 under user E2E200-owner for you.

2.

Start the change/impact analysis and list the results.

3.

Which objects are affected? List all objects that are in the transport request and also in the TBOM.


148


2012

E2E200


Task 3: Create a test plan based on the results of the Business Process Change Analyzer.

2012

1.

Create a test plan.

2.

Generate the test plan with the preselected test cases. Which test cases are selected?


149


E2E200

Solution 5: Business Process Change Analyzer Task 1: Record a technical bill of material (TBOM) for transaction CAT2. 1.

Log on to SAP Solution Manager with your user, E2E200-## (change ## to your group number). Navigate to the Test Management work center and choose Test Preparation. a)

Call transaction SM_Workcenter and go to the work center Test Management work center and the Test Preparation tab.

b)

Alternatively you can choose transaction SOLMAN_WORKCENTER and select Test Preparation in the tab Test Management

Figure 110: SAP Solution center: Work Centers


150


2012

E2E200


2.

In the Test Preparation view, select the Solution Manager project E2E200_## (## = group number) that you created in the exercise for Solution Documentation. Navigate to the Business Blueprint. Which transaction is it? a)

Figure 111: SAP Solution center: Work Centers

You can navigate to the Business Blueprint by clicking on Business Blueprint button. You should then reach transaction SOLAR01. 3.

In your project, select the business process step Record working times in backend, which you added in the exercise for Solution Documentation, and select the attributes of the related transaction. a)

Figure 112: Business Blueprint


2012


151


4.

E2E200

In the attributes of transaction CAT2, chose the TBOM tab. Start to create a technical bill of material for this transaction. Choose Create Option Dynamic. This means that a trace is executed to record all objects that are used in this transaction. a)

Figure 113: Attributes Maintenance

You are logged on in system RWE, client 801, and transaction CAT2.

Figure 114: Create TBOM

5.

Enter some working time in transaction CAT2 and finalize the creation of the TBOM. Make the following entries in transaction CAT2.

Figure 115: Time Sheet: Initial Screen

Do not change the default values for Data Entry Profile and Personnel Number.


152


2012

E2E200


Enter some working time entries and save it. After that, a TBOM with name and date will be created.

Figure 116: Time Sheet: Data Entry View

a)


2012


153


6.

E2E200

Display the object list of the newly created TBOM. a)

Figure 117: Attributes Maintenance Screen

In the following screen, you will see all objects that are used in transaction CAT2.

Figure 118: TBOM Content Display


154


2012

E2E200


Task 2: Perform an impact analysis run with the Business Process Change Analyzer. 1.

Navigate to the Test Management work center and select the BP Change Analyzer menu. Enter all relevant data in the Business Process Change Analyzer. Please use transport request RWEK900205 that was already created on system RWE:801 under user E2E200-owner for you. a)

In the following screen you will find the necessary entries.

Figure 119: Change Impact Analysis

2.

Start the change/impact analysis and list the results. a)

Select the Run field and, in the next screen, choose Start Immediately.


b)

After a few seconds, choose Refresh. If the run was successful, the status is set to Finished.


Select your project and choose Display Details.

Figure 122: Display Details


2012


155


3.

E2E200

Which objects are affected? List all objects that are in the transport request and also in the TBOM. a)

Choose Display Intersection to display the list of objects.

Figure 123: Details of selected projects

Task 3: Create a test plan based on the results of the Business Process Change Analyzer. 1.

Create a test plan. a)

Choose Create Test Plan.

Figure 124: Create Test Plan

b)

In the next screen, enter following values.

Figure 125: Create Test Plan


156


2012

E2E200


2.

Generate the test plan with the preselected test cases. Which test cases are selected? a)

After confirming the Create Test Plan screen, you will see the Test Plan:

Figure 126: Test Plan

Drill down in the test plan hierarchy until you see the test cases. The following test cases are preselected: • •

The automatic test case ZETIMERECORDING_HR. The manual test case ZDTIMERECORDING.

b)

Select all test cases and choose Generate Test Plan.

c)

In the Transport dialog box, save the test plan as local object. If successful, you will receive following message.

Figure 127: Information

2012


157


E2E200

Lesson Summary You should now be able to: • Get an overview about SAP’s methodology for testing and how it is used in SAP Solution Manager. • Determine the change impact with the Business Process Change Analyzer. • Get known the Test Management Work center.

158


2012

E2E200

Unit Summary

Unit Summary You should now be able to: • Describe the Solution Documentation process. • Describe the different types of documentation and what they are used for. • Explain the Architecture and Use Cases of the Solution Manager System Landscape Documentation. • Describe how to keep the Solution Landscape Documentation up to date. • Define a project in SAP Solution Manager using transaction solar_project_admin. • Assign the technical landscape to a Solution Manager project. • Use the Business Process Repository (BPR) as template to document core business processes. • Assign additional information to individual business process steps. • Define a new solution in SAP Solution Manager and transfer business process documentation to it. • Describe best practices to tailor solutions in SAP Solution Manager. • Describe Reverse Business Process Documentation (RBPD) with the Solution Documentation Assistant. • Describe the different possibilities for modelling business processes using new offline tools with interfaces to SAP Solution Manager. • Get an overview about SAP’s methodology for testing and how it is used in SAP Solution Manager. • Determine the change impact with the Business Process Change Analyzer. • Get known the Test Management Work center.

2012


159

Unit Summary

160

E2E200


2012

Unit 4 Enhanced Change and Transport Management

159

Unit Overview The Change and Transport System (CTS) helps you to organize development projects in ABAP Workbench and in Customizing, and then transport the changes between the SAP systems in your system landscape. As well as ABAP objects, you can also transport Java objects and non-ABAP objects in your landscape. In this unit Enhanced Change and Transport System (CTS+) will be introduced as well as some set up specifications and best practices.

Unit Objectives After completing this unit, you will be able to: • • • • • • • • • • •

2012

Describe the main features and best practices of the CTS. Describe the main features / advantages of the CTS+. Describe which objects can be transported with the CTS+. Describe the differences between the loose and close coupling scenario. Describe the concept of delivering new features for CTS+ with the SL Toolset. Use the Transport Organizer Web-UI for managing transport requests for non-ABAP developments. Release transport requests in CTS+ and import them into the target system. Describe the components of the SAP NetWeaver portal. Create a new iView in the portal content studio and transport it. Attach the transport package with the iView to a transport requests using the close coupling scenario. Know the advanced use case for SAP Enterprise Portal.


161

Unit 4: Enhanced Change and Transport Management

• • • • •

E2E200

Describe the integration of NWDI into CTS+. Describe the integration of PI into CTS+. Know about using CTS+ with LCM Lifecycle Management Console for SAP BusinessObjects BI. Know about using CTS+ with SAP HANA Studio for SAP. Explain the meaning of the most important CTS+ parameters for source and target systems.

Unit Contents Lesson: SAP Change and Transport System for ABAP ...................163 Lesson: Enhanced Change and Transport System CTS+ Overview ....174 Lesson: Working with CTS+ ...................................................194 Lesson: Enterprise Portal and CTS + ........................................209 Exercise 6: Portal Content Studio ........................................221 Exercise 7: Transport Package Editor ...................................225 Exercise 8: Transport Organizer Web UI................................233 Lesson: (Appendix) CTS+ Configuration For Other Scenarios ...........242 Lesson: (Appendix) Transport Parameters for CTS+ ......................265

162


2012

E2E200

Lesson: 161

Lesson: SAP Change and Transport System for ABAP

SAP Change and Transport System for ABAP Lesson Duration: 20 Minutes

Lesson Overview This lesson will give you an overview about the main features and functions of the Change and Transport System (CTS) for ABAP applications .


Describe the main features and best practices of the CTS.

Show CTS Demo.

Business Example New custom developments or customizing settings should be transported throughout the system landscape from the development system to the production system.

SAP Change and Transport System for ABAP

Figure 128: Change Control Management: Change and Transport System (SAP/ Non-SAP)

2012


163


E2E200

Figure 129: SAP Change and Transport System

The change and transport system is divided roughly in three areas: • • •

The change and transport organizer to manage transport requests, which consists of the transactions SE09, SE10 and SE01 The transport management system, which contains transaction STMS to manage the transport configuration OS-level tools like tp or R3trans, which are used to execute transport steps

Limitations of the Transport Organizer: • • • •

164

Transport of single objects (lowest granularity) Teamwork capabilities (one transport request with several tasks for different developers) No control of correct transport sequence No control of completeness of transport requests


2012

E2E200


Figure 130: Transport Organizer & Transport Requests

The Change and Transport System is integrated into the tools of the Development Workbench. Main features of the Development Workbench (DWB): • • • • •

Automatic recording of all changes in transport requests Object locking Classification of development objects in packages Version history Customizing logging

Figure 131: Release Transport Requests

After the release the transport request is exported as a data file to the transport directory (../trans/data) and the request is listed in the import queue of the following target system as defined in the TMS. This ensures the correct sequence for the target systems.

2012


165


E2E200

If the transport request contains repository objects the system creates automatically a new version of these objects in the version database of the development system.

Figure 132: Import Transport Request to Target System

• •

166

During import tp triggers R3trans to import the data into the target system and executes all relevant transport steps to generate and activate the objects. The transport request then appears automatically in the import queue of the next target system


2012

E2E200


Figure 133: Flexible Configuration of Transport Routes

• • •

•

•

Here you can see an example for a the transport routes of a complex customer system landscape. There are several production systems and a training system connected. The green lines are consolidation routes. They go out of the development system. Development classes and packages are assigned to consolidation routes. This determines where a certain repository object is transported to. The black lines are delivery routes from the QA system to the production and training systems. All customizing and workbench requests that are imported into the QA system are automatically forwarded into the import queues of the production and training systems. Transports of copies which are imported into the QA system do not follow the transport routes into the production and training systems.

Figure 134: Multi Developer Capability

2012


167


E2E200

The process for work with change requests is as follows: • •

The team lead- who has the responsibility for a specific implementationcreates a change request and adds the team members to it. All team members receive automatically a task inside the change request. Customizing or change of Repository objects done by the team member is then entered in the corresponding task.

There are two main types of change requests for recording changes: • • •

WB change request: They are used to record changes of repository obejcts, like reports, includes, tables, screens, transactions, and so on. They are also used to record all cross-client customizing changes, for example: logical systems, printers, file name defintions CUST change requests include all client-specific customizing changes, which are normally client-specific table entries

Figure 135: TMS Quality Assurance Procedure

TMS Quality Assurance increases the quality and the availability of the production systems by letting you check requests in the QA system before they are delivered to subsequent systems. To use this feature, activate the QA approval procedure in your QA system. When activated, transport requests are only forwarded to the delivery systems if all the QA approval steps are processed for each request in the QA system and each request has been approved. (When you configure the QA system, you determine how many QA approval steps have to be processed for each request.) If a check for an approval step is not successful, the entire request cannot be approved. Rejected requests are not imported into the delivery systems of the QA system.

168


2012

E2E200


If you reject requests, there is the risk that errors may occur when they are imported into the delivery systems. This is a result of the requests containing objects that are referenced from other requests. It is safer to correct an error using a subsequent transport.

Figure 136: Transport of Copies

Transports of Copies are special transport requests. These kind of requests are used to transport objects to only one specified SAP System, without delivery to another SAP System. Transport of copies are created manually using the CTO (Change and transport organizer) Advantages: • • • • • •

•

2012

Repository objects are locked as long as possible in DEV Number of Transports in Production is reduced Transports of copies are periodically imported into QAS but do not follow the transport routes into PRE Only the original transport request can reach PRE PRE remains a clean environment Transport of Copies are used in the Change Request Management to create test transports, which are only transported to the test system, but which are never transported to the production system. Releasing Transport of Copies also creates a new version of repository objects similar to normal workbench requests


169


E2E200

Figure 137: Project Assignment

The CTS Project assignment allows you to bundle transport requests which belongs to a specific implementation or maintenance project. The import queue of the target system can be filtered for a specific CTS project. All transport requests can then be imported either by using the import all button or import single (after selecting individual or all requests). Project assignment lowers the risk of forgotten transports.

170


2012

E2E200


Figure 138: Critical Objects Check

•

•

•

•

• • •

•

2012

To check if the change requests in an import queue contain critical objects that should not be imported into the target system, go to the Import Overview and choose Queue → Check → Critical objects. The object lists of the requests are checked to see if they contain critical transport objects. The results are displayed in a hierarchical list. Requests containing critical objects are marked with the appropriate icon. The critical objects are highlighted in color. Before performing this check, you need to have maintained the critical transport objects in the SAP System whose import queue you want to check for critical objects. To display or maintain the critical transport objects defined for the relevant SAP System, call transaction STMS in the SAP System for which you want to display/maintain the critical objects. Choose Overview → Imports → Extras →Critical transport objects. Since the table of critical objects is a Customizing table, it should be maintained in the development system, and then transported to other SAP Systems from there. The TMS check for critical transport object is executed at the time of the import into production. The transport parameter CHK_CRIOBJ_AT_EXPORT allows a check for critical objects before release. Critical Transport Objects have a long import runtime. During the time of the import, inconsistencies, dumps and, in rare cases, even logical errors (wrong results) can occur in the system. Therefore, critical transport objects should be known. Imports that contain critical transport objects should be imported during downtime or, at least, during times of low system usage. Business critical objects are central objects, which are used by many applications or very critical applications. If they are changed it might have severe side-effects in many areas. Therefore, an extended test is needed before these objects are imported into production.


171


E2E200

Examples of critical and uncritical objects: •

Uncritical Objects

•

– Forms, e.g. SAP Scripts – Authorizations – Simple Customizing (without generation of repository objects) Critical Objects

•

– Customizing with generation of repository objects (e.g. LIS) – Report sources – Dictionary Objects Very Critical Objects – –

•

Frequently used Sources (e.g. User Exits) Dictionary Objects which must be converted (esp. Big tables like vbap, coep) – Dictionary Objects which are frequently used by other objects (komk, komp, t001w) Critical Objects from a Business Perspective – – –

172

SD condition tables Central user exits Complete development classes in business critical areas


2012

E2E200


Lesson Summary You should now be able to: • Describe the main features and best practices of the CTS.

2012


173


Lesson: 172

E2E200

Enhanced Change and Transport System CTS+ Overview Lesson Duration: 20 Minutes

Lesson Overview This lesson will give you an overview about the Enhanced Change and Transport System (CTS+).


Describe the main features / advantages of the CTS+. Describe which objects can be transported with the CTS+. Describe the differences between the loose and close coupling scenario. Describe the concept of delivering new features for CTS+ with the SL Toolset.

Business Example Customer wants to use a common transport logistic tool for both, ABAP and non-ABAP developments.

174


2012

E2E200

Lesson: Enhanced Change and Transport System CTS+ Overview


SAP offers many tools and workbenches to develop applications or create content for end users. There are also many different tools which are used for transporting the applications from a development system to a productive system through a system landscape. In some cases, the tool supports a transport like e.g. CTS does it for the ABAP workbench. In other cases like e.g. in the Portal, there is an import and an export mechanism available, but the system administrator has to take care that the files are available at the right locations when performing an import. There is a difference between Export / Import and Transport. Export / Import means that the changes made in an application or newly created content can be collected and exported in a file-format. This file needs to be stored somewhere. An administrator has to upload the file to the target system and start the import or deployment. Transport includes logistics for the exported files. The administrator hast to start the import, but he does not have to take care of the location of the files. In addition, there is an option to track what has been imported, to monitor the results and to get reports on import statuses. CTS does all this for ABAP based programming and customizing.

2012


175


E2E200


Enhanced CTS offers the possibility to transport objects created in other languages than ABAP via the Change and Transport System of ABAP. The goal is to have one Transport Tool (CTS) which supports all Workbenches and Applications when it comes to transports. The tools for creating applications and creating content remain the same. Options to attach applications or content to a CTS transport request are integrated into the different workbenches. The level of integration differs for different workbenches. Enhanced CTS aims for a unified single transport tool which simplifies the life of an Administrator who is responsible for performing imports. He has to access only one tool to start imports for very different backends. Deployment tools are called automatically. It is very easy to monitor what has already been imported and if the import went well. The queues and the history in CTS provide a good overview on what needs to be imported. The usage of CTS+ for non-ABAP developments has a lot of advantages.

176


2012

E2E200


Enhanced CTS allows to: • • • • • • •

• • •

Use the ABAP change and transport system (CTS) for all transports Build transport routes with an arbitrary number of systems Define arbitrary system roles Define multiple direct successor systems for each system Support synchronized transports between ABAP and Java or other content Combined transport requests for mixed sets of objects (ABAP, Java, EP objects, PI objects, ) Non-ABAP applications inherit all properties of the ABAP Change and Transport System in terms of documentation, tracking and troubleshooting features Central administration of all transports (ABAP, Java, EP objects, PI objects ) in one User Interface (UI) Simplified transport management, to avoid inconsistent system states No need to upgrade of Java landscapes

A typical landscape consist of three systems for an application. One system where developments are done, one test system and one which is used productively by end-users. The set up may differ. For supporting transports, one additional system is needed where CTS can be used. Recommendations on which system should be used for CTS, will follow later on. The content is created or developed in the development system respective the corresponding development workbench. Within the workbench, the developer should find a mechanism to export what he did. During the export, he might have an option to choose a transport request and attach his files directly from within the workbench. The availability of this option depends on the application. If it is not available, a manual attachment process is needed to post the new content to CTS. After that, a transport request can be released and the import can be started. This is done within CTS. For the file types supported by now (see next figure) CTS calls the deployment tool (e.g. SDM) of the application to deploy the new content to the next system in the route. After a successful import into the QA system of the application, CTS forwards the transport request to the queue of next system – in this case the productive system. After a successful test, the administrator in CTS could start the import for the productive system. Some systems require post installation steps. If you are transporting epa-files containing roles for example, you have to assign the new roles which were imported to the users or groups which should use the new content. KM Documents require a manual import in the target system. Transport Requests are created in the communication system with the SID of the non-ABAP development system as part of the request name, e.g. JADK000129.

2012


177


E2E200

Figure 141: Supported Solutions and Deployment Options up to now

This slide lists the object types which can be transported via CTS+ out of the box and if the CTS Plug-in is not available (see following chapters for details about CTS Plug-in). Not all of these objects types were supported with the first release of CTS+ in SAP NetWeaver 7.0 SPS 12. A look into the release notes both of CTS+ and the application is always advised to find out about supported objects with the release that you currently have in place. In addition, the level of

178


2012

E2E200


integration is not the same for all supported files. Some require manual work when attaching them to a transport request, for others, you need to something in the target system after the import. •

•

•

DIP stands for Development Infrastructure Packages. This file format is used when transporting your Java applications from within the developer studio. You can use this to transport activities. With SAP NetWeaver Master Data Management 7.1 the following set of data model objects can be transported from a source system to a target repository: Tables & Fields, Relationships, Languages, Roles, URLs (Web Links), XML Schemas, Remote Systems, Ports, Validations and Calculations, Assignments, Workflows (new with SAP NetWeaver Master Data Management 7.1), Import Maps (with SAP NetWeaver Master Data Management 7.1), Syndication Maps (with SAP NetWeaver Master Data Management 7.1), Matching Rules including Matching Strategies (with SAP NetWeaver Master Data Management 7.1). You can use CTS to transport any file type that you might have. When importing, these files can be saved to a specific folder on the target system. This does not include any automatic deployment. This option is called loose coupling. You can find further details later in this presentation. Enhancements to CTS that will also be presented later, allow to define an application type. You could then use this application type to define a file share, where files associated with this application type should be stored.

Figure 142: Supported Solutions: New features and Milestones in CTS+

2012


179


E2E200

This slide give an overview about new supported scenarios available with new NetWeaver and Solution Manager releases. •

•

•

180

Starting with SAP NetWeaver 7.3 Portal, Change Recording is provided. Without Change Recording you have to add the objects that you would like to export to an epa-file manually. With Change Recording this can be automated. Whenever you change, create or delete an object, this is recorded in a so-called changelist. You can then let the system create an epa-file out of the changelist and attach it to a transport request. With this, it is even possible to transport the deletion of an object – a functionality that was missed by portal content administrators in the past. Change Recording runs on the development portal. As soon as you attach the changelist to a transport request, the CTS Communication System is contacted to get the default request and send over the epa file (like it was done before without Change Recording). There is also an integration of CTS+ in CMS of NWDI available. This integration can be used since SAP NetWeaver 7.0 SPS 14. It is integrated in the Assembly step in CMS and would attach the SCA to a transport request. Starting with SAP enhancement package 1 for SAP NetWeaver 7.0, the CM Services are provided. With that, CMS is not needed any more. It is still there and can be used. Maintenance is ongoing. But there is now the option to use CM Services and CTS instead of CMS. CTS takes over the tasks of creating a system landscape and moving the SCAs from one system to the other. CM Services are used e.g. to create the development configuration and to perform the exports. With CM Services, you can still transport complete SCAs. In addition, you do now have the option to transport on a more granular level. You can either transport the activities containing the sources that you changed (available since SAP enhancement package 1 for SAP NetWeaver 7.0) or the SDAs that were rebuilt because of your changes (available since enhancement package 2 for SAP NetWeaver 7.0). Transporting the sources would mean that a rebuild is needed on each system – on test and productive system as well, not only for the development system. SL Toolset is SAP new strategy to deliver software logistic functionality. Improvements in the CTS+ area are delivered with the CTS Plug-In as part of the SL Toolset. CTSPlug-In will only be available for the SAP Solution Manager.


2012

E2E200


Figure 143: Loose Coupling and Close Coupling

CTS+ offers two possible scenarios: •

Loose Coupling – –

•

No direct integration of CTS+ mechanisms into application Additional tool needed to create transport requests, attach files and release transport orders – Manual attachment of files to transport requests via file upload – Import only on file system level, manual actions for activation Close Coupling – – – – – – –

2012

CTS+ mechanisms are available via additional buttons, links and input-fields within the existing export UIs Automatic attachment of files to transport requests directly within the application (e.g. EP, PI, etc.) Get default transport requests Automatic creation of transport requests possible Automatic release of transport request possible Connection from application server to CTS server Automatic deployment and activation


181


E2E200

Figure 144: Enhancements of the CTS

This slide shows the main building blocks of CTS+: •

•

• •

182

The boxes in dark colors show the parts of CTS that were already in place and are used for ABAP transports. The boxes in lighter colors illustrate what has been added for CTS+. The Transport Organizer Web UI is an Web Dynpro ABAP Application which has to be used by applications to manage transport requests. It replaces the transaction SE09. SE09 can only be used for non-ABAP transports in case of the Dual Stack system SAP NetWeaver Process Integration. The CTS Deploy Web Services is needed to be able to deploy via e.g. SDM. CTS+ requires an AS Java for this Web Service and an AS ABAP for the rest of CTS.


2012

E2E200


Figure 145: CTS+ Components

Lets take a more detailed look at the systems involved when transporting via CTS+ and what runs where. As we have seen before, you need one system, where you can do an export (source system) and at least one where you can import (target system) what you exported before. In addition, you need a system where CTS+ runs. This should – in the case of non-ABAP – be the SAP Solution Manager. On the source system, an export client is needed. This can be a tool or a UI that you can use to package objects from the application to create an export file. If the application is supporting CTS+, then this export client will provide an option to attach the export package to a transport request in CTS. To get the transport request and some details about it, the export client contacts the CTS system. Within the Export Client, there should also be a link provided which can be used to open the Transport Organizer Web UI on the CTS system. The Transport Organizer Web UI is used to manage the transport requests for non-ABAP systems – details will follow later. As soon as the export is finished and the transport request has been released, the import into the target system can be started. The Deploy Web Service is used when importing files for Java applications. The Deploy Web Service client on the ABAP side hands over the files to the Deploy Web Service on the Java side which then starts the import service on the target system. A representation of the target system had been configured in CTS. This configuration contains information about the deploy URL of the target system and a user who does have permissions for the deployment. The import service on the target system which executes the deployment can e.g. be the deploy controller if the system is running on SAP NetWeaver 7.1 and up. The import service does the real deployment to the target

2012


183


E2E200

system. The connection between CTS and the target system remains open until the deployment finishes. After that, the administrator can find information about the success of the deployment and a detailed log file in CTS as well. •

•

•

•

•

184

Communication System: The communication system is the system, where the TMS transport systems (ABAP and non-ABAP) with their transport layer and transport route are configured. Deploy Web Service: The Deploy Web Service Client is needed on the ABAP side to enable the transport control program tp on SAP NetWeaver AS ABAP to communicate with the CTS Deploy Web service on SAP NetWeaver AS Java. It consists of two configuration parts: http connection (SM59) and logical port (LPCONFIG). Transport Organizer Web UI (ABAP): Web UI implemented as Web Dynpro ABAP application with basic SE09 functions to create and maintain transport requests for non-ABAP systems and JAVA stacks of dual-stack systems, attach non-ABAP objects and release transport requests. Export Client: tight integration of CTS+ in the application of the source system where non-ABAP objects are created (known as close coupling – available since SP Stack 14 for EP, NWDI, SLD, PI, KM); to enable this tight integration an RFC destination to the TMS communication system needs to be configured in the Visual Administrator of the source system (except for NWDI use case – here the NWDI server needs to be configured for tight integration, not the non-ABAP source system). The Export Client communicates with the enhanced Transport Organizer to fetch a proper transport request and to attach the non-ABAP objects directly with the application (e.g. EP Content Studio – Export Wizard). Import Service: import mechanism running on the target system (SDM, XI Import Tool, SLD Import, KM Import, etc.). During import of non-ABAP objects the transport control program tp calls the Deploy Web Service on the Java stack and the Deploy Web Service triggers the CTS+ Import Service on the target system (e.g. SDM) to deploy the transported objects.


2012

E2E200


Figure 146: Accelerated innovation via CTS Plug-In in SL Toolset

With the SL Toolset SAP delivers new functionality in the CTS+ area, the CTS Plug-In. •

•

Software Logistics Toolset (SL Toolset) stands for a product-independent delivery channel which delivers up-to-date software logistics tools and a unified consumption experience with the target to reduce total cost of ownership. CTS Plug-In

•

– Is delivered with SL Toolset – Has to be installed on SAP Solution Manager – Provides additional options where to use CTS+ – Is available for Solution Manager 7.10 and 7.0 SP25 CTS+ now supports – – – –

Lifecycle management console of SAP BusinessObjects BI SAP BusinessObjects Planning and Consolidation (MS Edition) Integrating your applications with CTS+ Support for additional applications is planned

For further information about the delivered software logistics tools, the supported implementation processes and SAP application products, see Central Release Note for Software Logistics Toolset 1.0 –1563579.

2012


185


E2E200

Figure 147: CTS Plug-In in SL Toolset

The SL Toolset can only be installed on the Solution Manager. Therefore the Solution Manager must be the communication system if the customer wants to use the new functionalities which the SL Toolset provides. To be able to use the new functionality of CTS+, some prerequisites apply: •

CTS+ System –

•

SAP Solution Manager has to be the CTS+ System – CTS Plug-In can only be installed on SAP Solution Manager. – CTS Plug-in of SL Toolset 1.0 SP1 requires SAP Solution Manager 7.1. – CTS Plug-in of SL Toolset 1.0 SP2 requires SAP Solution Manager 7.1 or SAP Solution Manager 7.0 EHP1 SP 25 at least. Applications to be used with CTS+ – –

CTS+ integration provided by SAP (e.g. for Lifecycle management console for SAP BusinessObjects BI 4.0): CTS+ Integration provided by vendor – or done by you

If you would like to start using the new functionality of CTS+, you have to download the required components from the SAP Service Marketplace (Add-On installation package SAPK-100AGINCTSPLUG CTS_PLUG_100: Add-On Installation). They can be found in the SL Toolset. New functionality of CTS is first provided with SL Toolset 1.0 SP1 and has been enhanced with SP2. After having downloaded the files, you have to install the Plug-In on your SAP Solution Manager with transaction SAINT. SAP Note 1533059 provides details on the installation process.

186


2012

E2E200


After having downloaded and installed the plug-in, you have to activate it if this is the first time that you installed the plug-in:. • •

•

2012

Call transaction SA38 on your SAP Solution Manager Run the program /CTSPLUG/CTS_ACTIVATION -> CTS Bootstrapper Plug-In, CTS Server and Services Plug-in are imported into your SAP Solution Manager No Activation required in case of updates – just install the current plug-in


187


E2E200

Figure 148: Using CTS+ for your own applications Landscape: Integrating your Application with CTS+ - Systems involved

•

•

If you would like to use CTS+ for your own applications, you should use CTS Plug-In provided with SL Toolset 1.0 SP2. As most probably the application that you would like to integrate does not run on SAP NetWeaver AS Java, you would need this version of CTS Plug-In at least to be able to provide an integration of CTS+ into your application on the export side via ABAP Web Services. Only starting with SL Toolset 1.0 SP2, the Export Web Services are provided. You will learn more in the reminder of this chapter. On the application side, there are two options: 1.

• •

•

188

You have an application where the vendor told you that he now supports CTS+. In this case, the vendor should provide you with the information about the prerequisites for his application and some documentation. 2. You implemented or plan to implement CTS+ for your own application. In this case, there are no general prerequisites. You can define them while implementing. If you would like to implement CTS+ for an application, the following systems are involved: On application side, you need a system where you would like to export something – the source system. In addition, you need one or several systems where you would like to import the objects or files that you exported before – the target system(s). In addition, you need a system which manages the system landscape and the transports for you: SAP Solution Manager. On this system, you have to install the CTS Plug-in taken from SL Toolset 1.0 SP2 at least.


2012

E2E200


Figure 149: Using CTS+ for your own applications Implementation: Integrating your Application with CTS+ - where to do what

Implementing CTS+ for your application requires actions at different points. Some of them are configuration tasks, some require programming. On this slide, we will give an overview on the different tasks. Consider if and which of them you can fulfill before starting your implementation. This slide shows a logical view on what has to be done where. The following list of required actions is not a step by step procedure. It describes what has to be done but not in a strict sequential order. It describes the process for transporting a new application content via CTS and what is required for which action. Sometimes there are dependencies between the different actions. 1.

2.

2012

On the CTS+ system, you need a representation for your source and target system(s). This requires creating systems in TMS and connecting them via transport routes. In addition, you need an application type for your application. The deployment method is associated with the application type. Therefore an application type is needed for every application. This step is a configuration task. The final goal when implementing CTS+ for an application should be to provide close coupling. This means that your application should provide an export tool that can be used to collect objects that you would like to export and / or to package all changed objects and attach this collection of objects automatically to a transport request in CTS. Having an export tool available within your application is a prerequisite for close coupling. The export tool might already exist within your application. It is also useful without having a CTS+ connection in place. You should use this tool (if already available) to integrate it with CTS+ so that users can continue working with a tool that they already know – enhanced by options to attach the exported package to a transport request in CTS. You will see later on what has to be done


189


3.

4.

5. 6.

190

E2E200

to achieve this. Nevertheless, you would still need an option to create a package or a file containing whatever you would like to export even if you plan to provide loose coupling. During the export process in case of close coupling, the user would have to attach the file to a transport request. At this point in time, the application has to get in contact with the CTS system to ask for a transport request and add the file to this request. You can either do this via an export API if your application is running on SAP NetWeaver AS Java or by calling Web Services running on the AS ABAP of the CTS system – details will follow. Your source system needs an SID so that CTS can recognize it and can create a transport request. In CTS, each system has to have an SID – it is a unique ID representing the system in the transport landscape. The ID of each transport request starts with the SID of the source system for which the request is created. If your application does by nature not have an SID consisting of three digits, you have to find an option to map it to one. In case of close coupling, the application also has to send the application type to the CTS system, In case of loose coupling, you have to choose the application type when attaching the object to a transport request in the Transport Organizer Web UI. For close coupling, you need a connection between your source system and the CTS system. This connection has to be created on the source system and contains information about the CTS system (SID, server name, log-on user or option for Single Sign-On). If there is no export tool available for or within your application, you can start with loose coupling on the export side After having attached something to a transport request, the request has to be released and can then be imported into the target system. Releasing the transport request and starting the import is done within TMS. Nothing has to be configured or implemented in here. Only when the import is started, CTS needs to know what to do with the file that you attached to the request before. As CTS does at first not know anything about your application, this is where you also have to implement something. In the first step, you created an application type for your application – now you need a description what to do if this application type is used. You can either implement an EJB or use scripting to describe the import. This deployment method has then to be associated to the application type that you created in step one. So this step requires configuration and programming. The deployment method and the script or EJB that you created should then call the deploy tool of your application which does the real deployment. The connection between the application and the CTS system remains open while the deployment takes place. After the import or deployment on the application side has finished, your application has to send back some information to CTS whether the import was successful or not. This information has to be mapped to the different return codes in CTS (0, 4, 8, 12). This information is needed to display the correct status of a transport


2012

E2E200


request in the import queue of the target system. A detailed protocol containing information on the import and especially error messages in case the import could not be done, should also be sent back to CTS. Possible scenarios on the export side: •

•

•

The first and easiest level could be to provide a loose coupling. This would mean that a user who would like to execute an export, uses the same process that he used before a CTS+ integration was available. He would download the file containing the exported data to a share or his local machine. After that he would open up the Transport Organizer Web UI, choose the correct application type and upload the file to a transport request (which already exists or which he has to create manually). This way of integrating CTS+ into the export process should only be a first step. You should aim for a close coupling integration which would simplify the life of the one who does the export a lot. An intermediate step could be to use a command line tool (provided by SAP) to attach the exported file to a transport request. Details are provided in SAP Note 1278181. The final and easiest to use solution would be close coupling. Close coupling would mean that the export process or tool (which is provided by your application) offers the possibility to directly attach the exported data (as a file) to a transport request. On SAP Solution Manager, you can find some ABAP Web Services (coming with CTS Plug-In) that you can use to e.g. ask for a transport request, attach data to the request or provide a link which can show additional information concerning (existing) transport requests.

Possible scenarios on the import side: •

•

•

2012

There are again two possible levels of integration. Loose coupling would mean that some kind of file system is used to store the files which are attached to the transport requests when they are imported. Some manual action would be required afterwards to deploy and / or activate the files depending on the application. If close coupling is provided, the changes that are part of a transport request are available on the target system after the transport request was imported successfully. There are different options to achieve this. You can either implement an EJB if you can use an SAP NetWeaver AS Java to trigger the deployment or you can create a script: For the application specific deployer using EJBs, you have to implement at first an EJB for your application type. Use the Import API to do so. The implementation has to be deployed to the system where the Deploy Web Service for this application type should be used. In most of the cases this should be the AS Java of the SAP Solution Manager. Integration into CTS import process via EJB is done by implementing a stateless session bean on application side. This EJB has to implement the DeployerEjb interface


191


E2E200

Beans. Implementing this interface will be looked up on the SAP NetWeaver AS JAVA where the Deploy Web Service is hosted and are then called during a CTS import. You need to implement following parts: – – •

The ejb file containing the code implementing the EJB The ear file packing the ejb.jar as an application and making it as deployable Using a script: –

–

–

192

The CTS+ integration module specifies a list of parameters provided to the script and defines valid return codes. There are also administrative rules about how the script should be properly activated. The script should be implemented as a standard batch script (.bat) for the Windows-like operating systems or as standard shell script (.sh) for the UNIX-like platforms. The decision point is a fact under which operating system(s) the SAP NetWeaver Application Server JAVA (JAVA AS) hosting the CTS+ Deploy Web Service runs. The Deploy Web Service delegates the deployment request to the well defined batch script and expects to get reasonable results back. What the script does and how it does it is up to the script provider. The script developer can implement, for example, simple ftp-based file copying or start any other script or run an available (if any) deploying client application. If you already have a deploying script you can re-use it. All that you have to do in the batch script for such a case is to adjust it and to handle the incoming parameters, so that your “real” deploying application could understand them. Then just call your application and when it finishes return the corresponding return code back to CTS. After you have created the deploying mechanism – be it EJB or Script – you have to configure your target system in TMS accordingly.


2012

E2E200


Lesson Summary You should now be able to: • Describe the main features / advantages of the CTS+. • Describe which objects can be transported with the CTS+. • Describe the differences between the loose and close coupling scenario. • Describe the concept of delivering new features for CTS+ with the SL Toolset.

Related Information Additional Information on CTS-Plugin and SL-Toolset: • • • • • •

SAP Service Marketplace: http://service.sap.com/changecontrol SAP Developer Network (SDN): http://www.sdn.sap.com/irj/sdn/cts SAP BusinessObjects Community (BOC): www.boc.sap.com Education and Certification possibilities: http://www.sap.com/education/ BPC SDN Publications: https://www.sdn.sap.com/irj/sdn/bpx-epm BPC Documentation (OKP, RKT) – –

•

• •

•

2012

http://service.sap.com/okp > SAP Business Planning and Consolidation http://service.sap.com/rkt > SAP Solutions for Enterprise Performance Management > SAP Business Planning & Consolidation BPC Setup and Application Guides for Root Cause Analysis and Change and Transport System – SAP Notes RCA: 1461749, 1343071, 1328011, 1265070, 1126554 – SAP Note CTS: 1582525 Documentation for CTS with CTS Plug-In: http://help.sap.com/saphelp_ctsplug100/helpdata/en/48/c4300fca5d581ce10000000a42189c/frameset.htm Guides on SDN: http://www.sdn.sap.com/irj/sdn/cts?rid=/webcontent/uuid/c0ce1dd8-c0202b10-d080-a1cd3e985af1 Documentation for SAP BusinessObjects BI 4.0: http://help.sap.com/businessobject/product_guides/boexir4/en/xi4_lcm_user_en.pdf


193


Lesson: 191

E2E200

Working with CTS+ Lesson Duration: 20 Minutes

Lesson Overview This lesson will explain how to work with the Enhanced Change and Transport System (CTS+) after it has been configuerd for a non-ABAP system landsacpe.


Use the Transport Organizer Web-UI for managing transport requests for non-ABAP developments. Release transport requests in CTS+ and import them into the target system.

Business Example CTS+ has been setup for a SAP NetWeaver Portal system landscape. New transport requests must be created, released and imported into the follow up target systems containing objects of the portal content studio.

194


2012

E2E200

Lesson: Working with CTS+

Working with CTS+

Figure 150: Roles in CTS+

•

This slide tries to show the tasks, that a certain role has to fulfill and how often this has to be done. In principle, four roles can be identified in the process of using CTS: –

–

–

2012

An Administrator on CTS has to do the initial configuration tasks. This is a one time task and he does not need any knowledge about the applications for this task. After that, he has to configure transport routes. To be able to do so, he needs to know about the applications and about the systems that are used. This brings him closer to the applications. This task occurs from time to time, whenever new systems are set up or a transport route has to be changed. An Administrator of the application has to do some settings to make CTS known by the application. This needs to be done only once per application. The Administrator of the application needs to know details about the CTS system – thats why he is working closely to CTS. A developer working within an application has to fulfill several tasks. Some of them are closely related to CTS+ and require some knowledge about Transport Requests. Others can be done without knowing anything about CTS. Most applications dont use any change recording as of today. Therefore content is created by the developers without contacting CTS. At the same time, this is the main task of a developer. After having created some content, the developer exports this content. When doing so, he needs to know about the transport


195


•

•

196

E2E200

requests that he should use. He can use one transport request to collect several content objects. During the export process, the developer can select a transport request. After having exported all necessary objects, the developer has to release the transport request. This is done via the Transport Organizer Web UI – a tool closely related to CTS+. After having released a transport request, the developer can and should monitor the transport. He can use the Transport Organizer Web UI for this as well. He can view the import log from within the Transport Organizer Web UI. Now the developer is working very close to the CTS system. If there was an error during the import, he has to work with the administrator if the error was caused by deployment issues and not by the content of the transport. – A Transport Admin of the CTS system has to start the imports from the queue of the respective system. Before doing so, he needs to know a bit about the content of a transport request. If a certain request requires e.g. a restart, this import should only be done if a downtime of the application is possible. Like the developer, the transport admin has to monitor the imports. These four roles are an example and try to show the different tasks within the different systems. They do not represent static roles. One user can fulfill tasks of several roles or several users might contribute to one role. In the portal use case, it might e.g. be helpful to have one developer who develops portal applications and someone else includes these applications into iViews and roles. Each role described on the slide has to work either within the application or within the CTS system. Nevertheless, there are tasks which are closely related to the other system and tasks which can be fulfilled with very little knowledge about the other side.


2012

E2E200


Figure 151: Creating Non-ABAP-Systems

To create a transport route in CTS, a representation of the source and the target system has to be created in CTS. In transaction STMS (in the system overview), you can create a non-ABAP system. Then, a wizard to create the system is started. In the first step, you can decide whether you want to create a source or a target system (a system can in exceptional cases also have both roles). Depending on the role of the system, you have to define different parameters. For a source system, the Transport Organizer has to be activated, for a target system, you have to define the deployment mechanism. If one target system has several usage types installed, you can also activate several deployment methods. The next step of the wizard will ask you for the passwords for the different deploy tools that you have selected. The options that you selected during the wizard can be changed later on. They are stored as properties of the system. This means that you have to open the configuration of the system and then you can change the properties manually. The wizard does not support this any more. These tasks have to be fulfilled by an administrator of the CTS system.

2012


197


E2E200

Figure 152: Creating Transport Routes

After having created the non-ABAP systems, the administrator of the CTS system can arrange the systems within transport routes. When doing so, he has to create a transport layer. There are two types of transport routes available: Consolidation and delivery. Consolidation is only used between development and QA systems. All following routes are normally defined as delivery. All transport requests are created in the development system and then imported in QA and Productive system consecutively.

198


2012

E2E200


Figure 153: The Transport Organizer Web UI

2012


199


E2E200

The Transport Organizer Web UI replaces the CTO (transaction SE09) for non-ABAP transports • •

•

•

200

From the STMS you can jump into the Transport Organizer Web UI. The Transport Organizer Web UI is an ABAP Web Dynpro Application which has been introduced with SAP NetWeaver SPS 12. In SPS 13, a new version has been provided. The name of the ABAP Web Dynpro application is CTS_BROWSER (from SPS 13 onwards). It is used to handle transport requests for non-ABAP systems. If you know how to transport in ABAP: SE09 can not be used for non-ABAP systems, the CTS_BROWSER has to be used instead. The Transport Organizer Web UI provides the features that a developer in the applications needs to be able to handle transport requests. He can e.g. create transport requests, attach objects and release the transport requests. In addition, he can view the status of released requests. It is also possible to configure the system in a way that transport requests are created and released automatically. The Transport Organizer Web UI is integrated into the applications which provide a close integration of CTS+ into their export tools. The developer can then change a transport request or create a new one directly from within the application by using a link opening up the Transport Organizer Web UI. He does not have to go to the CTS system separately. The Transport Organizer Web UI runs on the CTS system, but if Single Sign-On between the application and the CTS system is enabled, the developers experience is seamless. The Transport Organizer Web UI can be called with several URL parameters. This is why it might show different options when it is called from different places.


2012

E2E200


Figure 154: Transport Organizer - Modifiable Request

• •

•

•

•

•

2012

If you are working on a modifiable request, you have several options what you could do within the transport organizer Web UI One transport request is marked with a red arrow. This request is currently used as your default request. This means that this request will be displayed within applications which provide close coupling. On top of the list of requests, you can find several buttons to work with the requests: you can create or delete a request, you could choose a different request as the default one, you can attach objects or release the request. If you mark one request out of the list, you can find detailed information below the requests list in a second list. Here you can see the properties and change the Description on the tab Properties. On the tab Object List you can find out what has already been attached to a transport request. If you release a request, it is not modifiable any more. If you refresh the list, you will not see it any more in this list. You could the choose Released from the Status box. Then, different options are available for a transport request. The next slide explains the details. A new tab will be provided for modifiable transport requests. The tab is named Team. You can add several users to a transport request. When adding a user to the team, the option Preselected Request for added user is set by default. The request becomes the preselected request for the new team member. You can change this option. And the new team member can do so as well when he open the Transport Organizer Web UI by just marking another transport request and clicking on Preselect Request. All team members can add objects to the same transport request. This helps making sure that all objects belonging to one new feature are part of the same transport request. Every team member can release the transport request. It is not necessary that each team member releases the transport request. The whole transport request is released after one team member did so.


201


E2E200

Figure 155: Attach an Object: Loose Coupling

The button to attach an object manually to a transport request is now part of the tab Object List of the respective transport request. If an application provides loose coupling as integration level with CTS+, objects are attached to a transport request via the Transport Organizer Web UI. The developer uses the Attach button. A pop-up window comes up where the developer can then browse for a file and attach it to the transport request. With SAP Solution Manager 7.10 it is now possible not only to display the name of the EPA file but also the complete object list (SICF service CTS_OBJECTLIST_BROWSER).

202


2012

E2E200


Figure 156: Transport Organizer: Released Request

• •

• •

2012

This slide shows the Transport Organizer Web UI and its options if the list of released requests is displayed. A lock is now shown in front of the number of the transport request. The transport request can not be changed any more, it is not possible any more to attach objects or to set a standard request. The transport request can not be deleted. The properties and the attributes of a transport request can still be displayed, but not changed any more. A new tab Logs is added. The first column shows the systems where the transport request will be imported. The third column shows the status of the transport request for the respective system. You can move your mouse over the symbol and will get a text that explains the status. Clicking on the SID of the system will lead you to the log. For the first system (the development system) the export log will be displayed, for the following systems, the import log will be shown. Using this logs helps the developer to find out what went wrong in case of an error. The administrator of the CTS system doesn’t have to send logs around. Each developer can take a look on his own.


203


E2E200

Figure 157: Navigate through the Transport Logfiles (Java)

• • •

The transport logfiles can be reached from the Import History or from the Transport Organizer. In the detailed logfile for the Deployment step, you can see if the deployment was successful. You can also see further information, like host and port of the SDM.

Figure 158: Import via SAP Transport Management System

204


2012

E2E200


The import process is identical for ABAP and Non-ABAP transport requests. In both cases transaction STMS is used. In the screenshot above transaction STMS was included in the Portal as a transactional iView.

Figure 159: Import History: Non-ABAP Systems Inherit all Properties of ABAP

• • • •

2012

By using the ABAP Change and Transport System, Java applications inherit all properties of the ABAP CTS. The Import History can be reached from transaction STMS: Overview → Imports → → Goto → Import History Here, you can find the list of all transports which were imported into a system and the import timestamp. From the import history, you can navigate through the object list and to the transport logfiles


205


E2E200

Figure 160: System Specific Permissions Configuration: Standard Role SAP_CTS_PLUS

You can restrict the permissions that a certain user has for a specific system. One scenario could be that a developer should only export the objects that he created. The import should be done by someone else. The developer needs to have export permissions for the development system, but he should not be able to start the import. Another option would be to restrict the import permissions per system. Several administrators could have the permission to start the import for the QA system but only a few should be able to import into the productive system. This might be helpful if imports require post import steps that might include a system restart. Restarts have to be coordinated and agreed on within the company especially if productive systems are concerned. The permissions for systems have to be set via a role in the transaction PFCG. For the developer using the CTS+ functionality you can use the standard role: SAP_CTS_PLUS. Two new authorization are delivered with this role: •

•

S_SYS_RWBO is used to restrict the permissions for creating transport requests. You have to enter the SIDs of the systems for which the user should be able to create transport requests. S_CTS_SADM is used to restrict the permissions for importing.

If you need different settings for different users, you have to create different roles.

206


2012

E2E200


If the new authorization objects do not appear in the role (dependent on the SPS level): Copy the role, add these objects to the role and adjust the authorizations according to SAP note 1003674. Note: If you want to use the new authorization objects, you have to delete or deactivate the authorizations for the old objects C_CTS_ADMI and S_TRANSPRT.

2012


207


E2E200

Lesson Summary You should now be able to: • Use the Transport Organizer Web-UI for managing transport requests for non-ABAP developments. • Release transport requests in CTS+ and import them into the target system.

208


2012

E2E200

Lesson: 205

Lesson: Enterprise Portal and CTS +

Enterprise Portal and CTS + Lesson Duration: 30 Minutes

Lesson Overview This lesson will explain the structure and the objects of the Portal Content Directory. After this you will learn how to export objects in the portal content studio and attach them to transport request of the CTS+.


Describe the components of the SAP NetWeaver portal. Create a new iView in the portal content studio and transport it. Attach the transport package with the iView to a transport requests using the close coupling scenario.

Business Example A new iView shall be created in the SAP NetWeaver Portal system. This new iView shall be transported to the production system using CTS+.

2012


209


E2E200

Enterprise Portal and CTS +

Figure 161: Enterprise Portal Objects

When you look at a portal screen, there are several elements or components which might require a transport: •

• •

210

Corporate Branding: the branding of the portal consists of a theme, a framework page, a desktop and rule collections. These objects have to be transported to provide the same look&feel in the target system. Navigation (Roles): Content in the portal is assigned to a user by the help of roles. The roles consist of iViews, pages and worksets. Portal Content: the content displayed within an iView requires a transport as well. Depending on the type of content, different transport mechanisms have to be used. In some cases, it might be sufficient, to transport only the role with all its dependent objects, in other cases, it might be required to perform additional transports on the backend system landscape that is used.


2012

E2E200


Figure 162: Enterprise Portal Objects

• •

SAP delivers predefined content for the Portal as part of business packages. The business package is structured as follows: –

•

•

For each role, one or more business packages are provided with the required content. – Each business package contains the content needed to complete the various tasks a person with that role typically has to complete. These collections of task-oriented content are called “worksets.” – Each workset consists of those iViews required to complete the tasks in that workset. iViews are the smallest content units. They contain the actual resources needed to complete the tasks that make up each workset. The following PCD Objects may need to be maintained by means of SAP or other vendors shipments, for example, a Business Package shipped in iViewStudio: – Folders (and their content) – iViews – Pages – Worksets – Roles An iView is the basic unit of portal content – a small application that displays information – – –

2012

iView information can be in any format (texts, figures, graphs, reports, tables, charts etc.) iViews can be interactive, allowing you to perform business functions iViews can display information from any data source


211


E2E200

–

• • • • • •

iViews are based on portal components (e.g. developed in the SAP NetWeaver developer studio) The Enterprise Portal Import / Export iView is used to transport the PCD objects. Local changes to the current object version will be overwritten by the import of the associated EPA file. The file type for exports / imports of PCD Objects is EPA (Enterprise Portal Archive) Any PCD Object (including “folders” and their content) can be exported from one Enterprise Portal System and imported into another one. The EPA file may also contain *.PAR files, if the PCD objects being exported have been created based on their components. If PCD Objects are delivered as part of Business Packages, updates can be imported from iViewStudio.

Figure 163: Portal Content Studio

The Portal Content Studio is used to create e.g. iViews, pages and roles. A content developer can create the navigation structure in here. Very different applications can be integrated into the portal by the help of iView templates which are provided by SAP or have been developed by a customer or partner. All content objects (like roles, worksets, iViews, and pages) are available in the Portal Catalog and are maintained in the Portal Content Studio.

212


2012

E2E200


The Portal Catalog provides a central access point to all portal content objects stored in the PCD. It permits you to store, manage and organize content in a structured hierarchy.

Figure 164: Package Export Editor

•

•

• •

The Package Export Editor is used to export portal content (including roles, iViews, pages, rule collections etc). This tool is provided to portal administrators via the System Administration role. After having chosen the objects that require an export, a transport package named .epa is created. If CTS+ is not configured, the epa-file can now be downloaded to your client and is stored on the server. This epa-file can be imported on the target system. There is a special tool for exporting portal themes, the Theme Transport in the system administration role. Themes can not be part of an epa-file. The theme export requires a download. The next slide explains what changes if CTS+ is used. To learn more about transporting portal content, please have a look at http://help.sap.com/saphelp_nw70/helpdata/en/c5/56599164d0c04cb566ba0e2d7ed55c/frameset.htm

New: Change list •

2012

Change Recording can be turned on for the whole portal content catalogue or per folder as of SAP NetWeaver 7.3. A red bullet in the lower left corner of the folder indicates whether Change Recording is used for this folder. Please have a look at the end of this chapter for more info.


213


214


E2E200

2012

E2E200


Figure 165: Close Coupling for Transporting Portal Content

•

•

•

Since SAP NetWeaver SPS 13 the Package Export Editor supports CTS+. New fields have been introduced in the Package Export Editor for NW 7.0 SPS 13 / 14. The screenshot is taken from SPS 14. If a CTS+ system is configured in the Visual Admin, the user can choose whether he wants to use the classical way of exporting via the file system or the CTS+. Therefore the Drop Down Box Transport Method has been introduced. The fields Transport Request, Owner and Description are read from the CTS+ system. This is the request currently flagged with the red arrow in the Transport Organizer Web UI that we have seen before. In the CTS+ system, you can define a Transport Strategy for every non-ABAP system. This strategy decides on the behavior of the CTS System whenever an application asks for a transport request: –

•

•

•

• • •

•

2012

Smart: If there is no default request available for the user, the system creates a new one and flags it as the standard request. – Tagged: This is configured as the default value in the system. You must have created a transport request already in Transport Organizer Web UI and flagged it as the standard request. If there is none, there is no transport request taken from the CTS+ system. The field File name can only be edited if File system is chosen as a transport method. If you used the file name for information purposes for the administrator, you would now be able to use the field Note instead. The field Note can be used to add some comments concerning the specific file. The input field is only available if CTS is chosen as transport method. The text that you enter here will be added to the Transport Request documentation in the CTS system. Portal Themes can not be transported as part of an epa-file. In the moment, there is no option to transport Portal Themes via CTS+ except for file-system transport. Using this option requires a manual import in the target system. Every other object of the PCC (Portal Content Catalogue) can be added to an epa file when collecting the objects. When importing an Epa-file via CTS+, the Overwrite mode is used. Be careful when transporting Rule Collections. They might contain groups, roles or users which dont exist in the target system. Rules in the target system might be lost (remember the overwrite mode!) A more detailed description can be found on help.sap.com: http://help.sap.com/saphelp_nw70/helpdata/en/62/117d0cb40145d6bfc655dac7deb9c1/frameset.htm


215


E2E200

Figure 166: Best Practice Recommendation: Include iViews for Transport Management in the Portal

An optional configuration is to create an ABAP Web Dynpro iView which shows the Transport Organizer Web UI in the portal. This iView could be used by developers e.g. to take a look at the current status of their transports or to create new transport requests. The configuration has the advantage that all activities of a developer can be triggered directly from the Portal Development System: there is no need for logging on to the CTS+ Communication System.

216


2012

E2E200


Figure 167: Enhanced Change and Transport System Process

This picture illustrates the workflow within the portal using CTS+ for this course.

Figure 168: Outlook SAP NetWeaver 7.3 : Transport Portal Content using Change Recording- Change Recording Overview

Starting with SAP NetWeaver 7.3 Portal, Change Recording is provided. You have just seen that - without Change Recording - you have to add the objects that you would like to export to an epa-file manually. Wouldn’t it be great if there was a mechanism who does this for you? Change Recording can do so. Whenever you change, create or delete an object, this is recorded in a so-called changelist. You can then let the system create an epa-file out of the changelist and attach it

2012


217


E2E200

to a transport request. With this, it is even possible to transport the deletion of an object – a functionality that was missed by portal content administrators in the past. Change Recording runs on the development portal. As soon as you attach the changelist to a transport request, the CTS system is contacted to get the default request and send over the epa file (like it was done before without Change Recording).

Figure 169: Outlook SAP NetWeaver 7.3: Transport Portal Content using Change Recording Change Organizer

The Change Organizer is used to mange changelists. You can use it to e.g. create new changelists, do changes to existing ones and release changelists so that the epa-file is attached to a transport request. The UI is divided in an upper and a lower part. In the upper part, you can see a list of available changelists – be it for your user or for other ones. You can choose what should be displayed by using the arrow next to My Changelists. You can also create new changelists or delete the ones that you dont need any more. Deletion is only possible if the changelist is still open. As soon as you finished your changes, you can activate the changelist. This means that an epa-file containing all the changed objects is created and stored in the database. As long as an object is part of an open changelist, it is locked. Only the user (or team) which is assigned to the changelist can do further changes to this object. Activating the changelist also means that the locks are released. The activation does not include any activity which is related to CTS+. After you have activated the changelist, you can release it. With this step, the epa-file will be attached to a transport request in CTS. In the lower part of the screen, you can find details for the changelist selected in the upper part. A very important feature in here is Revert. You can select an object that is part of the changelist and undo this change by using the Revert button. This

218


2012

E2E200


is only possible for open changelists. The History can give some information about the changes done to this object. The Properties button shows details about this version of the selected object.

Figure 170: Features and Limitations of CTS+ in a Portal Environment

Here we try to answer the question what CTS+ in a portal environment does and what it is not capable of.

2012


219


220


E2E200

2012

E2E200

217


Exercise 6: Portal Content Studio Exercise Duration: 15 Minutes

Exercise Objectives After completing this exercise, you will be able to: • Assign a workset to your Portal role.

Business Example RWS is the communication system for the CTS+ The transport track JAD → JAQ → JAP was created on the communication system RWS. They all reference to the physical Portal system J2E.

Task: Assign the workset Working Time to your role.

2012

1.

Log on to the Enterprise Portal on system RWE with your user E2E200-## (Change “##” to your group number).

2.

Open E2E200-## tab and make sure that there is no content.

3.

In the Portal Content Catalog, navigate to the folder E2E200.

4.

Open the role E2E200-## (Change “##” to your group number).

5.

Assign the workset Working Time to the opened role as a Delta Link. The workset can be found in Portal Content → Content provided by SAP → End User Content → Employee Self Service → Worksets → Working Time.

6.

Refresh your browser and check if there is a new workset under your role.


221


E2E200

Solution 6: Portal Content Studio Task: Assign the workset Working Time to your role. 1.

Log on to the Enterprise Portal on system RWE with your user E2E200-## (Change “##” to your group number). a)

Use the URL: http://portal-rwe:50000/irj/portal or logon to the Enterprise Portal over your favorite menu.

2.

Open E2E200-## tab and make sure that there is no content. a)

Figure 171: E2E200-00- No Content yet available

3.

In the Portal Content Catalog, navigate to the folder E2E200. a)

On the tab Content Administration, open the folder Portal Content. Go to the tab Browse and open Portal Content.

Figure 172: Portal Content Catalog


222


2012

E2E200


4.

Open the role E2E200-## (Change “##” to your group number). a)

Open the folder E2E200 and double-click the role E2E200-##.

Figure 173: Open Your Folder

5.

Assign the workset Working Time to the opened role as a Delta Link. The workset can be found in Portal Content → Content provided by SAP → End User Content → Employee Self Service → Worksets → Working Time. a)

Right-click the workset Working Time and choose Add Workset to role → Delta Link

Figure 174: Add Workset to Role via Delta Link

b)

Choose Close to finish. Continued on next page

2012


223


6.

E2E200

Refresh your browser and check if there is a new workset under your role. a)

Refresh your Browser (F5) and you will see the new workset under your role.

Figure 175: Working Time

224


2012

E2E200

221


Exercise 7: Transport Package Editor Exercise Duration: 10 Minutes

Exercise Objectives After completing this exercise, you will be able to: • Create a transport package. • Attach a transport package to a transport request using the close coupling scenario.

Business Example To use the close coupling scenario in CTS+ you have to export your role first. If a transport is found your exported file gets immediately attached to this transport.

Task: Put your changes into a transport package and export the transport package to a transport request. 1.

Go to the Transport Package Editor → Export under the role System Administration and navigate to the folder E2E200.

2.

Create a new Transport Package. Assign the following attributes to your Transport Package (Change “##” to your group number): Transport Package Name: Transport_Package_User_##. Transport Package ID: Transport_Package _User_##. Transport Package ID Prefix: com.sap Master Language: English. Choose next, then choose finish. Open the object for editing.

3.

Assign your role to your transport package. Right-click on your role under folder E2E200 and select Add object to transport package. Click on Export. Which transport methods are possible? Answer: ___________________ What is the ID of the transport request? Answer: ___________________ Continued on next page

2012


225


E2E200

What is the name of the new created file? Answer: ___________________ 4.

Export the EPA file What is the name of the newly created EPA file? Answer: ___________________

226


2012

E2E200


Solution 7: Transport Package Editor Task: Put your changes into a transport package and export the transport package to a transport request. 1.

Go to the Transport Package Editor → Export under the role System Administration and navigate to the folder E2E200. a)

On the tab System Administration open the folder Transport → Transport Packages → Export. Go to Browse the Portal Catalog and open Portal Content.

Figure 176: Export Portal Content

2.

Create a new Transport Package. Assign the following attributes to your Transport Package (Change “##” to your group number): Transport Package Name: Transport_Package_User_##. Transport Package ID: Transport_Package _User_##. Transport Package ID Prefix: com.sap Master Language: English. Choose next, then choose finish. Open the object for editing. a)

Right-click E2E200 and choose New –> Transport Package Continued on next page

2012


227


E2E200

Figure 177: Create → Transport Package

b)

Step 1: Fill in General Properties as seen above. Change the “##” to your group-number. Choose Next.

c)

Step 3: Check the summary.

Figure 178: Check Summary

d)

Choose Finish.

e)

Select Open the object for editing and choose OK.


228


2012

E2E200


Figure 179: Transport Package Wizard

3.

Assign your role to your transport package. Right-click on your role under folder E2E200 and select Add object to transport package. Click on Export. Which transport methods are possible? Answer: ___________________ What is the ID of the transport request? Answer: ___________________ What is the name of the new created file?


2012


229


E2E200

Answer: ___________________ a)

Right-click your role and choose Add object to transport package.

Figure 180: Add object to transport package

Click-on Export and check the summary. b)

Possible transport methods: Answer: CTS and File System → check drop down box next to Transport Method.

c)

ID of the transport request: Answer: JADK9*****

d)

Name of new created file: Answer: –

4.

Export the EPA file What is the name of the newly created EPA file?


230


2012

E2E200


Answer: ___________________ a)

Click-on Start Export.

Figure 181: Start Export

b)

Name of the newly created EPA file: Answer: com.sap.Transport_Package_User_##_********_******.epa

Figure 182: Export Status

2012


231


232


E2E200

2012

E2E200

229


Exercise 8: Transport Organizer Web UI Exercise Duration: 10 Minutes

Exercise Objectives After completing this exercise, you will be able to: • Create and releases transport requests in the Transport Organizer Web UI. • Check the object list and the logfiles of transport requests.

Business Example You want to transport your newly created role into the quality and productive system using CTS+.

Task 1: Release your transport request in the Transport Organizer Web UI. 1.

Call the Transport Organizer Web UI by opening the Transport Management tab.

2.

Find your transport request. Is it flagged as a standard request?

3.

Enter a description for your transport request. (if not included automatically)

4.

Check the object list of your transport request.

5.

Release the transport request.

6.

Check the transport request log file.

Task 2: Import the transport request into the target system JAQ. 1.

Preparation: Delete the assignment of your role to the workset Time Recording. The development system JAD and the quality assurance system JAQ point to the same physical Portal system. Therefore, you need to delete the assignment of the workset so that you can verify that the transport was successful.

2.

Go to the import queue for system JAQ. (The iView for the import queue is part of the role Transport Management which is assigned to your Portal user.)

3.

Mark your transport request and start the import (only your transport request, not the whole queue). Continued on next page

2012


233


4.

E2E200

Check the import log files in the Import Queue. Which transport steps were performed during the import? Answer: ___________________ What was the return code of the import? Answer: ___________________

5.

234

Check if the workset is assigned to your role in the Portal.


2012

E2E200


Solution 8: Transport Organizer Web UI Task 1: Release your transport request in the Transport Organizer Web UI. 1.

Call the Transport Organizer Web UI by opening the Transport Management tab. a)

In the tab Transport Management open the iView Transport Organizer. If you get a warning from Internet Explorer about blocked content, click on that line and choose: Display blocked content.

2.

Find your transport request. Is it flagged as a standard request? a)

3.

Search for the transport request that you created earlier.

Enter a description for your transport request. (if not included automatically) a)

Mark the line of your transport request, go to the Properties tab and enter a description. Enter Transport_Package_User_## Change “##” to your group-number. Choose Save.

4.

Check the object list of your transport request. a)

5.

Go to the Object List tab and check if you can see the EPA file you exported before.

Release the transport request. a)

Choose Release to release the transport request.

Figure 183: Transport Organizer


2012


235


6.

E2E200

Check the transport request log file. a)

In the Status field, select Released. Go to the Logs tab and expand the entry JAD, then choose details. Scroll to the end of the window that opens and check the return code (should be “0”).


Figure 185: Transport Logs- Details


236


2012

E2E200


Task 2: Import the transport request into the target system JAQ. 1.

Preparation: Delete the assignment of your role to the workset Time Recording. The development system JAD and the quality assurance system JAQ point to the same physical Portal system. Therefore, you need to delete the assignment of the workset so that you can verify that the transport was successful. a)

In the tab Content Administration, open the folder Portal Content. Go to Browse the Portal Catalog and open Portal Content.

b)

Go to the E2E200 and double-click your role to open it. On the right side, the structure of the role is displayed.

Figure 186: Portal Content

c)

Mark the workset Working Time and press the Delete button.

d)

Confirm the deletion with Yes.


2012


237


E2E200

Figure 187: Webpage Dialog

e) 2.

Open E2E200-## tab and make sure that there is no content.

Go to the import queue for system JAQ. (The iView for the import queue is part of the role Transport Management which is assigned to your Portal user.) a)

On the tab Transport Management, open the folder STMS Queue.

Figure 188: Import Overview

Display import queue (Menu → Import Queue → Display). Choose system JAQ in the popup. Push button Refresh.


238


2012

E2E200


3.

Mark your transport request and start the import (only your transport request, not the whole queue). a)

Choose Menu → Request → Import.

b)

Mark request and choose: Select/Deselect Request. Check the Start Import window and choose Yes.

c)

Check the status of your transport request in the import queue. It should turn to yellow (“Request is ready for import again”)

Figure 189: Import Queue: System JAQ

4.

Check the import log files in the Import Queue. Which transport steps were performed during the import? Answer: ___________________ What was the return code of the import? Answer: ___________________ a)

Mark your transport request and choose Menu → Request → Display → Logs.

b)

Transport steps: Selection for Import, Import, Deployment

c)

Return code of the import: The return codes for all import steps should be 0.


2012


239


5.

E2E200

Check if the workset is assigned to your role in the Portal. a)

Log on to the Portal again or refresh your browser (F5). You should now see again the new workset Working Time under your role.

Figure 190: Working Time

240


2012

E2E200


Lesson Summary You should now be able to: • Describe the components of the SAP NetWeaver portal. • Create a new iView in the portal content studio and transport it. • Attach the transport package with the iView to a transport requests using the close coupling scenario.

2012


241


Lesson: 238

E2E200

(Appendix) CTS+ Configuration For Other Scenarios Lesson Duration: 15 Minutes

Lesson Overview This lesson will describe best practices for configuration of other scenarios using CTS+. The main building blocks of NWDI and PI are described and how the development infrastructure of these component is integrated into CTS+

Lesson Objectives After completing this lesson, you will be able to: • • • • •

Know the advanced use case for SAP Enterprise Portal. Describe the integration of NWDI into CTS+. Describe the integration of PI into CTS+. Know about using CTS+ with LCM Lifecycle Management Console for SAP BusinessObjects BI. Know about using CTS+ with SAP HANA Studio for SAP.

Business Example The different transport logistic tools of non-ABAP system shall be replaced by using CTS+. Therefore the different development environments shall be connected to CTS+

242


2012

E2E200

Lesson: (Appendix) CTS+ Configuration For Other Scenarios

CTS+ Configuration For Other Scenarios

Figure 191: Portal Application Objects

This slide demonstrates how which kind of portal objects are transported without CTS+: • •

2012

Objects developed by the Portal Content Studio are transported by using Export/Import functionality to files system level Portal runtime objects can be developed with NWDI. Thsese objects are uploaded to the portal DEV system and transported to the other systems using the CMS (Change Management Service) of the NWDI


243


E2E200

Figure 192: Example: CTS+ Setup with Portal Content Studio and NWDI

Now let’s have a look how these objects are transported using CTS+ in a typical scenario with Portal Systems (Single Stack Java and NWDI). •

•

244

A typical scenario where use cases are combined is the transport of portal content (e.g. Portal iView) together with their Java applications (e.g. Java Web Dynpro application). Depending on the existing Portal and Java landscape the transport scenario looks different. As the recommended development infrastructure for Java based developments is the NWDI and NWDI is tightly integrated with CTS+ the combined use cases NWDI and SAP Portal. CTS+ replaces both: the Export/Import of Portal Content objects and also the CMS of the NWDI. Even combined transports are possible


2012

E2E200


Figure 193: Java Development with NWDI

•

•

SAP NetWeaver Developer Studio is SAP’s own development environment for developing multi-layer Java-based business applications. The new development environment is based on the open source product Eclipse. It fully supports SAP’s component model Optionally the developer has a local engine in which he can make a first test. Then he deploys it into the central systems DEV, CONS, TEST, PROD. The Netweaver Development Infrastructure is located on a separate server. It consists of the following components:

•

DTR: Central store for all types of source files. The store is presented logically as a hierarchical files and folders structure. The contents are physically stored in a database and can be accessed using the open protocols WebDAV and DeltaV. The DTR provides central storage, versioning and management of java sources and other resources with an automated conflict detection and resolution. The Developer Studio enables comprehensive DTR support for all available project types (Web Dynpro, EJB,...). Distributed, concurrent development – the DTR addresses the needs of large scale development: –

–

2012

Some projects are so big that the development team is spread over different locations. The groups will work in parallel. The same requirements you have if you want to allow your customers to do modifications to your applications, which means modifications to the Java source code. The versioning mechanism of the DTR that spans repositories means that you can safely propagate changes from one DTR repository to another


245


–

–

E2E200

The conflict detection allows to detect, if two versions of one development object have been created in parallel and prevents inconsistent states of versions Conflicts that are reported by the DTR can of course be solved there: A conflict is always a uncertainty, which of two versions of a certain file shall be active in the DTR (see → workspaces for details); the content of the conflicting versions can be displayed and the user can decide how to solve the conflict (see → conflicts for details).

Files and Folders: –

–

Though the DTR stores all objects in a database the content of this database is presented to the DTR client in a files and folders fashion. This meets the concepts of the Eclipse-based SAP’s IDE the SAP NetWeaver Developer Studio. The storage of files is independent of the programming language so in principle all types of files can be stored and versioned, even if they are not part of the Java programming model.

Check in/check out model: –

•

To change a file in the DTR you must check it out: To change them you will use a copy in your local file system (see → changing resources for details). – Changed objects will be checked back in to the DTR server – all changes will be part of an activity then CBS: Build Environment. The CBS stores all imported libraries (archives) to start development of new Software Components (SCs). It also builds and stores all newly created development components Central Build: – – –

All libraries and executables are centrally stored in the CBS Files are checked in again when change is complete When a file is checked out, it is locked for other users

Identification of Dependencies: – –

Used development components are included into the build process Using development components are rebuilt again, because they were changed indirectly

Build Time Reduction: –

Dependencies are handled on Development Component level. This is the lowest granularity.

Versioning:

246


2012

E2E200


–

•

Assignment of version numbers to archives. These version numbers are checked by the Software Deployment Manager. No transport sequence violations are possible. CMS: Administration and quality management environment for (logical) development systems. It consists of the Landscape Configurator (responsible for the definition of development environments for specific SC releases (tracks with development configurations for development and consolidation)) and of the Transport Studio (that enables transport mechanisms for development components from Development → Consolidation → Assembly → Approval Definition of fixed Transport Tracks: –

The systems DEV, CONS, TEST, PROD must be delivered in this order. No exceptions are possible.

Approval Procedure: –

An approval is needed that the test was successfully executed

Support of different Landscape Topologies:

•

– 3-system-landscape (without CONS) – 4-system-landscape (with CONS) – Phased system-landscape Starting with enhancement package 1 for SAP NetWeaver 7.0, the CM Services are provided. With that, CMS is not needed any more. It is still there and can be used. Maintenance is ongoing. But there is now the option to use CM Services and CTS instead of CMS. If NWDI is not used, sources and libraries have to be stored on a file system. This setup has some risks and limitations: –

•

No central place for sources. Different developers could have local copies which are outdated. – No version management for sources. Old versions are not kept. – No conflict detection and resolution for sources. If two developers work on the same object they will overwrite each other’s changes. – No central build. Different developers could have local copies of the libraries which are outdated. – No automatic identification of dependent libraries. – No transport control. The developer is not forced to deploy to DEV, CONS, TEST, PROD in the correct order. SLD: SAP J2EE application that contains all relevant information about software products and components (both ABAP and Java) that can be installed in a system landscape. It also contains a description of the current system landscape. The SLD also stores the development configurations. For Java development, SLD provides the following services:

2012


247


– – –

E2E200

Definition of software components to be developed and their interdependencies Naming Service: Reserve name spaces for unique names of development components Storage of development configurations required for development Note: SLD is not part of NWDI, but already part of standard SAP Web AS Java installation. SLD is required by the NWDI.

•

The arrows here indicate from where the import into the different systems are triggered. Note that the developer triggers the transfer of his local development into the central DEV system by using the SAP NetWeaver Developer Studio. SAP NetWeaver Developer Studio uses the CBS and CMS to start the deployment into the DEV-System. The import into subsequent systems is triggered and controlled directly from CMS.

Figure 194: CMS Track Configuration without CTS+

248


2012

E2E200


Here you can see the classical design of a track in NWDI with 4 runtime systems connected. This setup has some limitations: • • • • • • •

2012

No reuse of ABAP transport knowledge – need to learn new concept Build transport routes with a limited number of systems in one track System roles (DEV, CONS, TEST, PROD) are predefined Development configurations and repair capabilities are predefined (DEV, CONS) No multiple direct successor systems for each system possible in one track Transport granularity after assembly is the complete Software Component (SCA) No synchronized transports between different object types and other content


249


E2E200

Figure 195: CMS Track Configuration with CTS+

• •

• •

250

If you are using CTS+ with NWDI, then the transport archive is created with the assembly step. This archive is then attached to a transport request which was created in the ABAP stack. If the NWDI is configured for the close coupling scenario, this step is done automatically. The import into the QA and PROD system is then done synchronously in the ABAP and JAVA stack with the same transport request. CTS+ also supports Single System Tracks in NWDI. In case of Single System Tracks, the tab Consolidation in CMS is not available any more. You can change a normal track into a Single System Track, but there is no way back. This single system track offers the advantage that in case of dual stack systems the ABAP and the Java part of a transport can be imported via the same transport request. In case of separate systems for ABAP and Java, the import can be started from the same CTS system. The transport requests are then part of different queues, but only one tool needs to be used to start the import. The disadvantages that you have to configure two systems and that the transport of the Java part can only be on the granularity of SCA remain the same as before. You cannot perform consolidation with a single system track since all activated changes are assembled. Everything that is activated in a Single System Track gets directly assembled, so you must remember to release your changes immediately after the activation.


2012

E2E200


Figure 196: NWDI - CTS+ Application Integration- (Close Coupling)

This screenshot shows what the integration of CTS+ in CMS looks like. In the top right corner, the User can find a link to the transport organizer Web UI. He can use it e.g. to check the available transport requests, create a new one or check the import status of already released transport requests. When the user clicks on Assemble Component(s) a new window opens up to set the Assembly Options. On this screen, the user can decide about the transport request to be used. A Link to the Transport Organizer Web UI is provided as well. In addition, the user can add some documentation to the transport request via the input field Note. The same transport strategies as for the portal can be used (Smart or Tagged).

2012


251


E2E200

Figure 197: CMS Services: Activity-based SDA Transport- CTS+ Integration in NWDS - Release Activities

• •

•

•

•

252

The activity-based SDA transport works like this: At first you have to download a development configuration in your Developer Studio – this step is not shown in the picture. After that you can start programming. The changes that you do are recorded in an Activity. After you finished the changes, you would check in the Activity and activate it. Activating the Activity means that the SDA(s) that are concerned by your activity will be (re-)build and deployed to the development system. These steps are the same if you work with CMS or CM Services. After having activated the Activity, you can release it. In our case (using activity-based SDA transport), this means that a dip-file which contains the re-build SCAs is created and attached to a transport request. DIP means Development Infrastructure Package and is a new file format that has been created for the CM Services. When using the activity-based SDA transport, the dip contains all the SDAs that had been rebuilt because of the changes that you did (also the dependent SDAs not only the ones that were directly concerned by the changes that you did. If you look into the details of the transport request where you attached the dip, you can also find some information about the changed objects. You can then release the transport request and transport it through your system landscape by the help of the mechanisms provided in TMS – the same that we were using before to import the transport request into the portal. Importing the request e.g. into the TST (Test) system, means that the SDA(s) will be deployed to the respective runtime system. In TMS, you will see the result of the import. The return code indicates whether the import was successful or not, the log shows details – which is especially helpful if the import wasn’t successful. When you release an Activity in the NWDS, a Transport Request is used. The Transport Request and the respective Transport Route depends on the Development Configuration for which you are developing (and that you downloaded to your developer studio before starting the development). This screen provides the same options that we already know from e.g. the integration of CTS+ in the portal: You can find some information about the transport request (the number, the description, the owner). You can use the button Create/Select to open the Transport Organizer Web UI. One additional option is provided in the developer studio: If you set the option Monitor Requests the Transport Organizer Web UI will be started automatically after you clicked on Release. You could then check whether the dip-file has been attached to the transport request and could release the transport request immediately. When working with the activity-based SDA transport, you can see a list of all the SDAs that had been rebuilt because of your changes. This is shown in the section Rebuilt deployable DCs. All the SDAs shown in here will be attached to the transport request as part of one dip file.


2012

E2E200


Figure 198: PI Components

SAP PI consists of the following components: •

Design Time / Configuration Time –

The Integration Builder: The Integration Builder Server Framework provides software logistics features like Locking, Versioning and Change List Management. It provides an Import/Export interface as well as an interface to CMS of the NWDI. It provides a client-server framework for accessing and editing two stores of Shared Collaboration Knowledge: 1.

2.

The Integration Repository: For the design and development of Interface, Process, and Mapping objects that are used to implement Integration Scenarios. The Integration Directory: For configuring scenarios from the Integration Repository in the concrete customer landscape.

By separating design time activities from configuration time activities, SAP can ship content for the Integration Repository, which each customer can implement for their specific landscape in the Integration Directory. As far as possible, the goal is to reduce the problem of developing interfaces to the simpler task of configuring interfaces. Features of the Integration Builder:

2012

–

Recording of Changes

–

– A change list per user is recorded automatically – All objects in the change lists are locked Granularity of Transports


253


E2E200

–

–

Transports can be executed for changelists (all changed objects by a certain user) – In addition single objects, namespaces or complete software components can be transported Versioning – –

–

Changed objects are recorded in a versions database Each PI repository object has a version history. The latest version is automatically active. Therefore no transport sequence violations are possible Supported Transport Mechanisms – – –

Export / Import Procedure on file system (*.tpz files) Interface to Change Management Service of NWDI Interface to CTS+

Special Aspects of the Integration Directory: –

Automatic source system mapping after the import

–

– Usage of Transport Targets in SLD Non-transportable fields must be maintained manually in the target Integration Directory

– •

– No automatic activation of the latest version Runtime –

– •

– E.g. users and passwords Integration Directory transports must be activated manually

The Integration Server: The central processing engine of the PI. All messages, whether SAP or non-SAP, A2A or B2B, regardless of backend technology or vendor, are processed in a consistent way. Central Monitoring: To give a comprehensive and focused view of all components and processes at runtime.

SLD –

The System Landscape Directory: a central repository of information about your system landscape and software components. This data is required during design- and runtime.

There are two main areas of content in the SLD: the software catalog and the system catalog –

254

The software catalog describes the installed products and their constituent components. The software catalog is delivered with content about all SAP products. Customers and partners can extend this catalog with information about software from other vendors.


2012

E2E200


–

The system catalog describes the systems in the data center from two perspectives: a logical view (business systems) and a physical view (technical systems). In other words, the system catalog describes the concrete implementation of the customer landscape.

Information from the software catalog is used in the IR to organize development efforts. Information from the system catalog is used in the ID to drive the specific configuration of Integration Scenarios. PI uses the SLD in several ways: – – –

Server for business system names (Landscape Description) Transport targets for directory content transports Management of software component versions and their dependencies (Component Information) Note: – –

During SLD downtime, operation of your PI system is endangered Often the SLD content is the prerequisite for the PI transportation. An error message will occur, if the imported Integration Repository or Integration Directory objects cannot find related entities from the SLD

Figure 199: Integration Repository Exporting a Software Component Version

This slide shows the integration of the PI Integration Repository with CTS+ (the integration of the Integration Directory is very similar)

2012


255


E2E200

The procedure is as follows: •

• • •

Log on to the IR of your PI development system. Select a software component version that you would like to export and select in context-menu choose Export. Select Transport Using CTS as the transport mode, enter a description and choose Continue. On the next wizard screen you can select into the transport all or a restricted number of objects. Choose Continue. The system now displays a proposed transport request (either a newly created one or an existing standard request for your user).

Figure 200: Best Practice Scenario for Double Stack Systems, e.g. PI

The following section describes the configuration and setup of CTS+ for a dual-stack system landscape, where the development and target systems are dual-stack systems (e.g. PI use case). The typical configuration for using CTS+ functionality for a dual-stack landscape is to setup/use the existing ABAP transport domain controller configuration. For using CTS+ functionality the CTS+ components need to be configured in addition to the existing ABAP transport configuration. The main difference to a non-ABAP system landscape is that each target system triggers the imports using the tp program running on that target system (same behavior as in ABAP). Having a dual-stack system landscape with a tp running on each system leads to the fact that the corresponding Deploy Web Service (DEPLOYPROXY) should run and should be configured for the Java stack part of that dual stack system. Therefore the corresponding Deploy Web Service Client consisting of the HTTP Connection and the Logical Port needs to be configured on the ABAP stacks of all target systems.

256


2012

E2E200


Figure 201: What CTS+ does not do

CTS+ is replacing the different transport logistic tools of non-ABAP development weorkbenches. Nevertheless within the Change Management process a lot of things are still missing: • • • • • • • • •

Synchronized import into complex system landscapes Control of Quality Gates between implementation phases Control over activities of developers and testers Defined Approval Process between Change Request and Change Integration into SAP Solution Manager Service Desk Detailed tracking of changes Monitoring and advanced reporting for change management process Flexible realization of ITIL based scenarios Enhanced functionalities for complex system landscapes not covered by the CTS

Theses open issues are addressed by Quality Gate Management and Change Request Management in SAP Solution Manager.

2012


257


E2E200

Figure 202: Knowledge Management Objects

• • •

•

•

•

258

In addition to the portal content, KMC (Knowledge Management and Collaboration) objects and configurations require also a transport. KM Content and KM Configuration have their own export/import tools (since SAP NetWeaver 7.0 SPS 13). You can transport KM Documents and KM Configurations (configarchives) via CTS+ in SPS 13 as well. In SPS 13, loose coupling has to be used which means that you have to attach the exported file manually to a transport request. 7.0 SPS 14, the transport for KM documents and KM configurations (configarchives) has been enhanced. When exporting documents, the transport request marked as default for this user in CTS is displayed. If another transport request is needed, the user has to go to the Transport Organizer Web UI to create one or to change the default. If you deploy KM Documents, the file is deployed to the import folder of KM. You can view it under Pending Imports and start the import manually whenever it fits. Please be aware that the import of a configarchive requires a restart. CTS+ does not perform this restart automatically nor does it check whether a transport request requires a restart. The check is planned for a future release.


2012

E2E200


Figure 203: Using CTS+ with LCM Lifecycle management console for SAP BusinessObjects BI (LCM)

•

CTS+ System

•

– SAP Solution Manager with CTS Plug-In installed SAP BusinessObjects BI – –

SAP BusinessObjects BI 4.0 LCM Frontend running on SAP NetWeaver

CTS Plug-In delivered with SL Toolset 1.0 SP1 and SP2 provides the capability to use CTS+ with SAP BusinessObjects BI 4.0. Make sure that you use the newest available version of SL Toolset. Remember that CTS Plug-in provided with SL Toolset 1.0 SP1 can only be installed on SAP Solution Manager 7.1 With SAP Solution Manager 7.01 SP25, you can also use LCM with CTS+. Installation of SL Toolset is not required. A report has to be executed to enable the functionality. Configuration for this case and details for the report are described in the documentation provided on the SAP Help Portal (http://help.sap.com/businessobject/product_guides/boexir4/en/xi4_lcm_user_en.pdf ). This option should only be used in exceptional cases on SAP Solution Manager 7.01 SP25 until SL Toolset 1.0 SP2 is available. The CTS Plug-In provided with SL Toolset 1.0 SP2 contains the same functionality and SL Toolset is the only way to get additional enhancements for CTS+. The LCM Frontend where you create jobs and attach them to a transport request has to run on SAP NetWeaver. See next slide for details. If you would like to use CTS+ with SAP BusinessObjects for previous releases, you can do so via loose coupling. This would mean that you create a file containing the objects that you like to transport on the source system, download it and attach it manually to a transport request by the help of the Transport Organizer Web UI. On the import side, you can then tell CTS to put the file to a file share e.g. on the target system when executing the import. This is also a loose coupling

2012


259


E2E200

mechanism. You would afterwards have to use LCM on the target system to import the job. In this case, CTS does the monitoring or tracking for you. The return codes in CTS do not reflect whether the import was successful or not. They only show whether the file arrived on the share or not. Note: Not all of the functionality of Lifecycle management console for SAP BusinessObjects BI is supported by CTS+.

260


2012

E2E200


Figure 204: Using CTS+ with LCM Landscape - What runs where?

•

•

•

If you would like to run SAP BusinessObjects BI 4.0 with CTS+, you have to use one LCM Frontend on SAP NetWeaver CE 7.2 SP3 for this. Starting with SAP BusinessObjects BI 4.0 SP2, SAP NetWeaver 7.3 is planned to be supported as well. In this picture, we show one source and one target system. This is just an example for the systems that might exist in a landscape. CTS+ can support also different landscapes. One other option is shown on the next slide. Export: 1.

•

LCM frontend connects remotely (Corba) to LCM backend. Data to be exported is collected in a LCM job. 2. LCM frontend connects via the Export Client to the CTS System to add the LCM job to a transport request and export it. Import: 1.

•

2012

As soon as the import is started in TMS, the Deploy Web Service Client hands over the LCM job to the Deploy Web Service. 2. The Deploy Web Service starts the Import of the LCM job on the target system (BO Target) and retrieves the import results. With future releases of SAP BusinessObjects BI, it is planned to support CTS+ integration in LCM for other platforms than SAP NetWeaver as well.


261


E2E200

Figure 205: Using CTS+ with BPC Change and Transport System Support for BPC (MS Edition)

Business Planning and Consolidation is a planning and consolidation application that meets budgeting, planning, consolidation, and reporting requirements. It supports an array of top-down and bottom-up financial and operational planning needs as well as consolidation processes. The user selects transport types and objects. The objects can be selected as per BPC applications. In BPC, applications are a kind of container or namespace which is used to group objects. One BPC system can comprise several applications – and in reality, there are in principle no BPC systems which consist of just one application. More information on SAP BusinessObjects Planning and Consolidation (BPC) is available on the SAP Help Portal at http://help.sap.com/saphelp_bpc10_ms/helpdata/en/a7/81a5d88e2445019dbbd592ff516299/frameset.htm

262


2012

E2E200


Figure 206: Planned: Using CTS+ with HANA- SAP HANA Studio for SAP HANA

SAP HANA integration into CTS+ is shown here as outlook. Further info regarding SAP HANA could be found in SAP note 1642937 - SAP HANA Appliance Software SPS 03 and SAP note 1514967 - SAP HANA: Central Note.

2012


263


E2E200

Lesson Summary You should now be able to: • Know the advanced use case for SAP Enterprise Portal. • Describe the integration of NWDI into CTS+. • Describe the integration of PI into CTS+. • Know about using CTS+ with LCM Lifecycle Management Console for SAP BusinessObjects BI. • Know about using CTS+ with SAP HANA Studio for SAP.

264


2012

E2E200

Lesson: 261

Lesson: (Appendix) Transport Parameters for CTS+

(Appendix) Transport Parameters for CTS+ Lesson Duration: 10 Minutes

Lesson Overview This lessons explains the CTS+ parameters for source and target systems.


Explain the meaning of the most important CTS+ parameters for source and target systems.

Business Example The transport parameters for CTS+ allow specific customizing and helps to set up CTS+ flexible to your needs.

Transport Parameters for CTS+

2012

Source System Parameters:

Target System Parameters:

NON_ABAP_SYSTEM

NON_ABAP_SYSTEM

COMMUNICATION_SYSTEM

COMMUNICATION_SYSTEM

NON_ABAP_WBO_CLIENT

CTS_SYSTEM_TYPE

NON_ABAP_WBO_INBOX

DEPLOY_DATA_SHARE

WBO_GET_REQ_STRATEGY

DEPLOY_WEB_SERVICE

WBO_REL_REQ_STRATEGY

DEPLOY_URL (SDM)

WBO_FILE_TRANSFER

DEPLOY_SLD_URL

WBO_USR_MAP_STRATEGY

DEPLOY_XI_URL

CTS_SYSTEM_MAPPING

DEPLOY_OUTBOX

CTS_SYSTEM_TYPE

CTS_SYSTEM_TYPE


265


E2E200

When a new non-ABAP system is defined in TMS the main transport parameters are set automatically. Nevertheless the customer can use following transport parameters for customizng the setup of CTS+. All parameters are set in transaction STMS -> Overview -> Systems. Select the source or target system and goto tabstrip: Transport ToolThe following parameters are supported: •

NON_ABAP_SYSTEM: By setting non_abap_system=true for a certain system, it will be marked as a system where no ABAP content will be exported from or imported into, but only files. This corresponds to the new R3trans feature to include FILEs into transport requests.

•

COMMUNICATION_SYSTEM: If the parameter non_abap_system=true is set for a certain system, you have to specify it’s communication system by setting the parameter COMMUNICATION_SYSTEM to the communication system’s SID. The communication system must not be defined as a non-abap system. The communication system serves as a system where all transport meta data is stored and which may also serve as the transport domain server.

•

NON_ABAP_WBO_CLIENT Client of the CTS system. Specify the client in which you want to use Transport Organizer for this non-ABAP system.

•

NON_ABAP_WBO_INBOX Path to the directory where Transport Organizer searches for files. This parameter enables you to choose between a close or loose coupling of your SAP applications and CTS: Close couplingYou need this parameter setting when you attach files to a transport request from a server share/mount. The default setting uses file streaming (see parameter WBO_FILE_TRANSFER). In the Loose coupling scenario you need this parameter setting when you attach files to a transport request from a server and not from a desktop (client).

•

WBO_GET_REQ_STRATEGY –

Tagged: Transport Organizer Web UI (or ChaRM) has to be used to create a request for an user and to mark them with a tag. If there is no tagged request found for a given user, the application reacts with an error

–

Smart If there is no tagged request available for an user; the transport backend creates a valid request. The export wizards in the applications are never interrupted, because there is always a valid request

•

266

WBO_REL_REQ_STRATEGY


2012

E2E200


–

Manual: Transport Requests can only be released using the Transport Organizer Web UI or ChaRM

–

Automatic: Transport Requests are automatically released from the Transport API after the objects are attached to the request

•

WBO_FILE_TRANSFER File transfer method between applications (clients) and the CTS system (streaming or file share/mount) You need this parameter only if you choose a close coupling. Parameters: Stream (default) or Share

•

WBO_USR_MAP_STRATEGY If you need to use User Mapping because the user ID’s are not the same in your Portal as in your CTS system, please have a look at note 1003764 and install the attached correction. Parameter value: System

•

CTS_SYSTEM_MAPPING Enter the system ID of your non-ABAP system if it is not the same as the name of the corresponding non-ABAP system in TMS. If possible, always create your non-ABAP systems in TMS with the same system ID that you gave the non-ABAP system when you installed it. You need this parameter if you want to create synchronized transports for ABAP and non-ABAP systems with different SIDs

•

CTS_SYSTEM_TYPE Classification of the systems in transaction SMSY for SAP Solution Manager scenarios When you create a non-ABAP system, this parameter is generated with the value JAVA automatically. For non-SAP systems, change this parameter to OTHERS.

•

DEPLOY_DATA_SHARE The directory where the CTS Deploy Web service accesses the data saved by the transport program tp If the CTS Deploy Web service is not on the CTS server and is on another server instead, you have to change this parameter. The server on which the CTS Deploy Web service runs must be able to access the transport directory. Specify the directory used by the CTS Deploy Web service to access the ABAP transport directory.

•

2012

DEPLOY_WEB_SERVICE


267


E2E200

Name of the Web service = CTSDEPLOY Additional Information on CTS+: SAP Service Marketplace: http://service.sap.com/changecontrol -> Resources on CTS+ SAP Developer Network (SDN): http://www.sdn.sap.com/irj/sdn/cts

268


2012

E2E200


Lesson Summary You should now be able to: • Explain the meaning of the most important CTS+ parameters for source and target systems.

2012


269

Unit Summary

E2E200

Unit Summary You should now be able to: • Describe the main features and best practices of the CTS. • Describe the main features / advantages of the CTS+. • Describe which objects can be transported with the CTS+. • Describe the differences between the loose and close coupling scenario. • Describe the concept of delivering new features for CTS+ with the SL Toolset. • Use the Transport Organizer Web-UI for managing transport requests for non-ABAP developments. • Release transport requests in CTS+ and import them into the target system. • Describe the components of the SAP NetWeaver portal. • Create a new iView in the portal content studio and transport it. • Attach the transport package with the iView to a transport requests using the close coupling scenario. • Know the advanced use case for SAP Enterprise Portal. • Describe the integration of NWDI into CTS+. • Describe the integration of PI into CTS+. • Know about using CTS+ with LCM Lifecycle Management Console for SAP BusinessObjects BI. • Know about using CTS+ with SAP HANA Studio for SAP. • Explain the meaning of the most important CTS+ parameters for source and target systems.

270


2012

Unit 5 Reporting And Analysis Tools

267

Unit Overview You will get an understanding of the shortages within an 3-tier landscape and understand the advantages of release management. To report and analyze your landscape from change management of view, Configuration Validation will be introduced within this unit. Furthermore you will learn how to secure the go live of a new business release using CDMC CTS. Additionally you can verify certain change management KPÍs and analyze them by running the transport execution analysis self service in SAP Solution Manager.

Unit Objectives After completing this unit, you will be able to: • • • • • • • • • • • •

2012

Understand the basis architecture of E2E Change Diagnostics. Find current configuration information with Change Reporting. Explain how to find out recent changes in the solution landscape with E2E Change Analysis. Know how to compare multiple systems with Configuration Validation. Understand the usage of target systems. Know how to use the report directory. Understand the risks of Import Single Strategy. Understand the risks of Inconsistencies in the Transport Landscape. Understand the basic idea and benefits of Release Management. Explain the system and clients roles in advanced system landscapes. Give some examples of advanced system landscapes based on specific customer requirements. Explain, which tools can be used to manage transport dependencies.


271

Unit 5: Reporting And Analysis Tools

• • • • • • • •

E2E200

Know the prerequisites to use CDMC CTS. Understand in which situation the CDMC CTS analysis could be used. Execute the activities for CDMC CTS Analysis in the custom Development Management Cockpit (CDMC). Analyze the results of the CDMC Analysis. Explain the value and the content of the Transport Execution Analysis service. Know the prerequisites, which must be fulfilled before service delivery can start. Judge in which situation the service delivery makes sense. Understand the main KPIs, which are used to measure the quality of software change management.

Unit Contents Lesson: Configuration Validation .............................................273 Exercise 9: (Optional) Change Diagnostics............................. 311 Exercise 10: Configuration Validation ...................................317 Exercise 11: Configuration Validation – Report Directory .............331 Lesson: Software Change Strategies ........................................338 Exercise 12: Software Change Strategies ..............................367 Lesson: Custom Development Management Cockpit (CDMC) - Change and Transport System (CTS) Analysis .......................................372 Exercise 13: CDMC Change and Transport System Analysis........407 Lesson: Guided Self-Services/ Transport Execution Analysis ............418

272


2012

E2E200

Lesson: 269

Lesson: Configuration Validation

Configuration Validation Lesson Duration: 40 Minutes

Lesson Overview Configuration Validation enables you to determine whether the systems in your landscape are configured consistently and in accordance with your requirements. You can check the current configuration of a system in your landscape using a defined target state (target system) or compare it with an existing system. You can execute checks that answer the following questions, for example: • • • • •

Were the desired security settings performed in the production system? Are the parameter configuration settings in accordance with my template? Have all transports from the development system arrived in the production system? How long did a particular transport from the development system to the production system take after it was released? Were particular notes imported into the production system?

Lesson Objectives After completing this lesson, you will be able to: • • • • • •

Understand the basis architecture of E2E Change Diagnostics. Find current configuration information with Change Reporting. Explain how to find out recent changes in the solution landscape with E2E Change Analysis. Know how to compare multiple systems with Configuration Validation. Understand the usage of target systems. Know how to use the report directory.

Business Example You want to find out changes in your system landscape centrally. Furthermore you want to find out fast whether your system configuration adheres to your template or given settings.

2012


273


E2E200

Motivation •

•

End-to-End Change Analysis and Reporting is an important part of End-to-End Change Control Management. If an unknown problem comes up, Change Analysis answers the question “What was changed in the system”? You should understand the big picture before starting a deeper root cause analysis. Symptoms for starting with change diagnostics could be the following: – –

•

The system behaves differently after a certain date or some changes. One landscape works differently from the other one. For example, QAS is working fine, but PRD has issues. We need a tool to report how/which/when changes are introduced to a landscape in order to: – – –

Detect the Root Cause of an Incident. Help analyzing your Transport Management. Enable reporting capabilities to analyze and compare the changed items within the systems to support the operation team.

Figure 207: Configuration Items Change Control Management- Transport Analytics / Configuration Validation

With Configuration Validation you are able to determine whether the systems in your landscape are configured consistently and in accordance with your requirements. You can check the current configuration of a system in your

274


2012

E2E200


landscape using a defined target state (target system) or compare it with an existing system. It is working as soon as you have set up diagnostics for the managed systems. You can execute checks that answer the following questions, for example: • • • •

Have all transports from the development system arrived in the production system? How long did a particular transport from the development system to the production system take after it was released? Were particular notes imported into the production system? Were the desired security settings performed in the production system?

Figure 208: Typical Questions

Benefits of E2E Change Diagnostics: • • • • • •

2012

Central entry point for analyzing changes in a solution. BI methods to drill down from overviews to detailed lists of changes. Providing hints for root cause analysis with data and trends. Providing accurate information on configuration parameters and their history (e.g. database parameters, ABAP parameters, JAVA parameters). Enabling the organization to standardize the solution configuration. Improving security by controlling the versions of configurations in use.


275


E2E200

Configuration Items

Figure 209: Configuration and Change Database (CCDB) - Configuration Stores

Any change of configuration items and the configuration data itself is stored in the configuration stores of the configuration and change database (CCDB). The configuration stores are part of the CCDB and contain all configuration details. What is a Config Store? Within the Configuration and Change Database: • •

The single configuration details are stored in containers of a defined type called Config Store. There are different types of Config Stores depending on the structure of the data.

The configuration items of existing systems are stored regularly in corresponding Config Stores. There are different types of Config Stores depending on the type of data stored in it. The most important types are xml, txt, ini, properties (two column based container: parameter, value), table (more than two column based container: key1, key2, value1, value2 …) and event (as table but event-based). The configuration items of existing systems are stored daily in corresponding Config Stores for different application layers. There are different types of Config Stores depending on the type of data stored in it. Details about the stores could be found in SAP Note 1230404 “E2E CA Store Content List”.

276


2012

E2E200


Store content is displayed differently according to its type. Hint: • •

* File name patterns are used for the file system extraction to extract several files with one store definition. Store names with wildcards are store definitions that define several config stores.

Figure 210: Data Collection Method- Snapshot or Timestamp

In E2E Change Analysis, we differentiate between two types of data: •

•

•

Technical configuration, such as OS, DB, and ABAP parameters. These parameters are not recorded by the Change and Transport System. A full snapshot of each configuration set is extracted daily. Changes that are recorded in transport requests are already documented in the managed systems. For these types of changes, only the number of events and the return code is displayed since the last data collection run is transferred to E2E Change Analysis. Objects of the transports could be displayed with the object list browser.

To get a complete list of all the defined Config Stores per technical system, the transaction CDDB could be used or go to the work center Solution Manager Administration → Infrastructure → Administration → Configuration Change Database. Information about this view you could obtain by pressing the question marks (1). You should choose a technical system for further analysis and display the store details (4). After choosing the technical system you can see details of all stores that you are interested in by clicking on the store details (4).

2012


277


E2E200

Naming Conventions: • • • • • •

Stores are defined in the Change Reporting Template Management: WebDynpro appliation - diagtpl_upload_app. Store Name: Name of the Config Store. The name can also contain wildcards. Then we talk about Config Store Definitions. Store Group: Superset of Config Stores. Name: Indicates to which entity in the product hierarchy the config store belongs. Store Type: Property, Table, Event, XML, Text. Store Category: Software Store or Config Store.

Data Collection Process

Figure 211: Change Diagnostics Architecture

The CCDB config stores are daily updated by extractors scheduled within the EFWK. The data are collected in Java-based systems using Diagnostics Agents and in ABAP-based systems by means of the Solution Tool Plugin Extractors. Additionally, all detected changes are aggregated into SAP BW into the change analysis info provider to provide change statistics. InfoCube 0SMD_CA02 (E2E Change Analysis II) is updated daily with changes provided by the CCDB. In the E2E Change Analysis BI reporting tool it is possible to navigate from the aggregated level of data (number of changes per day) to the detailed configuration data using the Change Reporting Viewer.

278


2012

E2E200


The Change Reporting Viewer can also be accessed directly from the RCA workcenter → System Analysis. Please check out the attachement of SAP Note 1365123 - Installation of Diagnostics Agents if you have not yet set up the Root Cause Analysis for your managed systems. Additionally please check out the EGI calendar for setup service schedule under http://service.sap.com/alm-services. Within the topic Expert Guided Implementation for Basic Configuration the setup of diagnostics is covered. The configuration data is collected from different sources of differing system types. In the above figure these are displayed as “Managed Systems” on the left side. The data is collected on a Product Instance Perspective, which means that an access is provided to data specific to the component in question, for example, CRM or PI, ABAP or Java-based systems. The technical infrastructure to collect the data into the Solution Manager Diagnostics and into the BI is the Extractor Framework (EFWK). The Extractor Framework guarantees that the strong emphasis on the Product Instance Perspective is available for the E2E applications displaying the data by enriching the data with additional information. The extracted configuration data is stored in the Configuration and Change Database (CCDB). The Configuration Validation and the Change Reporting use the data of the CCDB. However, for the E2E Change Analysis the CCDB data is aggregated and saved in an InfoProvider of Business Intelligence (BW) which allows using BW reporting capabilities by E2E Diagnostics applications. The Configuration Validation reads the CCDB data by means of a Virtual InfoProvider to provide BI reporting capabilities. The validated data is not stored in BI. The further information on E2E Diagnostics can be found at http://service.sap.com/diagnostics.

2012


279


E2E200

Figure 212: Extractor Framework Administration- User Interface

The Extractor Framework can be monitored in the workcenter Solution Manager Administration. Then click on Infrastructure → Administration →Extractor Framework. Or access the configuration extractors via transaction CCDB → Technical Systems → go to column Extractors. You see the status of all Extractors and use the Filter functionality and wildcards for your search. In the Log view you see the time of the last extractor run and if it was successful.

280


2012

E2E200


E2E Change Analysis and Change Reporting

Figure 213: RCA- E2E Change Analysis & Change Reporting

Change Analysis tracks all changes (e.g. technical configuration, code, content) which are applied to the managed systems. This information is especially useful if a few ad-hoc changes result in a disruption of a productive system, as it is possible to compare different systems and generate a report which contains the results. This approach identifies the problem by comparison rather than by drilling down, which is faster and easier in most cases.

Figure 214: How to Access Change Reporting

2012


281


E2E200

The change reporting function provides information about which and when changes were introduced into a software system landscape. For example, information about the current and historical values of technical configuration parameters, transport requests, or software maintenance activities can be provided from monitored systems. Change reporting can be accessed from the Root Cause Analysis work center via System Analysis. The change reporting function is the end-to-end solution operation standard to analyze, compare, and track changes in the software landscape. This ensures that all software changes remain transparent and traceable, which in turn increases the quality and availability of the software landscape. The change processes can be monitored continuously throughout the software application lifecycle. Change reporting is a stand-alone function as well as part of change analysis: You can access it as described above, or when viewing change details using change analysis.

Figure 215: Change Reporting: Application Overview

The Change Reporting application has two main functions: a Data Viewer and a Comparison Tool. They are located in two different tab strips to easily switch from one to another.

282


2012

E2E200


First let us focus on the Data Viewer: •

• • •

•

• • •

• • • • •

•

2012

The Data Viewer provides a snapshot of the Store content at a given timestamp of the selected Technical System. It also offers capabilities for searching and filtering store content. The left panel is a navigation panel with timestamp selection, a tree to navigate through the satellite landscape, and the Filtering/Searching tool. Change Reporting: Data View – Navigation Tree: The navigation tree displays the landscape and store content at the previously selected timestamp of the managed system. The user can now select the StoreGroup to inspect. StoreGroups have the yellow folder icon, with its source underneath (ABAP, OS, FileSystem, SAPoscol, Windows Registry, Engine Database, JMX, SLD, CTS). They can be attached to any landscape level. The other levels are related to the managed system landscape entities. The upper one is always the technical system. Moving the mouse over the icons will display tooltips showing more information on the entity (Entity level, PPMS ID, instance type, instance source). JMX Java Management Extensions. SLD System Landscape Directory. CTC Client Transport Control. The right panel provides the detail views (Store list and Store content). The timestamp selection defines at which date you want to view your data. It will then display in the Navigation tree and in the Store list only entities that have been created before that date. Search & Filter trays are by default collapsed and can be expanded at any time. A green light indicates if filter or search criteria have been applied. Independent “Reset” and “Apply” for both features. Any search criteria is then applied relatively to the eventual filters already applied.


283


E2E200

Now lets go to the Comparison Tool: •

• •

•

• •

•

It is often useful to know what has changed in a system between two timestamps, or what differs between two given systems from a configuration point of view. The embedded comparison tool of Change Reporting will enable the user to answer those questions. The upper panels are for system selection and compare options. The lowest part of the application displays the results of the comparison. When triggering a comparison, we need a reference system. It is always the system selected at application startup and is not selectable. We can only choose the timestamp of the reference system. The timestamp selection dropdown aggregates hourly the number of changes. Indeed, it displays the number of changes ( = number of elements ADDED + DELETED + CHANGED) in the time range. It may happen that the number of changes is 0. This is the case when an empty store is uploaded in the CCDB. The custom selection is filtering all existing systems to display only those having the same type as the reference. In this case, only ABAP systems can be selected as we choose the ABAP stack of B70 as reference satellite. Timestamp selection is also available and has the same features as in the reference selection.

Figure 216: Comparison Tool Layout

•

284

The upper panels are for system selection and compare options. The lowest part of the application displays the results of the comparison.


2012

E2E200


•

•

• •

• •

•

• • •

• •

When triggering a comparison, we need a reference system. It is always the system selected at application startup and is not selectable. We can only choose the timestamp of the reference system. The timestamp selection dropdown aggregates hourly the number of changes. Indeed, it displays the number of changes ( = number of elements ADDED + DELETED + CHANGED) in the time range. It may happen that the number of changes is 0. This is the case when an empty store is uploaded in the CCDB. The custom selection is filtering all existing systems to display only those having the same type as the reference. In this case, only ABAP systems can be selected as we choose the ABAP stack as reference satellite. Timestamp selection is also available and has the same features as in the reference selection. Landscape selection has an automatic helper mechanism from left to right to find the corresponding entity to compare. Manual selection in the custom tree is still possible in case the relevant entity is not found or on user needs. Once the reference and custom systems have been selected, both navigation trees are automatically updated to also reflect the selected timestamps. The user can now select entities he or she would like to compare. Once the user has selected two “comparable” entities (that is entities having the same type), the Compare button is enabled. The “Fast vs. Deep” comparison type option defines the algorithm that will be applied. When “Fast” is selected, the algorithm stops drilling down when it detects identical entities, and does not store those identical entities in the compare results. It is then called “Fast” as it is skipping any identical entities. It is particularly the case for deep xml stores. When “Deep” is selected, the compare algorithm compares all entities and stores them in the compare result (even if they are equal). Multi-Compare –

•

2012

By default, it is a one-to-one comparison between the selected reference and the custom entities. It is, however, possible for some elements type to compare one reference entity to multiple custom entities. – If you check the Enable multi-compare checkbox, the Custom navigation tree will be updated and will include a multi-selection capability. Depending on the selected comparison type (“Fast” or “Deep”), the filter dropdown is enabled or not. Indeed, the “Fast” algorithm does not store elements flagged as “equal”, so the Filter dropdown is disabled and limited to “Show only differences”


285


•

• •

•

•

E2E200

By setting the comparison type to “Deep” you are allowed to choose different filter options. With filter setting “Show ALL” also the equal elements are displayed. With filter setting “Show only Identicals” just the identical elements are displayed. Depending on the selected comparison type (“Fast” or “Deep”), the filter dropdown is enabled or not. Indeed, the “Fast” algorithm does not store elements flagged as “equal”, so the Filter dropdown is disabled and limited to “Show only differences” By setting the comparison type to “Deep” you are allowed to choose different filter options. With filter setting “Show ALL” also the equal elements are displayed. With filter setting “Show only Identicals” just the identical elements are displayed.

Figure 217: How to access E2E Change Analysis 2/2

The change analysis function provides an overview of the changes that have been applied to the managed systems. It also displays the number of changes per system, change category, and day. You can access it from the Root Cause Analysis work center. It reports changes of configuration items of a system (for example, OS, DB, ABAP parameters, Java parameters, transport requests, and Support Packages) and serves as a central entry point for root cause analysis. Change analysis helps you to keep track of the changes in your solution landscape. Your development system might behave differently than your production system. Or, J2EE instances of your productive system behave differently and you need to find out the reason. Therefore, regular snapshots of the configuration settings are taken and stored in the configuration and change database (CCDB) of SAP

286


2012

E2E200


Solution Manager. With this information, the change analysis function enables you to identify the changes. The change analysis function provides the number of changes and automatically takes you to the change reporting data viewer for the details and history of a changed item.

2012


287


E2E200

Figure 218: E2E Change Analysis- Overview

•

•

•

•

• • • •

•

•

288

The Change Analysis opens an Overview Tab Strip, and an additional tab strip for each product instance of the selected systems and for the hosts will be created. The tab strips description is composed of the system ID and the product instance. The Overview - Summary allows you to identify in a chart or table view the product instance that had the most or the most recent changes and should be analyzed first. The tab History of Changes for the last two years reads the data of the current quarter and the 8 quarters before and displays the number of changes for each quarter. As changes cannot be determined for the time prior to the setup of the E2E Change Analysis, the overview report History of Changes for the last 2 years may not necessarily show the changes of the last two years. The displayed timeframe is restricted by the setup of E2E Change Analysis. The report will probably take some time to display the result, because it reads data of several quarters. Below the diagram for the history of the last 2 years you find the table with the Last Change Date. The Last Change Date table lists the date of the most recent change per change group and type. Expanding the hierarchy node will display the change type. Depending on the type of the product instance, a Summary is displayed. For most types of product instances, additional buttons for details or grouped changes are offered. The example shows an ECC Server summary. The Product Instance - Summary allows you to identify (in a chart or table view) the grouped changes that are the best candidate for a further look on details. In the Product instance of type ABAP the details are grouped by Software Maintenance, Parameter, Transport Requests, SAP Notes and Miscellaneous.


2012

E2E200


Figure 219: E2E Change Analysis- ECC Server (Transport Requests)

The slide shows an example of the ECC-specific change group “Transport Requests”. It displays the number of transports per day for the choosen timeframe. Additional statistical information about applying of transport requests is available under Chart: Transports per Hour and Chart: Transports per Day. Cells with a green background color allow calling the Change Reporting Viewer to display the changed content of the ConfigStore. (System Demo) E2E Change Reporting and Analysis

2012


289


E2E200

Configuration Validation Reporting

Figure 220: Configuration Validation Challenges

Reporting and History of changes is important because it supports by • • •

290

Providing information for Root Cause Analysis Collecting metrics to evaluate and improve IT processes Prepare regulatory requirements by using the validation reporting.


2012

E2E200


For working with Configuration Validation you have to consider the following authorizations: •

BW Reporting.

•

– Role SAP_BI_E2E. Display Roles.

•

– Composite role SAP_CV_DISPLAY_COMP. – Role SAP_CV_DIS. Maintenance Roles.

•

•

– Composite role SAP_CV_ADMIN_COMP. – Role SAP_CV_ALL. Authorization for the following authorizations objects need to be adjusted according to customer needs or policy. – SM_CV_CPLM – Comparison Lists Maintenance. – SM_CV_REPE – Reporting Directory / Reporting. – SM_CV_TASM – Target System Maintenance. Access to the contents of security Config Stores –

Authorization object AI_CCDB_SC needs to be adjusted.

Figure 221: Configuration Validation - Goal

2012


291


E2E200

The main goal of the Configuration Validation application is to compare and validate current values of configuration items of many systems against a defined target or standard configuration. The validation results are displayed in the browser using Business Intelligence (BI) reporting capabilities. This allows you to perform an interactive cross-system configuration audit and configuration reporting for a large number of compared systems. In a target system its possible to specify per Config Item a compliant rule. If the rule applies to the corresponding Config Item of a comparison system the Config Item gets the status compliant (1 = yes) in the reporting output. Otherwise it gets the status non-compliant (0 = no).

292


2012

E2E200


Figure 222: Possible Reference Systems- Configuration Baselines

•

• •

•

•

Validation of the configuration items is based on the data stored in the configuration and change database (CCDB), which is a part of the E2E Diagnostics Infrastructure. The figure describes the architecture and data flow of the configuration validation and the functions of the components belonging to it. As first step, the single configuration items of existing systems are collected and stored by the Extractor Framework (EFWK) in the ConfigStores of the configuration and change database (CCDB). To make this configuration data available for BI reporting, the data from CCDB is read and evaluated by the function module RS_BW_BTC_SMD_CA2_COMPLIANCE1 and passed to the Virtual InfoProvider 0SMD_VCA1 and queries defined on it. The data is not stored in the Virtual InfoProvider 0SMD_VCA1; the validation reports use the appropriate BI structures and reporting features to display the results in the browser. In Solution Manager 7.0 EhP1 compliance is based on a consistency check. In SM7.1 you have the possibility to work with operators.

(System Demo) Configuration Validation: Ad-hoc Demo

2012


293


E2E200

Figure 223: Configuration Validation In Detail- Create Target System

• •

• •

•

294

The figure gives an an overview of the configuration validation procedure. In the first step, the target or baseline configuration is defined. It could either be based on a current configuration of an existing system or on a template. If an existing system is supposed to be used as reference system in the reporting, step 1 can be skipped. After the creation of the target system, the selection of the configuration items and their values can be adjusted in accordance with the requirements. At this step, you may define the systems that are to be compared with the reference system. During this step, it is possible to create a comparison list. This step and the use of the comparison list avoids that the user has to select the same comparison systems every time a report is executed. It is also possible to start an Ad hoc analysis (start directly with point 11) if you are not interested in a validation with help of a template. You could give in the compared systems, the config stores and config items directly into the variable screen after starting a report out of the Consistency Reporting area in the tab Report Execution.


2012

E2E200


Figure 224: Where can I start Configuration Validation?

The first option accesses the Configuration Validation tool from the Change Management work center of the SAP Solution Manager. On the left side, you see the Related Links section. In this section, you will find the links Maintenance and Reporting to start applications for target system maintenance and configuration validation reporting. Note: Not all config store types can be used for Configuration Validation. Text, Property, and table stores are suitable. XML in general not, the only exception is the saposcol config store. For saposcol a “on the fly” conversion towards a table format is done.

2012


295


E2E200

Figure 225: Reporting- Technical Background

SAP delivers a number of predefined validation reports for different validation areas such as security configuration validation or software level validation. The validation reports are BW WebTemplates with queries or views based on the Virtual InfoProvider 0SMD_VCA1 as data provider. BW WebTemplates allow the use of standard BW reporting capabilities such as user interaction, broadcasting, and publishing.

296


2012

E2E200


Figure 226: Reporting- Predefined Reports with Web Templates

To minimize efforts required for the implementation of configuration validation, a number of predefined validation reports are delivered for different validation areas. Those are: software validation, security validation, database validation, SAP BW validation, and customer-defined validation.

Figure 227: Reports Overview

2012


297


E2E200

Once you have specified the reference system and, if necessary, created a comparison list, execute the desired check reports. To do so, you directly access the functions of SAP BW and call BW-based Web templates directly in the BW system. You can use the Bookmarks option to select report variants that have already been created or create a new one. All users can access the bookmarks. Note: By default, the Consistency Check tray is collapsed. It contains all reports that were used up to SAP Solution Manager 7.0 Enhancement Package 1. As of SAP Solution Manager 7.1, new reports are available in the Operator Check and Configuration Reporting trays.

Target Systems

Figure 228: Target Systems- Variants for Creation

There are two variants to create a target system: •

•

Variant 1: Creation from manually selected ConfigStores. This option should be used to create a target system in case configuration items which have to be validated are not contained in the predefined validation templates. Variant 2: Creation in accordance to predefined templates. ConfigStores and configuration items are defined here based on the delivered templates that correspond to one of the predefined validation areas. Those are security validation, software validation, database validation, BW validation.

A new target system is created for both of the variants as displayed in the figure.

298


2012

E2E200


Figure 229: Target System Maintenance - Create Target System

The configuration items stored in the CCDB provide information about the technical configuration and the applied software versions of existing systems. This also includes system-specific configuration items like host name, IP address, and so on. However, no other system corresponds with all configuration items to another system. In addition, only some specific configuration items but not the complete system configuration might be relevant for validation. Thus, in many cases, instead of performing a validation against an existing system configuration, a validation against a defined target configuration is required, for example, to validate settings according to corporate security baselines or performance settings across a large number of systems. These target configurations are created based on existing system configurations, and stored in the Solution Manager as “Target Systems”. In the popup window the name for target system and a description must be provided. The name could be maximum 8 characters long and must not start with 0 which is reserved for SAP objects.

2012


299


E2E200

After the system ID and the description are provided, the Save button will finally store the content of the selected ConfigStores. Feedback regarding the results of the creation of the selected ConfigStores is provided. •

•

Variant 1: After the required ConfigStores are selected, click the button Create from selected Stores at the bottom of the screen. Add system ID and description and save. Variant 2: Add System ID and Description, Choose one of the templates to create a target system with, save and close. These templates contain preselected configuration items for the areas: ABAP and Java Software Level, ABAP Kernel Level, OS Level, SAP Notes, Transport Requests, ABAP Profile parameters and for ABAP Memory configuration.

The newly created target systems might be found and maintained under the link Edit, which is described in the following slide. (System Demo) Create Target System

After a target system is created, it is often necessary to adjust it to the customer requirements. For example, to perform a validation of security standards, the existing ABAP instance parameters need to be restricted to only those that are relevant for security validation.

Figure 230: Edit Target System- Maintenance Functions

300


2012

E2E200


This figure provides an overview of the maintenance options available for editing target systems. With these options it is possible to select, delete and insert entries. In the example, the entries that are not relevant for configuration validation will be deleted and only the necessary configuration items will be left. More information and examples regarding Configuration Validation could be found under http://wiki.sdn.sap.com/wiki/display/TechOps/ConfVal_Home and http://service.sap.com/changecontrol.

Figure 231: Operators and Target Systems in SAP Solution Manager 7.1

In Solution Manager 7.1 all rules are transparent and no rules are hardcoded. Operators are available for all types of Config Stores: property, table, text, and xml. Operators comprise the rule used for validation for a Config Item. After the reference configuration is prepared, it is possible to define systems for comparison. These might be, for example, “all ABAP production systems” or “all SAP BW systems” or “all systems relevant for critical Business Process”. It is not necessary to have these lists defined, since the restriction on the systems can also be done in the variable screen of the validation report. However, it is more convenient to create a comparison list while having in mind to use them regularly. In order to avoid selecting single systems one by one each time, a validation report is executed it is possible to create a list of these systems only once and use it for configuration validation reporting. A list of systems to be compared is named “Comparison List”.

2012


301


E2E200

Figure 232: Create a new Comparison List

After defining a target system and a comparison list, everything is ready to execute configuration validation reports in accordance with the validation area.

Figure 233: Report Execution UI

•

BW bookmarks –

302

It is possible to save drilldowns and other BeX formattings of a report by creating a BW-bookmark. It is possible to store those bookmarks centrally to share it with other users or for a quick reuse.


2012

E2E200


System Demo Execute Report

BW User Interaction

Figure 234: Validation Output

• •

• • •

•

2012

After the report is executed, the validation results are displayed. In this diagram, an output of the validation report is shown. The information is separated into different tabs corresponding to the validated areas. The first tab is an overview screen that comprises the results for all validated areas. The further tabs contain detailed information on the corresponding area. At the top of the screen, the system ID of the reference system and the list of the comparison systems and their installation numbers are displayed. In the middle of the screen, an overview of all areas covered by the report is displayed. For each validation category, the number of compliant and non-compliant systems is displayed. In case there is at least one system that is not compliant with the reference system, the validation category is highlighted in red. Only if all the systems are compliant, the validation category is marked green. SAP Solution Manager release 7.0: Validation for Standard Users, Gateway Security, and Gateway Reginfo is not done versus the configuration items of the reference system but in accordance with the rules that are listed in the SAP Note 1234799. The content of the ConfigStore of the reference system is not taken into account here.


303


E2E200

Figure 235: BI User Interaction - Filter Options

Filter single system: If a lot of the systems or configuration items are used for comparison, then the list of validated items displayed is very long. In this case, it is useful to filter values only for one system and hide all the other values. In the example, the configuration items for system C60 are filtered. This is possible by clicking with the right mouse button on the system name C60 and choosing the option Keep Filter Value from the drop-down list. Then the values for the selected system are filtered while all the other values are hidden. Now the table Not compliant items includes only values for the C60 system. Display reference values: In the middle part, a Navigation Block is provided aimed to restrict the displayed data. By default, only the non-compliant configuration items are displayed. The filter option in the navigation block can be removed to display also the compliant values, such as the values from the reference system. The filter may be removed by clicking the waste container icon in the filter column of characteristic Compliance.

304


2012

E2E200


Figure 236: BI User Interaction - Maintenance Options

Display validity date of displayed configuration data: In order to check when the configuration items have been updated, click the icon for the section: ConfigStore Valid To. The column ConfigStore Valid To is added to the table Not compliant Items. Export to Excel: Navigate to the enhanced menu of the context menu. To do this, click in any place of the table with the right mouse button and choose Enhanced Menu. Choose Export as CSV File or MS Excel 2000 File from the drop-down list.

Figure 237: Configuration Validation: Selected Items of one ConfigStore

2012


305


E2E200

System Demo BI User Interaction

System Demo Configuration Validation

Report Directory

Figure 238: Report Directory UI

Within the Report Directory we provide predefined target systems for reporting. Predefined reports enable a quick start up without the need to configure your own target systems. These reports cover some important KPIs for the transport execution processes. A regular monitoring of these KPIs is the basis for a continuous quality control and governance of these processes. Additional reports are available to check the latest available support packages and recommended SAP Notes via Online Recommendations.

306


2012

E2E200


Figure 239: Reporting using Config Store- ABAP_TRANSPORTS

The Reporting Directory offers predefined reports (without maintaining rules manually) to enable reporting for ABAP transports in the following directions: • • • •

2012

Production Backlog. Failed transports. Development Backlog. Local transports.


307


E2E200

Reporting of Production Backlog •

•

•

•

The goal of this report is to find the transports which are released in Development system (DEV) but not yet imported into Production system (PROD). For this purpose a Target System will be generated and filled with the actual transport requests that have been created in the provided Development system (DEV) and have the TRSTATUS different to “D”. This Target System is generated dynamically and used for the Configuration Validation. The name of the generated Target System you can find in the field “Target System to be generated as reference”. To execute the report please provide the Development (DEV) and the Production (PROD). The systems could be provided from the list of the existing systems available when you click the button at the right side of the corresponding field. After the DEV and PROD systems are provided click the button start report. At this point a new Target System will be generated and filled with the data.

• Note: You have the possibility to restrict the data range for the ABAP transport requests inserted into the generated Target System.

Figure 240: Example of Production Backlog

If transport requests are parked for a long time in the import buffers of QAS or PRD before they are imported, they might not work anymore because the context in which they were developed might have changed in the meantime.

308


2012

E2E200


A large import buffer in production with many old transport requests represents a major risk for the production system. If these are imported accidentally, the system will be aborted and must be restored. Transports that were applied accidentally are one of the main reasons for system restores. • •

As visible in the result screen are many transports from the development system missing in the production system. For more information about examples for configuration validation we recommend to visit an Expert Guided Implementation session. Please go to http://service.sap.com/Esacademy to find the EGI schedule.

Outlook

Figure 241: Outlook: Trend Analysis- What new in the next release

Compliance Trend Analysis based on Configuration Validation will be provided soon. You are able to schedule the validation periodically and store the results in BW.

2012


309


E2E200

Figure 242: Outlook: SAP Notes Validation- Validity information for SAP Notes (next release)

In order to support the validation of notes, its possible to retrieve the validity information of a note. That way the validation rules cover the full validity of a note and supports cross system validation even though the system are not exactly on the same software component level. System Demo Production Backlog

For more information please visit: http://wiki.sdn.sap.com/wiki/display/TechOps/ConfVal_Home

310


2012

E2E200

307


Exercise 9: (Optional) Change Diagnostics Exercise Duration: 10 Minutes

Exercise Objectives After completing this exercise, you will be able to: • Find information about changes for a customer system in SAP Solution Manager Diagnostics. • Use the E2E Change Analysis tool to discover all changes in the ABAP and JAVA stack of the SAP Solution Manager system RWS. • Find detailed information for each change.

Business Example You would like to find out whether your transports have all been successfully transported through your landscape and whether the system runs stable after the golive of a business release.

Task: Analyze the changes in the SAP Solution Manager system RWS within 05.03.2012 - 11.03.2012 (week 10).

2012

1.

Navigate to E2E Change Analysis. What is the path?

2.

What is the amount of changes for each main instance in week 10?

3.

Look at the ABAP instance RWS – Solution Manager ABAP Stack. For which change groups have changes been recorded?

4.

Look at the JAVA instance of RWS – Solution Manager JAVA Stack . For which change groups have changes been recorded?

5.

Which ABAP transport requests were imported into the RWS – Solution Manager ABAP Stack (check the transport request tab).


311


E2E200

Solution 9: (Optional) Change Diagnostics Task: Analyze the changes in the SAP Solution Manager system RWS within 05.03.2012 - 11.03.2012 (week 10). 1.

Navigate to E2E Change Analysis. What is the path? a)

Go to the Root Cause Analysis work center and choose End-to-End Analysis, Type Selection Scenarios. Then select system RWS and start change analysis in a new window or embedded, choosing Change Analysis.

Figure 243: SAP Solution Manager


312


2012

E2E200


2.

What is the amount of changes for each main instance in week 10? a)

Select the Overview and Summary tabs to see all changes for the scenario. The time frame This week is preselected when Change Analysis is started, but you can change the time frame using the drop-down menu every time.

Figure 244: Timeframe -> Overview -> Summary

Expand the Table view below the diagram. A table appears that shows the number of changes for each main instance per day. Summarize the number of changes for each main instance.

Figure 245: Table View


2012


313


3.

Look at the ABAP instance RWS – Solution Manager ABAP Stack. For which change groups have changes been recorded? a)

4.

E2E200

Select the tab for component RWS – Solution Manager ABAP Stack and choose Summary. Open the table below the diagram. The displayed table contains a list of all change groups. The change groups are Security, Software Maintenance, Parameter, Transport Requests, SAP Notes, and Miscellaneous.

Look at the JAVA instance of RWS – Solution Manager JAVA Stack . For which change groups have changes been recorded? a)

Click on the tab for component RWS – Solution Manager JAVA Stack and choose Summary. Open the table below the diagram. The displayed table contains a list of all change groups. The change groups are Dispatcher, Server. If changes occurred for the different change groups, you can see the number of changes per day in the table.


314


2012

E2E200


5.

Which ABAP transport requests were imported into the RWS – Solution Manager ABAP Stack (check the transport request tab). a)

Under RWS – Solution Manager ABAP Stack, choose tab Transport Requests. You now see the number of ABAP transports per day.

Figure 246: RWS - config store ABAP_TRANSPORTS

Click on a cell of the green line (transports per day). You will then see the detailed list of transport requests of that day displayed in the change reporting viewer.

Figure 247: Change Reporting

2012


315


316


E2E200

2012

E2E200

313


Exercise 10: Configuration Validation Exercise Duration: 15 Minutes

Exercise Objectives After completing this exercise, you will be able to: • Maintain a target system with reference configuration values; these values can be compared against existing systems in order to see if the defined configuration items are identical in all compared systems. • Maintain a comparison list with systems that will be compared against the reference system. • Execute different Configuration Validation reports.

Business Example You would like to know whether your systems were CDMC should be used are on the same ST-PI level. Furthermore you would like to have a template containing your defined configuration items that you than run against your systems to check regularly if all systems are compliant.

Task 1: Execute the predefined Configuration Validation report for Software Validation. 1.

Start the Configuration Validation Reporting application.

2.

Execute the report 0TPL_0SMD_COMPL_PARSEL_1CONFST for Consistency validation.

3.

Enter the reference system RWE 0120003411, the comparison systems RWS 0120003411 and RWZ 0120003411, the Config Store ABAP_COMP_SPLEVEL and the Configuration Item ST-PI . Execute the comparison. Are all systems compliant?

Task 2: Create a new comparison list that includes the systems RWS, RWE and RWZ. These systems will later be compared with the reference system. 1.

Create a new comparison list that comprises the systems RWS, RWE and RWZ. Name it CL## (where ## is your group number).


2012


317


E2E200

Task 3: Create a new target system. This will be used as a reference system for comparisons with other systems. 1.

Start the Configuration Validation Maintenance application.

2.

Create a new target system. Choose the following stores from the source system RWS: • ABAP_COMP_SPLEVEL • ABAP_INSTANCE_PAHI • ABAP_NOTES Choose Create from selected Stores. Enter the ID TS## (where ## is your group number) for your target system.

Task 4: Edit the target system. Only certain parameters of the selected config stores will be used for the comparison. 1.

By default, all items of the selected config stores are included in your new target system. However, you only want to compare a limited set of parameters, which are listed below. Delete all other parameters. ABAP_COMP_SPLEVEL • ST-PI ABAP_INSTANCE_PAHI • abap/heap_area_dia • abap/heap_area_nondia • abap/heap_area_total ABAP_NOTES • 1670650 - Collective Note with all corrections for CDMC (ST-PI SP05).

Task 5: Execute the Configuration Validation report. 1.

Execute the Configuration Validation report. Compare the values that are defined in your target system with the values of the systems RWS, RWE and RWZ of your comparison list. Are the systems compliant?


318


2012

E2E200


Task 6: The BW User Interaction allows you to display the result in different views based on BW query navigation options.

2012

1.

The result table on the right-hand side shows the comparison systems RWS, RWE and RWZ including the compared config stores, the config store items, and the item values. Include the reference system in this table, too.

2.

Display only the values for the system RWE in the result table.

3.

Remove the values of the configuration items from the result table.


319


E2E200

Solution 10: Configuration Validation Task 1: Execute the predefined Configuration Validation report for Software Validation. 1.

Start the Configuration Validation Reporting application. a)

2.

Go to the Change Management work center and choose Configuration Validation → Reporting Execution Tab.

Execute the report 0TPL_0SMD_COMPL_PARSEL_1CONFST for Consistency validation. a)

Choose the report and click on the link Start equality validation reporting, as shown in the picture below.

Figure 248: Consistency Validation


320


2012

E2E200


3.

Enter the reference system RWE 0120003411, the comparison systems RWS 0120003411 and RWZ 0120003411, the Config Store ABAP_COMP_SPLEVEL and the Configuration Item ST-PI . Execute the comparison. Are all systems compliant? a)

In the popup browser window enter RWE 0120003411 as reference system and RWS 0120003411 and RWZ 0120003411 as comparison systems. Use F4-help to choose ABAP_COMP_SPLEVEL as the Config Store. Use the F4-help in the Configuration Items field search for ST*. In the result list select following Item: ST-PI and click on Transfer button. If you perform all actions correctly, your variables will look like in the following picture. Choose Execute to start the comparison. You will then see the result screen in a BW Web template.

Figure 249: Variable Screen

Figure 250: Result Screen

Answer: All systems are compliant.


2012


321


E2E200

Task 2: Create a new comparison list that includes the systems RWS, RWE and RWZ. These systems will later be compared with the reference system. 1.

Create a new comparison list that comprises the systems RWS, RWE and RWZ. Name it CL## (where ## is your group number). a)

Choose Maintain Comparison Lists tab and in the Selection Lists assignment block click on the Create new Comparison List icon. In the dialog box, enter the name of your comparison list CL## (where ## is your group number) and a short description. In the Select Source Systems area, select the systems RWS (only ABAP), RWE and RWZ. Choose Create from selected and Close.

Figure 251: Save as Comparison List


322


2012

E2E200


Task 3: Create a new target system. This will be used as a reference system for comparisons with other systems. 1.

Start the Configuration Validation Maintenance application. a)

Go to the Change Management work center and choose Configuration Validation → Target System Maintenance Tab. You should see the following menu:

Figure 252: Target System Maintenance

2.

Create a new target system. Choose the following stores from the source system RWS: • ABAP_COMP_SPLEVEL • ABAP_INSTANCE_PAHI • ABAP_NOTES


2012


323


E2E200

Choose Create from selected Stores. Enter the ID TS## (where ## is your group number) for your target system. a)

In the Source System list select the source system RWS. If it does not appear automatically, choose Display all first.

b)

In the Select Config Stores area, select the three stores mentioned above.

c)

Choose Create from selected Stores.

Figure 253: Select Source Systems

d)

In the dialog box, enter the ID TS## (where ## is your group number) for your target system. Choose Save and Close.

Figure 254: Save as Target System

e)

The chosen Config Stores should bring back a green rating when saving the new target system.

Task 4: Edit the target system. Only certain parameters of the selected config stores will be used for the comparison. 1.

By default, all items of the selected config stores are included in your new target system. However, you only want to compare a limited set of parameters, which are listed below. Delete all other parameters. ABAP_COMP_SPLEVEL • ST-PI ABAP_INSTANCE_PAHI • abap/heap_area_dia • abap/heap_area_nondia Continued on next page

324


2012

E2E200


• abap/heap_area_total ABAP_NOTES


2012


325


E2E200

• 1670650 - Collective Note with all corrections for CDMC (ST-PI SP05). a)

In the Target System Maintenance, choose Edit Target System.

b)

In the Select Target Systems list, select the target system TS##that you just created. If it does not appear on the list, choose Display all first.

c)

In the area Config Stores of Target System area, select the config store with the store name ABAP_COMP_SPLEVEL. The store content is now displayed in the lower area of the screen.

d)

Select the software component ST-PI, which will be included in the target system.

Figure 255: Target System Maintenance

To delete all other software components choose Delete unselected . Save your settings. e)

In the Config Stores of Target System area, select the next config store with the store name ABAP_INSTANCE_PAHI and delete all parameters except for the three parameters mentioned above.

f) Note: To find the required parameters more quickly, you can choose Filter criteria.

. Use the wildcard * option in the filter

Repeat the steps for the config store ABAP_NOTES and only maintain SAP Note 1670650. Continued on next page

326


2012

E2E200


Task 5: Execute the Configuration Validation report. 1.

Execute the Configuration Validation report. Compare the values that are defined in your target system with the values of the systems RWS, RWE and RWZ of your comparison list. Are the systems compliant? a)

Go to the Change Management work center and choose Configuration Validation → Report Execution tab. In the next screen, expand the Reference system and comparison systems assignment block. Select your target system and your comparison list. In the lower part of the screen, choose a Operator Validation report. Select the report 0TPL_0SMD_VCA2_NCOMPL_CI_REF. Choose Start configuration validation reporting.

Figure 256: Report Execution

b)

On the next screen, you can control your settings. Choose Execute.

c)

This report shows non-compliant configuration items (config stores and configuration items selectable):

Figure 257: Save as Target System


2012


327


d)

E2E200

Expand the Navigation Block on the left hand side and change the setting of the Compliance filter, as shown in the pictures below:

Figure 258: Navigation Blocks

e)

Transfer your new filter settings, clicking on the Transfer button and check the result table.

Figure 259: Configuration Items


328


2012

E2E200


Task 6: The BW User Interaction allows you to display the result in different views based on BW query navigation options. 1.

The result table on the right-hand side shows the comparison systems RWS, RWE and RWZ including the compared config stores, the config store items, and the item values. Include the reference system in this table, too. a)

In the Navigation Block, click on the filter next to Compliance System and select the system roles Reference system and Comparison system.

Figure 260: Select Filter Value

2.

Display only the values for the system RWE in the result table. a)

In the result table right-click on system RWE and in the context menu, choose Keep Filter Value.



2012


329


3.

E2E200

Remove the values of the configuration items from the result table. a)

In the result table, right-click on a configuration item value. In the context menu, choose Remove Drilldown.


330


2012

E2E200

327


Exercise 11: Configuration Validation – Report Directory Exercise Duration: 10 Minutes

Exercise Objectives After completing this exercise, you will be able to: • Distinguish between Production and Development backlogs. • Identify Failed and Local Transports (real systems necessary). • Use the Report Directory to find out more details about the critical Issues identified by the Transport Execution Analysis.

Business Example Task: Execute the predefined Report of Production Backlog. 1.

Figure 263: DEV -> PROD

Start the Report Directory application.

2012

2.

What is the goal of the report 0PRDBLG- Report of Production Backlog?

3.

(Optional) What are the other reports of the Transport group and their goals?

4.

Execute the Report 0PRDBLG - Report of Production Backlog and interpret the results.


331


E2E200

Solution 11: Configuration Validation – Report Directory Task: Execute the predefined Report of Production Backlog. 1.

Figure 264: DEV -> PROD

Start the Report Directory application. a)

The Configuration Validation provides a report directory with pre-defined analyses which can be used to find more details on the critical issues identified by the Transport Execution Analysis. Select the tab Report Execution and choose Report Directory.

Figure 265: Report Directory


332


2012

E2E200


2.

What is the goal of the report 0PRDBLG- Report of Production Backlog? a)

In the Transports group choose Report 0PRDBLG (Reporting of Production Backlog) and go down to additional information block. There you can check the General Data for the chosen report, save the current selection as a new record in the report directory or get some more detailed information to the report by pushing on the question mark icon.

Figure 266: Reporting the Productive Backlog

Answer: The goal of this report is to find the transports which are released in Development system (DEV) but not yet imported into Production system (PROD). For this purpose a Target System will be generated and filled with the actual transport requests that have been created in the provided Development system (DEV) and have the TRSTATUS different to “D”.


2012


333


3.

E2E200

(Optional) What are the other reports of the Transport group and their goals? a)

Choose the report name 0DEVBLG - Development backlog and click on the Display detailed information on Report icon. The following window appears:


So, the correct answer: The goal of this report is to find the transports which are created in DEV but not yet released in DEV. Optional: Make you familiar with all report of the Transports group. •

0BADTRAN - Failed transports: The goal of this report is to find the transports which failed (RETCOD > 4).

•

0LOCTRA - Local transports: The goal of this report is to find the transports which are created in the provided system.

4.

Execute the Report 0PRDBLG - Report of Production Backlog and interpret the results. a)

to select development and production systems to Click on the icon be compared during the report execution. In the pop-up window click on the Display Systems button, select RWS and RWE and choose the button Transfer. As a development system please choose RWS and as a production system RWE. As a Transport Requests in Date Range parameters choose from 1.06.2011 to 30.06.2011. Check that your inputs are the same as in the picture below and choose Start Report button.


334


2012

E2E200



In the next window you could change the variables for comparison system RWE. You could also run this analysis by Suppress the query variable pop-up in the above screen. Choose Execute button to start the report.

Figure 269: Variables for ABAP TRANSPORTS

If you filled in all variables correctly the result looks like at the picture below and you can see that there is no compliance regarding the transports:


2012


335


E2E200


336


2012

E2E200


Lesson Summary You should now be able to: • Understand the basis architecture of E2E Change Diagnostics. • Find current configuration information with Change Reporting. • Explain how to find out recent changes in the solution landscape with E2E Change Analysis. • Know how to compare multiple systems with Configuration Validation. • Understand the usage of target systems. • Know how to use the report directory.

Related Information For more use cases for Configuration Validation we recommend you to attend the Expert Guided Implementation session that takes place for deepening the knowledge for this topic. Customers listen in the morning to the trainer remotely and in the afternoon they run the reports in their own landscape and have access to the trainer in case of questions. Information as well as registration opportunities could be found under: http://service.sap.com/esacademy

2012


337


Lesson: 334

E2E200

Software Change Strategies Lesson Duration: 45 Minutes

Lesson Overview Software change strategies include technical and organizational aspects. SAP’s best practices will be discussed within this lesson. As a result the right balance between system stability requirements and flexibility for the business departments can be determined.

Lesson Objectives After completing this lesson, you will be able to: • • • • • •

Understand the risks of Import Single Strategy. Understand the risks of Inconsistencies in the Transport Landscape. Understand the basic idea and benefits of Release Management. Explain the system and clients roles in advanced system landscapes. Give some examples of advanced system landscapes based on specific customer requirements. Explain, which tools can be used to manage transport dependencies.

Business Example Software change strategies include technical and organizational aspects. SAP’s best practices will be discussed. As a result the right balance between system stability requirements and flexibility for the business departments can be determined.

338


2012

E2E200

Lesson: Software Change Strategies

Challenges in a Three-System-Landscape

Figure 271: Three-System-Landscape

• • • •

A three-system-landscape consists of a development system DEV, a quality assurance system QAS and a productive system PRD. The development system DEV is needed to implement changes. The quality assurance system QAS is needed to perform functional tests and integration tests with production-like data. QAS is also needed to test the import of the change requests. Without a quality assurance system, the import of transports cannot be tested before it is imported in production.

Step 1: •

•

2012

The change request CR is released. Development objects which are locked, are released and the change request CR is written to the import queue of the quality assurance system. The import queue has two functions. The first one is that it contains all change requests that have been released, and the second is to remember the sequence, in which the change requests have been released.


339


E2E200

Step 2: • •

• •

The complete import queue for the quality assurance system QAS is imported. System QAS is used for first tests with production-like data and, therefore, the import of the complete transport buffer should be done in short time intervals, for example, every 15 minutes. This can be scheduled automatically. The change requests that are imported are also written to the import queue of the productive system PRD. This guarantees that the change requests and their import sequence to the quality assurance system QAS are remembered.

Step 3: The import buffer of the productive system is imported into production.

Import Single Strategy •

The single transport strategy shows the following problems and risks:

•

– Transport requests are imported in an individual sequence – Risk of forgotten transports – Risk of version downgrades by transport sequence violations The following recommendation you should follow:

•

340

– Use the Import Project ALL or Import ALL strategy There are several risks in a three-system-landscape. The following slides explain these risks in more detail.


2012

E2E200


Figure 272: Risk: Forgotten Transports

• • •

2012

Transport request DEVK900002 contains a report ZREPORT which calls the function module ZMODULE in request DEVK900001. In QAS DEVK900001 and DEVK900002 are tested together. The test is ok. But then only DEVK900002 is transported into PRD. The generation of ZREPORT fails, because DEVK900001 was forgotten and function module ZMODULE cannot be called.


341


E2E200

Figure 273: Risk: Downgrading Object Versions

• • • •

Transport request DEVK900002 contains a report ZREPORT which calls the function module ZMODULE, which is transported in request DEVK900001. In QAS DEVK900001 and DEVK900002 are tested together. The test is ok. However, only DEVK900002 is transported into PRD. It fails because DEVK900001 was forgotten. Now DEVK900001 is also imported into PRD. But the test in PRD fails again because now the old version of ZREPORT (version of DEVK900001) has overwritten the newer version (version of DEVK900002).

Inconsistencies in the Transport Landscape- Reasons and Possible Solutions •

There are several risks in a three-system-landscape: The following paragraph explain these risks in more detail. –

Reasons:

–

– Transport sequence violations – Transports which were not transported completely into all systems – Transports stay in the import buffer of QAS or PRD too long – Wrong initial system set up – Several parallel projects with different project timelines – Projects and maintenance in parallel Solutions: –

342

Forward all transport requests that are released in the development system quickly into the test and production system


2012

E2E200


Figure 274: Inconsistencies in the Transport Landscape

• •

• •

•

The development system DEV contains all developments. The quality assurance system QAS contains transports, which have already been imported into PRD, but also transports which have not been imported yet into PRD. Therefore all three systems are on different software levels. These different software levels in a three-system-landscape cause risks. One big risk is, that programs, which have been tested successfully in QAS might fail in PRD. The main reasons, why these inconsistencies cannot be avoided in such a transport landscape will be explained in more detail on the following slides.

Figure 275: Risk: Version Inconsistencies during Bug-fixing

Objects which have been changed in a project that is currently in transition cannot be maintained anymore during bug-fixing.

2012


343


E2E200

Figure 276: Version Compare for Fixes between DEV and PRD

•

• • •

344

You can compare the object versions in DEV and PRD before a maintenance task. If the versions are different, then you have to temporarily switch back an old object version from the version history in the development system. This object version is corrected and transported to production. In the next step the correction is done again with the latest object version. This procedure is not possible for BW objects, because they do not have a version history. The procedure to maintain two different versions of one object via versions, and to transport these versions through the system landscape is error-prone. Alternatively the developer can search for objects in transition with transaction SE03.


2012

E2E200


Figure 277: Risk: Detection of Cross Reference Errors during Bug-fixing

• •

•

•

In this example Object 1 was not changed by the project. But Obj1 uses Obj2, and Obj2 was changed. At the beginning Obj1 does still work. Now Obj1 has to be corrected. The new version of Obj1 does still work with the new version of Obj2. However, the new version of Obj1 does not work with the old version of Obj2. This is only detected in PRD. For example Object1 could be a program, which uses a data type Obj2, which has been declared in the data dictionary. If the new data type has only been brought to QAS but not to PRD, the program will work in QAS but it will fail in PRD, because the data type is not there. Another example for Obj1 could be a program that reads data from a table (Obj2). At the beginning, the program reads data from the first 3 columns of the table. Then, an additional column is added to the table. If the program now also reads data from the new column, this only works with the new version of the table. It will fail in PRD.

Figure 278: Cross-Reference Inconsistencies and Pre-Production

2012


345


E2E200

The system landscape topology, which can be used to detect cross-reference inconsistencies is a Preproduction system. A fourth system called Preproduction is brought between the QAS and the PRD. If this Preproduction system has the current software / configuration state of production, a cross-reference error can already be detected during tests in Preproduction.

Release Management

Figure 279: Working with Parallel Projects

Projects are defined by their release cycles. Any change, which is related to a project, moves synchronously from development through test to production or delivery.

Figure 280: Working with Parallel Projects: Object Conflicts and Object Dependencies

346


2012

E2E200


There are two types of problems when working with parallel projects. •

Object Conflicts: –

•

This means that the same objects are contained in different projects. The project which is imported last, overwrites the objects of the other project. Therefore, the project which was imported first might not work anymore after the import of project 2. Object Dependencies:

–

Objects in different projects use each other, for example, a program in project 1 calls an object included in project 2. If only one of the projects is imported into another system, it will fail. This problem is called cross-reference inconsistency.

Figure 281: Recommendation for Parallel Projects: Preproduction System

The solution for cross-referencing inconsistencies is a Pre-Production system. If the Pre-Production system has the current software / configuration state of production, the error can already be detected and fixed in Pre-Production.

2012


347


E2E200

Figure 282: Parallel Projects: Best Practice Recommendations

348


2012

E2E200


Figure 283: Parallel Projects: Bundle Transports in CTS Projects

• • • •

2012

SAP offers the use PROJECTS, to group comprehensive customizing and development activites. With projects, you can define the customizing scope you want to cover. Please note that this is only important if you have several, simultaneous project activities. By activating a CTS project to work with your customizing project, you can link every change request to a CTS project. The CTS project attribute of the change request lets you control the import of these changes into several target systems (transaction SPRO_ADMIN).


349


E2E200

Figure 284: CTS Projects in the Import Queue

•

•

•

350

If the project intersection check is activated for a CTS project a sequence is proposed between the requests of different projects if they contain identical objects. The Chain-symbol indicates that there is a predecessor transport in another CTS project which contains the same object. If you doubleclick on it, you see the predecessor transport request and the object in conflict. You can decide to include the predecessor transport in the import of the CTS project. If the project intersection is activated, the export of a transport request might have a long runtime. Therefore CTS projects that are completely imported should be closed (e.g. in transaction SPRO_ADMIN). Then they are not included in the intersection check any longer.


2012

E2E200


Figure 285: Release Management

Decision Criteria for Change Categories •

Urgent Corrections

•

– Critical Business Process does not work – Resolution of priority 1 incidents Low Impact Changes – –

•

Non-invasive repetitive changes were the impact is well known. A positive list should be provided (shift plans, read only reports, SAP script forms, authorizations, currency exchange rates, ) Bugfixes and Small Enhancements

– – – •

Corrections to existing functionality Resolution of incidents that come from the service desk procedure Small enhancement requests with limited effort (e.g. less than 5 days for development and testing) New Demand

– – –

Completely new functionality Enhancement requests with a major effort (e.g. more than 5 days) System outage required

• Note: Note 67739 explains the priority for problem messages, that customers send to SAP. The criteria for the category “very high” can be taken as criteria for emergency changes.

2012


351


E2E200

Figure 286: Release Management : Best Practice Recommendation

Figure 287: Release Management : Evaluation

352


2012

E2E200


Release Management - Maintenance Calendar •

• • •

2012

Especially for major releases it is required to set up and publish a fixed maintenance calendar for a complete year. This calendar also should include SAP maintenance activities (Support Packages and/or Enhancement Packages). The maintenance calendar needs to cover all relevant systems across the complete landscape. This will help to reduce integration tests for processes across system borders. A well defined maintenance calendar is an important condition for the approval process and for planning the changes. This calendar needs to include also the related test activities and code freeze periods. In order to measure and optimize downtimes caused by release imports, the pre-production system should be leveraged to verify import times.


353


E2E200

Figure 288: Maintenance Planning Calendar Example

• • • • • •

This example shows the maintenance calendar of a solution consisting of a BW, CRM and ERP system. Support Packages are imported from the end of January to beginning of February. Every second weekend, there are maintenance deliveries (Go-Lives of maintenance cycles). Sometimes, there are codefreezes due to quarter end activities. Projects can be incorporated into any maintenance cycle. This gives flexibility to the projects as there are many Go-Live windows. This calendar shows 2 Best Practices: –

–

All systems in a solution should be delivered with projects or maintenance cycles at the same time. This is due to the dependencies of changes in different systems (see “transport dependencies”). The system owners are also responsible for maintenance. First, the maintenance is planned. Then, the implementation projects consider the maintenance plan in their project schedule.

Advanced System Landscapes System and Client Roles

354


2012

E2E200


Figure 289: System Roles and Clients: Development System- 1/2

Figure 290: System Roles and Clients: Development System - 2/2

2012


355


E2E200

Figure 291: System Roles and Clients: Quality Assurance System

Figure 292: System Roles and Clients: Pre-Production System- 1/2

356


2012

E2E200


Figure 293: System Roles and Clients: Pre-Production System - 2/2

Figure 294: System Roles and Clients: Production System (PRD)

Figure 295: Recommended Transport Routes- Example: Single Track 4System Landscape

2012


357


E2E200

Figure 296: System Roles and Clients: Sandbox System (SBX)

Figure 297: System Roles and Clients: Training System (TRN)

Customer Requirements and Resulting System Landscapes

358


2012

E2E200


Figure 298: Scenario 1: Maintenance Scenario

•

• • • •

2012

This scenario typically consists of a SAP R/3 system and maybe a SAP BI system on an old release serving one or several countries. The major development cycle and the rollout are complete. Ongoing changes are limited to Support Packs, operating and database patches. SAP configuration changes are required to support minor business requirements. In this case a three-system-landscape might be sufficient. The maintenance transports are bundled into packages, so that they can be tested altogether. This scenario works well, if the number of urgent corrections is low. Non-urgent corrections should be released late, so that QAS stays close to PRD for the test of urgent corrections.


359


E2E200

Figure 299: Recommended Landscape for Maintenance Scenario: 4- System Transport Landscape

Explanation of the required system sizes: • • •

S: small data volume, no HA, small CPU, RAM M: full data volume, HA, reduced CPU, RAM L: full data volume, HA, full CPU, RAM

Figure 300: Scenario 2: Implementation Scenario

360


2012

E2E200


Figure 301: Scenario 2: Implementation and Country Rollout of a new SAP Business Suite Solution

•

This scenario typically consists of several SAP Business Suite products which are rolled out worldwide or in a major region. The instances are fully integrated. Three major activities need commence in parallel: –

• • •

2012

Implementation of Support Packs, operating and database patches to keep the production instances current – On-boarding of new countries into the new solution including user training and minor configuration changes to support local business requirements – Development of a new integrated release to support new business requirements driving more significant configuration changes and limited customization. The solution is rolled out sequentially, region by region. After the go live of a release, this release has to be maintained, while a new release is developed. The rollout plan and the development plan have to be synchronized, because a region needs a certain release level in order to go live.


361


E2E200

Figure 302: Recommended Landscape for Implementation Scenario: Extended Phased Transport Landscape

Explanation of the required system sizes • • •

S: small data volume, no High Availability (HA), small CPU, RAM M: full data volume, HA, reduced CPU, RAM L: full data volume, HA, full CPU, RAM

Why is a single track landscape not sufficient?

362


2012

E2E200


A single track landscape in principle does work. But it comes with the following limitations and risks: •

•

• • •

Challenges and risks arise mainly from the fact that all types of changes need to be managed in a single development system and in a single transport track. (In a best practices environment, there are 5 types of changes – emergencies, minor releases, major releases, standard changes and SAP maintenance) There are conflicts that will need to be managed explicitly by respective processes. These conflicts will lead to limitation in either the project development or the creation of corrections (one has to wait). Limited flexibility for developing new functions Limited test capabilities for testing new functions (time and environment) Risk for urgent corrections (the release/development status of the MDV system is different to the status of the production system. Potentially, in MDV there are new developments active → the objects that needs to be corrected has been changed by a new development project) – –

urgent corrections potentially take longer to be implemented the test environment for urgent corrections potentially is “far from production” (only the pre-production system reflects the status of production.

Deciding Factors for Choosing a Phased Transport Landscape • • • • •

2012

Major implementation projects (Major Releases) or upgrade projects are in the pipeline The overall change volume is high Safety/quality/availability of the production environment has a very high priority. At the same time, a high number of functional developments is required to meet the business needs (flexibility and agility) The majority of changes is performed in the implementation project. This means the number of project changes is significantly higher than the number of changes in the Production Support landscape. This has a major influence on the effectiveness and efficiency of the whole change management process → needs to be ensured by appropriate governance.


363


E2E200

Transport Dependencies and Solution Transports

Figure 303: Example for Solution Transports: Portal iView uses BI Webreport

Figure 304: Example for Solution Transports: Portal iView uses BI Webreport

Three Solution Manager Tools support solution transports: • • •

364

Task list (Transport Management with SAP Solution Manager) Quality Gate Management Change Request Management


2012

E2E200


To work with solution transports for all applications in SAP Solution Manager you should enable your non-ABAP systems for CTS+.

Figure 305: Synchronization of Projects across the Landscape

•

•

2012

This slide shows a three-system-landscape, that contains popular products of SAP. It also shows one topic, which has been discussed before. Since SAP delivers products on an ABAP and a Java-Stack, it has to be also assured, that the deployment of java-based solutions is integrated in the transport mechanism. This topic is adressed via CTS+(Enhanced Change and Transport System). Further level of control could be reached by using e.g. Change Request Management for transporting changes within a solution.


365


366


E2E200

2012

E2E200

363


Exercise 12: Software Change Strategies Exercise Duration: 15 Minutes

Exercise Objectives After completing this exercise, you will be able to: • Test your knowledge on system landscapes and transport strategies.

Business Example This exercise consists of questions and answers.

Task 1: Which of the following are risks when using the Import Single strategy? 1.

More than one answer is correct. Decide whether each answer is true or false. Question

True/ False

Inconsistencies between workbench and customizing requests Cross-reference inconsistencies due to forgotten transports Object versions in DEV and PRD can be different due to long-running implementation projects Wrong transport sequence

Task 2: What is recommended when several parallel implementation projects with different go-live dates are running in one transport landscape? 1.

Please choose the correct answer. Question

True/ False

Unit test client Separate development client for each project Preproduction system


2012


367


E2E200

Task 3: Which of the following are advantages of a phased system landscape? 1.


True/ False

Faster realization of business requirements Implementation projects and maintenance tasks can be separated. No code freeze required Clean environment for emergency corrections

368


2012

E2E200


Solution 12: Software Change Strategies Task 1: Which of the following are risks when using the Import Single strategy? 1.


True/ False

Inconsistencies between workbench and customizing requests Cross-reference inconsistencies due to forgotten transports Object versions in DEV and PRD can be different due to long-running implementation projects Wrong transport sequence a) Question

True/ False

Inconsistencies between workbench and customizing requests

False

Cross-reference inconsistencies due to forgotten transports

True

Object versions in DEV and PRD can be different due to long-running implementation projects

False

Wrong transport sequence

True

Task 2: What is recommended when several parallel implementation projects with different go-live dates are running in one transport landscape? 1.

Please choose the correct answer.


2012


369


E2E200

Question

True/ False

Unit test client Separate development client for each project Preproduction system a) Question

True/ False

Unit test client

False

Separate development client for each project

False

Preproduction system

True

Task 3: Which of the following are advantages of a phased system landscape? 1.


True/ False

Faster realization of business requirements Implementation projects and maintenance tasks can be separated. No code freeze required Clean environment for emergency corrections a) Question

370

True/ False

Faster realization of business requirements

False

Implementation projects and maintenance tasks can be separated.

True

No code freeze required

False

Clean environment for emergency corrections

True


2012

E2E200


Lesson Summary You should now be able to: • Understand the risks of Import Single Strategy. • Understand the risks of Inconsistencies in the Transport Landscape. • Understand the basic idea and benefits of Release Management. • Explain the system and clients roles in advanced system landscapes. • Give some examples of advanced system landscapes based on specific customer requirements. • Explain, which tools can be used to manage transport dependencies.

2012


371


Lesson: 368

E2E200

Custom Development Management Cockpit (CDMC) Change and Transport System (CTS) Analysis Lesson Duration: 45 Minutes

Lesson Overview This lesson will introduce Custom Code Management Cockpit - Change and Transport System Analysis. This analysis helps to secure the go live by carrying out e.g. an environment analysis and remote comparison for a specified object set out of your transports belonging to your business release.


Know the prerequisites to use CDMC CTS. Understand in which situation the CDMC CTS analysis could be used. Execute the activities for CDMC CTS Analysis in the custom Development Management Cockpit (CDMC). Analyze the results of the CDMC Analysis.

Business Example You are ready with the development of a new business release. It is your task to control the quality of the golive.

Introduction Custom code should be documented in SAP Solution Manager to make use of the integration aspect - good documentation of custom code should include: • • • • •

372

Which parts of the project are impacted by the custom code? Why has the custom code been created (business background)? Which systems are involved? Are there any dependencies between the custom code and other systems or functions? Which business processes and process steps are changed?


2012

E2E200

Lesson: Custom Development Management Cockpit (CDMC) - Change and Transport System (CTS) Analysis

• • • • •

What are the transactions or entry points of the custom code? Which interfaces are used to integrate the custom code with standard applications? Which development objects have to be transferred from development to quality assurance and production systems? How to operate the custom code? How to set up and execute integration and volume test for the custom code?

Figure 306: SAP Solution Manager Custom Development Management Cockpit

Custom Development Management Cockpit Most SAP customers modify or enhance their SAP standard software in some way. Some customers only add reports that are specific to their business, while others have complete custom developed add-ons (developed internally or by a third party). These changes allow customers to tailor solutions to their individual requirements. There are usually a large number of custom development objects in customer systems. This can lead to high operation costs for you because it can be difficult to identify any objects that your system does not use anymore. There can often be an unnecessarily high number of these obsolete objects. What are the issues you face? It can be challenging for you to keep track of all these changes to the standard configuration, and it becomes increasingly difficult over time as the number of development objects increase. Some objects may become obsolete without

2012


373


E2E200

anybody noticing. The person responsible for custom developments may be unavailable, for example. If you want to upgrade to a higher SAP release, or to apply a support package, you must check and adapt every custom development object manually. You must then test each object to ensure that it does not cause any problems in the new context. This process represents a considerable amount of effort. The Custom Development Management Cockpit addresses these issues by providing a set of features that support the handling and organization of ABAP custom development objects in SAP systems. You can use SAP CDMC to: • • •

Analyze custom developments in your SAP system, and identify obsolete developments (Clearing Analysis). Identify the potential consequences an upgrade can have on custom developments (Upgrade / Change Impact Analysis). Analyze the usage of customer objects in transport requests by carrying out quality checks to secure testing and that no object versions get overwritten (Change and Transport System Analysis).

There are three aspects of CDMC: 1.

Clearing Analysis Clearing Analysis is the analysis of custom objects and modifications made to SAP standard objects in order to identify the used and unused custom objects and modifications. You can delete custom objects and modifications not used in the system. This is referred to as the clearing process.

2.

Upgrade / Change Impact Analysis Upgrade / Change Impact Analysis identifies the impact that a support package or upgrade will have on any custom developments in the system and estimates the amount of work required to adapt them.

3.

Change and Transport System Analysis Find out the test scope for your customer business release and check for changed versions of objects in the environment.

This picture should illustrate the different roles of systems in a change and transport analysis. Change and Transport System Analysis (CTS):

374


2012

E2E200


Figure 307: Custom Development Management Cockpit- Change and Transport System Analysis (CTS)

With the Change and Transport System Analysis, you can identify and analyze the test scope of your custom developments and ensure that the risk of overwriting object versions or running in a situation of import errors coming from wrong sequence of transports or overtakers could be analyzed. Statistic System is the system (usually the Production System) where the collection of statistical data, e.g. executed transactions, programs, takes place. A job that is executed periodically (daily or weekly) transfers and condenses SAP standard statistics data and short dump evaluation in a CNV* database table. Analysis System is the system (usually the Quality Assurance System or Pre-production system) where all project-related analyses (including selection of relevant objects) are performed in the background, and the results are stored in a CNV* database table. Here the business release has to be imported before starting the analysis. Control System is the system (usually the central Solution Manager System), where all activities in systems with other system roles such as statistic system and analysis system are triggered from here via RFC connections. SAP recommends a three system landscape consisting of statistic system, analysis system and control system, each on one system ID. An alternative combination is to combine the analysis and control systems in one system ID.

2012


375


E2E200

Typically these roles would be taken over by the QAS system. The statistics system remains as a separate system ID. This approach has the side-effect of removing the integration aspects of CDMC into the central solution manager system, e.g. the launch of CDMC via the upgrade roadmap and display of the affected business processes. This is because the Control System is no longer the Solution Manager System in this case.

CDMC Change and Transport Analysis

Figure 308: Parts of CDMC

376


2012

E2E200


Change and Transport System Analysis helps the user in performing the quality checks by doing a usage analysis, environment analysis and remote comparison for a specified object set of requests in the analysis (QAS/Test) system. It gives the list of the objects that were used during the test phase. It also helps to check if the objects in the request are identical across the landscape. •

• • •

You can perform Test Scope Identification, Environment analysis, Test Coverage Analysis and Remote Comparison for a specified object set of requests in the analysis system(QAS/Test) and evaluate the result. It gives the list of the objects that are used during the test phase. It also helps to check if the objects in the project are identical across the landscape. You can find the dependency analysis for the objects referred in the transport request between the analysis and target systems. The CTS project helps the Project Manager or Release Manager to perform a risk assessment before the transport set is imported into production/target system.

Figure 309: Business Needs and Challenges for custom developments during test and go live phase

If we have several productive systems available we have to start several projects to get different environment analysis.

2012


377


E2E200

Figure 310: Transport Landscape and Typical Usage Scenario

CDMC CTS Analysis supports several use cases. Typical scenarios could be: Analysis System

Target System

DEV

TEST

TEST

Pre-Prod

TEST

Prod (If a Pre-Prod is not available)

Pre-Prod

Prod

If a Pre-Production System exists, the recommended scenario is: Analysis System TST, Pre-Prod

Target System Pre-Prod or Prod

Please consider to have statistics collection turned on for the productive system and for the system the test is running on to have valuable results for the test scope identification and test scope coverage results.

378


2012

E2E200


Figure 311: Process Flow: CTS Analyses within an Implementation Project Test Preparation

The starting point of a CDMC CTS Analysis project is usually the point in time after the transport requests to be analyzed are imported into the QAS system. •

•

•

The “Determine Object Set” identifies the objects included in the transport requests belonging to the Customer Project. Also Modifications, Enhancements and referred objects can be determined. The “Test Scope Identification” identifies changes to reports and transactions which are already used in production and should be therefore included into the test plan. The “Environment Analysis” identifies import errors due to missing dependent objects, before the import of the transport requests has been done into production . Note: In this example it is assumed that the statistic system is different from the target system. This can be the case if a PRE production system is available. In a three system landscape typically the statistic and the target system are the same which is then the PRD system.

2012


379


E2E200

Figure 312: Process Flow: CTS Analyses within an Implementation Project Test Preparation

The “Test Coverage Analysis” identifies changed reports and transactions which have not been executed in the test system. The “Remote Comparison” identifies if all objects have the same versions in all systems at the end of a project after the Project was imported into production.

Figure 313: Launching the Cockpit in Solution Manager

380


2012

E2E200


Figure 314: Phases of a CTS Analysis Project

A CTS Analysis project consists of five phases: Global Settings, Project Settings, Collect, Analysis and Display. In the Global Settings the statistics collection is activated for the analysis and the target system The Project Settings phase includes two tasks: Defining the system landscape for the project (as described above) and determine the object set. In the Collect phase Modified Objects, Enhancements are determined on the Analysis System. Also all customer objects and SAP objects referred by the customer objects are collected. The Analysis phase consists of the following activities: • • • •

Test Scope Identification on the Analysis System. Perform Environment Analysis. Test Coverage Analysis. Remote Comparison of all objects AFTER the transport requests have been imported into the Target System.

After each activity of the Analysis phase you can look at the analysis results and decide how to proceed with the listed objects.

2012


381


E2E200

The Activate Statistics Collection activity is identical to the activation step in the Clearing Analysis. For details see slides of that chapter. Note: For CTS Analysis Statistic Collection must be activated on both systems: Analysis and Target System! Statistic collection is optional but gives more information on the usage statistics of the analyzed objects and is therefore recommended!

Figure 315: Creating a CDMC CTS Analysis Project

The following are the steps in the Project Setting phase in a CTS project:

382


2012

E2E200


Project Settings: •

Define Project Landscape: –

•

The user can define systems with A (analysis), C(control), Statistics(production) and T(target) roles under the project landscape. – The control system is the system in which the CTS project is created (SAP Solution Manager system) – The analysis system is the system in which the object set is determined. – The target system is the system in which the transport request will be transported. The activities Environment Analysis and Remote Comparison require the target system in the landscape. – Statistics systems is the production system and is required to be added to perform the activities Test Scope Identification. If the target system is same as the statistics system then you can define target as the statistics system. Determine Object Set: –

You can specify the list of transport requests from the analysis system whose underlying objects has to be analyzed.

Figure 316: Set up the RFC Destination

If the user wants to perform the usage analysis for the analyzed objects then he can add a statistics system in his landscape. The functionality of these two activities is similar to Import Statistics and Top Down Analysis in the Clearing Analysis and is optional. If the user does not want to do the usage analysis in CTS Analysis then he does not need to add the statistics system in the project landscape.

2012


383


E2E200

Although the Statistic System is optional it is highly recommended to be included to get information for defining the test scope or information for the environment analysis. Note: The Statistic System is normally the Prod System. In case the Target System is also the Prod System both RFC destination point to the same system!

Figure 317: Process Flow Step by Step: Step 1: Import Customer Project into QAS System

The starting point of a CDMC CTS Analysis project is usually the point in time after the transport requests to be analyzed are imported into the QAS system.

384


2012

E2E200


Figure 318: Process Flow Step by Step: Step 2: Determine Object Set

The “Determine Object Set” identifies the objects included in the transport requests belonging to the Customer Project. Also Modifications, Enhancements and referred objects can be determined.

Figure 319: Phases of a CTS Analysis Project: Collect Modifications, Enhancements and Referred SAP Objects

2012


385


E2E200

The activities in the Collect Phase of the CTS Analysis Project determine the Modifications, Enhancements and Referred SAP objects in the analyzed transport requests on the Analysis System (QAS). The following are the steps in the Collect phase in a CTS project: Collect Phase: •

Determine Modified SAP Objects: –

•

The modified objects are selected out of the original object set. The application components and the development class (package) details of the modified objects are also fetched. Determine Enhancements: –

•

The enhancements are selected out of the original object set. Objects such as Customer-Exits, BADIs, and BTEs are collected. The application components and the development class (package) details of the enhancement objects are also available. Customer and Ref SAP Objects: –

The customer objects which are part of the user specified request list is determined. In addition, the SAP objects which are referred by these objects are determined.

Figure 320: Process Flow Step by Step- Step 3: Test Scope Identification in the QAS System

386


2012

E2E200


Test Scope Identification: •

•

This activity is used to identify the customer objects that are used in statistic system to identify the scope of objects to consider for the upcoming test. The usage information is taken from the statistic system. For this the extraction of workload statistics has to be activated in the statistics system. The results of this activity can be viewed from the Display results activity and you can also create a piece-list from the results list for the list of used objects.

The “Test Scope Identification” identifies changes to reports and transactions which are already used in production and should be therefore included into the test plan. Note: In this example it is assumed that the statistic system is different from the target system. This can be the case if a PRE production system is available. In a three system landscape typically the statistic and the target system are the same which is then the PRD system.

Figure 321: Usage Analysis Technique (Test Scope Identification and Test Coverage)

Test Scope Identification and Test Coverage Analysis identify the objects of the analyzed projects which have been used (on the statistic system for Test Scope Identification, on the analysis system for Test Coverage Analysis). Therefore statistics are evaluated on these systems (used reports, transactions and tables due to ST03N and table access statistics).

2012


387


E2E200

Then several iterations are started to determine in a static way all objects which are used by these reports and transactions. This gives us a complete list of all used objects within the CTS project.

Figure 322: Phases of a CTS Analysis Project Analysis Phase: Test Scope Identification

In the activity: Test Scope Identification statistics of the Statistic System (PRD) is evaluated and the set of used objects of the initial set of objects is determined. This gives a minimum set of objects which should be included in a test plan on the Analysis System.

Figure 323: Phases of a CTS Analysis Project: Analysis Phase-Test Scope Identification: Display Results

388


2012

E2E200


You can display the results of activity Test Scope Identification immediately after the activity has been finished.

Figure 324: Phases of a CTS Analysis Project Analysis Phase: Test Scope Identification: Results Details

For Test Scope Identification ONLY the statistics of the statistic system are evaluated to determine a list of all used objects (via top down analysis). Nevertheless the extended list contains additional information and therefore a complete list of all executable objects which: 1. 2.

2012

Contain the mentioned object Was found in the statistics of all involved systems (analysis and statistic system)


389


E2E200

Examples: 1.

2.

Report ZW_CTS_REPORT_4LEVEL_FM_NEW1 uses FM Z_W_FM_CTS_LEVEl1. This report was found in the statistics of target system RWE: Therefore LIMU object REPS is marked as used here in Test Scope Identification. The FM is also marked as used as it was found with the top-down-analysis beginning with the report. Nevertheless the list contains also the additional information that the report was also found in the statistics of the Analysis System RWS. FM Z_W_CTS_FM1 is used in two reports on the target system RWE. Both reports have been found in the statistics there. The FM is marked as used as it was found via top down analysis from the reports. The reports are NOT marked as used as they do not belong to the analyzed project NEW1! This means that all reports and transaction are evaluated on the statistic system independent to which transport request/project they belong to: we want to get a full list of all objects which should be included in a testplan. Please note that report ZW_CTS_REPORT_ONLY_IN_TARGET_2 even does not exist in the analysis system at all which is also not relevant here!

Additional Information: 1.

2.

390

There might be also other reports/transaction which uses the FM but they are not found in the statistics and therefore are not of interest here. (You can use the Where-Used-List functionality to get a complete overview). The Information of the extended list does not mean that the executable object is directly using the object: It was just found via top down analysis (3 Iterations). To get the complete call hierarchy also use the Where-Used-List (see example of the Where-Used-List in the last part of this chapter)


2012

E2E200


Figure 325: Process Flow Step by Step: Step 4: Environment Analysis

Perform Environment Analysis: •

•

•

•

On execution of this activity, the objects referred within the initial object set are determined and remote comparison of the referred objects between the analysis and the target system is performed. You can view the additional information about the number of objects from the incoming requests, objects supported by environment analysis, objects referred by the incoming objects and the number of objects to be compared against the target system in the activity log. The result contains the list of referred objects not included in the original object set and a status for each object. The object status will be Only in Analysis System or Only in Target System or Different version or Same version. The status same version gets a green traffic light. You can create a piece-list in the analysis system or in the target system for different object selections based on the status.

The “Environment Analysis” identifies import errors due to missing dependent objects, before the import of the transport requests has been done into production .

2012


391


E2E200

Figure 326: Phases of a CTS Analysis Project: Analysis Phase- Perform Environment Analysis

In the activity: Environment Analysis object references are checked on the Analysis and the Target system BEFORE the transport requests are imported into the Target system. This ensures that all referred objects have the same versions on both systems and exist.

Figure 327: Environment Analysis

392


2012

E2E200


Following objects are analyzed: Objects which are referenced by objects which are included in the analyzed transport requests and are NOT themselves included in these transport requests. These objects can be critical as they might have different versions in both systems or do not exist at all on the target system.

Figure 328: Phases of a CTS Analysis Project- Perform Environment Analysis: Result List

After performing the Environment Analysis you can display the results. In the picture above we can identify several problems. Lets have a look at two examples: 1.

2.

The report ZW_CTS_REPORT_SAP_INCLUDE_3 is referring a SAP include SAP_CTS_INCLUDE_ONLY_NEW2. This include only exists in the analysis system but not on the target system (maybe was created by applying a SAP note). The include is in a transport request which belongs to the parallel project New2. So testing in QAS system was successful, but nevertheless will give error on PRD system if only project New1 goes live (risk of parallel projects with different going live dates) Function module Z_W_CTS_FM_LEVEL_4 is using a customer table ZWCTS_TAB_DEEP which has a different version in the target system. Also this might results into an error after importing project New1 (maybe an additional field was added)

All these conflicts must be solved as they might result into syntax problems later in the production system!

2012


393


E2E200

Figure 329: Phases of a CTS Analysis Project- Perform Environment Analysis: Result List after ALL projects have been imported into Production

This pictures shows the situation after all projects (New1 and New2) have also been imported into the Target System. Now the Environment Analysis (started in a new CDMC project!) does not show anymore errors.

Figure 330: Process Flow Step by Step- Step 6: Test Coverage Analysis

394


2012

E2E200


Test Coverage Analysis: •

This activity is used to verify which portions of objects have been tested on the analysis system. It is based on the statistic information of the objects coming from analysis system. For this the extraction of workload statistics has to be activated in the analysis system.

The “Test Coverage Analysis” identifies changed reports and transactions which have not been executed in the test system. Note: Prerequisites for this activity- Statistic Collection on the Analysis be activated before under global settings.

Figure 331: Phases of a CTS Analysis Project- Analysis Phase: Test Coverage Analysis

In the activity: Test Coverage Analysis statistics of the Analysis System (QAS) is evaluated to verify that all critical objects have been tested before they are imported into production. Recommendation: For the analysis time interval use the time spend for testing the new objects of the analyzed project.

2012


395


E2E200

Figure 332: Phases of a CTS Analysis Project Test Coverage Analysis: Result List (Detailed View)

After performing the activity Test Coverage Analysis you can display the results. With that activity you can verify if all objects of the test plan have been accessed. In the list of used objects you can identify objects which have already been used/touched on the Analysis System and therefore probably have been tested. Hint: To display the executable objects switch to detailed view. Then press extended list.

396


2012

E2E200


Figure 333: Process Flow Step by Step- Step 7: Import Customer Project into Target System

After finishing all tests the new project is imported into the target system. Now the two transport requests belonging to project 11 (New1) should be imported into production. But Request RWSK90041 was forgotten and only RWSK90039 was imported. This will lead to inconsistencies between the Analysis and the Target System. This problem is addressed by the final Remote Comparison in CDMC.

Figure 334: Process Flow Step by Step- Step 8: Remote Comparison, Object Version Compare

2012


397


E2E200

The “Remote Comparison” identifies if all objects have the same versions in all systems at the end of a project. Perform Remote Comparison (Impact Analysis): •

•

On execution of this activity, the objects under the requests are determined and the remote comparison is performed for these objects between the analysis and the target systems. The result contains the list of objects included in the original object set and a status for each object. The object status will be: Only in analysis system or Only in target system or Different version or Same version. The status Same version gets a green traffic light. All other status gets a red traffic light.

• Note: Note that to execute a CTS project the RFC user to the analysis system destination should be a Dialog user.

Figure 335: Remote Comparison

In this activity all new imported objects are compared between the Analysis and the Target System.

398


2012

E2E200


Figure 336: Phases of a CTS Analysis Project- Analysis Phase: Perform Remote Comparison

In the activity Remote Comparison all object are checked on the Analysis and the Target system AFTER the transport requests are imported into the Target system. This ensures that all referred objects have the same versions on both systems and exist.

Figure 337: Phases of a CTS Analysis Project Perform Remote Comparison: Result List Problem 1: Forgotten Transports

After performing the Remote Comparison Analysis you can display the results.

2012


399


E2E200

The result list still shows errors due to the fact that not all transport requests from the project have been imported yet.

Figure 338: Phases of a CTS Analysis Project Repeat activity Perform Remote Comparison

The final activity Remote Comparison Analysis can be repeated. After re-importing all requests belonging to the project, Remote Comparison is triggered again.

Figure 339: Phases of a CTS Analysis Project Perform Remote Comparison, Final Result List

400


2012

E2E200


After finishing the Remote Comparison again the picture shows the final result list. Now all objects have a green traffic light. The only exception here is an object which was deleted by the project and gives a red rating: This is here just an additional information that a complete object was deleted and does not mean an inconsistency here.

Working with the Result List

Figure 340: Display Results of CTS Analysis

2012


401


E2E200

In this activity, you can view an overview of the analysis results and decide how to proceed with the listed objects. •

To access the CTS result list, click the Display Results activity in the Display phase. –

–

You can view the result list by selecting the transport requests that you want to view. In this case choose the transport request that you want to view, and choose Copy. The system displays the result list. The result list screen contains of the following areas: –

•

Navigation Menu: The Navigation menu is represented by different folders (left hand side panel) – Result List: The Result List is the table in the main UI frame – Menu Bar: You use the menu bar (top of screen) to switch between the compressed and detailed views, and view results. The navigation menu contains three views: – – –

–

402

Object View: In the object view, you can select the objects by object type and then sort the objects that you want to analyze. Function View: In the function view, you can view the results of the analysis activities associated with a CTS project. Severity: In the severity view, you can view the objects that have a particular severity. For example, you can view all objects that have the severity Red. Processing Status: The processing status view allows you to view the status of the objects. For example, you can see all the objects which are only in analysis system or only in target system or the objects having different versions in the analysis and target system


2012

E2E200


Figure 341: Display Results of CTS Analysis- Example of results list (compressed view)

The following are the features that are available to analyze the objects •

•

•

2012

Where-Used List: This feature helps you to identify if other references exist for a particular object, and identify how many references exist. It can be case that the person responsible for an object is not aware of all possible references for that object. For example, consider a customer function module used by colleagues in their objects. The author of this object may not be aware of these references. You can do the where-used list for the object in the remote system. Remote Comparison: This feature allows the author of the program to compare the version of an object with the version of that object in another system. For example, you can compare the version of an object with the version in the target system to determine if the object versions are equal. If the two versions are different, you must examine any possible reasons for this. Remote comparison can be performed for only one object at a time. If you have selected multiple objects and want to do a remote comparison then an information message is displayed accordingly. Extended List: This option helps you to view all the executable objects which are associated to the non executable objects and is provided in the detailed view only, as you can see the usage indicator for all the objects under all the object views and function views only in the Detailed View.


403


E2E200

Figure 342: Display Results of CTS Analysis- Example of results list (Object View)

Figure 343: Display Results of CTS Analysis- Example of results list (Detailed Object View)

404


2012

E2E200


Information Source: • • • •

SAP Note 1244713 - Information about how to install the Custom Development Management cockpit SAP Note 1348772 - Information about all the corrections for a Support pack Each ST-PI has their own collective SAP note that has to be applied before starting with the analysis. Example: SAP Note 1584299 - Collective Note with all corrections for CDMC (ST-PI SP04) has to be installed on all involved systems after the ST-PI is on all system on SP04.

To get the full picture about usage of CDMC please visit the market place and subscribe to the CDMC Expert Guided Implementation Session (4 days) under: http://service.sap.com/esacademy. An SAP expert provides you with detailed knowledge for CDMC topics in the morning and you have the chance to apply the analysis on your own systems and to get Backoffice support in the afternoon were needed.

2012


405


406


E2E200

2012

E2E200

403


Exercise 13: CDMC Change and Transport System Analysis Exercise Duration: 25 Minutes

Exercise Objectives After completing this exercise, you will be able to: • Execute the activities for CTS Analysis in the Customer Development Management Cockpit (CDMC). • Analyze the results of the CTS Analysis in CDMC.

Business Example The activities of a CTS Analysis project in CDMC are executed at differences phases of an implementation project. Here in the exercise we will simulate these different steps. Business Scenario: A new implementation project is in the integration test phase. Transport requests belonging to the project have been imported into the Quality Assurance system. This is the starting point of the CTS Analysis in CDMC. As the test coordinator you should execute the first activity (Test Scope Identification) of a new CTS Analysis project to find out which customer objects should be included in a regression test plan. After this you are the development lead and execute the Environment Analysis activity to evaluate if all dependent objects are present in the Production system to avoid syntax problems when the project goes life. In the next phase you are again the test coordinator. This step (Test Coverage Analysis) will be executed after the integration test phase has been finished to verify that all requested objects had been tested. Optional you can perform as the development lead in the last activity a version compare of all objects after the project has been imported into the Production system (will be done by the trainer) between the QAS and PRD system.

Task 1: Create a new CTS Analysis project in CDMC and define the project landscape. In this example the system RWE is the target system (production system), Solution Manager RWS is the cockpit system and RWZ is the test system. We will use the statistics from the RWE system for the Test Scope Identification 1.

2012

Enter the Customer Development Cockpit in the Solution Manager system. Continued on next page


407


E2E200

What is the transaction code for CDMC? 2.

Verify that the statistic collection is activated for systems RWE and RWZ. Do not change anything here!

3.

Create a new CTS Analysis project. Use: Project Name: 900## (## : your group number) Description: CTS Analysis group ##

4.

5.

Define Project Landscape for your project. Use: RFC Destination:

System Role:

RWE_CDMC_STAT

S (must be inserted manually)

RWE_CDMC_TARGET

T

NONE

C

RWZ_CDMC_ANALYSIS

A

Read the documentation of this activity step for explanation of the different system roles

Task 2: Determine the object set of the implementation project. Now we start analyzing the implementation project (CTS project assignment: RWS_P00011) 1.

In your CTS Analysis Project execute the following activities (can be executed in parallel): Determine Object Set (in the selection box choose CTS project RWS_P00011). Hint: You have to click on the expand button to see further selection criteria: • • •

2.

Determine Modified Objects. Determine Enhancements. Customer and referenced SAP Objects.

Which transport requests and how many objects belong to this CTS project?


408


2012

E2E200


Task 3: Identify the objects which should be included into a test plan As the test coordinator you want to know which objects should be included into a regression test plan. Therefore we can evaluate the statistic information out of the production system. This gives information which transactions and reports of the object list to be analyzed are already in use in the production environment. Via a top down analysis we get a complete list of objects which are in use. 1.

In your CTS Analysis Project execute activity Test Scope Identification In the popup for the analysis interval change the Analysis start date to: 01.02.2012 In the next popup fill in RFC destination: RWE_CDMC_TARGET (pointing to our production system).

2.

Display the results of this activity. In the following popup select all transport requests. How many Reports can you identify which should be included into a regression test plan?

Task 4: Perform Environment Analysis and analyze the results As the development lead you perform the Environment Analysis in the CDMC CTS Analysis project to identify possible problems before they go live into production. The Environment Analysis identifies dependent objects of the objects in the analyzed project which are not included them self in this project (e,g, are contained in a parallel project). Therefore if only the main analyzed project is imported later into production, these dependent objects are missing or have a wrong version. 1.

In your CTS Analysis Project execute activity Perform Environment Analysis In the popup fill in RFC destination: RWE_CDMC_TARGET (pointing to our production system).

2.

Display the results of this activity. In the following popup select all transport requests. What is the problem with the report: ZW_CTS_REPORT_NEW1_REF_NEW2?

3.

What is the problem with the data element ZW_CTS_DATA_DEEP?

4.

Perform a remote comparison for this data element. In the popup put in RFC Destination: RWE_CDMC_TARGET.What is the result?


2012


409


E2E200

Task 5: Perform Test Coverage Analysis and display the results Now let us assume that the test phase has been finished. As the test coordinator you want to know if objects which should have been tested were really tested. Therefore we can evaluate the statistic information out of the analysis system. This gives information which transactions and reports of the object list to be analyzed have been touched on the test. Of course the system cannot check if tests were really executed as intended: we just get the information that these objects obviously have been executed. 1.

In your CTS Analysis Project execute activity Test Coverage Analysis In the popup for the analysis interval change the Analysis start date to: 01.02.2012.

2.

Display the results of this activity. In the following popup select all transport requests.

3.

Where all 4 critical programs which have been identified in the Test Scope Identification activity really tested?

4.

Was the critical report ZW_CTS_REPORT_NEW1_REF_NEW2 from the Environment Analysis tested?

Task 6: (Optional): Perform Remote Comparison after import into production (demonstrated by the trainer). Now the go-life phase was entered and the transport requests have been imported into production (will be done by the trainer). Now we can perform the final activity to check if all objects of the analyzed project are really imported and if they have the same versions as in the test system.

410

1.

In your CTS Analysis Project execute activity Perform Remote Comparison In the popup fill in RFC destination: RWE_CDMC_TARGET (pointing to our production system).

2.

Display the results. Do all objects have the same versions?

3.

Can you be sure that all objects work like tested in the test system now?

4.

Name two reasons why the Remote Comparison activity might show differences in the versions of the analyzed objects:


2012

E2E200


Solution 13: CDMC Change and Transport System Analysis Task 1: Create a new CTS Analysis project in CDMC and define the project landscape. In this example the system RWE is the target system (production system), Solution Manager RWS is the cockpit system and RWZ is the test system. We will use the statistics from the RWE system for the Test Scope Identification 1.

Enter the Customer Development Cockpit in the Solution Manager system. What is the transaction code for CDMC? a)

Answer: CNV_CDMC Alternative you can use the related link: Custom Development Management Cockpit in the Implementation/Upgrade Workcenter

2.

Verify that the statistic collection is activated for systems RWE and RWZ. Do not change anything here! a)

3.

Goto: Global Settings → Activate Statistic Collection. The RFC destinations RWE_CDMC_STAT and RWZ_CDMC_STAT are pointing to the systems RWE and RWZ. Make sure that the active flag is set.

Create a new CTS Analysis project. Use: Project Name: 900## (## : your group number) Description: CTS Analysis group ## a)

4.

In the CDMC mark the Analysis: Change and Transport System Analysis Project. Then click on the Create button.

Define Project Landscape for your project. Use:


2012


411


5.

E2E200

RFC Destination:

System Role:

RWE_CDMC_STAT

S (must be inserted manually)

RWE_CDMC_TARGET

T

NONE

C

RWZ_CDMC_ANALYSIS

A

a)

In the CDMC overview open the folder: Change and Transport System Analysis. Click on the Execute button near your new created project.

b)

Under Project Settings click on the Execute button for: Define Project Landscape.

Read the documentation of this activity step for explanation of the different system roles a)

The user documentation for every activity is on the left side next to the Execute button. Click on the button for the documentation of activity: Define Project Landscape.

Task 2: Determine the object set of the implementation project. Now we start analyzing the implementation project (CTS project assignment: RWS_P00011) 1.

In your CTS Analysis Project execute the following activities (can be executed in parallel):


412


2012

E2E200


Determine Object Set (in the selection box choose CTS project RWS_P00011). Hint: You have to click on the expand button to see further selection criteria: • • • a)

Determine Modified Objects. Determine Enhancements. Customer and referenced SAP Objects.

Click on the Execute button for activity: Determine Object Set. On the following popup click on the Expand button to display more options. Scroll to the button and insert the CTS project ID RWS_P00011 manually under Request Attributes. Note: The F4-help cannot be used here as the project itself does not exist on the Test System

b) 2.

Execute the other three activities by clicking on the Execute button.

Which transport requests and how many objects belong to this CTS project? a)

Answer: RWSK940039 and RWSK940041 with 54 objects altogether After the activities have been finished click on the Activity Log button for activity: Determine Object Set. The log will display the necessary information.

Task 3: Identify the objects which should be included into a test plan As the test coordinator you want to know which objects should be included into a regression test plan. Therefore we can evaluate the statistic information out of the production system. This gives information which transactions and reports of the object list to be analyzed are already in use in the production environment. Via a top down analysis we get a complete list of objects which are in use. 1.

In your CTS Analysis Project execute activity Test Scope Identification In the popup for the analysis interval change the Analysis start date to: 01.02.2012 In the next popup fill in RFC destination: RWE_CDMC_TARGET (pointing to our production system). a) Continued on next page

2012


413


2.

E2E200

Display the results of this activity. In the following popup select all transport requests. How many Reports can you identify which should be included into a regression test plan? a)

Answer: 4 In the Result List choose: Function View → Test Scope Identification – Used objects. You find two objects of type R3TR PROG and two objects of type LIMU REPS as used. Both are relevant here: The LIMU REPS object is the report source of a program. Used means that the program of this report source was found as used in the statistic System. A transport request can contain both: The complete program including report source and text elements or just sub objects if this was changed.

Task 4: Perform Environment Analysis and analyze the results As the development lead you perform the Environment Analysis in the CDMC CTS Analysis project to identify possible problems before they go live into production. The Environment Analysis identifies dependent objects of the objects in the analyzed project which are not included them self in this project (e,g, are contained in a parallel project). Therefore if only the main analyzed project is imported later into production, these dependent objects are missing or have a wrong version. 1.

In your CTS Analysis Project execute activity Perform Environment Analysis In the popup fill in RFC destination: RWE_CDMC_TARGET (pointing to our production system). a)

2.

Display the results of this activity. In the following popup select all transport requests. What is the problem with the report: ZW_CTS_REPORT_NEW1_REF_NEW2? a)

Answer: the report is using two function modules and a table which would be not present in the production system and therefore results into syntax errors. In the Result List choose: Function View -> Environment Analysis results

3.

What is the problem with the data element ZW_CTS_DATA_DEEP? a)

Answer: it uses domain ZW_CTS_DOM_DEEP which has a different version in the target system.


414


2012

E2E200


4.

Perform a remote comparison for this data element. In the popup put in RFC Destination: RWE_CDMC_TARGET.What is the result? a)

Answer: The number of fields are different in both systems.

b)

For the Remote Comparison mark the line with the object name ZW_CTS_DATA_DEEP, then click on: Remote Comparison In the result list you can see the differences in both systems in different yellow colors.

Task 5: Perform Test Coverage Analysis and display the results Now let us assume that the test phase has been finished. As the test coordinator you want to know if objects which should have been tested were really tested. Therefore we can evaluate the statistic information out of the analysis system. This gives information which transactions and reports of the object list to be analyzed have been touched on the test. Of course the system cannot check if tests were really executed as intended: we just get the information that these objects obviously have been executed. 1.

In your CTS Analysis Project execute activity Test Coverage Analysis In the popup for the analysis interval change the Analysis start date to: 01.02.2012. a)

2.

Display the results of this activity. In the following popup select all transport requests. a)

3.

In the Result List choose: Function View → Test Coverage Analysis – Used Objects. Compare the list with result list of the Test Scope Identification and the Environment Analysis activities.

Where all 4 critical programs which have been identified in the Test Scope Identification activity really tested? a)

Answer: No. Only three of these reports were tested. (ZW_CTS_REPORT_SAP_INCLUDE_3 was not tested) .

4.

Was the critical report ZW_CTS_REPORT_NEW1_REF_NEW2 from the Environment Analysis tested? a)

Answer: yes


2012


415


E2E200

Task 6: (Optional): Perform Remote Comparison after import into production (demonstrated by the trainer). Now the go-life phase was entered and the transport requests have been imported into production (will be done by the trainer). Now we can perform the final activity to check if all objects of the analyzed project are really imported and if they have the same versions as in the test system. 1.

In your CTS Analysis Project execute activity Perform Remote Comparison In the popup fill in RFC destination: RWE_CDMC_TARGET (pointing to our production system). a)

2.

Display the results. Do all objects have the same versions? a)

Answer: Yes. (the only exception is an object which does not exist in both systems. This has only information character and can be ignored. In the Result List choose: Function View → Remote Comparison results. The column: Comparison Status shows that all objects now have the same version.

3.

Can you be sure that all objects work like tested in the test system now? a)

4.

Answer: No! in our case the second parallel project is still missing (see results of the Environment Analysis). Therefore a lot of objects now would run into syntax problems! The conflicts of the Environment Analysis must be solved before the project is imported into production!

Name two reasons why the Remote Comparison activity might show differences in the versions of the analyzed objects: a)

Possible reasons: 1. 2.

416

Not all transport requests of the analyzed projects were imported (forgotten transport requests). Another project might contain also some of the objects. Both projects were imported in a different sequence in both systems (overtakers).


2012

E2E200


Lesson Summary You should now be able to: • Know the prerequisites to use CDMC CTS. • Understand in which situation the CDMC CTS analysis could be used. • Execute the activities for CDMC CTS Analysis in the custom Development Management Cockpit (CDMC). • Analyze the results of the CDMC Analysis.

2012


417


Lesson: 414

E2E200

Guided Self-Services/ Transport Execution Analysis Lesson Duration: 35 Minutes

Lesson Overview This lesson introduces the guided self service procedure to you. The Transport Execution Analysis (TEA) self service helps to analyze the transport processes and provides recommendations on how to improve quality and reliability of these processes.


Explain the value and the content of the Transport Execution Analysis service. Know the prerequisites, which must be fulfilled before service delivery can start. Judge in which situation the service delivery makes sense. Understand the main KPIs, which are used to measure the quality of software change management.

Business Example You are responsible for the change management of your ERP system landscape and you wish to collect information about the quality of the software change management within this landscape.

418


2012

E2E200

Lesson: Guided Self-Services/ Transport Execution Analysis

Introduction into the Transport Execution Analysis Self Service

Figure 344: Guided Self Services- Overview

If you are an SAP Enterprise Support customer, you benefit from various SAP deliverables. SAP supports you with a wide range of services, like • • • •

Root cause analysis, which is essential in a production down situation, for example The holistic 360 Review Enterprise Support reports, individually adapted to your system landscape Continuous quality checks to optimize your business and many more useful service offerings

Furthermore, SAP also provides proven methods you can utilize for different areas such as • •

Business Processes Infrastructure

Finally, SAP provides you with the chance to empower yourself via the Enterprise Support Academy. In this context, you’ll also find detailed information about Guided Self Services, which is the focus of this chapter.

2012


419


E2E200

Guided self services are wizard based services that are executed by the customers themselves. They are: • • • •

Easy to Use No configuration needed No impact on the managed systems Can be used repetitively

With access to Guided Self Services, SAP provides: •

... a flexible management infrastructure for unlimited usage –

•

every Enterprise Support customer can run these services when and how often they want

– Customized to the customers individual situation ... SAP Intellectual Property (IP) to the customers IT organization according to SAP’s standards and best practices –

•

this IP is derived from and based on the experience of a multitude of service deliveries gained from thousands of SAP systems around the globe ... the latest available information on IT operations –

–

SAP regularly provides new patterns through content updates that can easily be retrieved via SAP Solution Manager and implemented without any Support Package change the customer can therefore benefit from new innovations over time and independent of new releases

Figure 345: Guided Self Services Service Portfolio in 2011

420


2012

E2E200


Figure 346: SAP Transport Execution Analysis

When should the Transport Execution Analysis be used? •

There are problems with software change management: –

•

Many errors occur in production (many dumps, import errors, OSS messages, etc) – Test systems behave different from production system, errors cannot be reproduced. Software change management is a focus topic – –

•

A change management tool shall be introduced (e.g. ChaRM) The measurement platform is used to measure Emergency Changes and Failed Changes – An assessment and benchmarking of the software change management processes against SAP Best Practices shall be done, in order to identify areas for improvement Problems are reported in the Early Watch Alert or in the Enterprise Support Report

At the end of the analysis you can generate a final report that includes detailed descriptions of the analysis results, the recommendations, and an action plan. The content of this report is dependent on the analysis results and can be adapted according to the individual situation.

2012


421


E2E200

Figure 347: Create a new Guided Self Service in the Solution Manager Work center

You will find the guided self services in the SAP Engagement and Service Delivery work center (transaction sm_workcenter). After choosing your solution you could start the service session. (System Demo)

422


2012

E2E200


Service Topic Details

Figure 348: Transport Statistics

Transport requests are evaluated regarding the time of import during the last 6 month. You could easily find out whether they are imported continuously into production or whether long term release cycles are used.

Figure 349: Emergency Changes

2012


423


E2E200

Here we will check for the time that transport requests spend until they are imported into the production system. mandatory testing procedures should be in place also for urgent changes. Only changes that are tested sufficiently should be imported into production.

Figure 350: Failed Changes

For this check the ratio between failed changes and workbench objects transported into Production in last six month will be measured.

424


2012

E2E200


Figure 351: Transport Backlog

The check shows e.g. the number of released transport requests that are not yet imported into production.

Figure 352: Software Maintenance

This check evaluates the level of compliance of the support packages and SAP notes according to SAP best practices and gives valuable recommendations regarding differences within your landscape.

2012


425


E2E200

Figure 353: Data Collection and Process Flow

Which technical requirements have to be fulfilled? An improved Wizard-based user interface is available as of SAP Solution Manager 7.1 Central preparation note: SAP Note 1074808 Requirements in managed systems: ST-PI 2008.1, SP4 and ST-A/PI 01N, SP1 is installed in the managed systems Requirements in SAP Solution Manager: as of ST-SER 2010.1 (SPS23) with latest content update

426


2012

E2E200


Figure 354: Empowering Customers Through Access to Guided Self Services

• • • • •

Expert Guided Implementation is a methodology that offers a balance of training, practical experience, and expertise on demand. An SAP expert provides you with detailed knowledge for specific topics – based on SAP Best Practices. Effective knowledge transfer through practical execution in your own system environment. Direct access to SAP experts for individual dialog plus Q&A. EGIs are available for all Guided Self Services.

In the morning there is always an empowering session held by an SAP expert, who explains the content of the session. In the afternoon you practice the same actions on your own SAP Solution Manager software. In case of issues or questions, you can contact the SAP expert directly by e-mail or phone.

2012


427


E2E200

Figure 355: Subscribing to an EGI

To benefit most from the EGI training, it is important that you ask yourself , before you register for the EGI , questions like: • • • • •

Which service is of interest to me? Who should execute the Guided Self Service? Which systems should be analyzed? Who will be responsible for the implementation? Who will be responsible for and who will execute the follow-up services?

Then you can register for an Expert Guided Implementation session. Within SAP Service Marketplace, you can choose the EGI for the related Guided Self Service and the calendar week via the Enterprise Support Academy link.

428


2012

E2E200


Lesson Summary You should now be able to: • Explain the value and the content of the Transport Execution Analysis service. • Know the prerequisites, which must be fulfilled before service delivery can start. • Judge in which situation the service delivery makes sense. • Understand the main KPIs, which are used to measure the quality of software change management.

2012


429

Unit Summary

E2E200

Unit Summary You should now be able to: • Understand the basis architecture of E2E Change Diagnostics. • Find current configuration information with Change Reporting. • Explain how to find out recent changes in the solution landscape with E2E Change Analysis. • Know how to compare multiple systems with Configuration Validation. • Understand the usage of target systems. • Know how to use the report directory. • Understand the risks of Import Single Strategy. • Understand the risks of Inconsistencies in the Transport Landscape. • Understand the basic idea and benefits of Release Management. • Explain the system and clients roles in advanced system landscapes. • Give some examples of advanced system landscapes based on specific customer requirements. • Explain, which tools can be used to manage transport dependencies. • Know the prerequisites to use CDMC CTS. • Understand in which situation the CDMC CTS analysis could be used. • Execute the activities for CDMC CTS Analysis in the custom Development Management Cockpit (CDMC). • Analyze the results of the CDMC Analysis. • Explain the value and the content of the Transport Execution Analysis service. • Know the prerequisites, which must be fulfilled before service delivery can start. • Judge in which situation the service delivery makes sense. • Understand the main KPIs, which are used to measure the quality of software change management.

430


2012

Unit 6 Transport Management with SAP Solution Manager

427

Unit Overview This unit deepens the knowledge about the deployment capabilities when working with Transport Management with SAP Solution Manager to best manage the risks associated with the implementation of changes. Ensuring technical and functional robustness will be gained by using SAP’s Best Practices for transport management. These best practices are explained in details within this unit.

Unit Objectives After completing this unit, you will be able to: • • • • • • • • • •

2012

Understand the best practices for Transport Management. Give an overview of the capabilities available in SAP Solution Manager for central transport management Explain the basics of Change Request Management configuration. Explain, how to prepare the infrastructure for the use of the Change Request Management. Explain how to manage your transports with a central transport infrastructure of SAP Solution Manager. Use the Task List for central transport management in SAP Solution Manager. Create, release and import transport requests in a managed target system using the task list. Define and activate Critical Transport Objects. Explain the approval process for Critical Transport Objects. Activate the Cross System Object Lock.


431


• • • • • •

E2E200

Explain the best practices to use the Cross System Object Lock in complex system landscapes. Explain the Dual Landscape Synchronization with Retrofit functionality of SAP Solution Manager. Know new features of Retrofit in SAP Solution Manager 7.1. Explain, how to perform Retrofit. Understand how to use Transport of Copies (ToC). Usage of Transport of Copy within your maintenance and implementation projects.

Unit Contents Lesson: Lesson: Lesson: Lesson: Lesson: Lesson: Lesson:

432

Introduction ............................................................433 Infrastructure for Change Control Tools ...........................438 Task List ...............................................................453 Critical Object .........................................................462 Cross System Object Lock ..........................................466 Retrofit .................................................................471 Transport of Copy ....................................................480


2012

E2E200

Lesson: 429


Introduction Lesson Duration: 15 Minutes

Lesson Overview This lesson will give you an overview about the main features and functions of the Transport Management with SAP Solution Manager.


Understand the best practices for Transport Management. Give an overview of the capabilities available in SAP Solution Manager for central transport management

Business Example Process and control software changes with SAP Solution Manager in your SAP system landscape without changing the change request workflow within your business department.

2012


433


E2E200

Transport Management with SAP Solution ManagerIntroduction

Figure 356: Change Control Management: Transport Management with SAP Solution Manager

The Scope of transport management with SAP Solution Manager is to establish one tool to manage and control transports and transport-related activities via phases of your project in SAP Solution Manager.

434


2012

E2E200


Figure 357: Transport Management with SAP Solution Manager - SAP Transport Best Practices

Using transport management with SAP Solution Manager you can control transports centrally via SAP Solution Manager by using SAP’s Best Practices for Transport Management. The following areas are addressed: CTS+ The enhanced Change and Transport System (CTS+) enables you to transport Java objects and SAP-related non-ABAP objects in your system landscape, alongside ABAP objects. You can also administer non-ABAP systems in a CTS transport domain in SAP NetWeaver Application Server ABAP. Transport of Copy If you want to test your software changes in one system without having them transported automatically to other systems in your transport track, you can trigger Transports of Copies. Such transports of copies are not transported across your system landscape but only into the next system and are therefore not imported into your production system. It makes them suitable for testing purposes. Reporting The change tracking function tracks changes in an SAP Solution Manager or IMG project. You can track transport requests from the system in which they are created, to the systems into which they are imported. All transport requests that belong to a project can be tracked across all the systems in the project landscape. You can go to the transport logs, the import queue, the transport request or task list, the SAP Solution Manager project, the satellite IMG project, or the CTS project.

2012


435


E2E200

Critical Objects A user attempted to export a transport request containing critical objects, but the export was terminated. You either have to remove the critical objects from the transport request, or explicitly approve transport of the critical objects. Cross System Object Lock The Cross System Object Lock ensures that when an object is changed in a managed system, it is locked in the central SAP Solution Manager system. Depending on the conflict scenario, this prevents changes being made to this object in any other transport request. Retrofit In system landscapes in which multiple releases are used, changes can be made in different development systems: This allows new developments to be made in the development system, and errors to be corrected or improvements to be made in a maintenance system for the production system landscape at the same time. The system release levels must be adjusted regularly. Since changes are made in parallel, changes cannot be transported between systems in transport requests, because current software versions may be overwritten and inconsistencies can occur. To avoid this, you can perform a controlled import into the target system. This is called retrofitting.

436


2012

E2E200


Lesson Summary You should now be able to: • Understand the best practices for Transport Management. • Give an overview of the capabilities available in SAP Solution Manager for central transport management

2012


437


Lesson: 433

E2E200

Infrastructure for Change Control Tools Lesson Duration: 15 Minutes

Lesson Overview This lesson will give you an overview about the Infrastructure for Change Control Tools with SAP Solution Manager.


Explain the basics of Change Request Management configuration. Explain, how to prepare the infrastructure for the use of the Change Request Management.

Business Example Process and control software changes with SAP Solution Manager along your whole SAP system transport landscape.

438


2012

E2E200

Lesson: Infrastructure for Change Control Tools

Infrastructure for Change Control Tools

Figure 358: Configuration of Change Request Management - Transport Management System

The Transport Management System (TMS) organizes, monitors and performs transports for all SAP systems within a system landscape. In addition, TMS is used to configure and manage the setting up of SAP systems and transport routes within a system landscape. Transport Management with SAP Solution Manager Transport Management System configuration must be performed at the managed systems. These configuration include the Activation of Trusted Services, Definition of transport routes, Transport Strategy, and the Activation of Extended Transport Control. Extended Transport Control The existence of this option depends on the tp parameter CTC (client dependent transport routes). Transport Routes Transport routes indicate the role of each system and the flow of transport requests.

2012


439


E2E200

A consolidation route is an export/import route. Typically, the consolidation route proceeds from the development system to the quality assurance system in a three-system landscape. Consolidation routes have names in order to be addressed. A delivery route is an another import route, In a three-system landscape, the delivery route is specified between the quality assurance system and the production system because there is no additional export from quality assurance system but another import in the production system. Delivery routes have no names. Transport Strategy The transport strategy is based on predefined transport routes. There are three different transport strategies available: • • •

Queue-controlled mass transports Queue-controlled single transports Workflow-controlled transports

For Change Request Management the queue-controlled single transport strategy is required. Trusted Services Trusted Services suppress the logon procedures in the target systems, after you have successfully logged on to a client in one of the systems in the transport domain. All other authorization checks in the TMS are then made on the user name that you used to start the TMS in the source system. This means that the identity of the user is not checked every time you use TMS to access a system, only when the user first logs on to a client in the transport domain. The only check made in the target system is to see whether the user has the correct authorization for the particular action (such as importing a transport request). TMS Trusted Services must only be used if the user names are the same in all clients in all SAP Systems in the transport domain.

440


2012

E2E200


Figure 359: Configuration of Change Request Management Projects

The Solution Manager project is represented as an IMG project in each satellite system and a CTS project in each satellite system client. A logical system is an application system in which the applications work together on a common data basis. In SAP terms, the logical system is a client. For each Solution Manager project, a project cycle is generated, which is represented by a task-list for managing the technical administration, and a cycle transaction for managing the organizational administration of the project cycle. The project assignment of each transport request is mandatory.

2012


441


E2E200

Figure 360: Configuration of Change Request Management- Solution Manager Projects

When a project cycle is being generated, all logical components are taken into account that belong to the project as well as the transport routes of all systems. Logical components incorporate logical systems that have the following system role types: • • • • •

Source System (development systems and starting systems) Target System (any system between the development and production systems) Production System (production systems and ending systems) Single System (evaluation systems without connection to a transport route) Post-Processing System (retrofit systems)

Tracks are being generated for each development system that matches to a system of role type Source System in the logical component and as a source of a consolidation route in TMS. Each track is represented by one CTS project. Projects of type maintenance are represented by transaction type SMMN. Projects of type implementation, upgrade and template are represented by transaction type SMDV.

442


2012

E2E200


Figure 361: Solution Manager Project is Enhanced by the Project Cycle

SAP Solution Manager projects can be extended by adding project cycles. Each project cycle is controlled by its phases. Project phases are static and linked to each cycle. Each project cycle phase offers certain functions, which differ according to the project type. Project cycles control the following things: • •

Whether or not transports are created, exported, or imported Incorporation of all logical systems that belong to a project

Project cycles can be closed after the Go live phase, or reset to one of the In Development phases. Note: The Preparation for Go Live phase is not intended for urgent corrections, but is rather a preparation phase for going live.

2012


443


E2E200

Figure 362: Configuration of Change Request Management IMG Project

Transport Management with SAP Solution Manager uses the CTS project status switches in order to lock exports and imports in the connected system. The task list tasks will open and close the status switch inherently when performing create, release, or import transports. Project assignment should be set to mandatory since only project import is being supported next to import subset for urgent changes. In the Workbench Organizer only “release task” can be performed.

Figure 363: Configuration of Change Request Management- Logical Systems and Logical Components

444


2012

E2E200


A logical component is an administrative entity which assigns logical systems, in the entire system landscape and across projects, to the following: • •

a main instance of a product with a product version, e.g. the main instance ERP Server of the product SAP ERP with the product version 6.0. the system roles or phases in a project, e.g. the system role development system for the configuration.

A logical component contains systems of the same product which belong together in terms of use / TMS. A logical system is a group of multiple clients with the same product and release. The logical system builds the frame for the transport in this landscape. Change Request Management requires at least a Development (D) and a Production (P) System. Everything between is classified as Target System (O).

Figure 364: Configuration of Change Request Management- System Role

Available system roles: • • • • •

D – Source System O – Target System P – Production System R – Post-Processing System (Retrofit) S – Single System

Define System Roles

2012


445


E2E200

You can define 10 user system roles in addition to the existing system roles. The system flags SAP and user system roles with icons. Define/Change System Roles Choose Utilities → System Settings → System Roles tab, to change user-defined system roles or define new system roles. You can change system role types or their sequence for the SAP Change Manager, e.g. as subsequent system in a transport path. The new/changed system roles are displayed in the Project Administration → System Landscape tab → Systems tab, and in all role selection possible entries help in the Solution Manager, except: The unchanged system roles from the client definition are displayed in the role selection possible entries help for ABAP-based main instances in the Clients tab in the Solution Manager System Landscape. Delete system roles If your user-defined system roles are used in your system landscape, you can change their names, but not delete them. You can neither change nor delete SAP system roles. Transport System Roles You can transport system roles with the Transport pushbutton.

Figure 365: Configuration of Change Request Management- Create Logical Component

Create Logical Components

446


2012

E2E200


You use logical components: • • •

In the project for Business Blueprint, Configuration, Testing, Customizing Distribution During operation of your solution in Monitoring for systems and business processes In Change Request Management

Prerequisites • •

You have assigned the systems to products which you want to use in logical components. You have flagged one main instance per system as relevant. You can only then use this system in a logical component.

Procedure for Creating Logical Components SAP delivers some predefined logical components. To create a new logical component in transaction SMSY: 1. 2. 3. 4.

Choose System Groups and Logical Components → Logical Components → , in the overview tree. Choose Create New Logical Component from the context menu. Enter the required data. Choose a product. You can create a new product in the Create Logical Components screen.

5. 6.

Choose a product version. Choose a main instance.

Read the online help to display all product versions/main instances. Choose a main instance. Save the changes.

2012


447


E2E200

Figure 366: Configuration of Change Request Management - Assign Logical Component to Solution Manager Project

Create a Solution Manager project You want to make changes in systems as part of your planned maintenance period, and import all these changes simultaneously into production systems at the end of the maintenance period. For this purpose, you want to create a maintenance cycle. A maintenance cycle is the period in time in which you: • • •

Make changes in maintenance systems Include these changes in new transport requests Import these requests into follow-on systems for testing

At the end of a maintenance cycle, all transport requests are imported into the production system at the same time. Subsequently, the maintenance cycle can be closed manually and a new one can be created, if necessary. A maintenance cycle and the tasks that have to be executed as part of the cycle are contained in a task list of the Schedule Manager. This task list is generated automatically when you create a maintenance cycle. -> Go to transaction SOLAR_PROJECT_ADMIN. Choose Project -> Create from the menu or the button Create Project (F5). The system should display the Create Project pop-up. Provide a name for your project. Choose the project type Maintenance Project. Maintain the mandatory fields on tab “General Data”: Maintain the system landscape on tab System Landscape -> Systems. Choose the logical component you created as simulation landscape. Open the value help for the logical components and go to the logical components for SAP SOLUTION MANAGER. Mark your logical component and confirm your selection. Save the project.

448


2012

E2E200


If a pop-up Enhancement for Documents appears choose continue.

Figure 367: Configuration of Change Request Management- Create IMG Project

When you generate the IMG projects, you distribute the following central project data into the component systems: •

Project standards:

• •

– Status values which do not yet exist in the component system – Keywords Project Team Members Country selection

Prerequisite You have assigned logical components to the project in the System Landscape tab. You now see the associated IMG projects, in the IMG Projects tab, i.e. all subprojects in the component systems which belong to your Solution Manager project. Procedure Generate IMG projects in the component systems

2012


449


E2E200

The green and red traffic lights indicate whether Project IMGs have already been generated and distributed. • •

Red (dot): Project does not yet exist Green (square): Project exists in the specified logical components and the assigned logical systems.

To generate and distribute a project: 1. 2. 3.

Choose the Logical Component for IMG Projects. Select the IMG project and choose Create IMG Project. You can create a transport request for the project in the following dialog box, if necessary. You can assign additional project team members to the transport request. The generation and distribution is started in the managed development systems. When the Project IMGs are generated in the development systems, everything is initially set in scope. As soon as the project exists, the green traffic light symbol appears. You also get a system message as soon as generation is finished.

4.

To go to the project IMG later and regenerate, select the subproject and Change.

You go to the header data of the project. Assign existing IMG project To assign another IMG project from the managed development, instead of the default IMG project: 1. 2. 3. 4. 5. 6.

Select an IMG project. Choose Replace. Confirm the confirmation prompt. Choose an IMG project from the list, and confirm the selection. You can create a transport request in the subsequent dialog box. You can assign tasks in this request to other project team members. Choose Continue to save your entries.

The newly assigned IMG project appears on the IMG Projects tab.

450


2012

E2E200


Figure 368: Configuration of Change Request Management- Activate Change Request Management

Navigate to the Project → tab Change Management. In the Change Request Management area you can activate the Change Request Management. Afterwards you can create the task list.

2012


451


E2E200

Lesson Summary You should now be able to: • Explain the basics of Change Request Management configuration. • Explain, how to prepare the infrastructure for the use of the Change Request Management.

452


2012

E2E200

Lesson: 447

Lesson: Task List

Task List Lesson Duration: 20 Minutes

Lesson Overview This lesson will give you an overview about the task list functionality with SAP Solution Manager.


Explain how to manage your transports with a central transport infrastructure of SAP Solution Manager. Use the Task List for central transport management in SAP Solution Manager. Create, release and import transport requests in a managed target system using the task list.

Business Example Carry out software changes with SAP Solution Manager along your whole SAP system transport landscape using SAP Solution Manager capabilities.

2012


453


E2E200

Task List

Figure 369: ChaRM over the Task list- Representatives of the Project Cycle

The project cycle is an abstraction layer, representing the fixed phase structure of a cycle that cannot be changed. The cycle task list represents the system landscape tracks and the tasks to be used by an IT administrator for managing project-related IT activities, especially imports. Custom task list templates with additional tasks can be created by customers. The cycle transaction represents the service request for managing the phase changes. Documentation, additional status, notification, electronic signatures, etc. can be managed from within the cycle transaction. Phase shifts should be done from within the cycle transaction but not from within the cycle task list, since additional activities and status can only be managed from within the service request. The project cycle has two representatives which can be seen in the system: The cycle transaction and the cycle task list.

454


2012

E2E200

Lesson: Task List

Figure 370: Transport Management with SAP Solution Manager - Task list: Manage your transports with a Central Transport Management Infrastructure

Manage your landscape and all transport activities via SAP Solution Manager The task list is the interface to the Change and Transport System in the satellite systems. You can create, release and import transport requests from there. From the task list you can: • • • •

2012

Create, Release and Import Transport Requests Access to all systems of project landscape (also multiple tracks are supported, such as SAP ERP, SAP Portal and SAP BW) Synchronize your transport activities Manage the phases of your project.


455


E2E200

Figure 371: Task List - Overview

TheTask Lists describe all activities which can be processed for a specific project. The task list is the interface to the Change and Transport System in the managed systems. You can create, release and import transport requests from there. The task list is normally used in the background by the CRM transactions (see chapter Change Request Management). Only the import of a project is to be done directly in the task list. Task-lists are based on project landscape role types: • • • • •

Source System Target System Production System Single System Post-Processing System

When a project landscape changes, the systems have to be deleted/inserted correctly by an administrator.

456


2012

E2E200

Lesson: Task List

Figure 372: Task List- General Tasks

The tasks inside the General Tasks folder are used for general maintenance tasks. The contained tasks refer to the overall project. Apart from the tasks, also the task groups and the task list have a status. Task groups are either locked or unlocked. The tasks initially have the same status as the task group to which they belong. Tasks can only be executed if the status of all task groups higher in the hierarchy is Unlocked. The status of the entire task list, which is the highest node in the task list display, can be Initial, Locked, Active, or Completed. Tasks that belong to a task list can only be executed if the task list is active. If the status of the task list is Completed, it can no longer be changed or activated, tasks in this task list can no longer be executed.

2012


457


E2E200

Figure 373: Task List - Project Track

The Project Track depends on the Logical Component which is assigned to the Solution Manager project. The single tasks are specific for a certain system. The project track can be locked or unlocked for activities about the task list status.

Figure 374: Task List- Log Monitor

458


2012

E2E200

Lesson: Task List

As soon as a task has been executed, its status is changed to the status of the (last) execution. If, for example, you start a task that returns the status Contains Errors, you then see this status in the daily overview, in the monitor, and in the task list. If, subsequently, you start the task again, but the task returns the status Warning, you see this status for the newly scheduled items in the daily overview, in the monitor, and in the task list. The former Contains Errors status in the task list has now changed to Warning, while the status of the previous execution remains unchanged in the daily overview and in the monitor.

Figure 375: Task List- Cycle Phase

Cycle Transaction The maintenance cycle has its own cycle transaction. In the cycle transaction you can switch the project phase. In the task list of the cycle transaction you can start the import of the project buffer. This triggers an Import Project All. Task List A structured group of tasks, which are executed periodically, and possibly by more than one user to complete a certain process, such as, period-end closing. The task list is displayed as a structure tree, into which you can insert different task types. The Phase of a cycle can be set by clicking on Phase. A Pop-up will appear wherein the next or previous phase can be set. After switching the phase the task list is automatically saved. It‘s only possible to switch to the next phase and not to jump directly e.g. from Development with Release to Go-Live.

2012


459


E2E200

Recommendation: Use the Service Desk Transaction to switch the phase of a cycle to Completed. System Demo Task List

460


2012

E2E200

Lesson: Task List

Lesson Summary You should now be able to: • Explain how to manage your transports with a central transport infrastructure of SAP Solution Manager. • Use the Task List for central transport management in SAP Solution Manager. • Create, release and import transport requests in a managed target system using the task list.

2012


461


Lesson: 455

E2E200

Critical Object Lesson Duration: 15 Minutes

Lesson Overview This lesson will give you an overview about the critical object functionality with SAP Solution Manager.


Define and activate Critical Transport Objects. Explain the approval process for Critical Transport Objects.

Business Example Process and control software changes with SAP Solution Manager along your whole SAP system transport landscape. You have a maintenance landscape and one or more project landscape for releases, for example. The challenge is now to monitor changes for critical objects. Your IT change process includes an approval procedure for critical objects.

462


2012

E2E200

Lesson: Critical Object

Figure 376: Critical Transport Objects- Approval Process

The benefits of this procedure compared to the TMS check for critical transport objects are: • •

Customizing entries can also be marked as critical. The check is performed at the time of the export from the development system. This gives the organization many options on how to deal with that critical object. If a critical object is only detected at the time of the import, it is often difficult to postpone a scheduled Go-Live.

Figure 377: Critical Transport Objects- Definition

First you must specify a set of critical transport objects. There are two types of critical objects: cross-client and client specific objects. For each type of critical object there is a separate maintenance interface.

2012


463


E2E200

For the definition of critical objects use the transaction /TMWFLOW/CMSCONF → select the critical object tab page or alternatively you can use transaction SPRO → SAP Reference IMG → SAP Solution Manager → Capabilities (Optional) → Change Management → Extended Configuration → Specify Critical Transport Objects The check can be activated on a system-level and a client-specific level. When a critical object is contained in a transport of the change transaction, no export is possible unless the change manager approves the critical object. In the Schedule Manager application log, you see the following information: • •

Transport object checks are activated. Request contains critical objects!

Only users with the role Change Manager can approve critical objects.

Figure 378: Critical Transport Objects- Approval via Task List

Critical transport objects can be displayed and approved via the task list (Area General Tasks).

464


2012

E2E200

Lesson: Critical Object

Lesson Summary You should now be able to: • Define and activate Critical Transport Objects. • Explain the approval process for Critical Transport Objects.

2012


465


Lesson: 459

E2E200

Cross System Object Lock Lesson Duration: 15 Minutes

Lesson Overview This lesson will give you an overview about the Cross System Object Lock functionality with SAP Solution Manager.


Activate the Cross System Object Lock. Explain the best practices to use the Cross System Object Lock in complex system landscapes.

Business Example You have a maintenance landscape and a project landscape for releases. The challenge is now to avoid software downgrade within parallel project development and maintenance.

Cross System Object Lock

Figure 379: Cross-System-Object-Lock (CSOL)- Downgrade Risks with Urgent Changes

466


2012

E2E200

Lesson: Cross System Object Lock

The locking of objects within an urgent change, prohibits an urgent change bypassing another with the same object, but a newer object version.

Figure 380: Cross-System-Object-Lock (CSOL)- Downgrade Risks with Parallel Projects

Normal Changes or project transports that share the same production system, but have different life cycles and can include different versions of the same objects. Depending on the life cycle of parallel projects and on object conflicts, objects might be downgraded.

Figure 381: Managing Complex Landscapes- Avoid Downgrades with Cross System Object Lock

2012


467


E2E200

The cross-system object lock ensures that when an object is changed in a managed system, a lock entry is created for this object in the central SAP Solution Manager system. Depending on the selected conflict analysis scenario, this lock entry prevents changes being made to this object in any other transport request. This applies to all satellite systems and clients for which the cross-system lock has been activated. With Cross System Object Lock a developer is informed about a conflict immediately when a change is made and the downgrade risks is limited significantly. • • • •

Lock Objects until transport reaches production environment Improved Customizing with SAP Solution Manager 7.1 Identify changes on the same objects across systems and projects (immediate message to the developer) Available for all transport tools in SAP Solution Manager (Task list, ChaRM, QGM)

Figure 382: Cross-System-Object-Lock (CSOL)- Cross-Client Example

The cross-system lock can be activated by the transaction /TMWFLOW/CONFIG_LOCK or alternatively using transaction SPRO → SAP References IMG → SAP Solution Manager → Capabilities (Optional) → Change Management Extended Configuration → Configure and Activate Cross-System Object Lock. There you can also find information regarding different locking modes that can be configured and configuration advices.

468


2012

E2E200

Lesson: Cross System Object Lock

You can see the active locks in transaction /TMWFLOW/LOCKMON. There you can also delete locks if needed.

2012


469


E2E200

Lesson Summary You should now be able to: • Activate the Cross System Object Lock. • Explain the best practices to use the Cross System Object Lock in complex system landscapes.

470


2012

E2E200

Lesson: 463

Lesson: Retrofit

Retrofit Lesson Duration: 25 Minutes

Lesson Overview This lesson will give you an overview about the Retrofit function with SAP Solution Manager 7.1.


Explain the Dual Landscape Synchronization with Retrofit functionality of SAP Solution Manager. Know new features of Retrofit in SAP Solution Manager 7.1. Explain, how to perform Retrofit.

Business Example You have a dual SAP system landscape represent by a maintenance landscape and a implementation landscape. The challenge is now to synchronize the maintenance changes from maintenance landscape with the implementation landscape.

Retrofit

2012


471


E2E200

Figure 383: Managing Complex Landscapes- Dual Landscape Synchronization with Retrofit

In a dual landscape you must ensure stability of production and manage complex projects at the same time. Topics to be addressed: • • • •

Different development system for production support and long term implementation projects Independent work of implementation team and maintenance team Ensure bug fixes can always be done in a close to production environment Synchronization of the two environments needs to be done

Retrofit improves the quality in running a phased transport landscape and reduces the amount of manual effort for double maintenance. The Retrofit is performed for a transport request which is controlled by SAP Solution Manager. The Retrofit is part of the Change Request Management Process supported by SAP Solution Manager and is performed within the SAP Solution Manager. The Retrofit can be performed between any types of landscapes.

Figure 384: Dual Landscape Synchronization with Retrofit - Addressing typical customer challenges

Enhanced Retrofit with 7.1

472


2012

E2E200

Lesson: Retrofit

With the new version of Retrofit functionality you can handle typical customer challenges within an dual landscape. The Enhanced Retrofit with SAP Solution Manager 7.1 includes the following features: • • • • • • • •

Support 100% of transportable objects Reduce manual effort (more automation) More information for users performing the retrofit (logging, messages, process control) Detect technical dependencies Customizing and BADIs for customer specific requirements Direct integration into UI Customizable Enhancement Possibilities

Sequence Dependency Sequence dependent means, that a transport request A contains an object X, that has already been touched by another transport request B –> in this case the transport requests A and B are sequence dependent to each other • •

•

A transport request can be sequence dependent to more than only one other transport request (different objects touched by different transport requests) A transport request A is only sequence dependent to an other transport request B regarding an object X, if the transport request B is the only one with these object X or the one which was released latest The transport request B can be sequence dependent to an other transport request as well – – –

A queue of sequence dependency exists The sequence dependency can be related to a complete different object which may not be contained in transport request A The queue (even if only two TRs involved) should be kept in sequence in order to avoid over takers

The sequence dependency is based on the objects in the Object List of the whole retrofit queue The dependency will be updated/deleted if a transport request has been retrofitted

2012


473


E2E200

Figure 385: Dual Landscape Synchronization with Retrofit - A 3-Step Approach

Improve process reliability for the retrofit process: • • • • •

Work List of all transports to be synchronized (down to object level) Tool based Minimized risk through integration in the maintenance project and changes Logging of the changes Less manual effort for double maintenance (conflict and sequence visibility)

How does it work:

474


2012

E2E200

Lesson: Retrofit

Figure 386: Enhanced Retrofit- Process Overview

2012


475


E2E200

The retrofit is always performed for a transport request, but based on the object categorization offers different options: •

Automatic Import for Objects of Transport Request into the Retrofit System –

•

Applies for all Objects of a Transport Request which have no conflict –> They have not been changed in the retrofit system – Retrofit is performed through a transport of copies which is automatically created and released and contains only the objects without conflicts (retrofit tool imports this transport of copies) – Around 90% of all transports and objects are handled with the “Automatic Import” Semi-Automatic Retrofit with Correction Workbench (Note Assistant) or BC-Sets –

•

Applies for all Objects of a Transport Request which have a conflict and which are supported by one of the tools (Repository Objects with Correction Workbench, Customizing via BC-Sets) –> This was already available with the “old” version of the retrofit. – Both tools offer the possibility to do adjustments, which are necessary in case of a conflict to not simply overwrite a change in the Implementation Project (Release Development) Manual Retrofit –

Objects with conflicts which have no tool support. Note: Conflict Detection is performed via Cross System Object Lock

Figure 387: Extended Scenarios: Prepare process

476


2012

E2E200

Lesson: Retrofit

You want to start the retrofit process for transport requests related to an urgent or normal change. Your change document has the status Authorized for Production (urgent change) or To Be Tested (normal change).

Figure 388: Extended Scenarios- Perform Retrofit

Proceed Retrofit Regarding the retrofit, an object of a transport request can only be in 3 different categories: •

It can be an auto import object (Retrofit Category 2, color green) –

•

The object has not been touched in the retrofit system and has no conflict in the retrofit system It can be a retrofit object (Retrofit Category 1, color yellow) –

•

The object has been touched in the retrofit system or has a conflict in the retrofit system, but there is a tool supporting the retrofit (SCWB or BC-Set) It can be a manual object (Retrofit Category 4, color red) –

2012

Object does not fit into the above categories and has to be retrofitted manually


477


E2E200

A transport request can be in 7 different technical categories, depending on the objects included in this transport request –> the numbering of the categories is purely technical •

•

A transport request is in category 2, as long as there are only auto import objects in it, it is in category 1 as long as there are only retrofit objects in it and in category 4 as long as there are only manual objects in it If there is more than one object category in the transport request, the category changes according to the table below –> the color indicating the category is adjusted to the object categories –> red if at least one manual object, yellow if at least one retrofit object

In compare with the first version of Retrofit are a lot of improvements and features are delivered with the latest version of Retrofit. The retrofitting itself takes part through SAP Solution Manager – either centrally from the task list or from the Change Document with a preset filter. A retrofit request on the target system needs to be specified and controlled by SAP Solution Manager. Note: Tight integration to development and change management process is possible as retrofit is a critical activity.

(System Demo) Retrofit

478


2012

E2E200

Lesson: Retrofit

Lesson Summary You should now be able to: • Explain the Dual Landscape Synchronization with Retrofit functionality of SAP Solution Manager. • Know new features of Retrofit in SAP Solution Manager 7.1. • Explain, how to perform Retrofit.

2012


479


Lesson: 472

E2E200

Transport of Copy Lesson Duration: 15 Minutes

Lesson Overview This lesson will give you an overview about the Transport of Copy.


Understand how to use Transport of Copies (ToC). Usage of Transport of Copy within your maintenance and implementation projects.

Business Example You want to reduce the number of correction transports at your maintenance and implementation projects. Before a transport request is released in a development system the change should be tested at quality assurance system before. The change is done in the quality assurance system with a transport of copy. If test failed the required correction can be done for original transport. After successful test the original transport is released in the development system.

480


2012

E2E200

Lesson: Transport of Copy

Transport of Copy

Figure 389: Transport of Copies

If you want to test your software changes in one system without having them transported automatically to other systems in your transport track, you can trigger Transports of Copies. Such transports of copies are not transported across your system landscape, and are therefore not imported into your production system, therefore they are suitable for testing purposes.

2012


481


E2E200

Lesson Summary You should now be able to: • Understand how to use Transport of Copies (ToC). • Usage of Transport of Copy within your maintenance and implementation projects.

482


2012

E2E200

Unit Summary

Unit Summary You should now be able to: • Understand the best practices for Transport Management. • Give an overview of the capabilities available in SAP Solution Manager for central transport management • Explain the basics of Change Request Management configuration. • Explain, how to prepare the infrastructure for the use of the Change Request Management. • Explain how to manage your transports with a central transport infrastructure of SAP Solution Manager. • Use the Task List for central transport management in SAP Solution Manager. • Create, release and import transport requests in a managed target system using the task list. • Define and activate Critical Transport Objects. • Explain the approval process for Critical Transport Objects. • Activate the Cross System Object Lock. • Explain the best practices to use the Cross System Object Lock in complex system landscapes. • Explain the Dual Landscape Synchronization with Retrofit functionality of SAP Solution Manager. • Know new features of Retrofit in SAP Solution Manager 7.1. • Explain, how to perform Retrofit. • Understand how to use Transport of Copies (ToC). • Usage of Transport of Copy within your maintenance and implementation projects.

2012


483

Unit Summary

484

E2E200


2012

Unit 7 Quality Gate Management

477

Unit Overview Within this unit you will learn how to manage solution transports with Quality Gate Management. Quality Gate Management gives you an overview of the status of the software distribution of your projects. It gives an integrated and consistent overview of the implementation of changes to your SAP software solution, for all operational units of the various organizations in a company. This increases the transparency of the software change process. Quality Gate Management combines different software developments in one logical structure. These developments are in turn collected in projects. You can organize and monitor the distribution of software by projects and their changes.

Unit Objectives After completing this unit, you will be able to: • • • • • • • •

2012

Explain the concept of solution transports and track synchronization with Quality Gate Management in SAP Solution Manager 7.1 Describe the tasks of a quality manager Know, how to prepare the solution Landscape to be able to work with Quality Gate Management Explain, how to set up the Quality Gate Management Explain the difference between implementation and maintenance projects and their phases Know, how Quality Gate Management can support in each project phase. Also, by operating with projects running in parallel. Know, how to synchronize projects across the ABAP and Non-ABAP system landscape. Create and release transport requests centrally in SAP Solution Manager for ABAP and non-ABAP environments.


485

Unit 7: Quality Gate Management

• • • •

E2E200

Know, how to avoid and manage risks of application changes in a project. Understand Best Practices that are used with the central Transport Management in combination with Quality Gate Management tool. Know how to setup the transport parameter for a java system. Know about the importance of logical components in QGM.

Unit Contents Lesson: Overview of Quality Gate Management ...........................487 Lesson: Setup of Quality Gate Management................................493 Exercise 14: Setup of Quality Gate Management......................503 Lesson: Project Phases and Quality Gates ................................. 511 Exercise 15: Project Phases and Quality Gates .......................523 Lesson: Central Transport Management ....................................527 Exercise 16: Transport Management in Quality Gate Management .539 Lesson: (Appendix) Prerequisites to Set Up Quality Gate Management 555

486


2012

E2E200

Lesson: 479

Lesson: Overview of Quality Gate Management

Overview of Quality Gate Management Lesson Duration: 15 Minutes

Lesson Overview Quality Gate Management combines different software developments in one logical structure. These developments are in turn collected in projects. You can organize and monitor the distribution of software according to individual projects and the changes made for them. In this way, Quality Gate Management ensures the full transparency of all software change processes, centrally managing the software distribution in complex system landscapes across technology stacks and application components. Technically based on the SAP Change and Transport System, Quality Gate Management integrates the various development workbenches in one central transport and change control system. It also synchronizes the software distribution in the different software stacks. Quality Gates provide a fast entry point to obtain a project and status overview for each project. Within the overview, the time schedule for the different projects is displayed, including the ratings of the passed Quality Gates.


Explain the concept of solution transports and track synchronization with Quality Gate Management in SAP Solution Manager 7.1 Describe the tasks of a quality manager

Business Example You work within the ESS (Enterprise Self Service) scenario. You have to enhance functionality in the portal and in the ERP backend. For this project you would like to use Quality Gate Management in order to manage the changes belonging to the project.

2012


487


E2E200

Overview of Quality Gate Management

Figure 390: Change Control Management: Quality Gate Management

Change control management is defined by several components and capabilities. Within this chapter we focus on the setup and usage of quality gate management. •

• • •

488

Quality gate management (QGM) provides an integrated and consistent quality process for managing projects over all operational units across the various organizations of a company. This enables you to: Monitor all software change processes and obtain full transparency of these processes Use a project-based approach to distribute software across systems Have an integrated and consistent overview of the implementation of changes to your SAP software solution.


2012

E2E200


Figure 391: Standard Application and Quality Management - One integrated and Consistent Quality Process

To start with QGM you should integrate QGM into your process by closing already released transports and assign open transports to quality gate management.

Figure 392: Quality Gate Management- Roles and Responsibilities

2012


489


E2E200

In principle, four roles can be identified in the process of using Quality Gate Management: •

•

•

•

A development lead is responsible for creating changes and transport requests, assigning them to the developers and releasing them, when the development is complete. An IT Operator is responsible for importing the transport requests into the test and production systems. He monitors the imports and fixes technical problems during the import process. The Quality Manager performs quality checks at certain project milestones. For example he checks if project documentation and test cases are available in a good quality. He also checks the result of automated quality checks like code inspection analyses or completeness of transports in the test system. The Quality Advisory Board is the steering committee for the implementation project. It supervises the risks of an implementation project

The required authorizations that should be assigned to the different responsibilities are: • • • •

Role 1: Role 2: Role 3: Role 4:

SAP_SM_QGM_ALL SAP_SM_QGM_TRANSPORT SAP_SM_QGM_STATUS_QM SAP_SM_QGM_STATUS_QAB

Figure 393: Important Role- Quality Manager

490


2012

E2E200


Figure 394: Important Role- Quality Advisory Board

Figure 395: Usage of Projects in SAP Solution Manager (TX SOLAR_PROJECT_ADMIN)

Quality gate management bundles transport requests in projects. This has the following advantages: • •

2012

Comprehensive customizing and development activities are grouped together. Basis for release management


491


E2E200

Lesson Summary You should now be able to: • Explain the concept of solution transports and track synchronization with Quality Gate Management in SAP Solution Manager 7.1 • Describe the tasks of a quality manager

492


2012

E2E200

Lesson: 485

Lesson: Setup of Quality Gate Management

Setup of Quality Gate Management Lesson Duration: 20 Minutes

Lesson Overview You work with different projects in SAP Solution Manager to document your processes. You will now set up the Quality Gate Management data of a project in several work steps: • • • •

Specify Q-Gates, milestones, quality manager, and quality advisory board members. Check the transport landscape to be used. Assign Q-Gates to system roles. Confirm system data.


Know, how to prepare the solution Landscape to be able to work with Quality Gate Management Explain, how to set up the Quality Gate Management

Business Example You know that Quality Gate Management is part of the SAP Solution Manager. Now, you wish to set up a project in the Quality Gate Management. You must give it the required data. This includes specifying the quality manager responsible, and the quality gate data.

2012


493


E2E200

Setup of Quality Gate Management

Figure 396: Create New Project

Using the project administration transaction SOLAR_PROJECT_ADMIN, you must have created the projects that you want to manage with quality gate management. You must insert your system roles according to the transport track. It will not work if you design the logical component in another way than the transport route was created.

Figure 397: Activate IMG Project within Project Administration

494


2012

E2E200


You have assigned logical components to the project on the System Landscape tab page. The IMG Projects tab page now contains the associated IMG projects, that is, all subprojects in the managed systems that belong to your Solution Manager project.

Figure 398: Work Center Change Management: Overview in transaction SM_Workcenter

• • •

2012

In the Overview you get a quick overview about the different projects and their status. You see all projects you are involved in, sorted by project phases. From here, you are able to jump directly into the Project view. You could assign projects as favorites for faster access.


495


E2E200

Figure 399: Set Up Quality Gate Management within Change Management Work Center

Choose Set up in the Project Area. You go to a window in which you perform the steps required to set up a project in the quality gate management and follow the guided procedure. It is also possible to maintain the project directly within transaction solar_project_admin.

496


2012

E2E200


Figure 400: Define Q-Gates and Milestones within Change Management Work Center

•

Specify the Q-Gate and milestone data. Proceed as follows: –

• •

2012

Enter the name of the quality manager and the person responsible from the quality advisory board, at the top. – To specify your own milestones as Q-Gates, choose Add Milestone, enter a name for the milestone, and set the flag in the Q-Gate column. – Enter the planned deadlines for all Q-Gates and milestones. You can upload template documents for Q-Gates. Select the row of the Q-Gate and choose Upload Template. The system administrator uploads the template documents into the system. These are templates for the project team members who can edit them by downloading them into the Open Q-Gate window, and then upload them again.


497


E2E200

Figure 401: Set up Business Partners within Change Management Work Center

There are the following roles in quality gate management to be maintained: • •

Quality manager (QM) responsible: A quality manager makes one status assignment in quality gate management. Quality advisory board (QAB): A member of the quality advisory board makes the second status assignment.

A business partner must be assigned to the users. If the business partner does not exist, the system will create it for you. If you have many users working with QGM you could create business partners via transaction BP_GEN.

498


2012

E2E200


Figure 402: Check Transport Landscape within Change Management Work Center

Display system transport landscape check: •

• • •

2012

The logical components that you use in your project are at the top. If you select a row, the system shows the system information (system/client/system role) of the logical component, at the bottom of the screen. Only logical components which have been assigned to the project in the project administration (transaction SOLAR_PROJECT_ADMIN) are shown. The TMS Check column indicates whether a logical component for the TMS has been configured correctly. Green = correct, red = incorrect. Select the logical components that you wish to use in the quality gate management, in the Include in Project column.


499


E2E200

Figure 403: Assign Q-Gates to System Roles within Change Management Work Center

• •

•

500

Assign or change system roles for Q-Gates. The phase is shown in the third column. You specify which Q-Gate is to be passed for which system. The project phases are shown, depending on the assignment to the Q-Gates, in the Phase column. You can only assign each Q-Gate once. You could have several system between 2 gates.


2012

E2E200


Figure 404: Check Configuration within Change Management Work Center

• • • • •

Finally, your project can be used in quality gate management. Quality gates can flexibly be assigned to systems and project phases. If a quality gate is assigned to a system this means that imports into that system are possible after the quality gate has been passed. If a quality gate is assigned to a project phase this means that this project phase starts at the latest when the quality gate has been passed. Additional quality gates can be defined. However, the project phases are fixed.

(System Demo) Create a New Project

Quality Gate Management- Exercises Introduction This exercise will teach you how the process for quality gate management in SAP Solution Manager 7.1 works. After this exercises you will be able to define quality gates, create changes, rate quality gates, create and release transports and trigger imports in quality gate management. System Landscape and Responsibilities :

2012


501


E2E200



502


2012

E2E200

495


Exercise 14: Setup of Quality Gate Management Exercise Duration: 15 Minutes

Exercise Objectives After completing this exercise, you will be able to: • Activate quality gate management for a new SAP Solution Manager implementation project.

Business Example You want to customize transaction CAT2 in the backend and you will also have to transport your iView for time recording in the portal. Both transport requests must be transported synchronously.

Task: Activate quality gate management for a new implementation project, QGM E2E ##. 1.

Log on to SAP Solution Manager with your user, E2E200-## (change ## to your group number) and copy the existing implementation project E2E200_QGM.

2.

Navigate to the Change Management work center and choose the Projects tab.

3.

In the Project Overview, select the project that you created.

4.

Set up quality gate management for your project by pressing the Set up button and select Quality Gate Management. The Define Q-Gates and Milestones dialog box appears. Enter the planned start date for each project phase. When you have entered all dates, choose the Next button. Enter the Quality Manager and the member of the Quality Advisory Board. Choose your user for the Quality Manager and your neighbor’s user for the member of the Quality Advisory Board. Alternatively, you can enter the instructor’s user, E2E200-00.

5.

In the Check Transport Landscape screen, you see the logical components of your project. Make sure that only the logical components Z_EP_CCM and Z_ERP_QGM are included in quality gate management. If other logical components occur, deselect them. Choose the Next button. Continued on next page

2012


503


6.

E2E200

Assign each Q-Gate to the system role and phase that should be used when the Q-Gate is passed. Make the following assignments. Q-Gate

System Role

Phase

Scope to Build

Development System

Build

Build to Test

Quality Assurance System

Test

Test to Deploy

Production System

Deploy

Choose the Next button and then choose Finish to confirm the data. Note: You can only activate Quality Gate Management successfully, if you have completed the creation of the IMG projects.

504


2012

E2E200


Solution 14: Setup of Quality Gate Management Task: Activate quality gate management for a new implementation project, QGM E2E ##. 1.

Log on to SAP Solution Manager with your user, E2E200-## (change ## to your group number) and copy the existing implementation project E2E200_QGM. a)

Copy the existing implementation project E2E200_QGM using transaction SOLAR_PROJECT_ADMIN.

Figure 407: SAP Solution Manager Work Center

Name your implementation project QGM_E2E_## (## = your group number). After pushing refresh in solar_project_admin you will get informed that the project is copied. Create an IMG project for both logical components. When asked to create a transport request, immediately choose No, Later. Finally, both IMG projects should show a green light.


2012


505


2.

E2E200

Navigate to the Change Management work center and choose the Projects tab. a)

Call SM_Workcenter –> SAP Solution Manager Work Center.

Figure 408: SAP Solution Manager Work Center

Then select the Change Management work center and the Projects tab.

Figure 409: SAP Solution Manager

3.

In the Project Overview, select the project that you created. a)

Figure 410: Change Management: SAP Solution Manager

4.

Set up quality gate management for your project by pressing the Set up button and select Quality Gate Management. The Define Q-Gates and Milestones dialog box appears. Enter the planned start date for each project phase. When you have entered all dates, choose the Next button.


506


2012

E2E200


Enter the Quality Manager and the member of the Quality Advisory Board. Choose your user for the Quality Manager and your neighbor’s user for the member of the Quality Advisory Board. Alternatively, you can enter the instructor’s user, E2E200-00. a)


b)

After you have finished, your input the screen should look like this:


When you have entered all dates, choose the Next button. c)


2012


507


E2E200

Figure 413: Maintain Project

After this, choose the Next button. 5.

In the Check Transport Landscape screen, you see the logical components of your project. Make sure that only the logical components Z_EP_CCM and Z_ERP_QGM are included in quality gate management. If other logical components occur, deselect them. Choose the Next button. a)

6.

Assign each Q-Gate to the system role and phase that should be used when the Q-Gate is passed. Make the following assignments. Q-Gate

System Role

Phase

Scope to Build

Development System

Build

Build to Test

Quality Assurance System

Test

Test to Deploy

Production System

Deploy


508


2012

E2E200


Choose the Next button and then choose Finish to confirm the data. Note: You can only activate Quality Gate Management successfully, if you have completed the creation of the IMG projects. a)

Choose the Next button. You should now see the following screen. The transport routes indicate that the TMS and the logical components are consistent.

Figure 414: Maintain Project

b)

2012

Choose Finish to confirm the data. Quality gate management is now activated for your implementation project.


509


E2E200

Lesson Summary You should now be able to: • Know, how to prepare the solution Landscape to be able to work with Quality Gate Management • Explain, how to set up the Quality Gate Management

510


2012

E2E200

Lesson: 503

Lesson: Project Phases and Quality Gates

Project Phases and Quality Gates Lesson Duration: 20 Minutes

Lesson Overview You use quality gates (Q-Gates) to indicate the end of a phase in SAP Solution Manager and to start the next phase of your project. This means that the import of transport requests is not possible until the Q-Gate immediately preceding it has been passed.


Explain the difference between implementation and maintenance projects and their phases Know, how Quality Gate Management can support in each project phase. Also, by operating with projects running in parallel.

Business Example You want to learn how to use Quality Gate Management during the different phases of your project. You need to know about the activities that you are allowed to carry out when switching the gates.

2012


511


E2E200

Project Phases and Quality Gates

Figure 415: Solution Manager Projects Enhanced by Project Phases

SAP Solution Manager projects can be extended by adding project phases. Maintenance projects could be enhanced by new maintenance cycles. Quality gate management projects have four phases were you could assign the systems variable to.

Figure 416: Work Center Change Management : Graphical View for several Projects

512


2012

E2E200


The Graphical view of your project contains an overview of the deadlines, Q-Gates, and milestones in your project. You can prepare existing projects for quality gate management, or change them, and manage document templates for the project Q-Gates, with Maintain Project.

Figure 417: Types of Projects Used in Quality Gate Management

The Solution Manager project is represented as an IMG project in each managed development system and a CTS project in each managed system client. Transport requests are managed by the CTS project. The project assignment of each transport request is mandatory.

2012


513


E2E200

Figure 418: Transport Restrictions via CTS Project Status Switches

•

• •

514

Imports into a system are only possible when the previous quality gate has been passed. Quality gate management uses the CTS project status switches to protect systems against imports. In this example, the quality gate “Build to Test” is passed. Therefore, imports into the QA system are possible. The quality gate “Test to Deploy” has not yet been passed. Therefore, imports into the PRD system are not possible.


2012

E2E200


Figure 419: Quality Gate Process

The rating of the quality gates follows the four-eye principle. The quality gate must be rated as “Passed” or “Partially Passed” by the quality manager and by a member of the quality advisory board. For urgent corrections you now have the possibility to reset the gates status to reopen it.

Figure 420: Work Center Change Management- System Landscape Graphic

2012


515


E2E200

This is a graphical overview of your system landscape. The systems are separated by Q-Gates. You can go to the Q-Gate screens. The color of the Q-Gates indicates their status: • • •

Grey: Q-Gate initial, not yet processed Orange: Q-Gate in process Green: Q-Gate passed

Figure 421: Checklist for Quality Gates : Best Practice Recommendation

• • •

516

The figure above shows SAP’s best practice recommendations on which information is to be available at the end of each project phase. In the quality gate it should be checked if all required information is available. Only in this case, the project can move forward into the next phase. You should use templates as well as service results to fill the gates.


2012

E2E200


Figure 422: Rating of Quality Gates

• • • • •

2012

You can edit data for the Q-Gate in the graphical, list, or project status view. In the graphical view, select a Q-Gate to open it. In the list view, put the cursor on a project and choose Open Q-Gate. In the list view, you can only open the currently active Q-Gate. In the project status view, putting the cursor on a Q-Gate activates the Q-Gate pushbutton. All views show information about the Q-Gate. Some fields are ready for input. You can upload, download or delete documents in the system, or enter issues, at the bottom of the screen.


517


518


E2E200

2012

E2E200


Figure 423: Project Phases - Possible Activities

• •

•

•

• •

•

2012

This picture illustrates which activities related to change control management could be carried out during different project phases. The scope phase begins at the Q-Gate “Scope to Build”. The Scope phase ensures that the tasks that are required for successful completion are performed in the project. You can verify the architecture and the technical prerequisites of the systems for your projects. The scope phase performs the following: – Document a functional or technical design – Document the requirements of departments – Evaluate technical implementation of the project The Build phase is the actual development process. Transport requests are created, in all systems in the project. The transports are imported into the subsequent systems together, to guarantee a correct function if the transport requests are functionally interdependent. In the Test phase, projects, or changes to projects are imported and activated in the test systems. The previously defined test cases (for example, integration and user acceptance test) must be accepted by the test team. If there are errors in the test cases, you must make the corrections which are assigned to the development systems in new transport requests. The test phase begins at the “Build to Test” Q-Gate. The entire project, with all changes and corrections, should be imported when switching into the Deploy phase. This ensures that all transport requests of a project are imported completely and in the correct sequence into the production systems. Project go live is the formal end, with the last Q-Gate. The deploy phase begins at the Q-Gate “Test to Deploy”.


519


E2E200

Figure 424: Quality Gates Between the Project Phases

There is a quality gate between each phase that must be passed before the project can be switched into the next phase. In addition, there is a quality gate at the start and at the closure of the project. The names of the quality gates are: • • • • •

520

Project Start Scope to Build Build to Test Test to Deploy End of Project


2012

E2E200


Figure 425: Automatic Reassignment of Changes in Maintenance Projects

When a maintenance project ends, you can close the project, by passing the End of Project Q-Gate. In this case, you close the last maintenance cycle without cycle switching. Note: You cannot close projects with open changes. To close a project that has open changes, set the status of finished changes to Completed. Changes that are not longer to be made can be set to Withdrawn. All other changes, which are neither Completed nor Withdrawn, have to be reassigned to another project.

2012


521


E2E200

Figure 426: Maintenance Cycle - Start of next cycle

• •

If you work with a maintenance project, you can create maintenance cycles for this project. In this case, a new Scope phase follows the Deploy phase. If a new maintenance cycle is created and appended at the end, the End of Project Q-Gate is moved to this new maintenance cycle. This means that you can only change the End of Project Q-Gate in the last maintenance cycle.

(System Demo) Rating of Quality Gates

522


2012

E2E200

515


Exercise 15: Project Phases and Quality Gates Exercise Duration: 15 Minutes

Exercise Objectives After completing this exercise, you will be able to: • Rate quality gates. • Upload documents into the quality gates.

Business Example RWS is the SAP Solution Manager system that contains all information about the systems landscape. You have set up QGM already and now you have fulfilled the milestone and you start with the development.

Task: Rate the Start of Project and Scope to Build quality gates. 1.

Select your Solution Manager project in the Overview. After this select the tab Quality Gates in the details for project(s) area.

2.

Open the Start of Project quality gate and set Status set by: Quality Manager to Passed.

3.

Your neighbor acts as a member of the Quality Advisory Board. Ask him or her to set the Status set by: Quality Advisory Board to Passed.

4.

What is the current phase of your project? Current phase: ________________________________________________

2012

5.

Repeat the steps that were described for the Start of Project quality gate for the next quality gate, Scope to Build.

6.

Go to the System Landscape Graphic tab and check your project.


523


E2E200

Solution 15: Project Phases and Quality Gates Task: Rate the Start of Project and Scope to Build quality gates. 1.

Select your Solution Manager project in the Overview. After this select the tab Quality Gates in the details for project(s) area. a)

2.

Open the Start of Project quality gate and set Status set by: Quality Manager to Passed. a)

3.

Your neighbor acts as a member of the Quality Advisory Board. Ask him or her to set the Status set by: Quality Advisory Board to Passed. a)

4.

Select Start of Project, push the Quality Gate Details button and set the Status set by: Quality Manager to Passed.

Select Start of Project, push the Quality Gate Details button and set the Status set by: Quality Advisory Board to Passed. Confirm the dialog box.

What is the current phase of your project? Current phase: ________________________________________________

5.

a)

In the Project Overview, choose the Refresh button in the project grid and check the entry in the Current Phase column. Your project should now be in the Scope phase.

b)

Also you can see in the Details for Project(s) area that the Q-Gate Status for Start of Project is set to Passed.

Repeat the steps that were described for the Start of Project quality gate for the next quality gate, Scope to Build. a)


524


2012

E2E200


6.

Go to the System Landscape Graphic tab and check your project. a)

The project should look like this:

Figure 427: Details for Project(s)-2

2012


525


E2E200

Lesson Summary You should now be able to: • Explain the difference between implementation and maintenance projects and their phases • Know, how Quality Gate Management can support in each project phase. Also, by operating with projects running in parallel.

526


2012

E2E200

Lesson: 519

Lesson: Central Transport Management

Central Transport Management Lesson Duration: 30 Minutes

Lesson Overview Changes in one system must be imported into the next system of your system landscape before they can be used productively. The corresponding Q-Gate must have been passed before you can import changes into a subsequent system.


Know, how to synchronize projects across the ABAP and Non-ABAP system landscape. Create and release transport requests centrally in SAP Solution Manager for ABAP and non-ABAP environments. Know, how to avoid and manage risks of application changes in a project. Understand Best Practices that are used with the central Transport Management in combination with Quality Gate Management tool.

Business Example Changes done in the development system must be imported into the next system of your system landscape before they can be used productively. The corresponding Q-Gate must have been passed before you can import changes into a subsequent system.

2012


527


E2E200

Central Transport Management

Figure 428: Synchronization of Projects Across the Landscape

In this example, the Solution Manager project comprises several SAP systems. The systems have dependent transports. All transports for the whole solution are bundled under the umbrella of the Solution Manager project. When the project goes live, all transport requests that belong to the same Solution Manager project are imported at the same time. So all dependencies are considered automatically.

Figure 429: Example- Portal iView Uses BI Webreport

528


2012

E2E200


Several transports could be included in one change and transported through the landscape.

Figure 430: Solution Transports and Track Synchronization

Changes could bundle transports within the same track or contain transports from different landscapes that belong together. The number of transport requests imported depends on where you call the Import. You decide whether you want to import an entire project, or all transport requests of a change, or a single transport request.

2012


529


E2E200

Figure 431: Work Center Change Management- Bundling Transport in Changes

•

•

•

530

You can display and edit your project in a list, in the List View. The following sub screens are available: – Project List – List of Changes for a Project – List of Transports for a Change The top list or table shows the projects which you have selected with the display filter at the top of the screen. The second table shows the changes made to the project selected in the first table. The third table contains the transport requests for the change selected in the second table. You can create new changes, release transport requests, or import from another system. A sub screen has several tabs in which you can perform other functions, such as check TMS configuration or go to the Q-Gate data.


2012

E2E200


Figure 432: One source of truth- To avoid and manage risks of application changes in a project

•

•

2012

The risks are collected automatically by the system. The quality manager can decide before each phase or phase completion, whether all transports have run correctly into the next system, or whether he must take measures to ensure that they do so. The quality manager can react to critical situations appropriately, and asses the project risk.


531


E2E200

Figure 433: Work Center Change Management: Projects - Risks

• •

The Risks View shows the risks associated with transports in your project. The view has two screen areas: – –

•

The top area contains the systems and the risk descriptions. The bottom area contains the change requests for your project which are affected by these errors. Risks can be, for example:

– – –

Transport error (return code = 8) Missing transport requests Transports that did not run synchronously

Figure 434: Quality Gate Management- Roles and Process Flow

532


2012

E2E200


In principle, three roles can be identified in the process of using quality gate management: • •

•

A transport manager is responsible for creating changes and transport requests and starting imports. The developer or content creator creates new developments for the application – for example, new iViews and pages within the portal. He or she has to take care that all the objects needed for a new feature are part of a transport request. The quality manager and the quality advisory board have to make sure that certain quality criteria are met at the end of a project phase. If these criteria are met, the quality gate can be set to “Passed”.

Figure 435: Quality Gate Management- Full Integration of CTS+

Enhanced CTS allows you to transport objects created in other languages than ABAP by using the Change and Transport System of ABAP. The goal is to have one Transport Tool (CTS) which supports all workbenches and applications when it comes to transports. The tools for creating applications and creating content remain the same. Options to attach applications or content to a CTS transport request are integrated into the different workbenches. The level of integration is different for different workbenches. Enhanced CTS aims for a unified single transport tool which simplifies the live of an administrator who is responsible for performing imports. He or she has to access only one tool to start imports for very different backends. Deployment tools are called automatically. It is very easy to monitor what has already been imported and whether the import went well. The queues in CTS provide a good overview on what needs to be imported.

2012


533


E2E200

Figure 436: Process Flow for Non-ABAP Environments 1/2

• •

•

534

For non-ABAP environments there is an additional step “Preselect transport request” that must be done by the developer. In non-ABAP environments the transport request must be selected in a separate step, before objects can be attached to it. This is different from ABAP environments, where the system asks you if several transport requests are available. All other steps of the quality gate management process are identical for ABAP and non-ABAP environments.


2012

E2E200


Figure 437: Process Flow for Non-ABAP Environments 2/2

1. 2. 3. 4. 5.

2012

Quality Gate Management: create workbench request Non-ABAP development environment: Perform the change and go to the export wizard. From there you can jump into the Transport Organizer Web UI Transport Organizer Web UI: Preselect the request that belongs to your change document as standard request Non-ABAP development environment: In the export wizard, attach the archive with the change to the preselected request Quality Gate Management: release transport request


535


E2E200

Figure 438: Efficient Transport - Best Practice

Figure 439: CSOL (Cross System Object Locking) Usage within QGM (Quality Gate Management)

The cross-system object lock ensures that when an object is changed in a managed system, it is locked in the central SAP Solution Manager system. Depending on the conflict scenario, this prevents changes being made to this object in any other transport request. This applies to all managed systems and clients for which the cross-system lock is active.

536


2012

E2E200


Prerequisites: •

•

The cross-system object lock has been configured and activated in Customizing for SAP Solution Manager, as follows: SAP Solution Manager → Implementation Guide → SAP Solution Manager Capabilities → Change Request Management → Extended Configuration → Configure and Activate Cross-System Object Lock. The default conflict analysis scenario is cross-project (Project Relation Cross), Change Type Relation Urgent Only, Object Type Client-Specific. If you want to use a different scenario, execute the /TMWFLOW/CONFIG_SERVICES report. Here, choose the Expert Mode radio button and select the relevant scenario from the Define Customized Conflict Scenarios screen section.

• Note: The system can only detect a conflict if the selected transport request was created in Change Request Management or Quality Gate Management. If the transport request was created locally, the system informs the user that there is no data for this transport request in the central lock management system.

2012


537


E2E200

Figure 440: Transport of Copies (ToC) within Quality Gate Management

•

• •

•

If you want to test your software changes in one system without having them transported automatically to other systems in your transport track, you can trigger Transports of Copies. Such transports of copies are not transported across your system landscape, and are therefore not imported into your production system, therefore they are suitable for testing purposes. Transports of copies can be created for a non-ABAP system only if SAP Note 1293449 has been applied in your system. In contrast to change request management, Quality Gate Management makes it possible to carry out the transport of copies to all systems involved in a QGM project, that is, not only to the consolidation system. The Target column indicates the target system of the transport of copies. If the target of this transport of copies is a target group, the target group will automatically be resolved to its various systems, so this transport of copies is listed several times, once for each target system.

(System Demo)

538


2012

E2E200

531


Exercise 16: Transport Management in Quality Gate Management Exercise Duration: 15 Minutes

Exercise Objectives After completing this exercise, you will be able to: • Create and release changes in quality gate management. • Create and release transport requests in quality gate management. • Trigger imports in quality gate management.

Business Example RWS is the Solution Manger system that contains all information about the system landscape. Z_ERP_QGM and Z_EP_CCM are logical components that describe transport landscapes for an SAP ERP system and a portal. Your customizing in ERP and your iview from the SAP Portal have to be transported together as solution transport. To mitigate risks you use Quality Gate Management to transport your changes.

Task 1: Create a change with a transport request in the ERP backend and a related transport request in the portal. 1.

Select your project, open the tab Changes and create a change. Enter the description “Solution Transport Portal-ERP”. Write down the number of the change. Change number: ______________________________________________

2.

Within your change, create a transport request of type Customizing for the ERP backend. Enter the short text “Solution Transport Portal-ERP / Time Rec”. Write down the transport request. ERP transport request: ________________________________________

3.

Within your change, create a transport request of type Workbench for the portal. Enter the short text“Solution Transport Portal-ERP / Time Rec”. Write down the transport request. Portal transport request: _______________________________________


2012


539


E2E200

Task 2: Perform a customizing change for transaction CAT2 in the ERP backend. 1.

Navigate to the customizing activity that you assigned to your implementation project for the step Record working times in backend. In SAP Solution Manager, call transaction SOLAR02 and select your implementation project. Navigate to the business process step Record working times in backend and select the Configuration tab. Double-click on the IMG object PCUI_ESS_CATS_004. Start the customizing activity Define Field Selection. Which system is assigned to the customizing activity? Answer: __________________________________________________ What is the transaction code of the customizing activity? Answer: __________________________________________________

2.

In the customizing transaction, select Data entry section and choose Influencing.

3.

In the next screen, select entry Z-E2E-## (## = your group number) and press Enter. Customize the visible fields for data entry in transaction CAT2. Add the additional fields Accounting Indicator, Activity Number, and Activity Type (change the first three entries from Hide to Input).

4.

Go to transaction SE09 and release the task of your customizing request in the development client, RWE-801. In transaction SE09, select all modifiable customizing requests for your user. If there are several, look at the short text to find the one that you created. Navigate to the transport request and put the cursor on the task below the transport request. Choose the Release button to release the task. Note: You are not authorized to release the transport request itself from transaction SE09. This must be done in the Quality Gate Management application.

Task 3: Assign your transport package to your transport request and export it. 1.

Log on to the portal and navigate to the Transport Organizer Web UI. Preselect the transport request that you created for the portal.


540


2012

E2E200


2.

Go to the Transport Package Editor and select the transport package that you created before in the CTS+ exercise. The name should be: Transport_Package_User_##. (## is your group number).

3.

Export the transport package to the transport request that you have created in the Quality Gate Management. Which export method is preselected? ______________________________ Which transport request is preselected? ____________________________ Note: The transport request contains the Time Recording workset. This was created in a previous exercise; therefore, it is already available.

Task 4: Release the transport requests in quality gate management. 1.

Release the portal transport request that belongs to your change.

2.

Release the ERP transport request that belongs to your change.

Task 5: Rate the Build to Test quality gate. 1.

Open the Build to Test quality gate and set the Status set by: Quality Manager to Passed.

2.

Your neighbor acts as a member of the Quality Advisory Board. Ask him or her to set the Status set by: Quality Advisory Board to Passed.

Task 6: Import the transport requests into the test systems. 1.

Import the transport request for the portal into the test portal.

2.

Log on to the portal and check the fields of the Time Recording application. Which fields are available? Answer: _____________________________________________________

3.

In quality gate management, go to the Risks tab and check the status of your change. Which risk is displayed? Answer: _____________________________________________________

4.

Import the transport request for the ERP backend.


2012


541


5.

E2E200

In the portal, check again the fields in the Time Recording application. Logon again to the portal or press the Refresh button of your browser. Which fields are available after the import of the ERP transport? Answer: _____________________________________________________

542


2012

E2E200


Solution 16: Transport Management in Quality Gate Management Task 1: Create a change with a transport request in the ERP backend and a related transport request in the portal. 1.

Select your project, open the tab Changes and create a change. Enter the description “Solution Transport Portal-ERP”. Write down the number of the change. Change number: ______________________________________________ a)

Go to the Details for Project(s) area. In the Changes tab, choose Create and enter the description.

Figure 441: Details for Project

2.

Within your change, create a transport request of type Customizing for the ERP backend. Enter the short text “Solution Transport Portal-ERP / Time Rec”. Write down the transport request.


2012


543


E2E200

ERP transport request: ________________________________________ a)

In the Transports tab, choose Create Transport Request. Select a customizing request for system RWE 801. Enter the short text.

Figure 442: Details for Project(s)

Figure 443: Create Transport Request

3.

Within your change, create a transport request of type Workbench for the portal. Enter the short text“Solution Transport Portal-ERP / Time Rec”. Write down the transport request. Portal transport request: _______________________________________ a)

In the Transports tab, choose Create Transport Request. Select a workbench request for system JAD. Enter the short text.

Figure 444: Create Transport Request


544


2012

E2E200


Task 2: Perform a customizing change for transaction CAT2 in the ERP backend. 1.

Navigate to the customizing activity that you assigned to your implementation project for the step Record working times in backend. In SAP Solution Manager, call transaction SOLAR02 and select your implementation project. Navigate to the business process step Record working times in backend and select the Configuration tab. Double-click on the IMG object PCUI_ESS_CATS_004. Start the customizing activity Define Field Selection. Which system is assigned to the customizing activity? Answer: __________________________________________________ What is the transaction code of the customizing activity? Answer: __________________________________________________

2.

a)

Answer: The system is RWE-801.

b)

Answer: The transaction code is CAC2.

In the customizing transaction, select Data entry section and choose Influencing. a)

Figure 445: Data Entry Section -> Influencing


2012


545


3.

E2E200

In the next screen, select entry Z-E2E-## (## = your group number) and press Enter. Customize the visible fields for data entry in transaction CAT2. Add the additional fields Accounting Indicator, Activity Number, and Activity Type (change the first three entries from Hide to Input). a)

Figure 446: Influencing Field

Save the changes in your customizing request. 4.

Go to transaction SE09 and release the task of your customizing request in the development client, RWE-801. In transaction SE09, select all modifiable customizing requests for your user. If there are several, look at the short text to find the one that you created. Navigate to the transport request and put the cursor on the task below the transport request. Choose the Release button to release the task. Note: You are not authorized to release the transport request itself from transaction SE09. This must be done in the Quality Gate Management application. a)


546


2012

E2E200


Task 3: Assign your transport package to your transport request and export it. 1.

Log on to the portal and navigate to the Transport Organizer Web UI. Preselect the transport request that you created for the portal. a)

Log on to the portal via the link: http://portal-rwe:50000/irj/portal with your user, E2E200-<##>. Select the Transport Management tab and the Transport Organizer page. Preselect the transport request you have created in the Quality Gate Management.



2012


547


2.

E2E200

Go to the Transport Package Editor and select the transport package that you created before in the CTS+ exercise. The name should be: Transport_Package_User_##. (## is your group number). a)

In the System Administration tab, choose Transport → Transport Packages → Export. Go to Browse the Portal Catalog and open Portal Content.

Figure 448: Portal Content

Select your transport package Transport_Package_User_##. 3.

Export the transport package to the transport request that you have created in the Quality Gate Management. Which export method is preselected? ______________________________


548


2012

E2E200


Which transport request is preselected? ____________________________ Note: The transport request contains the Time Recording workset. This was created in a previous exercise; therefore, it is already available. a)

Double-click on your transport package to open it.

Figure 449: Export

b)

Answer: The export method CTS is preselected.

c)

Answer: The transport request that you created should be preselected.

Figure 450: Start Export

Choose Start Export. If the export was successful, you will receive status information that the selected transport package was added to the related transport request.


2012


549


E2E200

Task 4: Release the transport requests in quality gate management. 1.

Release the portal transport request that belongs to your change. a)

In the work center, select your project and your change. Then select the portal transport request and choose Release Transport Requests.

Figure 451: Work Center- Release Transport Requests

2.

Release the ERP transport request that belongs to your change. a)

Select the related ERP transport request and choose Release Transport Requests.

Task 5: Rate the Build to Test quality gate. 1.

Open the Build to Test quality gate and set the Status set by: Quality Manager to Passed. a)

At the Quality Gates tab, select the Build to Test Q-Gate and choose Quality Gate Details. Set the Status set by: Quality Manager to Passed.


550


2012

E2E200


2.

Your neighbor acts as a member of the Quality Advisory Board. Ask him or her to set the Status set by: Quality Advisory Board to Passed. a)

At the Quality Gates tab, select the Build to Test Q-Gate and choose Quality Gate Details. Set the Status set by: Quality Advisory Board to Passed. Confirm the dialog box.

b)

In the System Landscape tab, your project should now look like this:

Figure 452: Details of Project(s)

Task 6: Import the transport requests into the test systems. 1.

Import the transport request for the portal into the test portal. a)

2.

Select your Quality Gate Management project, mark your change in the Changes tab. Then click on the button Manage Transport and select Import Transport Request of Change. On the next popup, select the CTS project RWS_P000## and mark the transport request for the portal. Click on OK to import the transport request immediately into the portal system JAQ.

Log on to the portal and check the fields of the Time Recording application. Which fields are available?


2012


551


E2E200

Answer: _____________________________________________________ a)

Log on to the portal. Navigate to your newly created role, Role_User_##, and then to the Working Time workset. Select the Record Working Time iView and check the fields.

Figure 453: Weekly View

The fields Att./abs. type and Total should be available. 3.

In quality gate management, go to the Risks tab and check the status of your change. Which risk is displayed? Answer: _____________________________________________________ a)

4.

Import the transport request for the ERP backend. a)

5.

Answer: The risk is Missing Synchronization.

Select your Quality Gate Management project, mark your change in the Changes tab. Then click on the button Manage Transport and select Import Transport Request of Change. On the next popup, select the CTS project RWE_P000## and mark the transport request for the ERP backend. Click on OK to import the transport request immediately into the client RWE-802.

In the portal, check again the fields in the Time Recording application. Logon again to the portal or press the Refresh button of your browser. Which fields are available after the import of the ERP transport?


552


2012

E2E200


Answer: _____________________________________________________ a)

Navigate to your newly created role, Role_User_##, and then to the Working Time workset. Choose the Record Working Time iView and check the fields. Compare the fields before and after you import the transport request in the ERP system.

Figure 454: Weekly View

You should now see the additional input fields Activity Number, Activity Type and Accounting Indicator, that you have customized before in transaction CAC2.

2012


553


E2E200

Lesson Summary You should now be able to: • Know, how to synchronize projects across the ABAP and Non-ABAP system landscape. • Create and release transport requests centrally in SAP Solution Manager for ABAP and non-ABAP environments. • Know, how to avoid and manage risks of application changes in a project. • Understand Best Practices that are used with the central Transport Management in combination with Quality Gate Management tool.

554


2012

E2E200

Lesson: 547

Lesson: (Appendix) Prerequisites to Set Up Quality Gate Management

(Appendix) Prerequisites to Set Up Quality Gate Management Lesson Duration: 20 Minutes

Lesson Overview You are going to use quality gates (Q-Gates) to indicate the end of a phase in SAP Solution Manager and to release the next phase of your project. This means that the import of transport requests is not possible until the Q-Gate immediately preceding it has been passed. Within this lesson you will find useful information about prerequisites regarding your transport landscape to set up QGM.


Know how to setup the transport parameter for a java system. Know about the importance of logical components in QGM.

Business Example You are interested to know how your TMS landscape could be used to include your SAP Portal within Quality Gate Management.

2012


555


E2E200

(Appendix) Prerequisites to Set Up QGM

556


2012

E2E200


Figure 455: Parameter CTS_SYSTEM_TYPE for Single JAVA Stacks

•

Required CTS settings: – –

•

Check or create transport routes between DEV → QAS → PRD If necessary, create a domain link between the SAP Solution Manager domain and the target system domain. Required Transport Parameters

•

– CTC = 1 (for ABAP and Double Stack Systems only) – Import_Single_Only=1 – Import_Single_Strategy=1 – No_Import_All=1 – Worklow_Strategy=0 Required Transport Parameters for JAVA standalone systems

•

– CTC = 0 – CTS_SYSTEM_TYPE = JAVA Required Transport Parameters for for the Transport Organizer –

• • •

2012

WBO_GET_REQ_Strategy: TAGGED (only for exclusive Q-Gate Management usage) – WBO_REL_REQ_Strategy: MANUAL After a landscape fetch, the CTS+ communication system will appear in SMSY. In transaction SOLAR_PROJECT_ADMIN an IMG project will be created for the Non-ABAP system in the CTS+ communication system. For more information, refer to the online documentation at http://help.sap.com → SAP NetWeaver 7.1 (or below) → SAP NetWeaver Library → SAP NetWeaver Key Capability → Software Lifecycle Management → Software Logistics → Change and Transport System


557


E2E200

Figure 456: Users in Satellite Systems: Client-Specific Transport Authorization Checks

Before setting up QGM please review the following SAP note: Note 1509091 - QGM: General note for Quality Gate Management 7.1. It is also possible to trigger the import directly for into the target client without using client 00 by applying SAP note 1384598 - Harmonizing RFC communication infrastructure for QGM/ChaRM.

Figure 457: Logical Components

558


2012

E2E200


Logical Components serve here as representative for the TMS track within the managed system. Before you could use them you have to check or to create Server, Database, Systems (T-Code : LMDB, SMSY) and to check or to create RFC Destinations (RFC Read Access, Trusted System RFC). Before ST-PI, SP4 please consider carefully SAP note 1572183 - Authorizations for SAP Solution Manager RFC user.

2012


559


E2E200

Lesson Summary You should now be able to: • Know how to setup the transport parameter for a java system. • Know about the importance of logical components in QGM.

560


2012

E2E200

Unit Summary

Unit Summary You should now be able to: • Explain the concept of solution transports and track synchronization with Quality Gate Management in SAP Solution Manager 7.1 • Describe the tasks of a quality manager • Know, how to prepare the solution Landscape to be able to work with Quality Gate Management • Explain, how to set up the Quality Gate Management • Explain the difference between implementation and maintenance projects and their phases • Know, how Quality Gate Management can support in each project phase. Also, by operating with projects running in parallel. • Know, how to synchronize projects across the ABAP and Non-ABAP system landscape. • Create and release transport requests centrally in SAP Solution Manager for ABAP and non-ABAP environments. • Know, how to avoid and manage risks of application changes in a project. • Understand Best Practices that are used with the central Transport Management in combination with Quality Gate Management tool. • Know how to setup the transport parameter for a java system. • Know about the importance of logical components in QGM.

2012


561

Unit Summary

562

E2E200


2012

Unit 8 Change Request Management

555

Unit Overview Within this unit you will learn how the Change Request Management process works. You will see how to use the SAP Solution Manager system for the Change Request Management scenario and you will be able to describe the various elements of Change Request Management as part of SAP Solution Manager. Additionally you are able to describe SAP’s best practices in transport management that are implemented in the SAP Solution Manager.

Unit Objectives After completing this unit, you will be able to: • • • • • • • • • • • •

2012

Know the technical basis of SAP Solution IT Service Management. Understand the Change Request Management integration into Application Lifecycle Management. Know the different user roles for Change Request Management. Understand the Change Request Management process. Understanding Project and Release Management with SAP Solution Manager. Know how to classify changes to different change types. Explain the relationship between Solution Manager Project and Project Cycle. Understand how the request for Change process. Learn about the usage of CRM Master Data. Know the Web Client UI for Change Request Management. Understand which project and process types are to be used with Change Request Management. Know the project and maintenance phases.


563

Unit 8: Change Request Management

• • • • • • • •

E2E200

Know the benefits for ALM integration with Change Request Management. Understand how Quality Gate Management integration is working. Understand how the integration of Enhanced Transport Management system and Change Management is working. Know how to monitor, track and report the transport requests/change documents. Use the Cross System Object Lock. Understand how the retrofit process in Change Request Management works. Know how to use the reporting functionalities in ChaRM. Know how the possible status within a normal change.

Unit Contents Lesson: Overview...............................................................565 Lesson: Project and Release Management .................................573 Lesson: Request for Change..................................................581 Exercise 17: Request for Change ........................................597 Lesson: Project and Process Types..........................................606 Exercise 18: Normal Change .............................................633 Lesson: ALM Integration .......................................................642 Lesson: Tools....................................................................654 Exercise 19: Reporting ....................................................671 Lesson: (Appendix) Change Request Management .......................677

564


2012

E2E200

Lesson: 557

Lesson: Overview

Overview Lesson Duration: 30 Minutes

Lesson Overview This lesson will give you an overview about the Change Request Management with SAP Solution Manager.


Know the technical basis of SAP Solution IT Service Management. Understand the Change Request Management integration into Application Lifecycle Management. Know the different user roles for Change Request Management. Understand the Change Request Management process.

Business Example You are using already the Solution Manager to transport changes along your system landscape. But the changes and transports are documented in excel sheets. You want to document changes that refer to corresponding transport requests. A change management integration into other Applications Lifecycle scenarios is desired e.g. regarding Test Management.

2012


565


E2E200

Change Request Management- Overview

Figure 458: Change Control Management- The whole is more than the sum of its parts

The scope of Change Request Management with SAP Solution Manager is to establish one tool and process to manage transports via SAP Solution Manager and manage and control the transport activities via phases of your project.

Figure 459: Integrated IT Service Management and Application Lifecycle Management

IT Service Management Integration

566


2012

E2E200

Lesson: Overview

SAP Solution Manager integrates Application Lifecycle Management and IT Service Management processes on a single platform. IT Service Management at SAP Solution Manager System is based on the SAP CRM 7.0 Ehp1. Manage IT and optimize business Main goals of IT organizations are to run SAP solutions efficiently and to help innovate and improve your business. You will learn how both of these goals can be achieved synchronously. This will optimize the value that IT provides for your business. Besides improving the efficiency of individual application lifecycle management (ALM) processes, it is important to integrate ALM with related areas like identifying improvement potentials for your business processes, managing your project portfolio, or running SAP IT Service Management. The whole solution is orchestrated around SAP Solution Manager.

Figure 460: Change Request Management embedded in Application Lifecycle Management

Change Request Management (ChaRM) strengthens the strategy of SAP Solution Manager as SAP’s application management platform which • • •

Ensures reliability. Reduces Total Cost of Ownership and increases Total Solution Value. Bridges the gap between business requirements and IT administration.

ChaRM provides full control & transparency over change execution and delivers predefined change management processes & workflows. It incorporates SAP’s best practices regarding transport management.

2012


567


E2E200

The transport mechanism and change control system is fully integrated to manage changes across technology stacks and application components.

Figure 461: Roles in Change Request Management- In a Nutshell

The change management processes are performed by different users with specific authorizations.

568


2012

E2E200

Lesson: Overview

Responsibilities: •

•

•

Requestor: To describe the change required in detail. To identify the priority of the request and describe why the capability is needed, and to identify the impact if the desired capability is not provided. Service Desk Employee: To act as the central point of contact between the users and IT Service Management. To handle incidents and requests, and provide an interface for other activities, such as Change, Problem, Configuration, Release, Service Level, and IT Service Continuity Management. Change Manager: –

• •

•

2012

To ensure that standardized methods and procedures are used for efficient and prompt handling of all changes, in order to minimize the impact of any related incidents on service. – To accept, or reject requests for change. – To monitor the Change Management process. – To release changes for production. Developer: To implement and document a change in the development system, to provide adequate test cases, or update existing ones. Tester: To follow instructions in the relevant test cases and make sure that the change has been promoted correctly into the consolidation environment. If a change causes incidents in the consolidation environment, it is the tester’s duty to set the status of the change back to “In Development”. IT Operator: To provide support if the Change Management process is impeded in any way. To import the change into the production environment.


569


E2E200

Figure 462: One central process to control change execution

Request for Change A request for change is a transaction you use to request a change of your software or a company system, for example, an enhancement or change to a function. A request for change can also be triggered by a problem message. It must pass through an approval process before a change can be made. You can categorize a request for change with regard to the type of change, for example, as a normal change, urgent change or general change. When request for change is approved by a change manager or another employee, change documents are created from the request for change and linked to it.

570


2012

E2E200

Lesson: Overview

Change Transaction / Document •

•

• • • •

2012

A change document is a transaction that documents the activities of the users that are involved in the change process, for example, developers, testers, and IT operators. A change document can be generated automatically by the system as soon as a change manager or another responsible employee approves the scope of a request for change and releases the scope content (different types of change documents) for development. In the work steps following the approval of the request for change, the change document forms the operational basis for developers, testers, and IT operators and passes through different phases, which depend on the type of the change document. You select the appropriate change document depending on the type of change. You can define your own change document types using customizing avenues of Solution Manager or use the change document types supplied by SAP. By default, the following transaction types are available for use. You can copy the transaction types and adapt them to your requirements: Change document Type

Transaction Type

Normal change

SMMJ

Urgent change

SMHF

Administrative change

SMAD

General change

SMCG

Defect correction

SMTM


571


E2E200

Lesson Summary You should now be able to: • Know the technical basis of SAP Solution IT Service Management. • Understand the Change Request Management integration into Application Lifecycle Management. • Know the different user roles for Change Request Management. • Understand the Change Request Management process.

572


2012

E2E200

Lesson: 565

Lesson: Project and Release Management

Project and Release Management Lesson Duration: 30 Minutes

Lesson Overview This lesson will give you an overview about Project and Release Management with SAP Solution Manager.


Understanding Project and Release Management with SAP Solution Manager. Know how to classify changes to different change types. Explain the relationship between Solution Manager Project and Project Cycle.

Business Example You have multiple development projects in parallel. The challenges is now to bundles changes which belong together in releases. These releases have to be controlled and monitored together via project phases like Test phase or Go Live phase.

Project and Release Management

Figure 463: Project & Release Management- End-to-End Change Control

Change Control

2012


573


E2E200

During the software lifecycle, changes of different types, risk/impact and criticality will need to be developed, tested and imported into production In order to manage all those changes in terms of control and documentation a well defined strategy is required supported by Change Request Management • •

•

This process controls changes in all projects types, such as implementation, template or upgrade projects, in a comprehensive workflow. You create requests for change, you edit them, and implement changes. You can perform the Change Request Management activities across systems and components. The administration of the change control comprises the following capabilities:

Enhanced Change and Transport System: •

Allows you to transport Java objects and SAP-specific non-ABAP applications in the system landscape, as well as ABAP objects.

Quality Gate Management: •

Provides a phase-based overview of the status of your software change projects. The project phases end in quality gates. Releasing a quality gate triggers transports into subsequent systems.

Change Request Management: •

Allows you to process your projects universally in SAP Solution Manager: from Change Management and project planning, through resource management and cost control, to the physical transport of the changes from the development environment into the production environment.

Figure 464: Project & Release Management- Release Strategy

Release Management Release Management is a strategy of managing software changes. The basic concept of Release Management is a bundling of changes based on certain criteria e.g. priority, type or impact and a controlled delivery. Note: Improved controlling and testing of changes up to production

574


2012

E2E200


Bundled changes (change types) belong to an overall release definition: • • • •

Major change Minor changes Low Impact changes Urgent changes

Content of a Release A release can contain changes of one or more change types. All changes belonging to one release will be handled as one entity in terms of documentation, integration testing and final transport into a production system. Using different change types guarantees the right control and testing approach for each change type. Release Strategy To manage changes different possibilities and strategies exist – from a permanent flow of changes up to a strict Release Management. A strict bundling of changes into different releases including various change categories/types enables an effective Quality Management process and reduces the frequency of importing changes to production. This is SAP’s recommended approach.

Figure 465: Project & Release Management- Import into Production

Import into Production Each release contains different types of changes which will be processed during the release cycle (e.g. one month). A release cycle usually consist of a Development, Test and Going Live Phase. All changes are transported together into production at the end of the release cycle (e.g. end of the month), before the next release starts. Only exception exists for urgent changes. This will be imported twice into production since it will stay in the import buffer until the whole project will be important. By doing so the right sequence of transports is secured.

2012


575


E2E200

Advantages of Bundling Changes to Releases Frequency of changes to production is dramatically reduced • •

End users will not be confused by frequently changed functionality The rollout of new functionality can be done in a controlled way, including announcement, end user training, testing and documentation

For each type of change the right testing approach is taken •

• • •

Enough time for testing invasive changes in major changes Common regression and integration testing for several projects in one run – resulting in lower cost and reduced risk (dependencies are taken into account) Appropriate tests and infrastructure for testing minor changes Reduction of daily changes to the absolute emergencies No restriction to non-invasive standard changes (can be imported as needed – without impacting stability/consistency of the landscape → maximum flexibility)

The risk of inconsistencies (“forgotten transports” or sequence violations) is reduced Reduced administration efforts for transport management as all projects move from one phase to another at a single point in time Using change categories consequently still allows flexibility for urgent changes.

Figure 466: Usage of Projects

Usage of Projects

576


2012

E2E200


In some cases bundling of changes into releases slows down the realization time of changes. This leads to the parallel project approach. Advantages of using projects are: • • •

Comprehensive customizing and development activities are grouped together Basis for Release Management Better planning of resources

Release Management with SAP Solution Manager: Change Request Management Change Request Management workflows are based on best practices of how to manage short-term changes, maintenance projects, and new implementations. • • • •

Urgent changes for immediate change Normal changes for mid-term and long-term changes Maintenance projects for housekeeping activities Implementation projects for new implementations

Figure 467: Solution Manager Project Is Enhanced by the Project Cycle

Solution Manager Project SAP Solution Manager projects can be extended by adding project cycles that control project phases. Project phases determine whether or not transport requests can be created, released, or imported. Project phases are visible in the blueprint and configuration transactions. cProjects can be used to extend project management capabilities and to manage multiple phase-specific projects. Project Cycle:

2012


577


E2E200

Controls the following activities in change control management over the whole duration of a project: • • •

Requests of change and the resulting changes in the systems that are used in your project Transporting changes to the follow-on systems Change logistics, that is, which transports can be transported into the follow-on systems at which point in time

You create a project cycle for implementation, maintenance, and template projects. From a technical perspective, the project cycle is a preconfigured service transaction (delivered by default as transaction type SMDV). The maintenance cycle is a special type of project cycle where it is possible to pass through the stages several times. It is created for maintenance projects. You always create a project cycle for a project if you want to work with change transactions. You use the project cycle to control which changes activities are permitted in which phase. The project cycle phases determines the sequence of tasks in task lists. Through its phase structure, the project cycle offers an operational enhancement to the project plan. Phases in the Project and Maintenance Cycle: The phases in project and maintenance cycles define which activities are permitted as part of change control. Each phase in the project and maintenance cycle corresponds to the status defined in the status profile for the corresponding transaction types. You configure these settings in transaction SPRO → SAP Preference IMG → SAP Solution Manager Implementation → SAP Solution manager → Capabilities (Optional) → Change Management → Standard Configurations → Transaction Types → Status Administration → Define Status profile for User Status. Phase structure:

578


2012

E2E200


Project and maintenance cycles have the following standard phases: • •

Created In Development w/o Release – –

•

A transport request can be generated but not released. Use this phase if developments are not to be transported to the test system straight away. In Development with Release –

•

You can only release transport requests once you have reached this phase. It is initiated by the change manager or the change advisory board and allows you to release transports and to import them into the test system for developer tests.

Test –

•

Once changes to the project have been imported into the test system, this phase can start and integration testing can commence. Using defect corrections, you can only eliminate errors that have occurred during testing. Go Live Preparation

– •

Users with the corresponding authorizations can make additional required changes. Go Live

–

All changes that were successfully tested in the test phase are imported into the production system.

You can display the phases in the Project Phases assignment block of the Service Desk transaction. The current phase for the cycle is highlighted. You change the phases and therefore the status of the cycle by choosing Actions. To switch from one project phase to the next, you should use only the required action in the project or maintenance cycle. You can use the task list to switch project phases, but recommended way is to use corresponding Service Desk transaction. Example: In a three-system landscape, all transport requests for urgent changes that have the To Be Tested status are in the import buffer of the production system. If you switch the phase in the task list and not in the maintenance cycle, the system does not issue a warning, and the urgent changes would be imported into the production system without being tested. If you switch the phases of the maintenance cycle, the transport requests are checked. The user is therefore aware of the situation and can act accordingly.

2012


579


E2E200

Lesson Summary You should now be able to: • Understanding Project and Release Management with SAP Solution Manager. • Know how to classify changes to different change types. • Explain the relationship between Solution Manager Project and Project Cycle.

580


2012

E2E200

Lesson: 573

Lesson: Request for Change

Request for Change Lesson Duration: 30 Minutes

Lesson Overview This lesson will give you an overview about the Request for Change with SAP Solution Manager.


Understand how the request for Change process. Learn about the usage of CRM Master Data. Know the Web Client UI for Change Request Management.

Business Example A software change should be done in the landscape to fix a issue or enhance functionality. Before a change can be done you have to document the requirements. Afterwards the responsible person has to approve the change before the development can be started.

2012


581


E2E200

Request for Change

Figure 468: What Happens Without Change Request Management?

• •

•

IT organizations continue to face pressure to deliver on high business demand. With increased business and IT complexity, reduced resources, distributed teams, and regulatory / sustainability constraints, IT organizations need better planning? But how do IT organization identify the priorities?

Extreme Pressure on IT to Delivery • • • •

582

Increase business and IT complexity. Reduced resources. Distributed teams. Additional regulatory and sustainability.


2012

E2E200


Change Process

Figure 469: Request for Change with new process

The new standard process for request for change shows some new features like: • • • •

New status for validation of RfC by change manager. Approval procedure with SAP workflow integration. New status while RfC is being implemented. Possibility to extend the scope of a request for change.

Figure 470: Process Details Change Request Management- Request for Change

2012


583


E2E200

Processing a request for change. The process describes how you can create, edit, approve, and implement request of change in the context of a maintenance cycle or implementation project. With this process and the documentation of all related tasks, you can find out at any time where a request originated, who implemented it and when the change was implemented in a production environment. Prerequisites: • •

•

You have already performed the customizing settings under the transaction SPRO. The users involved in the change management process have the required authorizations. The system administrator has created user roles that include these authorizations and assigned these roles to the respective users. These roles were created in SAP Solution Manager and in the managed systems. For more information, see the Security Guide for SAP Solution Manager on the SAP Service Marketplace at http://service.sap.com/instguides --> SAP Components –> SAP Solution Manager . On the right side you find it under point 4 Operations. You have created a project in SAP Solution Manager, activated Change Request Management for the project, and generated a project or maintenance cycle.

Figure 471: Creating and Approving a Request for Change in SAP Solution Manager

A request of change can be created out of an incident or a problem or directly as a request for change.

584


2012

E2E200


RfC Process •

• • •

•

•

•

•

•

2012

A processor in the department discovers a required change in a transaction that is used, for example, an error or a missing function. This processor can now create a support message directly from the transaction, allowing him to describe the situation and request a change. The message appears in the work list of a service desk employee who processes the message and creates a request for change. In SAP Solution Manager, he/she opens the Change Management work center or starts CRM Web Client UI directly using transaction SM_CRM. The service desk employee can create the request of change from scratch or reference an existing template from which the available information can be copied. The system forwards the request of change to the change manager. He/she can see the requests of change and change documents for which he/she is responsible in the Change Management work center or CRM Web Client UI. The change manager is responsible for prioritizing the request according to its impact (for example, high, medium, or low) and to define its scope. He or she also specifies for which systems the change is relevant. The type of the change document determines the definition of the scope. You can define your own change document types using the customizing possibilities of Solution Manager or use the copies of the change document types supplied by SAP: – Normal change. – Urgent change. – Administrative change. – General change. – Defect correction. The change manager assigns the request of change to a project and, optionally, a solution for documenting the changes. The change manager can also assign various documents, test cases, and additional information relevant to the change process, such as which business process is affected. If the error is serious enough to justify implementing a correction, the request of change is released for approval. The scope of the request for change must be approved before a change document defined in the scope will be generated. In the standard system, the change manager is entered as the approver – however, if required, you can also enter an additional business partner (such as the change advisory board). In the following work steps, the change document forms the operational basis for developers, testers, and IT operators and passes through different phases, which depend on the type of the change document.


585


•

• •

• •

E2E200

A request for change can still be changed or extended after its approval. You can add further documentation or extend the scope by adding a complementary change transaction, for example. The change document appears in the work list of a developer who implements the change and releases it for testing. All users involved in the change process can navigate from the change document to the corresponding target systems in the maintenance or project landscape. The developer can switch the status of the change document he or she is working on and certain actions have to be carried out, such as the release of a transport request. Depending on the type of change document, these actions are carried out either automatically when a change is saved for example, in case of urgent change, or explicitly by the IT operator, for example, in case of a normal change. As soon as the tester confirm successful end of the test activities, the change can be transported through the system landscape to the production system. The change manager completes the request of change. If all change documents for a request of change have been fully processed, the request of change is also completed.

Master Data

Figure 472: Master Data- IBase Management: IBase Information

Installed Base An installed base represents the collection of products that a particular customer has purchased. It is used to track and maintain products for which service must be rendered. It contains information about the serviceable items and other supporting information relevant to a service scenario.

586


2012

E2E200


Installed bases are used for managing objects that are installed (or are going to be installed) at the customer’s site, for example devices, machines, or software. An installed base describes the hierarchical structure of these objects and their individual parts (components), and can be the reference base for services.

Figure 473: Master Data- IBase Management: Installed Base (IBase)

Data integration for IBase More information about SAP ERP Asset Management integration you can find here: http://help.sap.com/saphelp_crm700_ehp01/helpdata/en/c8/81019f46894b5fb841a373a5639ed4/frameset.htm More information about CMDB you can find here: https://websmp204.sapag.de/~sapidb/011000358700000197002011E.pdf.

2012


587


E2E200

Figure 474: Master Data- IBase Management: SAP Systems in IBase as Installed base components

Installed base component An installed base components is used to describe a system landscape / reference systems which, for example can be the source of a request for change. Individual elements of an installed base at the customer site that contain service-relevant information can be referred to in business processes. All components for an installed base are arranged in a structure. An object becomes a component of this installed base by being included in an installed base structure. You can assign additional objects to each installed base component. In this way, an installed base can be organized hierarchically and on multiple levels.

588


2012

E2E200


Figure 475: Master Data- Business Partner Person, Group and Organization

The classification of a business partner as a natural Person (for example, a private person), Group or Organization (legal person or part of a legal person) is called the business partner category. The above mentioned business partner categories are delivered for SAP systems. Additional categories cannot be defined. The Organization represents units such as a company, a department of a company, a club, or an association. In addition to a legal person, parts of a legal person can be mapped as a business partner. Organization is an umbrella term for mapping every kind of situation in the day-to-day business activities. Therefore, a branch or purchasing department, for example, represents just parts of a legal person. A Group specifies a shared living arrangement, a married couple, or an executive board. For SAP Solution Manager scenarios this category is of lower importance. The business partner category cannot be changed after a business partner has been created/saved. For general Business Partner settings choose the following IMG path: SAP Solution Manager → Implementation Guide → SAP Customizing Implementation Guide → Cross-Application Components → SAP Business Partner

2012


589


E2E200

Figure 476: Master Data- Partner Function filled in by Business Partner

A Business Partner represents a person or organization which can be used as an identification within a Partner Function. By maintaining a business partner in a partner function you identify for each transaction which user or organization is currently acting in this partner function (role). The change management process are performed by different user role with specific authorization. These user roles are represented by Partner Function, for example developer, change manager, tester etc.

Web Client UI

Figure 477: Web Client for Change Management- User access to system and Web Client UI

Preconfigured Change Management composite roles for the different user views (requester change manager, developer, tester) are available. CRM Business Role

590


2012

E2E200


It describes the user interface of SAP CRM and displays the functions in the CRM Web Client. The most important business role in SAP Solution Manager is “SOLMANPRO” (IT Service Management). It can be assigned to end-user via: • • •

SU01 using parameter CRM_UI_PROFILE. Organizational model (HR-ORG). PFCG role which is linked to a business role.

A user can have multiple business roles. With the help of this Business Role SOLMANPRO, it is possible to: • •

Control structure of navigation bar and the logical links in the CRM Web UI Define which links are available on the Work Center pages and the Direct Link group

Figure 478: Authorization for Change Management- Web Client UI Authorization Roles

Note: The SAP_SM_CRM_UIU_* roles only control UI visibility and navigation. Users need standard roles for other authorizations (create, change, etc.)

2012


591


E2E200

Figure 479: Web Client UI for Change Request Management- Request for Change

Creating a Request for Change Open CRM Web Client UI using transaction SM_CRM and in the Create section choose Request for Change. Make an entry in the mandatory fields, or choose an appropriate option: • • •

Description Customer Reporter This field should be prefilled with your business partner, but you can change it.

•

Change Manager Enter the business partner of the change manager responsible for approving or rejecting the request.

•

Approval Procedure By default, the Change Request Approval Procedure is selected. On the Text assignment block, describe the change to be implemented. Choose Save.

592


2012

E2E200


Request for Change supports multiple change documents • • •

Definition of scope for a request for change scope is done via scope assignment block. All kinds of change documents can be combined without restriction. Scope assignment block gives instant overview about all change documents and their status.

Figure 480: Assign Business Process Structure and Documents for Request for Change description

Document the request for change with more information about what and where should be changed. • • •

2012

Assign the process documentation. Assign project information. Assign business process structure.


593


E2E200

Figure 481: Request for Change- Approval Procedure

Starting the Approval Process and Approving a Request for Change A request for change, has been validated by a change manager, who has also added more information to it. It now needs to be approved in order follow-on change documents will be generated by the system. Using Approval Procedures You can use approval procedures to control the approval process for request for changes. In an organization, certain processes must be approved by responsible persons before they can be finalized. Approval procedures can be edited manually or integrated into the workflow. For all information relevant to the approval of a request of change, see the Approval assignment block of the respective request of change. Using the customizing possibilities of Solution Manager (available via transaction SPRO) you can maintain the approval settings for your change process.

594


2012

E2E200


Features: •

•

In the header data of the change request, you assign the approval procedure. By default, the approval procedure Change Request Approval Procedure is suggested for use. The following functions are available in the Approval assignment block: –

• •

You can monitor the approval steps and the corresponding information. For example, you can see which business partner has approved the respective step and when the approval took place. – The change manager is entered as the approver by default. You can also add other approvers. – The parties involved in the change request enter their approval activities. Here, the options Approved, Not Relevant, and Rejected are available. The approvers can add additional comments to the activity, for example, explanations of a rejection. – As long as the status of the request of change has not been set to Approved, you can add additional or remove existing approval steps and approvers. In the Change Management work center, you see the requests of change awaiting approval that are assigned to you. You can use workflow functions for the request of change approval process so that approvers are informed when requests of change should be approved.

Activities: • •

•

A service employee creates a request of change and the change manager classifies it, for example, as a normal change. The change manager checks the request and defined change documents and releases it for approval. The request of change has the status To be Approved. The system thus starts the approval procedure. As soon as all approval steps have been completed, the request of change has the status Approved and after the change manager set the status of the request for change to “Release for Development”, the change documents are generated.

(System Demo) Create a Request for Change

Recommendation: Use the new CRM Web UI instead of the Work Center to perform your change transactions.

2012


595


596


E2E200

2012

E2E200

589


Exercise 17: Request for Change Exercise Duration: 15 Minutes

Exercise Objectives After completing this exercise, you will be able to: • Create and approve requests for change. • Provide documentation in a request for change.

Business Example RWS is the SAP Solution Manger system which contains all information about the system landscape. RWE is an ERP system which is managed by RWS.

Task 1: Create a request for change. Describe your requirements. In this part you are acting as a Requester. 1.

Exercise preparation: Before to start with the exercise, activate Change Request Management functionality for a project.

2.

Log on to the SAP Solution Manager system and open Solution Manager IT Service Management (ITSM) using transaction SM_CRM.

3.

In the ITSM Web UI create Request for Change using the corresponding link in the Create section on the left hand side.

4.

Maintain the General Data in the Details assignment block.

5.

In the Change Planning block on the right hand side, choose Approval Procedure Change Request Approval Procedure.

6.

Maintain a Description of Change in the Text assignment block.

7.

Save your request for change and go back. Write down the number of the request for change.

Task 2: Find the request for change and take it into process. In this part you are acting as a Change Manager. 1.

Log on to the system and navigate to the ITSM Web UI using transaction SM_CRM.


2012


597


E2E200

2.

In the ITSM Web UI use one of the search functions to find the request for change you created as a Requestor

3.

Open the request for change by clicking on its ID.

4.

Switch into edit mode.

5.

Enter a project into the Change Planning box and Execute action Check Request for Change via Actions button on top menu.

6.

Execute action Validate Request for Change and save request for change.

7.

Go to the Change Request Scope assignment block and choose Edit. Press the Insert button, select change category Normal Change and add Installed Base 1 and the component 174, for the production client 803 of RWE system. Save your Request for Change.

8.

Execute action Release for Approval and save it.

9.

In the Approval assignment block, approve the Normal Change and save it.

10. Execute the action Release for Development and save your changes. 11. Check, that the Normal Change was created successfully and write down its ID. 12. Go into your normal change and maintain all necessary information, such as description and responsible employees.

598


2012

E2E200


Solution 17: Request for Change Task 1: Create a request for change. Describe your requirements. In this part you are acting as a Requester. 1.

2.

Exercise preparation: Before to start with the exercise, activate Change Request Management functionality for a project. a)

Call transaction SOLAR_PROJECT_ADMIN and double click on the project that was created by you in the solution documentation unit on the 1st day or by your instructor.

b)

Navigate into the System Landscape tab and Change Management sub-tab.

c)

In the Change Request Management block choose Activate Change Request Management and confirm the system message asking you, whether you really want to change this field.

d)

Click on the Create Task List button and provide a name for your project Cycle.

e)

Navigate into the Task List and unlock project trucks for JAD and RWE by clicking with the right mouse button on the each of them and choosing Lock/Unlock Group/Subsequent groups.

f)

Click on the Phase button and switch the project phase to Development with Release.

g)

Save the changes and leave the Task List.

Log on to the SAP Solution Manager system and open Solution Manager IT Service Management (ITSM) using transaction SM_CRM. a)


2012


599


3.

E2E200

In the ITSM Web UI create Request for Change using the corresponding link in the Create section on the left hand side. a)

Figure 482: SAP Solution Manager IT Service Management

4.

Maintain the General Data in the Details assignment block. a)

5.

Write a short description for the change and search for your user (F4 help) in the partner functions fields Customer and Change Manager. The Reporter field will be fulfilled automatically with your user name.

In the Change Planning block on the right hand side, choose Approval Procedure Change Request Approval Procedure. a)

6.

Maintain a Description of Change in the Text assignment block. a)

7.

Go to the Text assignment block, select Add Text and maintain Description of Change.

Save your request for change and go back. Write down the number of the request for change. a)

Request for Change number: __________________________________


600


2012

E2E200


Task 2: Find the request for change and take it into process. In this part you are acting as a Change Manager. 1.

Log on to the system and navigate to the ITSM Web UI using transaction SM_CRM. a)

2.

In the ITSM Web UI use one of the search functions to find the request for change you created as a Requestor a)

In the ITSM Web UI you can find your request for change. Select Change Request Management menu on the left hand side and choose Requests for Change.

b)

Figure 483: Request for Change

Find your request for change using search criteria (e.g. by its number). 3.

Open the request for change by clicking on its ID. a)

4.

Switch into edit mode. a)

Switch into Edit mode by choosing

.


2012


601


5.

E2E200

Enter a project into the Change Planning box and Execute action Check Request for Change via Actions button on top menu. a)

6.

Execute action Validate Request for Change and save request for change. a)

Execute action Validate Request for Change via Actions button and save request for change. The status of your request for change will be automatically set to the value Validation.

Figure 484: Processing Data

7.

Go to the Change Request Scope assignment block and choose Edit. Press the Insert button, select change category Normal Change and add Installed Base 1 and the component 174, for the production client 803 of RWE system. Save your Request for Change. a)

Figure 485: Change Request Scope

8.

Execute action Release for Approval and save it. a)

Execute action Release for Approval via Actions button and save it again.

Figure 486: Actions

b)

The status of your Request for Change will automatically be set to value To be Approved.

Figure 487: Actions


602


2012

E2E200


9.

In the Approval assignment block, approve the Normal Change and save it. a)

Go into the Approval assignment block and choose Edit List. Change entry Activity to Approved and save it.

Figure 488: Approval Block

b)

The status of your request for change will be automatically set to value Approved.

Figure 489: Processing Data

10. Execute the action Release for Development and save your changes. a)

Once status is Approved Change Manager has to execute action Release for Development via the Actions button and save the changes.

Figure 490: Actions

b)

The status of your request for change will automatically be set to Being Implemented. The Status of the normal change in the Scope assignment block is Created. You are able to navigate into the follow-up document by clicking its Object ID.

Figure 491: Change Request Scope

c)

Remark: In general, operational activities like triggering the creation of a change document in our case the creation of a Normal Change, are always linked to a certain status of the current request for change. This ensures consistency between the administrative view and the technical execution. Continued on next page

2012


603


E2E200

11. Check, that the Normal Change was created successfully and write down its ID. a)

Change document number: __________________________________

12. Go into your normal change and maintain all necessary information, such as description and responsible employees. a)

Go into your normal change by clicking on its ID and switch into the Edit mode. You can maintain a Description for your change document and assign responsible employees in the General Data area of the Details assignment block.

Figure 492: General Data

604


2012

E2E200


Lesson Summary You should now be able to: • Understand how the request for Change process. • Learn about the usage of CRM Master Data. • Know the Web Client UI for Change Request Management.

2012


605


Lesson: 598

E2E200

Project and Process Types Lesson Duration: 35 Minutes

Lesson Overview This lesson will give you an overview about the Project and Process Types for Change Request Management with SAP Solution Manager.


Understand which project and process types are to be used with Change Request Management. Know the project and maintenance phases.

Business Example A software change should be done at the system to fix an issue or enhance a functionality for instance. Before a change can be done you have to document the requirements. Afterwards the responsible person has to approve the change before the development can be started.

606


2012

E2E200

Lesson: Project and Process Types

Project and Process Types

Figure 493: Change Request Management- Transaction Types

Transaction Type Change Request Management is processes technically based on transaction types, each process (urgent change, normal change etc.) has its own transaction type. Transaction types represent a set of different configuration settings. This set of configuration settings represents information and functions within a process. A transaction type defines properties and characteristics of a business transaction (for example sales order, service request) and specifies the control attributes (for example, text determination procedure, partner determination procedure, status profile, organizational data profile). A transaction type controls processing of a specific business transaction. New Transaction Types for Change Request Management 7.1 • • •

2012

As of SAP Solution Manager 7.1 completely new transaction types are available for Change Request Management. New transaction types can only be created and processed via the new CRM Web Client UI. All new functionalities and features are only available for new transaction types.


607


E2E200

Figure 494: Process Type- Supporting all types of changes

Normal Change A normal change is a project-based implementation of a new functionality, or new features for a specific process, for example, for bigger changes that are released on a quarterly basis. Usually, normal changes do not comprise bug fixes. Urgent Change An urgent change has to be imported into the production as quickly as possible and its main goal is the bug fixing in the productive environment. An urgent change can be described as the smallest subproject that could be transported and has its own cycle. This transaction is only permitted within a maintenance cycle. Admin Change An IT operator wants to initiate a change that does not have to be transported with a transport request, for example, an account number or number range change in a system. To do so, he or she creates an administration change. General Change You want to request a change that does not require a connection to the SAP Change and Transport System. This can be, for example, the repair of a printer or computer in your organization. Defect Correction During the test phase, errors are detected in the test systems, and are reported to the developers by defect corrections. The developers correct these errors. If all error messages have been closed, the maintenance cycle proceeds to the Go Live Preparation phase.

608


2012

E2E200


Figure 495: Implementation Project- Project Type - Project Cycle

The project cycle distributes consistently any change to any system of the project Landscape. One implementation project can have multiple systems assigned to it, including the corresponding transport routes (one logical system for Workbench requests and one logical system for Customizing requests, for example). A project cycle belongs to exactly one implementation, upgrade or template project. For Implementation, Upgrade and Template Projects, normal changes can only be approved during the project phase development w/o release and development with release. For these project types no urgent changes are possible. This is not necessary, because the new functionality is not yet life in production.

2012


609


E2E200

Figure 496: Project Phases - What Happens When?

610


2012

E2E200


Phases of a Maintenance / Project Cycle •

Created

•

– Initial status of a maintenance cycle In Development without Release –

•

Changes can be developed, and transport requests and transport tasks can be created. Exports, however, are not permitted (except in the case of urgent changes). Export of urgent changes are permitted in every phase except for the Go-Live phase. When using the normal change transaction (SMMJ), this phase is not recommended because transport of copies cannot be exported. In Development with Release –

•

Transport requests can be released from within a normal change. For normal change, the IT operator has to use the task list to import all released corrections into the test systems or he has to schedule regular import batch jobs in the satellite systems.

Test –

•

The test phase is necessary for integration and regression testing. No normal changes can be released any more, so a code-freeze can be guaranteed. To fix errors which occurred during the integration test, defect corrections have to be used. Urgent changes can be used as in the previous phase. Unfinished developments will not be included in the actual test and go-live, they can be included in the next test phase. Preparation for Go-Live –

•

If changes still have to be made after the test phase has been completed, transport requests and tasks can be created and released as part of the Preparation for Go-Live phase, but only by using the task list of the Schedule Manager. Go-Live –

•

Importing the entire project buffer into the production system. No type of changes can be released during this phase. Being Completed

–

•

If there are no open transport requests, the maintenance cycle can be closed by setting the status to To be closed. Subsequently, a new maintenance cycle can be created. Completed –

2012

Maintenance cycle is closed. No further changes in this maintenance cycle are possible.


611


E2E200

When completing the maintenance cycle all open requests and transactions will be decoupled from the task list. When generating a new task list for the same project, all open requests and transactions will be linked to this new task list and can be processed further.

Figure 497: Maintenance Project- Project Type - Maintenance Cycle

Definition of a Maintenance Project • • • •

The maintenance project is prerequisite for production support. A maintenance project manages maintenance cycles as long as defined by the project lifecycle. The maintenance cycle distributes consistently any normal, admin, in some cases general or urgent changes to any system of the project landscape. One maintenance project can have multiple maintenance systems assigned to it, including the corresponding transport routes (one logical system for Workbench requests and one logical system for Customizing requests, for example). A maintenance cycle belongs to exactly one maintenance project.

It is the central unit for all information, such as logical component and system landscape, and the high level project plan. It closes the gap between planning and software logistics: • • •

SAP Solution Manager project IMG project CTS project

Definition of a Maintenance Cycle

612


2012

E2E200


A maintenance cycle is the period of time in which you • • •

Make changes in maintenance systems Include these changes in new transport requests Import these requests into follow-on systems for testing

At the end of a maintenance cycle, all transport requests are imported into the production system at the same time. Subsequently, the maintenance cycle can be closed manually and a new one can be created, if necessary (but only in compliance with the rules of the change requests that belong to the maintenance cycle).

Figure 498: Maintenance Cycle- Urgent Change

Urgent changes are fast changes that have to be imported into the production environment as quickly as possible. An urgent change can be described as the smallest subproject of a broader maintenance project cycle. Urgent changes can be performed during the maintenance project phases “Development w/o release” up to “Go Live Preparation”. Urgent changes can be approved and developed but not exported during Go-Live Phase.

2012


613


E2E200

Figure 499: Process Details Change Request Management- Urgent Change

Urgent Change An urgent change is represented by a singular task list that is created when an urgent change is being generated by releasing the corresponding requests for change for development. An urgent change task list is closed when the urgent change is closed. An urgent change can be described as the smallest subproject of a broader maintenance project cycle. Technically, an urgent change is managed by “import subset” and is automatically merged into the current open maintenance cycle. Processing Urgent Changes This process makes urgent changes in your production system. This transaction is only permitted within a maintenance cycle. The urgent change is mainly used for fast implementation, for example, if you want to fix an error in existing functionality. The change is transported into the production system faster than a normal change. Pre- requisites A request for change has been created, its scope, including at least one urgent change, has been defined and approved. The request for change has been released for development and the change document of the type urgent change has been generated by the system. The request for change is linked to a maintenance project. Urgent changes can only be used in maintenance projects.

614


2012

E2E200


Process The change document is forwarded to the designated developer, who sets the status to In Development in the WebClient UI when he starts making the change. To do so, he chooses Action Set to “In Development”, and saves the change document. The developer creates a transport request in the Transport Management assignment block, and adapts the data in the popup displayed by the system. The developer logs on to the development system directly, in the Landscape assignment block. The developer makes the urgent change in the assigned development system, tests it, and releases his task in the transport request, in the Transport Management assignment block. The developer releases the transport request manually in the Transport Management assignment block. The transport is exported from the development system. No transport of copies is created, as in the normal change process. The developer forwards the urgent change to testing, by choosing Actions Pass Urgent Change To Test . He then saves the change document. The change document is now in status To be Tested and the transport is imported into the test system. The IT operator calls up the document from the Change Management work center, or from his work list in the WebClient UI. He assigns the document to a tester, who in turn can see it in his work center or work list. The tester (or another developer with a test user role) logs on to the designated test system via the Landscape assignment block, to check the urgent change. If the change contains no errors, the tester performs the action Confirm Successful Test in the change document, which is then in status Successfully Tested. If errors occurred during testing, the tester returns the change document to the developer, by choosing action Reset Status to In Development , so that the urgent change can be corrected. This new change has to be tested, and the process is repeated. The change manager approves the urgent change for import into the production system, by choosing action Release Urgent Change for Production , and forwards the change document to an IT operator. The status of the document is now Authorized for Production. The operator calls up the document via the work center or his work list in the WebClient UI. He triggers the import of the urgent change into the production system, by choosing Action Import Urgent Change to Production. The status of the urgent change is now Imported into Production.

2012


615


E2E200

The requester (or the change manager) confirms that the change has been made, by setting the status of the change document to Confirmed, using the action Confirm Urgent Change. And after that the change document can be completed via action Complete Urgent Change. The change document is now locked for editing, and the status of the request of change is updated to Implemented. This is only true if all follow-on change documents related to the request of change are in final status. The last change document related to a request of change that has the status Completed updates the request for change. •

•

•

Remark: To import a transport request for urgent changes into parallel systems, use the report /TMWFLOW/SCMA_BTCH_SYNC_TEST. For more information, see SAP Note 817289. After the transport request of the urgent change document is imported into the quality and production systems, the transport request remains in the import buffer, so that the changes are not overwritten by other transport requests in the normal change cycle. Remark: You can choose between two tasks list variants, with different transport sequences into the production system: Use SAP0 if there are urgent and normal changes in your landscape, and SAP1 if you use urgent changes only.

You make these settings in the project administration, on the Change Request Management tab page. If you want to set multiple change documents to the next status (from Approved for Import to Production, for example), execute the batch job CRM_SOCM_SERVICE_REPORT. You can also use this report to import all changes at a scheduled time, into the follow-on systems. (System Demo) Urgent Demo

616


2012

E2E200


Figure 500: Maintenance Cycle- Normal Change

The normal change relates to the life cycle of the project: statuses of a normal change depend on the phases of the project cycle. Each project can have as many normal changes as required. A normal change can be shared by multiple developers, and multiple transport requests and transport tasks can be created. A normal change phase depends on the phase of the project cycle. Normal changes can only be distributed using the import project method. • •

2012

Transport requests/tasks can be created and exported from within the Transport Management assignment block. Project exports and imports can be managed by the maintenance task list.


617


E2E200

Figure 501: Process Details Change Request Management- Normal Change

Normal Change A normal change is generated as a follow-up transaction by the “Release for Development ” activity. Normal changes are directly linked to a project cycle transaction and project cycle task list. From within a normal change, the creation of a transport request and transport task and the release of related transports are controlled by the request of change or normal change transactions. Imports are done by means of import projects from within the cycle task list. A normal change can be shared by multiple developers, and multiple transport requests and transport tasks can be created Processing Normal Changes You use this process to perform normal changes in your maintenance landscape, and to implement features in your development landscape. Pre-requisites •

•

618

A request for change has been created and in its scope one or more change documents of the type normal change have been defined. The scope of the request for change has been approved by responsible employee(s). The request for change has been released for development. To be able to process the normal change and to use the test transport functionality and to use the test transport functionality, the assigned maintenance cycle needs to be in the phase Development with Release.


2012

E2E200


Remark: If the phase is Development without Release, you cannot export anything except urgent changes. You can create transport requests and make changes in the development system, but you cannot release your original transport request or generate test transports (transports of copy). Process The lead developer who heads a team of developers calls up the change document from his work list in the Change Management work center or directly from the WebClient UI, and sets the status to In Development . The lead developer creates a transport request in the development system via the Transport Management assignment block. She adapts the relevant data in the popup, for example, the description for the transport request and whether it is a workbench or a customizing request. She additionally creates a task for each of the developers in her team. The developers log on to the development system via the Landscape assignment block. They implement the requested features in the development system. When the features have been implemented, the developer release their tasks in the transport requests in the transport organizer transaction (se09) in the development system. After the transport request task has been released, the developer can create a test transport using the corresponding button in the Transport Management assignment block. The transport of copy has been created and released automatically. The test transport will be imported into the test system with the next run of the background job or could be imported manually by developer or IT operator using the task list. The original transport request remains changeable and in case of negative test result the developer performs the correction and saves it in the newly created task of the same transport request. After the task is released the developer can generate a new test transport and the testing must be repeated. After all developers completed their activities and released all tasks in the original transport request, the lead of developer’s team performs the action “Pass Normal Change to Test ”and the test transport including all released tasks has been generated and released by the system. The status of the normal change becomes “To be Tested”. The lead developer assigns the change document to the IT operator to dispatch it to a tester. The tester starts testing the correction by logging on to the test system via the Landscape assignment block. He checks the change in the test system. Remark: The transport of copies needs to be in the test system, for the tester to see and test the change.

2012


619


E2E200

Preforms the action “Confirm Test Success ”to indicate, that the changed functionality has been successfully tested or the action Reset Status to “In Development ”in case of some issues or bugs. The change document is now in the status “Successfully Tested ”and the original transport request has been released by the system. When all change documents of the project have the “Successfully Tested ”status the project phase has to be set to “Test” by the responsible employee, for example change manager. All released transport requests are to be imported into the test system for regression testing. No normal change transport requests can be released in the development system for this project , excepting the defect corrections their main goal is to support the bugs fixing during the test phase. At the end of the “Test” phase all changes should be successfully tested and issues and bugs fixed. The project phase has to be set to “Go Live Preparation” and after that to “Go Live”. After aligning with the change manager, the IT operator imports all transport requests into the production system. Via the document flow, he navigates to the task list and triggers the import to the production system. To be able to trigger the import, the maintenance cycle must be in the Go Live phase. Only then the transport to the production system can take place. Remark: You can change phases in the maintenance cycle via the Actions dropdown list in the change document.

Figure 502: Normal Changes Use Test Transports

Normal changes are exported as test transports, which are performed as transports of copies.

620


2012

E2E200


In the “Development with Release ”project cycle phase and in the “In Development” status of the normal change transaction the developer can trigger generation of test transports for successful unit testing. A test transport will also be generated automatically by the system when the status of the normal change has been set to “Pass Normal Change to Test”. The system generates and exports transports of copies from the workbench or customizing requests of the activity. When the status is set to “Successfully Tested”, all transport requests will be exported and put in the import queue of the quality system. •

No new transport requests can be created for the normal changes. Normal changes are imported by using the “import project” method from within the cycle task list.

• • •

Transport requests can be imported once into each project system that has the role type target or production. During the in Development status only test transports can be performed. Test transports are exported and transported as transports of copies into the consolidation buffer.

Benefits of using test transports are: • •

Workbench objects in transition stay locked in the development system. The number of erroneous customizing and workbench requests is reduced. This reduces the import time in production.

Figure 503: Consistency of Urgent Corrections and Maintenance Activities

2012


621


E2E200

Urgent changes are transported individually and thus have no time dependency with respect to other changes. Urgent changes are imported by the transport method import subset and stay in the transport buffer after import. Urgent changes are propagated into other systems at the end of phases in the maintenance cycle together with the normal corrections by the transport method import project all. For normal changes, the import into the follow-on systems occurs in the historical sequence.

Figure 504: Differences Between Normal and Urgent Changes

(System Demo) Normal Change

622


2012

E2E200


Figure 505: Maintenance Cycle- Defect Correction

A defect correction is supposed to be created by a tester, but only in the test phase of a certain project: • • • •

Log on to development system. Create transport request. Create transport task. Release transport request.

The test phase represents the integration test phase within a project cycle. Therefore, detect corrections are not directly linked to a request for change but to the project cycle. The change manager, quality assurance manager or project manager has the ability to create defect corrections for a certain project when he or she switches a phase to “Test”. Defect corrections do not require an approval. The import of corrections into test systems must be performed by the IT operator by means of periodically running import jobs.

2012


623


E2E200

Figure 506: Process Details Change Request Management- Defect Correction

Characteristics of a detect correction: • • • • •

can only be used in the test phase. do not require an approval. allow the insertion of any system of the system landscape as a reference, supposedly a test system. must be released before the status preparation for go-live is set. allow the user to create and release transport requests.

Error Correction Processing Since the defect correction is used during integration testing and this testing is based on the entire project (that is, all changes), it is not related to a specific change or a request for change. It is used to report an error identified during testing to development and to allow the responsible developer to correct the error using a transport request. Since the scope of the project was approved using requests for change, defect corrections do not include any approval steps. Defect corrections are necessary because no new normal change transport requests can be created in the test phase since this would distort the specified and approved scope of the project.

624


2012

E2E200


Process •

• • • •

A tester wants to send a message about an error detected during testing to the developer. He creates an defect correction in the WebClient UI and describes the observed symptoms. The IT operator forwards the defect correction to the developer responsible who sets the status of the change document to In Correction. The developer creates one or more transport requests and corrects the error in the development system. To submit the change for another test, the developer sets the status to To Be Retested using the Retest defect correction action. After importing the transport buffer into the test system again, the tester checks the functions and confirms the success by setting the status to Successfully Tested.

Figure 507: Maintenance Cycle- Administrative Change

Admin change can be created during all operational phases of a project and allow the logon to any project landscape system. Admin change is intended to manage changes that do not require to create a transport request, for example, database or parameter changes. Non-SAP systems can also be handled with admin changes.

2012


625


E2E200

Figure 508: Process Details Change Request Management- Administrative Change

Administrative Change Administrative changes allow the user to perform actions where no transport request is needed (including logon that can be performed within one particular system): server switching, browser update, etc. An administrative change can be created during all phases of a project and allows logon to any system that is part of the project. Access to the task list is provided.

626


2012

E2E200


Administration Change Processing •

•

An IT operator (or administrator) wants to initiate a change that does not have to be transported with a transport request, for example, an account number or number range change in a system. To do so, he or she creates an administration change. Pre-requisites –

•

A request for change with an admin change transaction in the scope has been created, approved and assigned to a processor. – The IBase of the relevant production system is assigned to the request for change. Process

–

– – – –

–

2012

In the Change Management work center or in the WebClient UI, the IT operator calls up the administration change from the change documents assigned to him or her. In the administration change, he or she chooses Actions Set to “In Process”. The status of the change is now In Process. The processor logs on to the Landscape assignment block in the assigned development system and makes the requested change. The processor returns to the administration change and chooses Actions Set to “Complete” . While saving, the system changes the status to Completed. The IT operator confirms that the change was made and chooses Actions Confirm Administrative Change . The message is completed.


627


E2E200

Figure 509: Maintenance Task - Complete a Project Cycle

Step 1: After the Go-Live start the guided completion process for the cycle by switching the cycle phase from “>Being Completed” to “Completed”. You will see an overview of all checks which will be performed for completing the cycle, and information about the importance of the checks. Some checks may be ignored, some must not be ignored (red icon). Step 2: The task list to be completed will be checked for unfinished required tasks. With the help of the IMG the single tasks can be set as obligatory. Step 3: Still opened transports have the attribute SAP_CTS_PROJECT and will be assigned automatically to the next cycle. It is possible to complete a project cycle and its task list, although it still has changeable change transactions and transport requests assigned to it. Step 4: The system saves the change transactions and transport requests while the cycle is completed, and provides them automatically with the next cycle when it is created. All change transactions can be used within the new cycle.

628


2012

E2E200


Step 5: • •

Agree the summary to proceed and to switch the maintenance cycle to “Completed”. A new Cycle can be created in transaction SOLAR_PROJECT_ADMIN.

Figure 510: ChaRM Process Type- General Change

General Change •

• •

2012

A general change document can be created during all phases of a project. The change document “general change” is totally independent of a project and can even be used without a project. General change documents provide an abstract status scheme for the implementation of those kind of changes. Use Case: The general change document supports the documentation of all non-system related changes (e.g. printers or other IT-assets) or other legacy systems changes


629


E2E200

Figure 511: Process Details Change Request Management- General Change

Processing General Changes You want to request a change that does not require a connection to the SAP Change and Transport System. This can be, for example, the repair of a printer or computer in your organization. Pre-requisites •

•

630

You have created a request for change and specified in the scope assignment block that the change is to be a general change. The request for change was approved and its scope released for development. The object affected by the change is maintained in the system with an installation.


2012

E2E200


Process •

• • •

• •

• • • •

2012

Depending on the type of change, the responsible processor selects the change document in his or her work list in the Change Management work center or on the WebClient UI. It has the status “Created”. The processor documents that he or she is making the change by choosing Actions Set to “In Process” in the change document. Once the processor has made the change, he or she releases it for testing and chooses Actions and then “Pass General Change to Test”. The processor documents the change and the successful test and sets the status by choosing Actions Set to “To be Documented” . Following that, the processor enters the reporting person as the next processor in the change document. The reporting person chooses Actions Set to “Change Analysis” to check whether the changes were made according to the requirements. If the change was performed correctly, he or she chooses action Confirm General Change. The process is thus complete and the general change has the status Confirmed. If the change was not successful, he or she chooses Actions Failed . In case of a failed modification, it is possible to search for an alternative solution. To do so, the processor chooses Actions Restore Source. The processor marks the change as canceled by choosing Actions Set Change to “Canceled” . The change document is closed and cannot be edited further.


631


632


E2E200

2012

E2E200

623


Exercise 18: Normal Change Exercise Duration: 30 Minutes

Exercise Objectives After completing this exercise, you will be able to: • Process the developer’s tasks with the help of a normal correction. • Pass the normal correction to the tester.

Business Example RWS is the Solution Manger system that contains all information about the system landscape. RWE is a system that is managed by RWS. You have to carry out changes in RWE. Afterwards an unit test should take place.

Task: Find the change document. Take the change document in development. In this part you are acting as a Developer. 1.

Log on to the SAP Solution Manager system and open the ITSM Web UI with transaction SM_CRM. Select the Change Management link on the left hand side and choose Change Documents. Find your change document (normal correction) using one of search criteria, e.g. Change Document ID.

2.

Click on the document ID to navigate to the change document. (Fast Entry view).

3.

Go into change mode.

4.

Verify that the IBase component equals the IBase component of the production system (174 RWE system, client 803) and change it manually if necessary. Note: The IBase component is used to calculate the maintenance system. Therefore, it is crucial that you use the correct IBase component here.

5.

Set the change document to In Development and save the document.

6.

Go into the Transport Management assignment block and click on the icon Transport Request to create a new transport request. In the dialog box, check if your user is the owner of the transport request and assigned to the tasks. For this exercise, you need a customizing transport request. You can deselect the workbench request. Continued on next page

2012


633


E2E200

Your customizing transport contains the number of your change document in its description. Write down the transport request number. 7.

Log on to the development system.

8.

Maintain the Table/View T009T using transaction SM30.

9.

Save your entry. When prompted for a transport document, choose your own customizing task by choosing the Own Requests button.

10. After saving your entry, call transaction SE09 in the development system. Choose the customizing task that refers to your change document number and release it. Note: Do not release the transport request; this will be done by SAP Solution Manager in the background. Furthermore, you are not allowed to release the transport document because the CTS status switches do not authorize you to do so. 11. Leave the development system and come back into the Solution Manager (RWS), to your normal correction. Check whether your transport request includes some critical objects. 12. (Optional) If your transport request includes any critical objects, logon as a Change Manager and approve changes to critical objects. 13. As a Developer - execute action Pass Normal Change to Test and save. The status of your Normal Change will be set to To Be Tested by the system and a Test Transport (Transport of copy) will be released. Use the Task List functionality to import the Test Transport into the target system. Leave the document. 14. Logon as a Tester into the Solution Manager System RWS and navigate to your normal change. Use the Landscape assignment block to logon into the Quality Assurance system (RWE, client 802). Call transaction SM30 and check, whether the changes performed on table T009T are available here.

634


2012

E2E200


Solution 18: Normal Change Task: Find the change document. Take the change document in development. In this part you are acting as a Developer. 1.

Log on to the SAP Solution Manager system and open the ITSM Web UI with transaction SM_CRM. Select the Change Management link on the left hand side and choose Change Documents. Find your change document (normal correction) using one of search criteria, e.g. Change Document ID. a)

Figure 512: Change Request Management

2.

Click on the document ID to navigate to the change document. (Fast Entry view). a)

3.

Go into change mode. a)


2012


635


4.

E2E200

Verify that the IBase component equals the IBase component of the production system (174 RWE system, client 803) and change it manually if necessary. Note: The IBase component is used to calculate the maintenance system. Therefore, it is crucial that you use the correct IBase component here. a)

Figure 513: Reference Objects

5.

Set the change document to In Development and save the document. a)

Choose Actions drop-down list and execute action Set to ‘In Development’. Save the document.

Figure 514: Actions

6.

Go into the Transport Management assignment block and click on the icon Transport Request to create a new transport request. In the dialog box, check if your user is the owner of the transport request and assigned to the tasks. For this exercise, you need a customizing transport request. You can deselect the workbench request.


636


2012

E2E200


Your customizing transport contains the number of your change document in its description. Write down the transport request number. a)

Go into the Transport Management assignment block and click on the icon Transport Request to create a new transport request.

b)

Check in the dialog box if your user is the owner of the transport request and assigned to the tasks. For this exercise, you need a customizing transport request. You can deselect the workbench request.

Figure 515: General Data

c)

Create the transport request and save your changes. Your customizing transport contains the number of your change document in its description.

Figure 516: Change Documents

d)

Write down the transport request number. Transport Request number: ____________________________________


2012


637


7.

E2E200

Log on to the development system. a)

Go into the Landscape assignment block and in the Actions column click on the link Logon to System to log on to the development system via a trusted RFC connection.

Figure 517: Landscape Box

8.

Maintain the Table/View T009T using transaction SM30. a)

9.

In the development system call transaction SM30. In the Table/View field, enter T009T. Choose Maintain. Perform some changes in the table.

Save your entry. When prompted for a transport document, choose your own customizing task by choosing the Own Requests button. a)

10. After saving your entry, call transaction SE09 in the development system. Choose the customizing task that refers to your change document number and release it. Note: Do not release the transport request; this will be done by SAP Solution Manager in the background. Furthermore, you are not allowed to release the transport document because the CTS status switches do not authorize you to do so. a)

After saving your entry, go to transaction SE09 in the development system, choose your user name, select Customizing Requests as a Request Type and Modifiable as a Request Status and click on Display button.

b)

Navigate to your transport request and select the task below the transport request. Release the task by choosing


638


2012

E2E200


11. Leave the development system and come back into the Solution Manager (RWS), to your normal correction. Check whether your transport request includes some critical objects. a)

To perform the check go into the Transport Management assignment block and refresh the entries by clicking on the Refresh icon. . In the Critical Objects column check for the lightning icon for your transport request.

Figure 518: Transport Request

Note: All changes to critical objects need to be approved by Change Manager before to complete development . 12. (Optional) If your transport request includes any critical objects, logon as a Change Manager and approve changes to critical objects. a)

Find your change document and choose it by clicking on its ID. In the Transport Management box click on the icon Process Critical Objects .

b)

In the coming up dialog window choose Customizing Objects, select the row with the object to be approved and click on the icon Approve Object.

Figure 519: Approve Object

c)

The system status will be automatically set to green and you can close the dialog window. Go back to your normal change and check the status of critical objects in the Transport Management assignment block. The lightning icon should disappear now.

13. As a Developer - execute action Pass Normal Change to Test and save. The status of your Normal Change will be set to To Be Tested by the system and a Test Transport (Transport of copy) will be released. Use the Task List functionality to import the Test Transport into the target system.


2012


639


E2E200

Leave the document. a)

In this step you are acting as a Developer. Switch to Edit mode and perform the action Pass Normal Change to Test via Actions button. Save your changes.

Figure 520: Actions

The status of your normal change will be set to To Be Tested and a Test Transport (transport of copy) will be automatically created and released. Use the Task List functionality (transaction SCMA) to import the Test Transport into the target system. The original Transport Request remains changeable. b) Note: You have also a possibility to generate some Test Transports in the “In Development” phase using the button Test Transport.

Figure 521: Test Transport

14. Logon as a Tester into the Solution Manager System RWS and navigate to your normal change. Use the Landscape assignment block to logon into the Quality Assurance system (RWE, client 802). Call transaction SM30 and check, whether the changes performed on table T009T are available here. a)

Call transaction SM_CRM and find your change document.

b)

In the transaction for the normal correction switch to the change mode and logon to the test system (RWE, client 802) choosing the link in the . Call transaction SM30 and check the entries in Landscape box table T009T. If the test was successful, set the change document status to Successfully tested. Leave the document.

640


2012

E2E200


Lesson Summary You should now be able to: • Understand which project and process types are to be used with Change Request Management. • Know the project and maintenance phases.

2012


641


Lesson: 632

E2E200

ALM Integration Lesson Duration: 25 Minutes

Lesson Overview This lesson will give you an overview about the ALM integration for Change Request Management with SAP Solution Manager.


Know the benefits for ALM integration with Change Request Management. Understand how Quality Gate Management integration is working. Understand how the integration of Enhanced Transport Management system and Change Management is working.

Business Example You are using already Change Request Management to document and control your change along your system landscape. Testing is done manually and you have to document the test result in external files which are not linked to change documents from Change Request Management.

642


2012

E2E200

Lesson: ALM Integration

ALM Integration

Figure 522: Change Request Management- SAP Solution Manager specific ALM integration

Manage IT and optimize business Besides improving the efficiency of individual application lifecycle management (ALM) processes, it is important to integrate ALM with related areas like identifying improvement potentials for your business processes, managing your project portfolio, or running SAP IT Service Management. The whole solution is orchestrated around SAP Solution Manager. More information you can find at SAP Service Marketplace https://service.sap.com/rkt-solman.

2012


643


E2E200

Incident and Problem Management

Figure 523: ITIL compliant Incident & Problem Management processHandover to Change Request Management

Application and Problem Management This process provides central message management and processing. The Application Incident Management, with its integration of SAP Customer Relationship Management (SAP CRM) IT Service Management, allows you to contact all parties involved in a message. These include all users of the system landscape or your company’s solutions, such as employees, customers, consultants or support staff. If your IT system landscape also contains SAP solutions, customer’s SAP experts and SAP Service & Support staff can also communicate via the Incident Management. Incident Management can include an external Help Desk, set up service connections, and access SAP Service & Support. The generic Incident Management solution reports problems, helps to find solutions, and supports efficient message processing. You can create messages directly in an SAP transaction. Incident Management gathers all relevant system information, which considerably speeds up the solution process. The generic Incident Management solution reports problems, helps to find solutions, and supports efficient message processing. You can create messages directly in an SAP transaction. Incident Management gathers all relevant system information, which considerably speeds up the solution process.

644


2012

E2E200


Creating a Request for Change from an Incident or Problem From incident or problem message in the WebClient UI, choose Create Follow-Up and select Request for Change. The system generates a new request for change. It contains data from the incident, for example, the number of the incident in the Relationships assignment block and the installed base in the Scope assignment block. Complete the request for change with more details. Save the request for change.

Quality Gate Management

Figure 524: ChaRM Integration with Quality Gate Management

SAP offers both quality gate management (QGM) and change request management as standardized change control tools. Both QGM and Change Request Management offer a central transport mechanism and change control system to manage changes across technology stacks and application components. However, whereas QGM focuses on the quality process by means of quality gates, Change Request Management provides a process-oriented workflow for the approval and realization of changes. You can decide to use one of the two tools or both together.

2012


645


E2E200

Figure 525: ALM Integration- Quality Gate Management

Implementation Project (ChaRM) •

All types of changes including invasive changes

Maintenance Project (ChaRM) •

Small enhancements and Bug fixes (+ Re-Import of Emergency Changes)

Quality Gate Management in combination with Change Request Management (Define Quality Gates with QGM, Approve & control your changes with Change Request Management)

646


2012

E2E200


Figure 526: Mapping of Phases in Change Request Management and Quality Gate Management

Accordingly, an SAP Solution Manager project can be a QGM project, a Change Request Management project, or both. Note the following restrictions: • •

•

•

•

•

A Change Request Management project can only be enabled for QGM in the development phase. Change Request Management can only be activated for a QGM project if the project was completely maintained in QGM. This means all the configuration steps must be done in project maintenance. Change Request Management can only be activated for a QGM project as long as no quality gate was passed in QGM and no transport requests or changes were created in QGM. If the transport requests were deleted or decoupled, and all changes were withdrawn or finished, this means that a project can also be Change Request Management-enabled. You can enable a Change Request Management project by maintaining QGM data directly in the Change Management work center or using transaction SOLAR_PROJECT_ADMIN. For more information, see SAP help: Setting up Quality Gates and Assigning Project Phases. For a Change Request Management & QGM project, the transport features are only available on the Change Request Management side.

QGM delivers transport risk visualization, the project calendar and locks import with segregation of duty.

2012


647


E2E200

In change request management you would manage the changes with workflow and reporting possibilities within the CRM UI were you could use very flexible the assignment blocks.

Test Management

Figure 527: Test Management Integration- Improved traceability with Change Request Management

Test coordinator assigns related test plans or test packages to change document, in which context it is then available for execution and reporting for test results. Tester can access assigned test packages also via change document. • • • •

Allows to manage larger changes that need involvement of several testers Improved traceability including test execution and results Assign test packages and test plans to change request and change documents Access test packages directly via change requests and change documents

It is also planned to integrate the Business Process Change Analyzer into the Request for Change to start an impact analysis directly out of the Web UI, starting with ST, SP05.

648


2012

E2E200


Figure 528: Test Management Integration- Web Client UI

You can assign test plans and test packages to requests for change and change documents and thereby document and track the corresponding tests as well as navigate directly to execution. You assign test plans and test packages in the Test Management assignment block. The assignment block must be in change mode.

2012


649


E2E200

Integration of Non-ABAP Systems

Figure 529: CTS+: One Transport Tool for Multiple Content Types

Change and Transport System (CTS) and NetWeaver Development Infrastructure provide powerful functions to control transports in ABAP and JAVA. What was missing? • • • •

Synchronized import into double stack systems A solution for the transport of Portal content A central administration interface for all types of transports and systems Tracking and management of Non-ABAP objects with Quality Gate Management and Change Request Management

The open issues are addressed with the Enhanced Change and Transport System • •

• • • • •

650

Connect Non-ABAP Systems to standard CTS Non-ABAP applications inherit all properties of the ABAP Change and Transport System in terms of documentation, tracking and troubleshooting features Manage transport of ABAP and non-ABAP-objects centrally Allows combined transports for mixed objects (ABAP, JAVA, ) Allows synchronized changes to business processes which run in ABAP and JAVA 100% Compatible with SAP Solution Manager No need for upgrade of Java landscapes


2012

E2E200


Enhanced Change and Transport System (CTS+) •

•

•

Enhanced CTS offers the possibility to transport objects created in other languages than ABAP via the Change and Transport System of ABAP. The goal is to have one Transport Tool (CTS) which supports all Workbenches and Applications when it comes to transports. The tools for creating applications and creating content remain the same. Options to attach applications or content to a CTS Transport Request are integrated into the different workbenches. The level of integration is different for different workbenches. This is explained in detail on the following slides. Enhanced CTS aims for a unified single transport tool which simplifies the live of an Administrator who is responsible for performing imports. He has to access only one tool to start imports for very different backends. Deployment tools are called automatically. It is very easy to monitor what has already been imported and if the import went well. The queues in CTS provide a good overview on what needs to be imported.

Figure 530: CTS+: Process Flow for Non-ABAP Environments

ChaRM Process Flow for Non-ABAP Environments For Non-ABAP environments there is an additional step “Preselect transport request” that must be done by the developer. In Non-ABAP environments the transport request must be selected in a separate step, before objects can be attached to it. This is different from ABAP environments, where the system asks you if there are several transport requests available. The system logon does not work for all development environments. Therefore the developer must logon manually to the development environment in some cases. All other steps of the Change Request Management process are identical for ABAP and Non-ABAP environments.

2012


651


E2E200

Differences between the ABAP and Non ABAP scenario • • • •

Instead of logging on the managed system using trusted RFC destinations, now the start URL of the non ABAP system is called Transport Requests are created on the CTS+ controller system which is usually different from the development system The Transport Organizer Web UI is used instead of the Transport Organizer (transaction SE09) Only workbench requests are needed. No tasks of transport requests are used.

Regarding Transport of Copies with CTS+ please see SAP Note 1293449 ChaRM: New “Transport of Copies” of SAP Solution Manager.

652


2012

E2E200


Lesson Summary You should now be able to: • Know the benefits for ALM integration with Change Request Management. • Understand how Quality Gate Management integration is working. • Understand how the integration of Enhanced Transport Management system and Change Management is working.

2012


653


Lesson: 644

E2E200

Tools Lesson Duration: 30 Minutes

Lesson Overview This lesson will introduce monitoring and reporting capabilities within Change Request Management. It will also show how the Best Practices for SAP Transport Management are integrated into Change Request Management.


Know how to monitor, track and report the transport requests/change documents. Use the Cross System Object Lock. Understand how the retrofit process in Change Request Management works. Know how to use the reporting functionalities in ChaRM.

Business Example You need to report what kind of changes were implemented. Also you would like to ensure that certain objects are not allowed to be changed and that you will get informed as change manager as soon as the same objects are changed in different projects.

654


2012

E2E200

Lesson: Tools

Monitoring / Tracking and Reporting

Figure 531: Roles in ITSM Analytics

Typical Questions to Be Answered by Change Request Management Reporting Operational Questions for the Project Manager •

Which transport requests were imported into which systems?

•

– No manual tracking necessary Which change requests are in process or completed ...?

•

– For example, at the development close Which change requests are part of a customer development cycle? –

Transparency of the scope of a release

Reporting on Key Performance Indicators for Future Process Improvements •

How many urgent and normal corrections were created?

•

– Which percentage of changes was urgent? How long do requests for change take to be completed?

•

– Per organization, user, type, step How many requests for change were rejected or withdrawn? –

2012

Per organization, user, type, by whom and why


655


E2E200

Figure 532: Change Request Management Monitoring- Web Client UI

Powerful Search and Monitoring • • • • • • • • •

Multiple search criteria that can be combined completely free Save search settings for later reuse and direct access Graphical representation of search results as Pie Charts or Bar Charts Supported Full Text Search with TREX engine Post-processing via spreadsheet export Different values to show (Status, Priority, Report, Category etc.) Pie Chart/ Bar Chart Navigation into details e.g. click on graph Definition of different views (result list)

Process •

•

656

Open Web Client UI with transaction SM_CRM → menu Change Request Management → Start search with certain parameter (e.g. Business Partner, Priority or Status) Click on button Open Chart to display result in pie chart or bar chart.


2012

E2E200

Lesson: Tools

Figure 533: Change Request Management Reporting

Change Request Management Reporting Change Management Reporting in SAP Solution Manager requires that the monitored systems are included in projects for which Change Request Management is activated. Data from satellite systems is collected every hour (default setting) and after each import that is scheduled by means of the task list. Information on transported objects can be collected on demand. Object reporting increases the data volume in the SAP Solution Manager if large system landscapes are managed. You can evaluate change requests and change documents by various criteria and display the results in an overview. Reporting data is automatically fetched from the satellite systems that are involved in a project by means of the Change Request Management tracking background job. No additional activation is required. This reporting data does not, however, include information about objects that were transported in transport requests. If you require the reporting service to provide this data, too, you have to activate a separate reporting function as described in the IMG activity. Prerequisites To be able to choose and display transport objects, you have to activate the object reporting service. You can perform this using IMG activities: transaction SPRO → SAP Reference IMG → SAP Solution Manager Implementation Guide →

2012


657


E2E200

SAP Solution Manager → Capabilities (Optional) → Change Management → Extended Configuration → Configure Change Request Management Reporting Service. To use the reporting service for retrieving data from the managed systems in your system landscape, the managed systems must have at least the following Support Package level: Release

Level

4.6 C

51

4.6 D

42

6.10

45

6.20

56

6.40

15

7.00

06

7.1

06

• •

•

You have checked that your database has enough capacity. The object reporting data is stored in the /TMWFLOW/REP71* and /TMWFLOW/REPE7* tables. These tables can take up a lot of space in your database. We therefore recommend that you check the storage space in these tables on a regular basis by using a corresponding database monitoring tool. You have change authorization for the Transport Management System (TMS).

Activities 1. 2.

In the program field, enter /TMWFLOW/CONFIG_SERVICES. Select Object Reporting Active and then choose Execute.

If object reporting is deactivated (Object Reporting Not Active is selected), no transport object data is fetched from the satellite systems. Note: The /TMWFLOW/CONFIG_SERVICES program always shows the current reporting status (Object Reporting Active, for example) For more information about the reporting function, see the Knowledge Warehouse documentation for Change Request Management. Remark: The collector can only run once the last run has been completed. The date and time of the last data collector run are shown in the report under Status of Data. If the data collector is not running in a particular system (due to system downtime, for example), this system is displayed as below the date and time display as a

658


2012

E2E200

Lesson: Tools

discrepant system. You can update the information about the managed systems by choosing Refresh All Systems. The discrepant systems disappear when you update the display.

Figure 534: Change Request Management- Reporting

Start reporting from WebClient UI To call the report: • •

Go to the Change Management work center. Open menu Reports.

Example 1: You want to analyze transactions for a solution and urgent changes. You want to display transaction and project data. To do so, choose Header and Project in the Results List group box. Expand the Transaction Data tree and enter SMHF in the Transaction Type field. The system checks whether transactions exist in the context of the specified solution in which urgent changes were created. If transactions exist, the system displays the following information in a table: • • • • • • •

2012

Transaction number Transaction description Transaction type Created on System status User status Project name


659


• • • • • •

E2E200

Project type Logical component IMG project Transport track CTS identifier Status of the project

Remark: Not all transactions contain data in the areas displayed. In this case, the columns in question are empty. Example 2: You want to analyze transactions for a solution and transport request . You only want to see information about the transaction. To do so, choose Header in the Results List group box. Expand the Transport Requests tree and enter the transport request in the Request/Task field. The system checks whether transactions exist in the context of the specified solution in which the transport request was created. Since no transactions exist in this context, the system displays the following message: No matches found for the specified selection criteria.

Figure 535: Change Request Management- Solution (Independent) Reporting

Access Change Request Management Reporting

660


2012

E2E200

Lesson: Tools

You can evaluate change requests and change documents by various criteria and display the results in an overview. • • • •

SOLAR_EVAL /n/TMWFLOW/REPORTINGN Web Client UI or Workcenter for Change Management

Features: Selection criteria

Meaning

Solution

Selected solution is inserted automatically

Solution structure

Select individual structure elements for the solution, for example, business scenario or process.

List of all results

Restrict the information displayed to certain data such as header data (date for a change process), project data, data for a transport request. • • •

2012

Display Layout Max. number of hits

Transaction data

Select one or more transactions using various criteria. If you want to display data for all urgent changes to the selected solution, for example, enter SMHF in the Transaction Type field.

Organizational unit

Restrict the displayed transaction data using attributes such as organizational unit, reference object, code, and partner.

Project header

Select a project (Project ID field) or several projects using various criteria, such as project type, transport track, and IMG project. Select one or more task lists.

System data

Select one or more logical systems.


661


E2E200

Support packages

Select Support Packages and SAP Notes

Transport requests

Select transport requests and tasks.

Transport objects

Select a DDIC or repository object. Select a Customizing object.

Additional Information: Many more combinations of selection criteria are possible. You can narrow down a query by returning to the selection screen and entering more information. If the result list does not provide enough detail, you can always return to the selection screen to select a different view (Result List group box → Display field) The Header view displays the least amount of detail; the Header, Project, Task List, and Transports view, for example, displays more details.

Figure 536: Administrative Functions- Change Tracking

Change Tracking • • •

Analyze transports between systems Missing transports are shown in the records Sequence violations are shown for workbench and customizing transports

The Change Tracking function of Change Request Management allows you to track everything relating to changes within the context of a Solution Manager project, or an IMG project. It is possible to track all transport requests from the

662


2012

E2E200

Lesson: Tools

system where they are created, to the systems into which they are imported. Within the project context, all transport requests that belong to a particular project can be tracked across all the systems in the project landscape. Project analysis: track all changes for one Solution Manager project or for one IMG project System analysis: compare change requests within systems, differences in the number of change requests, and differences in the sequence in which requests are exported and imported Request analysis: track change requests, starting with the system where the request was created, to all systems into which the transport is imported Start analysis: Transaction /TMWFLOW/TRMO → Choose Tracking Example: Analyze all open transactions / changes. After specifying a valid project and Search for the Project Status the Project Landscape View will be displayed to analyze the Track Status for this project.

Administration

Figure 537: Task List- Overview

Maintenance Task List describe all activities which can be processed for a specific project. Most of the tasks can be invoked directly out of the transactions or change documents. The task list is the interface to the Change and Transport System in the satellite systems. You can create, release and import transport requests from there. The task list is normally used in the background by the CRM transactions. Only the import of a project by the project manager is done directly in the task list.

2012


663


E2E200

Task-lists are based on project landscape role types: • • • • •

Source System Target System Production System Single System Post-Processing System

When a project landscape changes, the systems have to be deleted/inserted correctly by an administrator. Phases can be shifted from within the cycle task-list (as well as the cycle transaction). Cycle task-lists can be activated, locked, and completed. Tree structures can be locked against usage from Normal Changes, test messages, and administration messages.

Figure 538: Task List- Log Monitor

Use the Daily Overview area to find detailed log information via the Schedule Manager Monitor. As soon as a task has been executed, its status is changed to the status of the (last) execution. If, for example, you start a task that returns the status Contains Errors, you then see this status in the daily overview, in the monitor, and in the task list. If, subsequently, you start the task again, but the task returns the status Warning, you see this status for the newly scheduled items in the daily overview, in the monitor, and in the task list. The former Contains Errors status in the task list has now changed to Warning, while the status of the previous execution remains unchanged in the daily overview and in the monitor.

664


2012

E2E200

Lesson: Tools

Figure 539: Administrative Functions- Scheduling

Scheduling can be done via transaction /TMWFLOW/MAINTINST. Herein also Projects, Maintenance Cycles and Urgent Changes can be analyzed. Example: Analyze all existing active Urgent Changes and the corresponding transport requests.

Cross System Object Lock

Figure 540: Cross-System-Object-Lock (CSOL)- Cross-Client Example

The cross-system lock can be activated by the transaction /TMWFLOW/CONFIG_LOCK

2012


665


E2E200

You can see the active locks in transaction /TMWFLOW/LOCKMON. There you can also delete locks if needed. Examples for CSOL: •

Cross-project and client-specific

•

– Urgent changes cannot interfere – Error – All other changes are recognized – Warning Cross-project and cross-client –

•

Urgent changes cannot interfere, but only regarding cross-client Customizing, ABAP, and DDIC – Error – All other changes are recognized – Warning Project-specific and client-specific

– –

Urgent changes cannot interfere - only for Customizing but not ABAP and DDIC data – Error All other corrections regarding Customizing between projects are recognized, ABAP and DDIC changes are only recognized within a project – Warning

Figure 541: Cross-System-Object-Lock (CSOL)- Process

The Cross system object monitor occurs if an object is already locked by another transport request.

666


2012

E2E200

Lesson: Tools

Critical Object Approval

Figure 542: Critical Transport Objects- Integration into Change Request Management Process

Critical Object Approval Process Critical objects are approved at the time of export. •

Critical objects are defined as: – – –

Modifications Workbench objects in transport piece list format Customizing objects in transport piece list format

Critical object check is activated for each logical system: • • • •

R3TR objects LIMU objects Logical objects for Customizing views Table entries for Customizing tables

Modification approval is activated once in SAP Solution Manager: •

2012

Activate for each logical system


667


E2E200

Definition and Approval • • • • • •

For each type of critical object there is a separate maintenance interface. There are two types of critical objects: cross-client and client specific objects. First you must specify a set of critical transport objects. For the definition of critical objects use the transaction /TMWFLOW/CMSCONF → select the critical object tab page The check can be activated on a system-level and a client-specific level. When a critical object is contained in a transport of the change transaction, no export is possible unless the change manager approves the critical object.

• In the Schedule Manager application log, you see the following information: • • •

Transport object checks are activated. Request contains critical objects! Only users entered as Change Manager can approve critical objects (Transport Management Assignment Block).

Retrofit

Figure 543: Dual Landscape Synchronization with Retrofit

668


2012

E2E200

Lesson: Tools

Improve process reliability for the retrofit process • • • • •

Work List of all transports to be synchronized (down to object level) Tool based Minimized risk through integration in the maintenance project and changes Logging of the changes Less manual effort for double maintenance (conflict and sequence visibility)

Figure 544: Dual Landscape Synchronization with Retrofit Integration into Change Request Management Process

Start Retrofit Monitor Manage Retrofit centrally from the maintenance cycle task list • •

Start retrofit for all transports of the maintenance project Get full visibility of all dependencies

Integration within Change Management Process Start Retrofit integrated from Urgent and Normal Changes • •

Start from Urgent Change when it is “Authorized for Production” Start from Normal Change when it is “Successfully Tested”

After executing the action Start Retrofit the Retrofit Transport Request Selection window occurs.

2012


669


E2E200

(System Demo) Retrofit Process

670


2012

E2E200

661

Lesson: Tools

Exercise 19: Reporting Exercise Duration: 20 Minutes

Exercise Objectives After completing this exercise, you will be able to: • Use Change Management reporting to find, transport requests, and transported customizing objects.

Business Example RWS is the Solution Manger system that contains all information about the system landscape. RWE is a satellite system that is managed by RWS.

Task 1: Search for a certain request for change. 1.

Log on to the SAP Solution Manager system, call transaction SOLMAN_WORKCENTER, and choose the Change Management tab. In the contextual navigation panel choose Reports menu and in the Reports tab click on the Report link in the type column of Reports table.

2.

In the Result List screen area, choose Header, Project, Task List, and Transports via the F4 help button.

3.

Expand the Transaction Data screen area.

4.

In the Document Number field, fill in the number of your change document, which you wrote down in the Request for Change exercise.

5.

Execute your selection.

6.

Check your results and find the transport request.

Task 2: Search for a request for change that contains a certain transport request and display the transported objects. 1.

In the Result List screen area choose Header, Project, Task List, Transports, and Objects via the F4 help button.

2.

Open the Transport Request screen area.

3.

In the Request/Task field, fill in the number of the transport request you wrote down in the step before.

4.

Execute your selection. Continued on next page

2012


671


5.

E2E200

Check your results and find the object. Note: The name of the object is case-sensitive

Task 3: Search for a request for change that contains a certain object.

672

1.

In the Result List screen area, choose Header, Project, Task List, Transports, and Objects via the F4 help button.

2.

Open the Transport Objects screen.

3.

In the Table Name field, enter T009T. In the Table Keys field, fill in your object from the exercise before. The key fields are case–sensitive.

4.

Execute your selection and check your results.


2012

E2E200

Lesson: Tools

Solution 19: Reporting Task 1: Search for a certain request for change. 1.

Log on to the SAP Solution Manager system, call transaction SOLMAN_WORKCENTER, and choose the Change Management tab. In the contextual navigation panel choose Reports menu and in the Reports tab click on the Report link in the type column of Reports table. a)

In the contextual navigation panel on the left-hand side, open the Reports menu.

Figure 545: Reports- 1

b)

In the work area choose Reports tab and in the Reports table click on the Report link in the Type column, choose the Report link.

Figure 546: Reports- 2


2012


673


2.

E2E200

In the Result List screen area, choose Header, Project, Task List, and Transports via the F4 help button. a)

Figure 547: Result List

3.

Expand the Transaction Data screen area. a)

4.

In the Document Number field, fill in the number of your change document, which you wrote down in the Request for Change exercise.

Execute your selection. a)

6.

.

In the Document Number field, fill in the number of your change document, which you wrote down in the Request for Change exercise. a)

5.

Expand the Transaction Data screen area by choosing

Choose

or press F8.

Check your results and find the transport request. a)

Write down the transport request number: _________________

Task 2: Search for a request for change that contains a certain transport request and display the transported objects. 1.

In the Result List screen area choose Header, Project, Task List, Transports, and Objects via the F4 help button. a)

In the Result List screen area, choose Header, Project, Task List, Transports, and Objects via the F4 help button.


2.

Open the Transport Request screen area. a)

3.

Expand the Transport Request screen area by choosing

.

In the Request/Task field, fill in the number of the transport request you wrote down in the step before. a)


674


2012

E2E200

Lesson: Tools

4.

Execute your selection. a)

5.

Choose

or press F8.

Check your results and find the object. Note: The name of the object is case-sensitive a)

Write down the name of the object ____________________

Task 3: Search for a request for change that contains a certain object. 1.

In the Result List screen area, choose Header, Project, Task List, Transports, and Objects via the F4 help button. a)


2.

Open the Transport Objects screen. a)

3.

Expand the Transport Objects screen area by choosing

.

In the Table Name field, enter T009T. In the Table Keys field, fill in your object from the exercise before. The key fields are case–sensitive. a)

4.

Execute your selection and check your results. a)

2012

Choose

or press F8.


675


E2E200

Lesson Summary You should now be able to: • Know how to monitor, track and report the transport requests/change documents. • Use the Cross System Object Lock. • Understand how the retrofit process in Change Request Management works. • Know how to use the reporting functionalities in ChaRM.

676


2012

E2E200

Lesson: 667

Lesson: (Appendix) Change Request Management

(Appendix) Change Request Management Lesson Duration: 20 Minutes

Lesson Overview You are going to use change request management. Within this lesson you will get an overview about the basic status settings in a normal change.


Know how the possible status within a normal change.

Business Example You wish to know the details regarding the actions to be carried out when working with normal changes. For further information please visit: http://scn.sap.com/people/dolores.correa/blog/2011/12/28/change-requestmanagement-scenario-new-features-in-sap-solution-manager-71

(Appendix) Change Request Management Detail status schema for a Normal Change

Figure 550: Normal Change in Phase “Development without Release”

2012


677


E2E200

Figure 551: Normal Change in Phase “Development with Release”

Figure 552: Normal Change in Phase “Development with Release”

Figure 553: Normal Change in Phase “Test”

678


2012

E2E200

Lesson: (Appendix) Change Request Management

Figure 554: Normal Change in Phase “Go Live”

2012


679


E2E200

Lesson Summary You should now be able to: • Know how the possible status within a normal change.

680


2012

E2E200

Unit Summary

Unit Summary You should now be able to: • Know the technical basis of SAP Solution IT Service Management. • Understand the Change Request Management integration into Application Lifecycle Management. • Know the different user roles for Change Request Management. • Understand the Change Request Management process. • Understanding Project and Release Management with SAP Solution Manager. • Know how to classify changes to different change types. • Explain the relationship between Solution Manager Project and Project Cycle. • Understand how the request for Change process. • Learn about the usage of CRM Master Data. • Know the Web Client UI for Change Request Management. • Understand which project and process types are to be used with Change Request Management. • Know the project and maintenance phases. • Know the benefits for ALM integration with Change Request Management. • Understand how Quality Gate Management integration is working. • Understand how the integration of Enhanced Transport Management system and Change Management is working. • Know how to monitor, track and report the transport requests/change documents. • Use the Cross System Object Lock. • Understand how the retrofit process in Change Request Management works. • Know how to use the reporting functionalities in ChaRM. • Know how the possible status within a normal change.

2012


681

Unit Summary

682

E2E200


2012

Unit 9 Maintenance Management

673

Unit Overview Within this unit you will get knowledge about the types of support items that SAP delivers. The support package stack strategy and enhancement package concept will be explained as well as the role of SAP Solution Manager in the maintenance process such as System Recommendations or Upgrade Change Impact Analysis.

Unit Objectives After completing this unit, you will be able to: • • • • • • • • • • •

2012

Understand SAP’s Maintenance Strategy Explain the support package stack strategy Describe main types of support items delivered by SAP Execute side effect reporting for a Support Package queue Understand the difference of the enhancement packages and support packages. Describe the enhancement package concept. Know the cycle of discovering, implementation and activation of Enhancement Packages. Know the software lifecycle management tools to implement patches and find information on current patch levels. Know how to work with System Recommendations. Perform an upgrade or change impact analysis with the custom development management cockpit. Know SAP’s best practice recommendations for maintenance management.


683

Unit 9: Maintenance Management

E2E200

Unit Contents Lesson: SAP Maintenance Strategy .........................................685 Lesson: Types of Maintenance ...............................................697 Lesson: SAP Enhancement Packages ......................................713 Lesson: Maintenance Optimizer ..............................................729 Lesson: System Recommendations..........................................742 Exercise 20: System Recommendations................................751 Lesson: Upgrade / Change Impact Analysis ................................760

684


2012

E2E200

Lesson: 675

Lesson: SAP Maintenance Strategy

SAP Maintenance Strategy Lesson Duration: 15 Minutes

Lesson Overview This lesson will give you an introduction into the Maintenance Management at SAP.


Understand SAP’s Maintenance Strategy Explain the support package stack strategy

Business Example Maintenance Management covers software correction packages: from discovery and retrieval to test scope optimization, including deployment into the production environment. • •

2012

You need to plan the maintenance of the systems in your landscape and thus you need to know about SAP´s release strategy. SAP Notes provide a solution for known issues. SAP Notes are usually applied upon request. SAP Notes are collected and released as Support Packages. Support Packages are applied to SAP solutions to comply with legal requirements or run on latest technology. You need to understand why SAP recommends to implement support package stacks regularly instead of implementing SAP notes or support packages on request only.


685


E2E200

Figure 555: Change Control Management- Maintenance Management

Maintenance Management supports the customer in planning and implementing the available SAP software updates. Tools and procedures are in place to eliminate known side-effects, estimate the impact on custom code and minimize the downtime. There is a clear differentiation between bug fixes and new functionality which is delivered in enhancement packages and support packages.

SAP Release and Maintenance Strategy • •

•

•

686

In October, 2011 SAP announced a maintenance extension for the SAP Business Suite 7 core applications to 2020. SAP extends mainstream maintenance for SAP Business Suite 7 core applications (SAP ERP 6.0, CRM 7.0 , SCM 7.0, SRM 7.0 and PLM 7.0) by 5 years through December 2020. The longer maintenance also applies for SAP NetWeaver as the technological basis of the core application releases, and for the enhancement packages. For dependent applications SAP will decide on a case by case basis whether existing releases of these applications will follow the longer maintenance or whether SAP will ship new releases that can then be run together with the core application releases. The maintenance extension benefits all customers: – Customers already running Business Suite 7 applications – Customers implementing Business Suite 7 applications – Customers still running older releases and upgrading to Business Suite 7 In this context, it is important to know that there is one key restriction in this extension: SAP NetWeaver 7.0x Java will not be part of the maintenance extension to 2020 but will be supported, as previously announced, to December 2017. This decision is based on the fact that with Java, SAP is


2012

E2E200


• •

dependent on external vendors (e.g. for JDBC drivers). SAP NetWeaver 7.0x Java is based on Java J2EE 1.4 (released in 2002, so it will be 15 years old by 2017) which has reached its end of life and will not be supported by most vendors beyond 2012. Maintenance for SAP NetWeaver 7.0x ABAP, as well as for the higher SAP NetWeaver releases, (ABAP and JAVA) will be extended to 2020. To sum it up: – – –

•

SAP NetWeaver 7.0x JAVA – will be supported to 2017 SAP NetWeaver 7.0x ABAP – will be supported to 2020 SAP NetWeaver 7.1 and higher (ABAP and Java) – will be supported to 2020 There are three main areas that are impacted by this decision:

–

•

SAP NetWeaver 7.0x Java and dual stack systems, e.g. Portal or PI: Customers running such systems should upgrade to SAP NetWeaver 7.3 by the end of 2017 – Applications based on SAP NetWeaver 7.0x Java: These applications will be supported to 2017, and customers should upgrade to higher versions by the end of 2017. Some applications are enabled to run on SAP NetWeaver 7.3 and may be supported to 2020. – Java-based components of SAP ERP 6.0 and SAP ERP 6.0 EHP 1-3: These components are running on SAP NetWeaver 7.0x Java. Customers running such components should implement at least SAP ERP 6.0 enhancement package 4 which contains updated content enabled for SAP NetWeaver 7.3. Supporting SAP NetWeaver 7.0x Java to 2017 means that the overall support duration is unchanged (then: mainstream maintenance to 2015, extended maintenance to 2017; now: mainstream maintenance to 2017 – the originally planned extended maintenance has been transformed into a longer mainstream maintenance; no extended maintenance will be offered for SAP NetWeaver 7.0x Java after 2017). Approximately 250 add-on product versions of add-ons either to the SAP Business Suite 7 core applications or SAP NetWeaver maintenance phases had to be aligned. In general, there are three distinct categories: –

•

2012

Java add-ons running on SAP NetWeaver 7.0x Java will be supported to 2017 – Java-add-ons running on higher SAP NetWeaver releases will be supported to 2020 – ABAP add-ons will be supported to 2020. More information regarding SAP Business Suite could be found under http://service.sap.com/businesssuite.


687


E2E200

Figure 556: Release and Maintenance Strategy- Overview for Core Application Releases

This slide shows the new maintenance duration for the SAP Business Suite 7 core application releases. It shows the long planning horizon that SAP is offering for the Business Suite 7 releases – to the end of 2020, which means customers have unparalleled long-term planning security. The SAP Business Suite includes the core applications (SAP ERP 6.0, SAP PLM 7.0, SAP CRM 7.0, SAP SCM 7.0, SAP SRM 7.0), supplementary applications and industry applications. Please refer to SAP Note 1648480 for more information on restrictions with regard to SAP NetWeaver 7.0x Java. Special rules may apply to applications in the SAP Business Objects portfolio. Refer to the white paper “SAP’s Release Strategy for Large Enterprises” at http://service.sap.com/releasestrategy for more information.

Figure 557: Maintenance for SAP Business Suite1

688


2012

E2E200


1: The SAP Business Suite includes the core applications (SAP ERP 6.0, SAP PLM 7.0, SAP CRM 7.0, SAP SCM 7.0, SAP SRM 7.0), supplementary applications and industry applications. 2: For detailed information please refer to SAP Note 1648480.

2012


689


E2E200

Figure 558: Product Availability Matrix: What is it?

•

•

•

•

•

The Product Availability Matrix (PAM) bundles technical and release planning information on SAP software product versions for quick reference. You find information on the availability and maintenance end dates, as well as release information (languages, country versions, DB-platforms, JSE-platforms etc.). The PAM information is based on the internal Product & Production Management System (PPMS). PPMS is the central knowledge repository for technical information on SAP software components and software products. The technical and release planning information on SAP product versions are directly displayed in the Product Availability Matrixon SAP Service Marketplace at http://service.sap.com/pam. The Product Availability Matrix also offers quick links and additional information area for release planning information on SAP components for quick reference. Quick views like Active Ramp-Ups could be used. The Product Availability Matrix bundles technical and release planning information on SAP components for quick reference. You will find information on the availability of SAP component releases (product versions), maintenance end dates, and upgrade paths, as well as technical release information (DB platforms, JSE platforms, operating systems, languages, countries, etc.).An SAP component release is structured into instances. An instance is a bundle of technically dependent software component versions to be installed on one single logical system. The technical release information is displayed per instance. Example: The product version SAP NetWeaver 7.0 is structured into the instances Application Server ABAP, Application Server Java, Enterprise Portal, Frontend, etc. The Application Server ABAP itself consists mainly of the software component versions SAP BW 7.00, SAP ABA 7.00, SAP BASIS 7.00 and SAP kernel 7.00 32-BIT (or a newer downward compatible one). Choose one of the other tab strips to find additional technical release information. You will see a second row with one or more tab strips, depending on the complexity of the SAP component. These tab strips name the system instances within the SAP component for which a given type of release information is relevant. As each system instance carries several sets of release information, you may see the same system instance under operating systems as well as under web browsers, for example. Note: A type of release information entitled xyz platform always refers to a combined release information of xyz and an operating system. For example, a database platform is a combination of database version and operating system version, and a web browser platform is a combination of a web browser version and an operating system version.

690


2012

E2E200


Figure 559: Displaying details of a software product version

•

•

•

•

•

2012

The PAM information is based on the internal Product & Production Management System (PPMS). PPMS is the central knowledge repository for technical information on SAP software components and products. A lot of teams wordwide – like the product management as well as cross-teams such as the validation teams – and some tools provide input to PPMS. Many tools are consuming PPMS data they need for their processes and purposes, both internal tools as well as tools accessible for customers or even running on customers site. Examples are the Product Availability Matrix, the Software Distribution Center and the SAP Solution Manager with its various applications such as Maintenance Optimizer, Business Process Repository or Diagnostics. So, PPMS is the foundation for more than 70 internal and customer tools, services and processes and therefore high quality of all data maintained is crucial for both internal use as well as customer. You can visit http://service.sap.com/pam for more information.


691


E2E200

Support Package Stacks

Figure 560: Version Information of ABAP Systems System - Status

The version information of ABAP-based systems can be accessed through the menu bar: System → Status → (Button) “Component information” The version information of a JAVA-based system can be seen in the Component Information http://:/sap/monitoring/ComponentInfo. For each software component, the version string shows release, Support Package, and patch level.

692


2012

E2E200


Figure 561: Maintenance Management - SAP Support Package Stacks

Advantages of applying Support Package Stacks are: • • • • •

Contain the optimal combination of Support Package and patch statuses for the individual components at the given time Reduce the complexity of Support Package application Increase quality and transparency SP Stacks are already tested at SAP SP Stacks are well known at SAP Note: SAP recommends to apply a Support Package Stack as a whole to update an SAP system.

•

On the Service Marketplace, there is a support package stack calendar which shows the planned availablity of the support package stacks for the different products. It can be found under http://service.sap.com/sp-stacks. You can use this calendar to schedule your maintenance projects. Products which are new or still in the ramp-up phase have a high support package stack frequency (such as monthly). Older and stable releases only deliver Support Package Stacks twice a year.

General recommendation: •

2012

Besides single corrections through SAP notes that usually are applied in a reactive mode, it is recommended to set up a proactive maintenance concept for the SAP systems. The import of SAP Support Packages should be scheduled on a regular basis as part of the Maintenance Calendar.


693


E2E200

Maintenance Management - Benefits of Support Packages •

Regular import of SAP Support Packages offers advantages like: – –

– –

Proactive solutions of known problems Basis for a fast reaction on problems: Avoid the need to implement many single notes or even Support Packages in order to be able to implement a single note to solve a problem Troubleshooting is easier on a current Support Package level Besides proactively avoiding potential issues, a regular import of Support Packages also helps to ensure agility for implementing new functions (on urgent business requirements) – these functions might have dependencies to new EhPs and/or SPs. Each Enhancement Package requires as a pre-requisite the installation of a certain Support Package Stack.

Customer Aspects

Figure 562: Maintenance Management- Best Practice Recommendations

694


2012

E2E200


Figure 563: Maintenance Management Best Practice Recommendations

2012


695


E2E200

Lesson Summary You should now be able to: • Understand SAP’s Maintenance Strategy • Explain the support package stack strategy

696


2012

E2E200

Lesson: 687

Lesson: Types of Maintenance

Types of Maintenance Lesson Duration: 20 Minutes

Lesson Overview This lesson will give you an overview about different kinds of maintenance type items and how SAP delivers them.


Describe main types of support items delivered by SAP Execute side effect reporting for a Support Package queue

Business Example You need to plan the maintenance of the systems in your landscape and thus you need to know how SAP is delivering support items for ABAP and Java.

Corrections / Change

Figure 564: Types of Corrections

The standard correction process has different stages.

2012


697


E2E200

Support Package Stack: •

Description: The Support Package Stack is a list of ABAP and Java Support Packages for all software components (SC) included in SAP NetWeaver. It is used to bring each Software Component of SAP NetWeaver to a defined SP level.

ABAP Support Package: •

Description: ABAP Support Packages contain quality improvements for the SAP system, or make necessary adjustments due to legal changes, for example. The objects affected are replaced in your system.

Java Support Package: •

Description: Java Support Packages are used to ship correction levels of software components. They correspond to the ABAP Support Packages.

The emergency correction process contains: SAP Note Correction (ABAP): •

Description: SAP Note Corrections contain single ABAP corrections.

Java Support Package Patch: •

Description: A Java Support Package patch contains corrections for the Java Software Components. Java Support Package patches are normally created and released on demand. They correspond to a SAP Note that describes the same correction.

Java Single Patch: •

698

Description: A full version of a single Development Component. Java single patches correspond to a SAP Note that describes the corresponding prerequisites and dependencies.


2012

E2E200


Figure 565: Component Model and Maintenance (ABAP)

The SAP component model for ABAP objects is shown above: • • •

Products are updated by installations and upgrades. Software components are updated by support packages and add-ons. Single objects can be updated by SAP Notes.

Figure 566: SAP Note in the Service Marketplace

2012


699


E2E200

SAP Notes describe how to remove known errors in the SAP system. They include a description of the following: • • •

The symptoms of the error The root cause of the error The release and Support Package status for which they are valid

They contain (depending on the type of error): • • •

Workarounds. Descriptions of how to correct the source code (correction instructions) Links to Support Packages that correct the problem

Correction instructions change single lines of coding. SAP Notes with correction instructions are implemented with the Note Assistant in the development system, and then forwarded by transports to production.

Figure 567: Correction Instruction: Changing a Function Module

700


2012

E2E200


Which objects can the Note Assistant handle? •

New Objects can be created

•

– CLAS: Global ABAP Classes (ABAP-OO) – INTF: Interfaces (ABAP-OO) – REPS: ABAP programs and includes – FUNC: Function modules with interface and all attributes – DYNP: Screens with all attributes – TYPD: Type Pools – WAPP: Business Server Pages – SMIM: MIME objects (only with small data volume) – IAMU, IARP, IASP, IATU: Internet transaction server – ENH*: Enhancement objects Objects which are not supported: – – – – – –

2012

Creating an entire function group BSP applications Deleting an object Changes to tabular content (R3TR TABU) Language dependent texts DDIC objects


701


E2E200

Figure 568: Note Browser

•

• • •

702

You can use the SAP Note browser to search for all the SAP Notes that are available in your system. The browser also displays SAP Notes that are assigned to another processor, and SAP Notes that have already been implemented. Select all notes with the implementation status Completely implemented. Call transaction SNOTE → GOTO → SAP Note Browser. Manual implemented SAP Notes could be registered as completely implemented in SE38 with SCWN_REGISTER_NOTES. More information about the note assistant can be found in the service market place under alias /NoteAssistant.


2012

E2E200


Figure 569: ABAP Support Packages

You can browse for the support packages in the Service Market Place. It is available under http://service.sap.com/swdc. ABAP Support Packages: • • • • •

2012

All note corrections within a certain time period are bundled into a support package. A support package contains full objects, not just single lines of coding. Support packages are delivered for each software component. Support packages are incremental. That means that all support packages of a software component must be implemented. Support Packages contain all objects that were changed in a certain time period.


703


E2E200

Side-Effect Reporting

Figure 570: Side Effects of Single Notes

In some cases, SAP Notes and Support Packages are dependent on each other. Resolving a particular issue with one SAP Note may cause new issues to arise in other areas. To resolve these new issues, SAP publishes new SAP Notes that are related to the original SAP Note. Before implementing an SAP Note, you should check if it has any side effects. On SAP Service Marketplace at http://service.sap.com/notes you can view any known side effects on the Side Effects tab of a single SAP Note. The upper table on this tab displays other SAP Notes that can be corrected using this SAP Note, whereas the lower table shows other SAP Notes that correct the side effects of this SAP Note.

704


2012

E2E200


Figure 571: Side-Effects Reporting: Calculation for Support Package Queues

SAP Support Packages are collections of SAP Notes that provide software corrections. Since SAP Notes in subsequent Support Packages solve most of the side effects caused by a Support Package, these notes must be excluded from the list of side effects. Only side effect notes which are not contained in the import queue need to be imported separately after a Support Package import. For open topics of Side Effect reporting, see SAP Note 684859.

Figure 572: Maintenance Optimizer Transaction

2012


705


E2E200

The files selected for implementation and product maintenance are listed in a table which also contains details and information about side effects of the corrections for each Support Package as well as for the whole stack. You can order the side effect from the Service Market for the single ABAP Support packages or for the whole Support package stack. A link will be provided to you were you can select the side effects you want to download. To allow easier detection of these interdependencies, a reporting tool is available on the SAP Service Marketplace. When importing a Support Package or SAP Note, you can check for known side effects and find relevant SAP Notes to treat these. Using the tool, you can proactively prevent problems that may occur as a result of applying Support Packages or SAP Notes, not only accelerating and improving the quality of issue resolution, but also reducing maintenance effort and costs. Access this topic directly at http://service.sap.com/side-effects.

Figure 573: Number of Known Side Effects over the Time

The number of known side effects of a support package rises continuously after the time of the development close. Most side effects are known at the time a support package is released. However, if you execute the side effect report several times, you might see more known side effects if you execute the reporting at a later point in time.

706


2012

E2E200


Figure 574: Component Model and Maintenance (JAVA)

Software maintenance is organized into three tiers: •

•

•

Products are installed or undergo an upgrade to a new release. A release is a full delivery of software components that provide new functions (and possibly user interfaces) or improvements. Installation and upgrade are not performed with Change Management Service (CMS) resources. A Support Package (SP) is (unlike ABAP) a full delivery of one (or more) software component(s) and contains a number of fixes. The usual file format of an SP is the SCA format. Support Packages are implemented using the Java Support Package Manager Tool (JSPM). JSPM distinguishes between systems that are under NWDI control and systems that are not under NetWeaver Development Infrastructure (NWDI) control. Java-based Support Packages are cumulative. Update from a lower SP Stack to a higher SP Stack only requires the import of the appropriate target SP Stack. Fixes are full deliveries of a development component that allow a quick error correction, before the complete SP is available. The usual file format is the SDA format. –

•

Hint: SAP usually does not yet deliver fixes. The smallest unit of delivery of SAP software is a Support Package. Development Objects (DOs): – –

2012

Stored as versioned files in the source repository (DTR) Example: Web Dynpro view, table definition, Java source file


707


E2E200

Java Corrections

Figure 575: Java Support Packages

Figure 576: Java Fixes

• • •

708

Java Objects are grouped in development components. Development components are grouped in software components. The smallest unit that can be delivered is a complete development component (fixes). Fixes should only be applied in emergency situations and with guidance from SAP Support.


2012

E2E200


Figure 577: Java Patches

•

See http://service.sap.com/SWDC for schedule details and updates.

Figure 578: Java Patches are described in SAP Notes

This note describes a problem which is solved by support packages or patches. In section “Solution” you can find the name of the support package and patch that solves the problem.

2012


709


E2E200

Figure 579: SAP Service Marketplace - find Support Packages and Patches

•

• •

710

Java Support Packages and Patches are delivered as full Software Component Archives. Support Packages have patch level 0. Patches have a higher patch level. Patches are always created for the highest Support Package Level. They are also created for lower Support Package Levels, if required. If you click on “Info” of a patch, you see a list of notes that describe the individual corrections, which are solved with the patch. For Support Packages, there is a summary note which describes all corrections in the Support Package.


2012

E2E200


Figure 580: Types of Content Corrections in SAP Web AS

To find out the current Support Package Level of all software components running on the Java system see: http://:/sap/monitoring/SystemInfo → Software Components → all components You can also find the information in transaction SMSY and LMDB when the SLD information are fetched for the managed systems.

2012


711


E2E200

Lesson Summary You should now be able to: • Describe main types of support items delivered by SAP • Execute side effect reporting for a Support Package queue

712


2012

E2E200

Lesson: 702

Lesson: SAP Enhancement Packages

SAP Enhancement Packages Lesson Duration: 25 Minutes

Lesson Overview This lesson will give you an overview about the SAP Enhancement Package concept.


Understand the difference of the enhancement packages and support packages. Describe the enhancement package concept. Know the cycle of discovering, implementation and activation of Enhancement Packages.

Business Example You need to plan the maintenance of the systems in your landscape and you also need to know what kind of enhancement packages have to be implemented and activated.

2012


713


E2E200

SAP Enhancement Packages

Figure 581: SAP Enhancement Packages (incl. SP-Stacks) - Installation with Regular Maintenance + Selective Activation

Enhancement Packages are optionally installed and activated software innovations. They include software innovations like UI simplifications, functional enhancements and Enterprise services. SAP enhancement packages are built on top of each other. Enhancement packages are not support packages: Support Packages contain corrections and legal changes. EHPs are shipped as a delta shipment to SAP ERP 6.0, SAP CRM 7.0, SAP SCM 7.0 and SAP SRM 7.0. •

•

•

714

Customers have the need to stabilize their core systems and yet to still deliver ongoing innovation. With the SAP enhancement package concept SAP tackles this challenge. SAP enhancement packages represent a software delivery strategy that allows you to get innovations on top of SAP ERP 6.0 without the need for fully upgrading your current release. With SAP enhancement packages, the methodology for implementing new functionality has significantly changed. You can now install new functionality, without any change for end users right at the outset. Therefore, the SAP enhancement packages installation should be performed in a normal maintenance window as part of your existing regular Support Package Update with only minor additional effort. Afterwards, you can activate new functionality when you want to, and you know exactly which functional changes will occur and what you have to test after the activation of the new functionality. SAP’s aim is to provide new functionality for well-defined user groups without side effects for the rest.


2012

E2E200


•

•

•

Support Packages contain only corrections and legal changes; in case you only want to maintain your current state, SAP assures that your system will stay stable and compliant. As SAP leverages the Enhancement and Switch Framework to deliver new functionality, the installation of an SAP enhancement package has no impact on existing business processes or user interfaces, as long as no business function has been activated. However, SAP enhancement packages require a defined SAP ERP Support Package Stack, including a certain level of SAP ERP and SAP NetWeaver Support Packages. Furthermore, you potentially need to perform a modification adjustment (SPDD/SPAU). If you have modifications to the SAP code in your system and you separate the installation of the Support Package Stack and the installation of the SAP enhancement package into two steps, you need to perform the modification adjustment twice (and in part for the same objects), since SAP enhancement packages also contain corrections from the equivalent Support Package Stacks. 1. Selective Installation: – –

Each enhancement package contains new versions of existing software components You only update software components, which are related to the functionality you want to use.

After installation:

•

– No UI or process change until a Business Function is activated (ABAP) – One common regression test for both, SP and enhancement package 2. Selective Activation – –

New functionality must be explicitly switched on to become active in the system (EHP5: ~600 Business Functions). If activated: Changes are predictable, only well described changes in the activated areas.

The SAP enhancement package is designed to decouple technical installation from business innovation. You can install SAP Enhancement Packages combined with Support Pack Stack as a maintenance activity with only minor additional effort.

2012


715


E2E200

The Enhancement Package Lifecycle includes 5 steps: •

Step 1: Discover

•

– Receive an overview of available enhancements – Understand their potential business benefits – Identify enhancements relevant for you Step 2: Evaluate & Decide

•

– Evaluate relevant enhancements – Understand their particular benefit for you – Assess effort and impact of their implementation Step 3: Prepare & Install – –

•

Download, load, and install the relevant components SPDD/SPAU and Regression for the updated components → One common regression test for both, SP and enhancement package Step 4: Activate & Configure

•

– Check dependencies – Activate business functions – Configure new capabilities Step 5: Test & Go-Live – – –

716

Use templates for acceptance testing Complete relevant end user training Go-Live


2012

E2E200


Figure 582: Example: SAP Enhancement Package 5 SAP ERP 6.0

A selective exchange of one component is possible: With SAP EHPs you can selectively update software components. Note that matching combinations of software components as well as PI/EP/BW content and Java software components are grouped by technical usages. As the number of software components is limited, for example, a separate installation of logistics and financials (both are located in the core software component SAP/EA_APPL) is not possible. This is realized by strict separation of technical installation and implementation of the new functionality. New functionality (Business Functions) must be explicitly switched on to become active in the system. However only Backend functionality (ABAP) is switchable. Enhancement packages for NetWeaver are immediately active after installation. If activated, changes are predictable and you find well described changes in the activated areas.Testing is simplified with templates, provided for every Business Function. With the Switch Framework it is possible to control the activation of SAP ERP objects. Activating a Business Function triggers switches. The switch controls whether the switch-controlled code is executed or not at runtime. The Switch Framework is a proven concept (already used to retrofit Industry Solutions in ERP 6.0). Activation Procedure: Starting the job SFW_ACTIVATION_SF0X by choosing Activate changes in transaction SFW5 for the planned business function will run a repeat immediately to run the activation of DDIC and BC sets. Two alternative installation approaches (for SAP ECC Server) exist:

2012


717


E2E200

1) Broad Installation (Customers IT strategy for EHP installations): 1. 2.

Proactively add full scope of new functions to be in best shape to activate further business functions as soon as these are requested by the business. Use synergy effects with your maintenance cycles to avoid a separate regression test.

Advantages when working with the broad installation principle: Minimize initial effort for analyzing new functions. Be in best shape for new implementations. Main Disadvantage: All Installed EHP components have to be updated with every future SAP enhancement package installation. Potentially additional adjustment effort and downtime must be considered. 2) Selective Installation Approach (Business drives Implementation): 1. 2. 3. 4.

Look at the technical usages offered. Exclude the ones that you do not use on this system. For the remaining technical usages check if the enhancements inside potentially add value for you. If yes, install these technical usages on a sandbox system and test them.

Activated EHP components have to be updated with every future SAP enhancement package installation. Customers who have activated an industry business function set have to include the corresponding industry software component version into the EHP installation. Once you got the names of the required business functions, you have to find out the software components you need. In addition to ABAP software components, you might need to update Java components, portal content, or XI content as well. To help you ensure consistency, we have bundled ABAP components, Java components, portal content, and XI content as Technical Usages. A Technical Usage bundles a number of business functions and instances and components that are needed to make a particular business function work. It synchronizes the changes over the different stacks and components. For example, some changes in an ECC core component may need additional Portal and XI content. New business functions are mapped to technical usages by a note or documentation. A technical usage contains all components that have to be installed in the instances so that you can use a business function. New: Deactivating Business Functions

718


2012

E2E200


Activating and using the contents of a business function stores data on databases, executes process steps, changes user interfaces, sets statuses, and much more. Therefore, for technical reasons, it is not possible to reverse the activation of a business function, since this can lead to irreparable data inconsistencies the system. This is especially the case for live systems. Nonetheless, it would be helpful in many cases to be able to first test a business function without having to build a separate system for the test. For this reason, SAP delivers some business functions for which it is possible to reverse their activation. This type of business function is called reversible. For more information go to: http://help.sap.com/saphelp_tm80/helpdata/en/35/1b33b3e7764177a3218ae08f6637f0/frameset.htm The mapping of business functions and technical usage is done with the help of a SAP Note. You will find all specific information in the SAP enhancement package master guide. Please remember: SAP enhancement packages are a delta shipment for SAP ERP 6.0, so please check if additional technical components (such as TREX) are required. You find more information about this in the release notes, documentation, and the Master Guide. This mapping of software components to technical usages is done by the maintenance optimizer. Equivalent Support Packages •

•

•

SAP enhancement packages also contain a certain level of corrections and therefore require an equivalent Support Package Level for the software components which remain on version 600. Therefore, EHPs should always be installed together with the required Support Package Stack. As a consequence, customers have to adjust possible modifications and test the application, however, this was the same with the pure Support Package Stack installation. Efforts should be expected to be comparable or slightly higher. Equivalent Support Packages (see also SAP Note 1064635): –

•

Are time-synchronized SPs for different versions of one software component (SWC). – Contain identical corrections for capabilities that both versions have in common. – Differ only with respect to corrections for new capabilities (which are only provided by the higher software component version). Support Package Stacks for SAP ERP include Support Packages for SAP NetWeaver.

Installing SAP Enhancement Packages - Things You Should Know Before:

2012


719


E2E200

EHP Facts: •

•

•

Only one EHP Level per system: One application system can only consist of one EHP level (e.g. EHP4 or EHP5). Hence installed EHP components have to be updated with every future EHP implementation. Industry solutions: Customers who have activated an industry business function set have to include the corresponding EHP industry software component during installation. EHP installation and functional activation is partially non-reversible.

Technical Delivery: •

•

EHPs are “cumulative”: When installing the latest EHP you will automatically get all functionality delivered with previous Enhancement Packs. Delta Shipment: Technically the EHP installation delivers only changed objects to your system: –

•

In case you have installed EHP5 you will only install the new objects of EHP 6. – In case you have installed EHP 4 you will install EHP 5 and EHP 6 objects in one step. SAP NetWeaver 7.0 enhancement package: The application update brings a new enhancement package for SAP NetWeaver 7.0

Project Perspective: •

•

•

720

Modification adjustment: After installing Enhancement Packages modifications must be adjusted – even if no business function has been activated. Regression test required: The installation of an SAP Enhancement Package requires a full regression test – even if no business function has been activated. Effort estimation: Most customers say that the installation effort is a bit higher with EHP’s (without activating business functions) compared to pure Support Package updates.


2012

E2E200


Figure 583: Business Function Prediction for SAP® ERP - Helps you to Identify the new Functionality you Need

The prediction is based on customers system usage (ST03). You will receive an overview about enhancements that suits your business. Direct access to all project relevant information: • • •

Overview presentation & documentation. Release notes & test case catalogs. Mapping to technical usage.

To get the complete overview of new enhancement package functionality use the solution browser tool or the enhancement package infocenter. Both can be accessed via SAP Service Marketplace at www.service.sap.com/erp-ehp.

2012


721


E2E200

Figure 584: Enhancement Package Information Center- General Information

•

• •

• •

The central starting to point to get information about SAP enhancement packages is the SAP Enhancement Package Information Center. You can access it on the SAP Service Marketplace using the quick link /ERP-EHP. There, you will find the EHP FAQ document, for example, the EHP Must Know Guide and you will get direct access to the EHP forum and the Wiki pages. The Enhancement Package Information Center is the single point of access to all information related to a business function for the business expert. Here, you can find presentations, documentation, release notes, test catalogs and Learning Maps. The business function documentation allows the user to get to know the capabilities behind a business function and how to use them; learn about options the business function provides; and notes which software components are needed. Note that each business function has a technical name. This identifier is important to determine which parts of the system need to be updated. Get information on which business function (this is the switchable unit which is well described from a functional perspective) should be used. Documentation for each EHP business function is given here: – – – –

•

722

Technical Usages that are required to use the business function Additional business functions that must be activated as well Prerequisites that must be satisfied before the activation Features that become available when the business function is activated – Test catalog in order to test the new functionality Test case templates will be available for each business function that is new to an enhancement package.


2012

E2E200


•

These templates can be called directly from the switch transaction. The link to the corresponding test case is located right next to each business functions. The SAP test case templates help you to plan and perform your acceptance test and train your end users for the selected business functions. By that you are also able to narrow down the test scope because functional changes are documented for each business function. You can find these test cases before installing EHP in SAP Service Marketplace. All test cases are available as documents in the enhancement package information center and can be downloaded. Secondly after installing EHP via the switch framework. Test cases are shipped with the enhancement package and are part of the installation (SAP ECC). From there, you will (by drilldown) enter the test workbench. Test cases can be transported to SAP Solution Manager via workbench request.

•

• • • •

•

•

• •

2012

Further Services and Tools: Accelerated Innovation Enablement (AIE), Business Function Prediction and Solution Browser could be accessed from this site. SAP Solution Browser Tool: http://service.sap.com/solutionbrowser The solution browser tool for SAP ERP is an online tool and is accessible in the SAP Service Market Place or alternatively on http://erp.fmpmedia.com/ This tool is a kind of database which contains all information about release delta functionality It helps to identify new features that have been added between two releases of SAP ERP or any of the available enhancement packages and helps to find details of their respective business benefits The user logs on directly and freely and will get a selection on release delta functionality filtered by source release, target release, solution area and module. The customers are strongly encourage to use this tool to get an insight into new functionality that the new ERP release brings and to evaluate relevant new functionality which can then be mapped against the customer requirements Doing so, the solution browser tool for SAP ERP provides the input to build a value proposition for the upgrade Accelerated Innovation Enablement (AIE): Go to http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000732294&_SCENARIO=01100035870000000202& if you are interested in a certain functionality and wish to gain insight into the new features. Five days of SAP enablement will help you to evaluate the innovation capabilities of the latest SAP EHP. You will be trained by an experienced service architect.


723


E2E200

Figure 585: SAP Solution Manager - BPCA- Impact Analysis of Planned Business Functions Activation

The BPCA provides a list of all available business functions based on deployed EHPs and shows all affected business processes which will be impacted before activating the selected EHP business function. Pre-requisites: • • • •

(Lean) documentation of business processes BPCA triggered trace in order to create technical bill of material (TBOM) of critical business processes EHP deployment in DEV or sandbox system SAP Solution Manager 7.0 EHP1 SP23 or higher or SAP Solution Manager 7.1

(System Demo) SAP Enhancement Package Info Center

724


2012

E2E200


Figure 586: Switch Framework: Transaction- SFW5 Transport of Switch Settings

The switch transaction shows all the business functions that can now be activated after the installation of the new software components. In the switch framework transaction you can: • • • •

View the list of business functions available with the latest system setup Access documentation, release notes, test catalogue, and possible dependencies Install the relevant documentation, refer to SAP note 1066110 System preparation (to be performed on every system): Disable all batch jobs → e.g. report BTCTRNS1 (see SAP Note 37425) and close system for end-users (lock end- users) → Transaction EWZ5.

Afterwards you can activate the chosen business functions and perform the configuration tasks. Choose Activate Changes. The batch job for DDIC and BC set activation starts immediately → job name: SFW_ACTIVATION_SF0X (which calls report SFW_ACTIVATION_IN_BACKGROUND). By that the new coding becomes effective. All other parts of the system remain stable. •

If you like to transport the activations & customizing the following pre-requisites must be considered: – –

2012

Same ERP release with same EHP and SP-Stack installed Same technical usages installed → number and release of all software components installed in one system are the same


725


•

E2E200

Benefits: –

•

Switch settings and respective customizing can be transported across the landscape – (Adjustments after) SAP corrections can be transported – Customer enhancements can be transported. Drawbacks: –

•

Projects for activation of new business functions have to be synchronized / aligned. Overview about important SAP Notes:

–

•

SAP Note 1324838 - Mapping of Business Functions to Technical Usages – SAP Note 1524246 - Relationship of licenses and business functions – SAP Note 337623 - Customizing after installation or upgrade – SAP Note 868771 - Copy Special Customizing – SAP Note 908007 - Special functions in Switch Framework / SFW5 Important Links: – –

SAP Roadmaps (central entry page for innovation related contents): http://service.sap.com/roadmap Enhancement Package Info Center: ERP: http://service.sap.com/erp-ehp CRM: http://service.sap.com/crm-ehp SCM: http://service.sap.com/scm-ehp SRM: http://service.sap.com/srm-ehp PLM: http://service.sap.com/plm-ehp

– – – – – – –

726

Business Function Prediction: http://service.sap.com/BFP Online Knowledge Products: http://service.sap.com/OKP Upgrade Info Center: http://service.sap.com/upgrade Best practises for Application Life-Cycle Management: http://service.sap.com/alm ERP Solution Browser: http://sapsolutionbrowser.com A full list of guides can be found here:http://service.sap.com/ehp-inst Enterprise Support → Services Offerings: http://service.sap.com/enterprisesupport →SAP Enterprise Support Services


2012

E2E200


Figure 587: Overview Business Function Scope UI in SAP Solution Manager

Implementing SAP Innovations via Business Functions could be managed with help of the SAP Solution Manager. After having identified the relevant business innovations the program management and Business Process Experts could now use the projects to assign test cases, re-use the BPR and assign the business functions as well as scope the business functions for activation, activate them and configure them. Please go to: http://help.sap.com/saphelp_sm71_sp01/helpdata/en/45/51fbdbd4941803e10000000a1553f7/frameset.htm for further information. The topic is handled in an EGI called Solution Documentation.

2012


727


E2E200

Lesson Summary You should now be able to: • Understand the difference of the enhancement packages and support packages. • Describe the enhancement package concept. • Know the cycle of discovering, implementation and activation of Enhancement Packages.

728


2012

E2E200

Lesson: 718

Lesson: Maintenance Optimizer

Maintenance Optimizer Lesson Duration: 20 Minutes

Lesson Overview This lesson will give you an overview about the Maintenance Optimizer with SAP Solution Manager.


Know the software lifecycle management tools to implement patches and find information on current patch levels.

Business Example You have to plan and to carry out the maintenance in your landscape and want to know how the maintenance optimizer could support you.

2012


729


E2E200

Maintenance Optimizer: Introduction and Overview

Figure 588: Maintenance Optimizer and SAP Global Support Backbone Interaction

This picture provides an overview of the maintenance optimizer procedure. The administrator checks the Support Package Levels in the SAP Solution Manager and starts a new maintenance process from there. After selecting a system, the SAP Solution Manager provides a link to the SAP Service Marketplace where the latest support packages can be selected and added to the download basket or the MOPZ carries out automatically the delta calculation for the Support Package Levels. In the next step, there is another link from the SAP Solution Manager into the SAP Service Marketplace. Now, the administrator has to confirm the patch files in the download basket. The patch files can now optionally be downloaded via Software Lifecycle Manager to a central file share. From there, it can be implemented in the managed systems. Finally, the status of the maintenance activity is maintained in the SAP Solution Manager. All activities except for the EHP implementation (from EHP4 on) of the support packages can be done in the SAP Solution Manager. Single track system update is possible from SP18. Note that track update of the whole system landscape is still in piloting phase. Maintenance activities require considerable manual effort:

730


2012

E2E200


Various types of changes have to be applied to maintain a system landscape, e.g. • • • •

OS & DB patches, SAP kernel patches. Support packages. Enhancement Packages. Legal Change Packages and HR support packages.

Different objects have different deployment mechanisms . Correctness of landscape data is the key for a successful EHP installation: • • •

A correct landscape configuration is a major prerequisite for error-free execution of MOPZ. Erroneous or incomplete landscape information can result in failure of the update procedure. Guidance is required to correctly enter all information needed during the update process.

Solution: SAP Landscape Verification • • • • •

Helps to analyze system landscape data in SAP Solution Manager System Landscape (SMSY) in order to identify issues in landscape description. Integrated in SAP Solution Manager 7.1. SAP Landscape Verification promotes the “landscape pattern” concept. Maintenance Optimizer is the central application for all software maintenance activities in a system landscape. Maintenance Optimizer supports all maintenance types: – – – – – – –

Enhancement Package (EHP) installation. Support Package installation. Upgrade. Legal Change Package installation for SAP ERP HCM Solutions. HR Support Packages. Support of SAP Add-Ons. Support of Java Patches.

Maintenance Optimizer provides a powerful automatic delta calculation feature to ensure all needed maintenance files will be downloaded.

2012


731


E2E200

Figure 589: Maintenance Management- Overview and Integration

If you use the SAP Solution Manager Maintenance Optimizer - as strongly recommended and already required for downloading Support Packages in general - he calculates the needed software components and Support Packages automatically. Create a new maintenance transaction for updating your system with SAP enhancement packages for SAP ERP 6.0. A guided procedure leads you through the preparation process for updating your systems. Select all systems that are affected by the application of the SAP enhancement package. In the next step of the guided procedure, you select the Technical Usages you want to apply to your systems. The Solution Manager Maintenance Optimizer automatically calculates all needed Support Packages and new software component versions needed for installing the previously selected Technical Usages. As a result, the Solution Manager Maintenance Optimizer creates the Stack-XML file that can be read by the installation tools to create a valid import queue. You can find further information about the Solution Manager Maintenance Optimizer at service.sap.com/solman-mopz, detailed documentation at help.sap.com > SAP Solution Manager > (select your preferred language) in the “Change Management” section.

732


2012

E2E200


Maintenance Optimizer in Detail

Figure 590: Perform Implementation - process view - Deployment of changes throughout the landscape

The following main features of Maintenance Optimizer are available with SAP Solution Manager 7.1: Enhanced user experience: Improved Guided Procedure, WebDynpro based UI, Improved Frontend, Simplified Navigation. Redesigned back-end: Extended Features, Landscape Awareness (Supports distributed landscapes, Hubs, and the automatic delta calculation for connected systems), Support Package Stack Ranges. Support of SAP Add-Ons: Identify installed Add-On Products, Include Additional Add-Ons. Additional Java Patch Download: Java Patch Selection, Java Patch Download. Support of HR CLCs and HR Support Packages: Include HR Country Legal Changes and HR Support Packages. Better information: Direct access to Logs, Traces, XML Stack File and Documentation, PDF export.

2012


733


E2E200

Figure 591: Maintenance Optimizer- Prerequisites

Your S-user must be assigned to the same customer or corporate number as the S-user which your administrator entered in the SAP-OSS RFC destination. If this is not the case, the maintenance optimizer will not be able to read your download basket. This is done in transaction AISUSER. Always log on to the SAP Support Portal with the same S-user which is assigned to your Solution Manager user. If you do not do this, the maintenance optimizer will not be able to confirm and approve any files you place in that S-users download basket. You have installed the SAP Download Manager locally (available in the SAP Software Distribution Center in the SAP Support Portal). Settings like http services and BC-set activation are included in the basic setup in transaction SOLMAN_SETUP. Further information: • •

SAP Support Portal http://service.sap.com/solman-mopz You have configured the maintenance optimizer in SAP Solution Manager as described on SAP Help Portal at http://help.sap.com → SAP Solutions → SAP Solution Manager → SAP Solution Manager → Maintenance Management → maintenance optimizer.

Landscape pattern have now to be maintained in transaction LMDB. Deployment recommendations are published here: https://www.sdn.sap.com/irj/sdn/landscapedesign → section Distribution Models

734


2012

E2E200


There you find also details about hubs please refer to the guide “SAP Business Suite Landscape Implementation - Technical Planning Guide”. •

The new guide gives customers essential information regarding: – – –

Building blocks for system landscapes. Planning the system landscape. Distribution scenarios (hub, sidecar, embedded deployment) and example implementations.

Figure 592: Maintenance Optimizer Transaction- Select Target State

The SAP Solution Manager Maintenance Optimizer calculates the needed software components and Support Packages automatically. Create a new maintenance transaction for e.g. updating your system with SAP enhancement packages for SAP ERP 6.0. A guided procedure leads you through the preparation process for updating your systems. Select all systems that are affected by the application of the SAP enhancement package. In the next step of the guided procedure, you select the Technical Usages you want to apply to your systems. The Solution Manager Maintenance Optimizer automatically calculates all needed Support Packages and new software component versions needed for installing the previously selected Technical Usages. As a result, the Solution Manager Maintenance Optimizer creates the Stack-XML file that can be read by the installation tools to create a valid import queue.

2012


735


E2E200

To summarize: •

First you have to bring your SAP Solution Manager up-to-date before starting the maintenance. In order to use the Maintenance Optimizer application, you need SAP Solution Manager 7.0 with SP23 or higher in your system landscape. Your system landscape has to be maintained in the Solution Manager system. You can find more information about the SAP Solution Manager at help.sap.com > SAP Solutions > SAP Solution Manager. Please make also sure that you have installed the latest SPAM/SAINT update in your system.

•

•

•

Secondly, as you need a certain Support Package level in your system let the Solution Manager Maintenance Optimizer calculate the needed (and equivalent) Support Packages for you. They can be included in the installation queue - the details are explained in the next step. Thirdly please note that if you have an add-on installed in your system, ask your add-on provider whether it is compatible with the SAP enhancement package for SAP ERP 6.0. See SAP note 1318299 for details of add-ons delivered by SAP. Fourthly read the documentation and the referenced notes to check that all other prerequisites are met.

(System Demo) Maintenance Optimizer

Software Lifecycle Management Tools

736


2012

E2E200


Figure 593: Software Lifecycle Toolset

•

•

•

•

•

•

•

SAP provides you with tools and processes to manage your system landscape throughout the entire life cycle. Besides initial implementation of an application, the tools support continuous application and system optimization that result from business or organizational changes, as well as the implementation of additional functions. Software logistics aims to simplify and automate life-cycle management while reducing administration effort. SAPinst: SAP provides a powerful state-of-the-art set of tools that offers an integrated framework for the whole planning and installation process. SAPinst is the standard SAP installation tool, covering a broad range of platforms and products and both the ABAP and Java technology. Whether you install an SAP NetWeaver system, an SAP ERP system or a standalone engine – such as SAP liveCache – you can handle all these installations easily through the uniform look and feel of the SAP installation tool. SAPup/SAPJup: These are the standard SAP upgrade tools for ABAP and Java for the execution of the main upgrade activities. The tools share a similar architecture in that they both consist of an upgrade program (SAPUp or SAPJup) and a control program (Upgrade GUI or SDT GUI). SAP delivers changes to ABAP components in the form of ABAP Support Packages. These are imported using the Support Package Manager. Add-ons (such as industry solutions, plug-ins, and partner projects) are installed with the Add-On Installation Tool using the same technology. With the help of optimized maintenance tools, you can enhance and update SAP systems fast and with great flexibility. In SAP NetWeaver 2004s, the Java Support Package Manager (JSPM) has been introduced, in order to simplify the Support Package management process for Java applications at customer site. The JSPM must be called at the operating system level. SAP Enhancement Package Installer (SAPehpi): Use SAPehpi to install SAP enhancement package 1 for SAP NetWeaver 7.0 or SAP enhancement package 4 for SAP ERP 6.0 and higher. Install SAP EHPs in one process with the SP stack. You can find more information at http://www.sdn.sap.com/irj/sdn/softwarelogistics regarding software lifecycle tools. Note: If the installation tools like SPAM or SAINT import SAP Support Packages or SAP Support Package Stacks, the system is checked for a valid maintenance certificate. Fore more info please go to http://service.sap.com/maintenancecertificate. The Maintenance Certificate is stored in SAP system license store (transaction: SLICENSE). SAP import tools (e.g. SPAM, SAINT, JSPM,) check for valid Maintenance Certificate and the import is stopped if no Maintenance Certificate is available.

2012


737


E2E200

Figure 594: Software Logistics Toolset 1.0

Software Logistics Toolset stands for an SAP application product-independent delivery channel. This delivery channel includes own development tact’s, validation and test cycles as well as own shipment dates for dedicated software logistics tools. Thus, we are able to continuously provide you with software logistics tool improvements and deliver them in regular intervals, independent from SAP application product shipments. The Software Update Manager replaces SAPehpi/SAPup/SAPJup in certain areas, for example updating/upgrading to SAP Business Suite 7 Innovations 2011. New system installation 1. 2. 3.

SAPInst – installation of a new system including tech. usage “Central Applications”. Maintenance Optimizer – create stack.xml file and download required files. SAPehpi – installation of latest SP-Stack and optionally additional technical usages alternative: SPAM (for SP-Stacks only) or SAINT (for additional technical usages).

Upgrade 1. 2.

738

Maintenance Optimizer – create stack.xml file and download required files. SAPup (ABAP) / SAPJup (Java) – technical usage “Central Applications” is part of upgrade export, additional technical usages and SPs can be included into upgrade.


2012

E2E200


Update 1. 2.

Maintenance Optimizer – create stack.xml file and download required files. SAPehpi – installation of enhancement package including latest SP-Stack and selected technical usages.

For more information about available SL Toolset 1.0 improvements see: Central Release Note for Software Logistics Toolset 1.0 – 1563579 • •

SAP Service Marketplace quicklink ~sltoolset blog in SDN: http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/24127.

Figure 595: Overview About Main Steps Of EHP- Installation Procedure

The picture illustrates the use of the stack XML to feed the actual installation tools. The SAP Solution Manager creates a customer specific stack XML which contains the information about the queue of selected support and enhancement packages. For more information about the stack definition XML file, see SAP Note 884537.

2012


739


E2E200

Now the installation tools use this information to bring the specific system to a well-defined and consistent system state. The tool to use for installation depends on the type of software component: • • • • •

740

ABAP and Java software components are installed using the SAP enhancement packages installer with minimal downtime. Portal Content is installed using the JSPM tool. XI Content is usually uploaded from within the Integration Repository, which is part of usage type Process Integration (PI) of SAP NetWeaver. BW Content is applied as common Support Packages. Alternatively ABAP components can be installed using the SAINT tool and Java software components can be are installed using the JSPM tool. Please note that there might be limitations.


2012

E2E200


Lesson Summary You should now be able to: • Know the software lifecycle management tools to implement patches and find information on current patch levels.

2012


741


Lesson: 731

E2E200

System Recommendations Lesson Duration: 25 Minutes

Lesson Overview This lesson will give you an overview about the System Recommendations with SAP Solution Manager.


Know how to work with System Recommendations.

Business Example You are focusing on security-relevant SAP notes and want to get an overview about all relevant notes on the tab “security relevant notes” in System Recommendations. You are also interested in missing SAP Notes for a certain application component.

System Recommendations: Overview Software security remains a critical topic of interest to all companies and to the information technology industry. The security of a specific system thereby also significantly depends on the secure installation and operation of this system. SAP gained a lot of experience from its support for and engagement with numerous customers. It uses the resulting best practices not only for further improvements and enhancements of its support offering but also makes them available as recommendations, services and tools directly to its customers. Using the new application System Recommendations within the SAP Solution Manager you can track down critical Security Notes which are required for your systems. You could use Configuration Validation to analyze the security configuration for system landscape. To keep your SAP systems up-to-date and secured you have to apply various types of notes and patches. System Recommendations shows all relevant notes and patches for the selected systems in the SAP Solution Manger and helps you to keep all of your systems up-to-date.

742


2012

E2E200

Lesson: System Recommendations

Figure 596: System Recommendations: Overview

System Recommendations is a new functionality in SAP Solution Manager, focusing on SAP Notes. It provides a tailored recommendation of SAP notes which should be applied to a selected managed system, and this recommendation is calculated based on the actual “SAP notes status” of this system. Questions like “Is a specific SAP note already implemented in the system?” or “Which version do the implemented SAP notes have? Are there newer versions available?” are taken into account when calculating the recommendation for a system. System Recommendations collects needed information from the managed systems via a background job that should be scheduled on a regular basis (a direct refresh of the already calculated information for a specific system can also be started directly). The calculation itself is done in SAP’s Global Support Backbone, which means that there is no load being generated on the SAP Solution Manager system or on the managed system. The recommendation is divided into the following note categories: • • • • •

2012

Security-relevant notes. Performance notes. HotNews. Legal change notes. Correction notes (for ABAP and Java).


743


E2E200

After the recommendation has been calculated, the user can set various statuses for the recommended notes, like “to be implemented”, “not relevant” or “postponed”. This, in combination with a filter displaying only notes with a certain status, helps to keep an overview of all the recommendations and helps keeping track of tasks which are assigned to those recommendations.

Figure 597: System Recommendations: Process Flow

The following steps are necessary to run System Recommendations: • •

•

The SAP-OSS RFC connection needs to be set up correctly All managed systems have to be connected to SAP Solution Manager and documented in transaction SMSY, and they have to be assigned to a product system and to a solution Authorization object: SM_FUNCS (Control access and visibility of tabs in System Recommendations)

To collect this data automatically for the use within System Recommendations you should set up a batch job in the “Settings” area of System Recommendations. System Recommendations is part of the “Change Management” Work Center in SAP Solution Manager. More information is available within the following blog: http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/24227 or in the online Help:http://help.sap.com/saphelp_sm70ehp1_sp26/helpdata/en/83/68fad4952d42a192469fa02586aeff/frameset.htm

744


2012

E2E200


Figure 598: SAP Solution Manager Security Services- support your security patch management by using System Recommendations

2012


745


E2E200

The Security Patch Day of SAP takes place on every 2nd Tuesday per month. •

•

•

•

•

•

•

At the end of that day you can inspect the updated list of Security Notes on the page /securitynotes in the Service Marketplace. Here you see the complete list of all Security Notes. Use the application System Recommendations to check which of the Security Notes are relevant for the various systems of your system landscape. (Usually you have scheduled the check as a background job, therefore you check the results e.g. on Wednesday.) You can create change requests directly from that tool. The EarlyWatch Alert report and the corresponding tool RSECNOTE show strong recommendations from Active Global Support concerning HotNews and other important notes which are relevant for a given system. Usually you create and check these reports at the beginning of the next week. You will run a Risk Assessment concerning the criticality of the Security Note as well as concerning the risk of applying a change which might touch productively used business processes. As a result you decide which Security Notes should be applied as part of a monthly patch cycle and which will be part of the next maintenance cycle. Using the application Configuration Validation you can create a report which checks which systems comply with your security policy. Therefore you add all notes which should be installed into the target system definition of the Configuration Validation. Within the current month you apply the selected Security Notes and you run regression tests (if necessary) to ensure productively used business processes are working properly. As part of the next maintenance cycle you will update the Kernel, apply Java Patches and ABAP Support Packages. As part of this update you will get the corrections of the Security Notes, too. However, some of the Security Notes describe configuration changes which you can apply now as well. While working on the update it might be the case that you will get new Security Notes from newer Patch Days. You should include these if possible. Finally you run a complete test of your business processes.

Hot News SAP HotNews are priority 1 (very high priority) SAP customer notes. These notes tell you how to resolve or avoid problems that can cause the SAP system to shut down or lose data. If you are affected by these problems, you must ensure that you are aware of these notes. Recommendation: Set up regular procedures to check for new HotNews. Define a responsible person to check for new HotNews and creation of requests for change. Requests for change are forwarded to the person responsible for the process.

746


2012

E2E200


Figure 599: How System Recommendations supports your security Process flow

As the engineer is focusing on security-relevant SAP notes, he now finds all relevant notes on the tab “security relevant notes”. To get more information on the recommended SAP notes, he can drill down further into each one of them, read the description of the note (by clicking on the notes title) and select a status – new, to be implemented, postponed, not relevant - for every note.

2012


747


E2E200

Figure 600: System Recommendations- Key Elements

System Recommendation can also be used for Java systems. The procedure is exactly the same as described above; the only difference is that the Java patch notes will only show up on the tab “correction notes”. With the button “Add to download basket”, the Java patches containing the selected notes directly can be added to the download basket in SAP Service Marketplace. An integration into Maintenance Optimizer to approve the download basket is also available. Integration: •

748

For Customers using the Change Request Management functionality in SAP Solution Manager, System Recommendations provides integration into the Change Request Management to trigger a Request for Change for the SAP notes selected for implementation. Integration into Maintenance Optimizer is provided to directly download the Java Patches containing relevant Java Patch notes. Integration into SAP Service Marketplace is available to directly add selected Java Patches to the users download basket. Additionally, integration into Configuration Validation (starting with SP03) exist to enable the compare of systems in your landscape. You could validate the notes that e.g. in status “To be implemented” in all systems of your solution.


2012

E2E200


Figure 601: What’s coming next with System Recommendations? Outlook

To give improved support for testing, the object list will be provided (planned for ST SP05). Thus the BPCA analysis could be started and used for testing integration. In case Change Request Management is not used an integration to transaction SNOTE in the development is provided. The SAP Note that is to be implemented will be sent to SNOTE and can be implemented there. Additional info regarding the correction instruction will be listed to provide a better overview about the impact and effort that has to be expected when implementing the SAP Note. The flat list view is also available and provides improved searching possibilities.

2012


749


750


E2E200

2012

E2E200

739


Exercise 20: System Recommendations Exercise Duration: 15 Minutes

Exercise Objectives After completing this exercise, you will be able to: • Understand how the data collection from the managed systems is been organized. • Apply System Recommendations to find out the SAP notes and corrections missing into each of the managed systems.

Business Example System Recommendations automatically provides a tailored recommendation of SAP Notes for ABAP and Java-based SAP systems that is missing on a selected solution. Based on the actual status of the system, you find missing SAP notes including security notes, performance-relevant notes, Java patches, legal change notes, high priority “HotNews” as well as general SAP Notes. A system and security engineer who is responsible for various SAP systems wants to find out exactly which patches released from SAP on the monthly Patch Day are relevant to secure his system(s). In this exercise you will learn how System Recommendations can help to fulfill this task.

Task 1: Use System Recommendations to find the SAP notes, that need to be implemented in each of the managed systems. 1.

Start System Recommendations. Use solution System_Recommendations for this task. Set the time frame to released from 01 December 2011 to 19 January 2012.

Task 2: 1.

How is the automatic data collection for missing SAP Notes in the managed systems organized within System Recommendations?

2.

Are all technical systems from your solution System_Recommendations checked?


2012


751


E2E200

Task 3: Perform the System Recommendations check for the technical system RWE[ABAP] and the application components IS-H-CM and IS-H-PA. 1.

Use the filter functionality within the Application Component area for this task. Assign a status to those SAP Notes.

Task 4: Download the work list for the found SAP Notes in an excel sheet. 1.

Task 5: Start the approval process for the relevant notes using Change Request Management workflow of SAP Solution Manager 7.1 1.

752

-


2012

E2E200


Solution 20: System Recommendations Task 1: Use System Recommendations to find the SAP notes, that need to be implemented in each of the managed systems. 1.

Start System Recommendations.


2012


753


E2E200

Use solution System_Recommendations for this task. Set the time frame to released from 01 December 2011 to 19 January 2012. a)

To start System Recommendations call transaction SM_WORKCENTER and select tab Change Management. On the left hand side choose System Recommendation.

Figure 602: Change Management

On the right hand side in the area Filter System Recommendations by: add the necessary information. To get the exact recommendation, first select the solution System_Recommendations. This results in a list of product systems RWS, RWE and RWZ which are part of this solution. Select the relevant Product System, we use RWE in this exercise, and the Technical System RWE [ABAP], as shown at the picture below.

Figure 603: Specify Data

To look only for notes within a specific time range a timeframe can be set accordingly. Please choose the time frame as given in above figure.

Task 2: 1.

How is the automatic data collection for missing SAP Notes in the managed systems organized within System Recommendations?


754


2012

E2E200


a)

To find out more information about the data collection for SAP Notes use the link Settings on the right hand side of System Recommendations navigation area.

Figure 604: Change Management

The System Recommendations Settings wizard will be opened in a new browser window. Now you can schedule a job for the systems that you wish to include into the automatic check.

Figure 605: Settings for the Automatic Check

b)

To check which technical systems are included into the automatic check go to the second step in the System Recommendations Settings wizard by choosing the Next button. Here you can check and maintain the list of technical systems that should be considered for the System Recommendations check.


2012


755


E2E200

Figure 606: Add Technical Systems

2.

Are all technical systems from your solution System_Recommendations checked? a)

Yes

Task 3: Perform the System Recommendations check for the technical system RWE[ABAP] and the application components IS-H-CM and IS-H-PA. 1.

Use the filter functionality within the Application Component area for this task. Assign a status to those SAP Notes. a)

In the Application Component filter you could choose the components to reduce the amount of recommended SAP notes, for example IS-H-CM and IS-H-PA

Figure 607: Application Component

(Optional) After you fulfilled all settings you can save your filter using button Save Filter to re-use it later. Continued on next page

756


2012

E2E200


b)

Click on Apply Filter button to start the calculation of the System Recommendations. There are two different Views to display the list of recommended notes: Application Component view (this is the default) or Software Component view. The views can be changed using the dropdown box View.

Figure 608: Prepare Working List

When using the Software Component view, the information SP related or SP independent is displayed. SP related means that this note is relevant for the system, the SP level will be given and there is a correction instruction available.

Figure 609: Software Component View

To get all information on the recommended SAP notes jump into the service market portal by clicking on its title in the Short Text column.

Figure 610: Short Text

Mark the notes that need to be implemented and set the status of the marked notes on To be Implemented using the Set Status button.


2012


757


E2E200

Figure 611: Set Status

Task 4: Download the work list for the found SAP Notes in an excel sheet. 1. a)

You could download your work list of SAP notes and their status by using the Export button:

Figure 612: Export to MS Excel

Task 5: Start the approval process for the relevant notes using Change Request Management workflow of SAP Solution Manager 7.1 1.

a)

To request the implementation of the selected notes create Request for Change by click on the Create Request for Change button . In the new opened browser window change to Edit mode and add all necessary information for the Request for Change.

Figure 613: Request for Change

Create a new normal change. Now you could follow the Change Request Management procedure as described in the previous chapter of the E2E200-training.

758


2012

E2E200


Lesson Summary You should now be able to: • Know how to work with System Recommendations.

2012


759


Lesson: 748

E2E200

Upgrade / Change Impact Analysis Lesson Duration: 25 Minutes

Lesson Overview This lesson will give you an overview about the Custom Development Management Cockpit Upgrade and Change Impact Analysis with SAP Solution Manager.


Perform an upgrade or change impact analysis with the custom development management cockpit. Know SAP’s best practice recommendations for maintenance management.

Business Example Your system landscape is up and running for a long time. You wish to reduce the maintenance effort by knowing which of your custom objects are really be used in your system and affected by the implementation of support packages.

Upgrade / Change Impact Analysis With the Upgrade/Change Impact Analysis, you can find out about the technical impact of an SAP Upgrade or Support Package on your custom developments and estimate the amount of work required for adapting them. In particular, in case custom-developed solutions use some SAP standard objects that are changed in the course of the upgrade or Support Package, Enhancement Package implementations adjustments of custom developments are required.

760


2012

E2E200

Lesson: Upgrade / Change Impact Analysis

Figure 614: Parts of CDMC

The Custom Development Management Cockpit addresses these issues by providing a set of features that support the handling and organization of ABAP custom development objects in SAP systems. You can use SAP CDMC to: • • •

2012

Analyze custom developments in your SAP system, and identify obsolete developments (Clearing Analysis). Identify the potential consequences an upgrade can have on custom developments (Upgrade / Change Impact Analysis). Analyze the usage of customer objects in transport requests by carrying out quality checks to secure testing and that no object versions get overwritten (Change and Transport System Analysis).


761


E2E200

Figure 615: Upgrade/Change Impact Analysis- The Challenge

To identify the potential consequences an upgrade can have on custom developments the above questions need to be answered.

Figure 616: Custom Development Management Cockpit - Upgrade Change Impact Analysis (UCIA)

This picture should illustrate the different roles of systems in a Upgrade Change Impact Analysis. •

762

Upgrade Change Impact Analysis (UCIA):


2012

E2E200


With the Upgrade Change Impact Analysis, you can analyze the technical impact of an SAP Release Upgrade or a Support Package Upgrade on your custom developments and estimate the amount of work required for adapting them. •

•

•

•

Analysis System is the system (usually the Quality Assurance System) where all project-related analyses (including selection of relevant objects) are performed in the background, and the results are stored in a CNV* database table. Control System is the system (usually the central Solution Manager System), where all activities in systems with other system roles such as statistic system and analysis system are triggered from here via RFC connections. Reference System is the system in which the upgrade or other planned change has already been carried out, so that the SAP objects exist there in the version from after the change. During the impact analysis, this version is compared against the version from before the change that is stored in the analysis system Define participating systems and roles in CDMC projects check and fulfill prerequisites for CDMC installation. Following steps are required: – – – –

Install ST-PI on Solution Manager (control center ). Install ST-PI on Quality System or Development box (analysis system, “as-is”). Install ST-PI on a “upgraded” box (containing new SAP code, reference system ). Set Up RFC connection from SAP Solution Manager to Satellites and maintain necessary CDMC roles and authorizations (SAP Note 1244713).

Implementation of the collective note – the number depends on the support package of the ST-PI. Note: The ST-PI level has to be the same on all involved systems! • •

2012

An Upgrade/Change Impact Analysis project consists of five phases: Global Settings, Project Settings, Collect, Analysis and Display. The Project Settings phase includes two tasks: Defining the system landscape for the project (as described above), and displaying the relevant SAP Notes. In the general settings for your CDMC installation, you defined SAP Notes that are likely to be relevant for your projects. When you execute the function for activity Display SAP Notes, you get a list of Notes and can check the ones that are likely to contain useful information for your current project. In the Maintain adjustment times activity, you define the average adjustment times per object type for your custom developments.


763


•

• •

• •

•

•

764

E2E200

The Analysis phase consists of the following activities: – Find Referred SAP objects. – Import Statistics. – Perform Usage Analysis. – Find changed SAP objects. – Perform remote comparison. – Calculate Adjustment Times. – Customer batch input analysis. – Analyze external subroutine calls. When the comparison is finished, you can look at the analysis results and decide how to proceed with the listed objects. In the “global settings” phase, the preparations for an Upgrade/Change Impact Analysis project is limited to the maintenance of average adjustment times per object type. These times reflect the average duration that is necessary to adjust a custom development in the course of an upgrade. This information will be the basis for a first effort estimation to adjust the custom objects in the course of an upgrade to ensure a better planning security and helping to keep the upgrade costs within the given budget. The Project Overview screen is your central “cockpit” for all activities in an Upgrade/Change Impact Analysis (UCIA) project. The project tree (as shown on the slide) contains all activities for a UCIA project. Each activity has an executable function, which you start by choosing the Execute symbol next to the relevant activity. You also get the admin information that you require to monitor the progress of each activity and of the project as a whole, for example the activity status and the runtime. An activity log with more detailed status information is available for each activity that has been executed. In addition, the Project Overview screen contains general information about your project and the participating systems, so that you have it at hand at any time during your project.


2012

E2E200


Figure 617: Analysis Phase of a UCIA Project (1)- Analysis System

In the first analysis activity, a list is prepared that contains all the SAP objects that are being used in your custom developments. You can choose if you want the list to cover all objects in the customer namespace or only objects from the specified development classes (packages). All project-related analyses (including selection of relevant objects) are executed in the analysis systems, and the results are stored in a CDMC database table. This is to avoid putting too much load on the production system. The role analysis system is usually taken over by the QAS system (quality assurance system) and should contain a consistent set of custom development objects used for the subsequent analysis activities. If this is not the case, a system reconciliation needs to be performed with the Check TADIR inconsistencies activity. A typical analysis system would be a QAS system.

2012


765


E2E200

Figure 618: Analysis Phase of a UCIA Project (2)- Reference System

In this activity, you find the intersection of the SAP objects used in the customer-specific objects and the SAP objects changed during the upgrade (or other change). When using a reference system, the program for this activity runs in the reference system. If you want to check the implications of a transport for a support package or correction, you can specify this transport in the dialog box that is displayed when you execute the function. The reference system is the system in which the upgrade or other planned change has already been carried out, so that the SAP objects exist there in the version after the change. During the impact analysis, this version is compared against the version from before the change, which is stored in the analysis system. The test system for the upgrade may be used as the reference system.

766


2012

E2E200


Figure 619: Analysis Phase of a UCIA Project (3)

In the last activity of this phase, you compare the found objects in the reference system or knowledge base to their counterparts in the analysis system. The program that runs in this activity performs the comparison and evaluates the results. For each custom object, the program notes if it is affected by the planned upgrade or change or not. In addition, the program uses the results of the comparison and the adjustment times you specified earlier to calculate the estimated effort required to adjust these objects. This activity, like all the others, is triggered from the control system and obtains the required information from the analysis system and the reference system through the RFC connections. If the knowledge base is used, no RFC connections are necessary to the reference system as the knowledge base data is stored in the control system. The control center for all CDMC projects is located in the control system. All activities in systems with other system roles are triggered from here via RFC connections. CDMC projects and their process trees are created and accessed in the control center. The results of the analyses are transferred from all other systems to this system so that you can view and maintain them here. Usually, this system role is taken over by the central Solution Manager system, as it provides integration aspects into other Solution Manager applications.

2012


767


E2E200

Figure 620: Analysis Phase of an Upgrade/Change Impact Analysis Project

An Upgrade/Change Impact Analysis project consists of four phases: Project settings, collect, analysis, and display. The project settings phase includes three activities: Defining the system landscape for the project (as described above), displaying the relevant SAP Notes and to maintain the adjustment times. The background for the activity of displaying the relevant SAP Notes is as follows: In the general settings for your CDMC installation, you defined SAP notes that are likely to be relevant for your projects. (This is described in more detail in the overview tutorial for CDMC.) When you execute the function for activity Display SAP Notes now, you get this list of Notes and can check out the ones that are likely to contain useful information for the project at hand. In the activity “maintain adjustment times” you define the average adjustment times per object type for your custom developments. The CDMC overview screen is your central entry point for a clearing analysis or an upgrade/change impact analysis project. The CDMC can be started from the Upgrade roadmap, the Implementation/Upgrade work center, or from SAP Solution Manager by using transaction code CNV_CDMC (CDMC users need a special authorization role; see SAP Note 1244713). On the overview screen, the parts of CDMC are clustered in a folder structure. The folders are also called “nodes.” On this screen, you can also execute the activities of the Global Settings phase. An activity documentation is available for every activity within that phase, which can either be executed via the Execute button or another dedicated button.

768


2012

E2E200


Figure 621: Phases of a Upgrade/Change Impact Analysis Project

The Project Settings phase includes five tasks: • • •

•

•

Defining the system landscape for the project (as described above). Get Copied Programs List (In this activity, you identify the custom objects copied from SAP objects.) Maintain Copied Programs List (CDMC returns a list of all customer programs copied from the SAP programs from the ANALYSIS system. You can then add an object to the list and, delete, change or save any object in this list.) Displaying the relevant SAP Notes. In the general settings for your CDMC installation, you defined SAP Notes that are likely to be relevant for your projects. When you execute the function for activity Display SAP Notes, you get a list of Notes and can check the ones that are likely to contain useful information for your current project. In the Maintain adjustment times activity, you define the average adjustment times per object type for your custom developments.

Within the Global Settings phase, the preparations for an upgrade/change impact analysis project are limited to the maintenance of average adjustment times per object type. These times reflect the average duration that is necessary to adjust a custom development in the course of an upgrade. This information will be the basis for a first effort estimation to adjust the custom objects during an upgrade to ensure better planning security and help keep the upgrade costs within budget. Find Referred SAP Objects

2012


769


E2E200

In this activity a list of all the SAP objects that are referred in custom developments in the analysis system is prepared. The customer objects list can include either all objects in the customer namespace or only objects of the specified development classes (packages) or piece lists or Solution Manager projects or Solution Manager solutions. Found objects will only be considered once. Import Statistics If the user wants to perform the usage analysis for the impacted objects then he can add statistics system in his landscape and execute the activities Import Statistics and Perform Usage Analysis in the Analysis phase. The functionality of these two activities is similar to Import Statistics and Top Down Analysis in the Clearing Analysis and the execution of these activities is optional. Find Changed SAP Objects •

•

In this activity you determine the intersection of the SAP objects that are referred by custom objects and the SAP objects that are affected by an Upgrade or Service Pack application. This activity runs in the reference system provided the user has chosen a reference system instead of a Knowledge Base while defining the UCIA project landscape.

Perform Remote Comparison In this activity, CDMC compares the relevant objects in the reference system / reference information base against their counterparts in the analysis system. For each custom object, the program determines if it is affected by the planned upgrade or change. In addition, the program uses the results of the comparison and the adjustment times you specified earlier to calculate the estimated effort required to adjust these objects. Calculate Adjustment Times On execution of this activity a background job is scheduled in the control system performing the following steps: 1.

2. 3.

Check whether the activities ’Maintain Adjustment Times’, ’Find Referred SAP Objects’, ’Find Changed SAP Objects’ and ’Perform Remote Comparison’ have been executed successfully for that project The adjustment times entered by the user in activity ’Maintain Adjustment Times’ are saved for all referred SAP objects Adjustment times are cumulated for all customer objects by adding the adjustment times of all referred SAP objects

Customer Batch Input Analysis This activity which runs in the analysis system returns a list of all customer batch input programs affected by an upgrade or Support Package implementation. Analyze External Subroutine Calls

770


2012

E2E200


In this activity which runs in the analysis system CDMC determines a list of all the custom programs containing external subroutine calls to standard SAP programs that are changed by an upgrade or a support package application.

Figure 622: Working with the UCIA Result List: Object-Oriented Selection and Sorting Criteria

When the comparison is finished, you can look at the analysis results and decide how to proceed with the listed objects. The example given here has been simplified to show you the basic structure of the list. In the real CDMC environment, you have various options for viewing and filtering the data. For example, you can choose between a compressed view and a detailed view. You can also calculate total adjustment times for different sets of objects to get a clearer idea of the amount of work that is required in different areas. You can also set the status for each object you analyzed and assign a “processor,” that is, a person who should analyze the given object in more detail and decide how to handle it. You can download the results in a piece list and send them to the assigned processors. The meaning of the traffic lights in the Impact column is as follows: • • •

A green traffic light means that no adaptation of the object is required in connection with the planned upgrade or change. A yellow traffic light means that adaptation of the object is probably required. A red traffic light means that the object must be adapted to ensure it functions correctly after the upgrade (or other change).

The traffic lights in the Impact column of the compressed view represent a summary evaluation for each custom object. This evaluation is based on a detailed analysis of each SAP object used by the given custom object.

2012


771


E2E200

The detailed view shows the results of the analysis and provides more information about the rating criteria. For example, if the data type for a data element changes during the upgrade, the data element gets a red light in the detailed analysis, and all custom object that refer to this data element also get a red light in the summary impact evaluation.

Figure 623: Working with the UCIA Result List- Indirectly Impacted Objects

By clicking the Comparison Result button in the Result List, you have access to a list of objects that have been affected in the upgraded system. This is a good way to figure out what objects we need to focus our efforts on.

772


2012

E2E200


Figure 624: Working with the UCIA Result List- Assigning a Processor

You can also set the status for each object you analyzed and assign a “processor”, that is, a person who should analyze the given object in more detail and decide how to handle it. You can download the results in a piece list and send them to the assigned processors. The process for obtaining and analyzing the objects in question according to the use case looks like this: • • • • •

• •

Select the objects you would like to analyze. Determine the estimated effort connected with the affected objects (option with maintained adjustment times). Assign a processor to the objects. Send notification to the processors. Analyze the impact the SAP object has on the customer object by using the following features: – Remote comparison of referenced SAP objects – Retrieval of further object details Set the status of each object to be analyzed. Monitor the status of the development activities centrally in SAP Solution Manager.

(System Demo) Working with the Result List

2012


773


E2E200

Figure 625: Maintenance Management- Summary of Recommendations

774


2012

E2E200


Lesson Summary You should now be able to: • Perform an upgrade or change impact analysis with the custom development management cockpit. • Know SAP’s best practice recommendations for maintenance management.

2012


775

Unit Summary

E2E200

Unit Summary You should now be able to: • Understand SAP’s Maintenance Strategy • Explain the support package stack strategy • Describe main types of support items delivered by SAP • Execute side effect reporting for a Support Package queue • Understand the difference of the enhancement packages and support packages. • Describe the enhancement package concept. • Know the cycle of discovering, implementation and activation of Enhancement Packages. • Know the software lifecycle management tools to implement patches and find information on current patch levels. • Know how to work with System Recommendations. • Perform an upgrade or change impact analysis with the custom development management cockpit. • Know SAP’s best practice recommendations for maintenance management.

776


2012

E2E200

Course Summary

Course Summary You should now be able to: •

2012

Know to use the capabilities SAP offers to manage Change Control Management.


777

Course Summary

778

E2E200


2012

Feedback SAP AG has made every effort in the preparation of this course to ensure the accuracy and completeness of the materials. If you have any corrections or suggestions for improvement, please record them in the appropriate place in the course evaluation.

2012


779

e2e200 en Col93 Fv Inst a4

Recommend Documents