Smi310 en Col84

SMI310SAP Solution Manager:

Implementation Projects withSAP Solution Manager

SAP Solution Manager

Date

Training Center

Instructors

Education Website

Participant HandbookCourse Version: 84Course Duration: 3 Day(s)Material Number: 50095974

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

Copyright

Copyright © 2010 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purposewithout the express permission of SAP AG. The information contained herein may be changedwithout prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary softwarecomponents of other software vendors.

Trademarks

• Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® areregistered trademarks of Microsoft Corporation.

• IBM®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®, RS/6000®, AIX®,S/390®, AS/400®, OS/390®, and OS/400® are registered trademarks of IBM Corporation.

• ORACLE® is a registered trademark of ORACLE Corporation.• INFORMIX®-OnLine for SAP and INFORMIX® Dynamic ServerTM are registered

trademarks of Informix Software Incorporated.• UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group.• Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®,

VideoFrame®, MultiWin® and other Citrix product names referenced herein are trademarksof Citrix Systems, Inc.

• HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, WorldWide Web Consortium, Massachusetts Institute of Technology.

• JAVA® is a registered trademark of Sun Microsystems, Inc.• JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for

technology invented and implemented by Netscape.• SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP

EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.comare trademarks or registered trademarks of SAP AG in Germany and in several other countriesall over the world. All other products mentioned are trademarks or registered trademarks oftheir respective companies.

Disclaimer

THESEMATERIALS ARE PROVIDED BY SAP ON AN "AS IS" BASIS, AND SAP EXPRESSLYDISCLAIMS ANY AND ALL WARRANTIES, EXPRESS OR APPLIED, INCLUDINGWITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY AND FITNESS FOR APARTICULAR PURPOSE, WITH RESPECT TO THESE MATERIALS AND THE SERVICE,INFORMATION, TEXT, GRAPHICS, LINKS, OR ANY OTHER MATERIALS AND PRODUCTSCONTAINED HEREIN. IN NO EVENT SHALL SAP BE LIABLE FOR ANY DIRECT,INDIRECT, SPECIAL, INCIDENTAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES OF ANYKIND WHATSOEVER, INCLUDING WITHOUT LIMITATION LOST REVENUES OR LOSTPROFITS, WHICH MAY RESULT FROM THE USE OF THESE MATERIALS OR INCLUDEDSOFTWARE COMPONENTS.

g2010029103157

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

Typographic ConventionsAmerican English is the standard used in this handbook. The followingtypographic conventions are also used.

Type Style Description

Example text Words or characters that appear on the screen. Theseinclude field names, screen titles, pushbuttons as wellas menu names, paths, and options.

Also used for cross-references to other documentationboth internal and external.

Example text Emphasized words or phrases in body text, titles ofgraphics, and tables

EXAMPLE TEXT Names of elements in the system. These includereport names, program names, transaction codes, tablenames, and individual key words of a programminglanguage, when surrounded by body text, for exampleSELECT and INCLUDE.

Example text Screen output. This includes file and directory namesand their paths, messages, names of variables andparameters, and passages of the source text of aprogram.

Example text Exact user entry. These are words and characters thatyou enter in the system exactly as they appear in thedocumentation.

<Example text> Variable user entry. Pointed brackets indicate that youreplace these words and characters with appropriateentries.

2010/Q1 © 2010 SAP AG. All rights reserved. iii

About This Handbook SMI310

Icons in Body TextThe 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'spresentation.

iv © 2010 SAP AG. All rights reserved. 2010/Q1

ContentsCourse Overview ......................................................... vii

Course Goals .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .viiCourse Objectives ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Unit 1: Introduction to SAP Solution Manager Implementation. 1SAP Solution Manager Supporting Implementations ... . . . . . . . . . . .2

Unit 2: Prerequisites for Implementation Projects ............... 23Technical Prerequisites for Implementation Projects .. . . . . . . . . . . . 24

Unit 3: Project Preparation ............................................ 33Project Administration ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Unit 4: Use of Roadmaps .............................................. 63Working with the Roadmap Methodology... . . . . . . . . . . . . . . . . . . . . . . . 64

Unit 5: Business Blueprint............................................. 91Business Blueprint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92Document Management .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128Reporting... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .152

Unit 6: Realization ...................................................... 157Configuration and Development .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .158Testing ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .185

Unit 7: Final Preparation .............................................. 227E-Learning ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .228

Unit 8: From Implementation to Operations ...................... 235From Implementations to Operations ... . . . . . . . . . . . . . . . . . . . . . . . . . .236

Unit 9: Service Desk.................................................... 247Working with the Service Desk... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .248

Unit 10: Managing Projects - Beyond Implementation ......... 257Template Management .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .260Solution Documentation Assistant .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .278

2010/Q1 © 2010 SAP AG. All rights reserved. v

Contents SMI310

Business Process Change Analyzer .. . . . . . . . . . . . . . . . . . . . . . . . . . . . .293

Unit 11: Authorization and Roles.................................... 311Working with Authorizations and Roles ... . . . . . . . . . . . . . . . . . . . . . . . .312

Unit 12: Additional Information...................................... 325Further Information ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .326

Index ....................................................................... 333

vi © 2010 SAP AG. All rights reserved. 2010/Q1

Course OverviewThe SAP Solution Manager is an integrated, customer platform that provides theprocedures, tools and content needed to successfully and efficiently implement,operate and optimize their SAP and non-SAP solutions, regardless of thecomplexity of the system landscape. The purpose of this course is to introduceyou to the SAP Solution Manager and is focused on the implementation portfoliodelivered with this lifecycle platform.

The information in this course pertains to the following SAP SoftwareComponents and releases:

• SAP Solution Manager 7.0 EhP1• SAP CRM 5.0• SAP ERP 6.0

Target AudienceThis course is intended for the following audiences:

• Project managers/leaders, project team members (applicationconsultants/business process experts), test organizers and testers responsiblefor managing, documenting, configuring and testing SAP solutions

Course PrerequisitesRequired Knowledge

• SAP01 – SAP Overview• SM100 – Introduction to SAP Solution Manager

Recommended Knowledge

• Functional knowledge of Business Configuration (BC) Sets• Basic knowledge of testing strategies and testing tools such as Test

Workbench and eCATT• SMI210 – SAP Solution Manager: Implementation Methodology Overview

OR• Knowledge/Experience using the ASAP methodology

2010/Q1 © 2010 SAP AG. All rights reserved. vii

Course Overview SMI310

Course GoalsThis course will prepare you to:

• Understand the concept of SAP Solution Manager with the focus onsupporting implementation (and upgrade) projects

• Explore tools, contents, and methods in detail to successfully and efficientlyimplement complete software solutions and new enhancements

• Use the tools, content, and methods, provided to successfully and efficientlyimplement your SAP/non-SAP solution

Course ObjectivesAfter completing this course, you will be able to:

• Explore the key concepts of SAP Solution Manager in the context ofimplementation projects

• Understand the concepts of application lifecycle management (ALM) andhow SAP Solution Manager supports ALM

• Define a project and document the system landscape for the solution to beimplemented

• Design and document the project scope, including its business requirements• Configure the project scope• Organize, perform and document all project-related test activities• Use roadmaps as the underlying project methodology• Explore reports to support project management activities• Learn about handling problem messages in implementation projects• Get an impression of how SAP Solution Manager supports the maintenance

of your productive environment• Learn about implementation-related topics, such as template management,

Solution Documentation Assistant and Business Process Change Analyzer• Get technical background information as required for your project role• Locate additional information about the SAP Solution Manager

viii © 2010 SAP AG. All rights reserved. 2010/Q1

Unit 1Introduction to SAP Solution Manager

Implementation

Unit OverviewSAP Solution Manager is SAP's service and support platform to help youimplement and operate your SAP solution efficiently. Together with the SAPService Marketplace, SAP Solution Manager represents SAP's strategic serviceinfrastructure that guides our customers through all stages of their SAP solutionlife cycle.

Unit ObjectivesAfter completing this unit, you will be able to:

• Define the drivers for new implementation projects• Describe the use of SAP Solution Manager in implementation projects• Outline the key benefits of SAP Solution Manager in implementation projects• Extend the notion of implementation support to a holistic application

lifecycle management approach

Unit ContentsLesson: SAP Solution Manager Supporting Implementations ... . . . . . . . . . . . .2

2010/Q1 © 2010 SAP AG. All rights reserved. 1

Unit 1: Introduction to SAP Solution Manager Implementation SMI310

Lesson: SAP Solution Manager SupportingImplementations

Lesson OverviewThis lesson introduces SAP Solution Manager as a platform to supportimplementation projects. This concept is extended to the idea of applicationlifecycle management, which SAP Solution Manager supports with a dedicatedportfolio of tools, services and methods.

Lesson ObjectivesAfter completing this lesson, you will be able to:

• Define the drivers for new implementation projects• Describe the use of SAP Solution Manager in implementation projects• Outline the key benefits of SAP Solution Manager in implementation projects• Extend the notion of implementation support to a holistic application


Business ExampleThe SAP Solution Manager is a platform that provides the integrated content,tools, and methodologies that you need to implement, support, operate andmonitor your enterprise's solutions from SAP and non SAP. With SAP SolutionManager, you can minimize risk and increase the reliability of your IT solutions.It helps you to manage your core business processes and link business processes tothe underlying IT infrastructure.

The following brief storyline sets a broad frame for this course:

As a globally operating sales company, you intend to implement dedicated parts ofan SAP CRM and SAP ERP solution, with the SAP Solution Manager. Duringthis course, you will explore the different roles and tasks involved in such animplementation procedure.

• As a project manager, you will establish a project framework, includingdefining the project, introducing project team members to the project, andsetting project-specific standards.

• As a business process expert or application consultant, you will beresponsible for the central business process design, and the documentation tobe implemented in the later configuration phase.

• As a test coordinator, you will familiarize yourself with all the necessarysteps from test planning to test execution and test reporting.

• As a tester, you will learn how to test the implemented solution and providefeedback about problem resolution.

2 © 2010 SAP AG. All rights reserved. 2010/Q1

SMI310 Lesson: SAP Solution Manager Supporting Implementations

As a central lifecycle management platform, SAP Solution Manager providesaccess to all connected (managed) systems.Typically it is the task of a systemadministrator or technical expert to provide the underlying IT infrastructure forthe project. Since this course focuses on business-oriented implementations, thetechnical aspect will not be covered here.

What Drives New Implementations?

Figure 1: Implementation Accelerators / Drivers

There are different triggers, mainly driven by business demands, that may lead tothe preparation and execution of implementation projects:

• Internal business needs, e.g., functional enhancements required to increaseuser productivity

• Requirements collectively generated through user groups & events, such asthrough DSAG and ASUG

• Market-driven needs, e.g., the need to comply with financial andenvironmental legislation

• Increased competitiveness, such as fulfilling sustainability criteria to increasethe corporate image

• End of maintenance of a software release

This may ultimately lead to the implementation of a new solution, or innovationvia new enhancements.



Implementing Solutions with SAP Solution Manager

Figure 2: Implementation Project Phases

An implementation project is typically prepared along the following ASAP phases.

Note: ASAP is AcceleratedSAP, the methodology that underlies theimplementation of SAP solutions.

Phase 1 – Project Preparation

In the project preparation phase, you define the framework for your implementationproject. This includes setting project goals and objectives, determining theimplementation scope, defining the implementation strategy and plan, anddetermining the implementation tasks.

SAP Solution Manager supports this phase with the following functions:

• Creation of an implementation project• Assignment of project team members and their roles in the project• Definition of project standards, e.g., documentation types to be applied

consistently throughout the project• Definition of the system landscape for all systems to be managed during the

implementation• Assignment of an underlying project methodology



Primary roles involved: Project Manager, System Administrator

Phase 2 – Business Blueprint

In the business blueprint phase, you determine the detailed project scope forimplementation. The business blueprint portrays your business process, includingthe functional requirements to be implemented.


• Evaluation of SAP predefined implementation content• Creation of the business blueprint, including:

– Editing and scoping of the process structure to reflect your businessprocesses

– Documenting your requirements• Generation of a business blueprint document• Sign-off of the business blueprint, including a freeze of the business

processes tobe implemented

Primary roles involved: Business Process Expert, Application Consultant

Phase 3 – Realization

In the realization phase, you configure and test the business processes defined in thebusiness blueprint phase. Additionally, you document all your customer-specificdevelopments and prepare concepts for end-user documentation and training.


• Performing technical configuration, e.g. establishing connectivity betweensystems

• Performing business process configuration• Executing and documenting customer-specific developments• Preparing and executing test activities• Preparing training, e.g., by assigning e-learning material to process structure

Primary roles involved: Business Process Expert, Application Consultant, TestOrganizer, Tester

Phase 4 – Final Preparation

In the final preparation phase, you prepare and conduct end-user training andperform final testing on the application and managed systems, before going live.You also finish preparing and perform data conversion from legacy systems to theproduction system. You should also resolve all open issues.


• Performing final test activities• Creation and distribution of learning material



Primary roles involved: Quality Manager, Tester, Business Process Expert,Application Consultant

Phase 5 – Go Live & Support

In the go live & support phase, you move your implemented solution to aproductive environment, establish a support organization for end users, andoptimize the system performance and technical environment, as far as possible.


• Transfer of your implemented solution into the operative environment• Setting up of a service desk (if not already implemented)

Primary roles involved: Cross-application team staffed with people from projectand support organizations

Phase 6 – Run

The primary goal of this phase is to ensure the operability of the solution. Itincludes the concepts of the Run SAP Roadmap but goes beyond it. This phase isnot explicitly covered in this course.

The following capabilities are cross-functions because they can be accessedthroughout the implementation project:

• Issue tracking and project reporting, to track and monitor open issues and theproject progress, e.g., during the business blueprint and configuration

• Service Desk for problem message handling

– Ideally already in place during the implementation project– To be implemented at the latest before going live

• ASAP Implementation Roadmap, as a methodical guide through your entireimplementation project

The ASAP phases can be mapped onto the phases of the application lifecyclemanagement (ALM), an SAP approach that provides support along the lifecycle ofboth SAP and non-SAP solutions, by offering tools, methods, and services andan organizational model.In this sense, the ALM approach is more holistic thanthe ASAP approach, because it also covers aspects of deploying and optimizingyour solution. More details on the application lifecycle management is providedin the following chapter.



Figure 3: Benefiting from SAP Solution Manager During Implementations

Figure 4: SAP Solution Manager as a Single Source of Truth

SAP Solution Manager is the single source of truth, helping you to maintainand store all business-process-related information and technical data to operatededicated application lifecycle management (ALM) processes.

In implementations, this includes:

• Central maintenance and access to all managed systems• Central design and storage of all your business processes• Central definition, maintenance and storage of all business process and

technical documentation• Central creation and storage of test information• Central creation and storage of custom developments



By doing so, you maximize transparency and collaboration within your projectteam. The investments made in the implementation project can be transferred toother supporting processes of the application lifecycle, e.g. process informationand system data can be used later, in technical system monitoring and businessprocess monitoring.

Beyond Implementing Solutions - Application LifecycleManagement

Figure 5: What is Application Lifecycle Management (ALM)?

The scope of the ALM offering of SAP

• SAP provides 10 core processes for ALM, to support both projects andsolutions (Business Configuration and Business Continuity) throughout theentire life cycle, which consists of phases

• The required functionality is delivered by capabilities of SAP SolutionManager and other integrated tools

• SAP provides service and support offerings that help customers to useall these features

• The experience of SAP in ALM of how to best manage the applicationlife-cycle, are summarized in best-practice methodologies, organizationalmodels, and standards

To sum up, SAP Solution Manager is the platform to support ALM.



In the following, you will learn more about all phases of the ALM cycle accordingto ITIL.

• Requirements: Gather requirements for new/adapted applications, based onyour business needs

• Design: Translate requirements into feature specifications (businessblueprint)

• Build & Test: Prepare application and operational model for deployment• Deploy: Incorporate operational model in the existing IT environment and

install the application on top of the operational model• Operate: Deliver the service required by the business• Optimize: Analyze the results of the service level performance and act upon it

Figure 6: Requirements phase

Before an improvement or innovation project begins, you collect and evaluateall functional and non-functional requirements during the requirements phase.SAP supports this phase with content and tools. At this stage, your primaryconcern is to evaluate scenarios and their respective business processes and checktheir viability for your project. In the SAP Solution Manager environment, youcan use SAP Business Maps for knowledge transfer and more detailed processanalysis. Their content is stored in the Business Process Repository (BPR), SAP’sprocess library. This includes content designed specifically for implementationsthat you can use in your projects. In many projects, however, you need first toanalyze which transactions and processes are currently in use so that you candefine the project scope. For this purpose, SAP Solution Manager Enterprise



Edition includes the Solution Documentation Assistant, which performs automaticanalyses to enable you to detail your core business processes in a BusinessBlueprint, quickly and efficiently.

Figure 7: Design Phase

In the design phase, you use the findings from the requirements phase to specifyprecisely how your application or IT operation processes are to function, andwhich IT applications should be used to map the processes. A 2004 universitystudy on project management found that only 43% of all projects reflect theirclients’ strategies, and only 13% boost the value of the IT solution. One quarterof all projects begin with insufficient resources. To enable you to deal withimpending bottlenecks quickly and efficiently, it is essential that you haveprofessional, transparent project management procedures and a clearly-definedproject scope. With these in place, you will be able to safeguard your company’sinvestments, deploy resources for specific objectives, set priorities, and ensure thateveryone involved in a project communicates well. During this phase, applicationlife-cycle management provides you with roadmaps (proven procedures for projectmanagement) and project management activities, using tools such as projectadministration functions. The standardized processes also help you draw up awell-defined, transparent conceptual design (Business Blueprint) for your project.



Figure 8: Build and Test Phase

Figure 9: Example - Blueprint and Configuration of Business Processes

In the build and test phase, you implement the scenarios and processes definedin the design phase, in accordance with your requirements. You set up a systemlandscape for configuring and testing the planned scenarios and processes. You usethe build and test phase to set up the system landscape that will run your scenariosand business processes, to realize the scenarios and processes you defined in therequirements phase. You adopt the structure used in the Business Blueprint, whichhelps you configure your solution around your business processes and duringsubsequent testing activities.



Implementation comprises the following steps:

• Continuous monitoring of project targets, especially costs, deadlines, andresources

• Active implementation of organization and Change Management• Elaboration of training materials and end user documentation• Creation of end user roles and implementation of authorization and security

concept• Elaboration and implementation of realization specifications for customer

developments

SAP Solution Manager assists you in configuring your systems around yourprocesses. You can navigate directly to the SAP Implementation Guide (IMG)in the different development systems being managed, and set up the systemscentrally from SAP Solution Manager. You can also document the configurationsettings centrally. Furthermore, by integrating existing testing tools, SAP SolutionManager supports you in organizing and documenting the results of a range oftesting activities, from unit testing through to integration testing.

Figure 10: Example - Central Test Management and Execution in SAPSolution Manager



Figure 11: Deploy Phase

In the deploy phase, the application goes into live operation. Communicationchannels are critical during this phase, because they enable the smooth transfer ofinformation to end users. Final preparation transfers the results of the realizationphase into the live solution. All open issues concerning the final steps for goinglive are clarified. Once this phase has been completed, the production businessprocesses of your solution can run. As in the build and test phase, the TestManagement capabilities of SAP Solution Manager provide valuable support; thesame utilities and tools can be used to test various aspects of the system, such asperformance, load, and interfaces. At this stage, the Learning Maps created in SAPSolution Manager are distributed to the relevant end users, who can then use themfor self-study, to tailor content to their working environment and provide feedbackon individual units, or the Learning Map as a whole. Feedback can be evaluatedand used to improve the training materials. This phase facilitates the transitionfrom a pre-production environment to production operation. During this phase,it is important that support is provided to end users, not just in the critical daysafter going live, but in the long-term as well. SAP Solution Manager’s integratedService Desk can do this. Before production can go live, the cutover plans must beimplemented, which involves transferring data verified in the realization phasefrom the legacy system to the production system. Tested configuration settingsas well as modifications and customer developments are also transported to theproduction system. Controlled and quality-assured change management is a keyelement in highly integrated solution landscapes, to ensure that SAP applicationsare highly available and operate reliably. Throughout the entire life cycle ofan SAP solution, most changes and enhancements are made at the applicationlevel. They involve transferring custom software developments or Customizingsettings made within the scope of projects or customer defined shipment cycles, toproduction operation. Such changes require a traceable, standardized IT process



that covers planning, approval, development, testing, and finally deployment toproduction. Using such a standardized process minimizes the risk of adverselyaffecting productive business processes.

Figure 12: Operate Phase

The operate phase groups tasks that are performed after system start-up. Most ofthese tasks involve system administration, system monitoring, message processing(Service Desk), root cause analysis, issue management, and service delivery.SAP Solution Manager enables simple and complex processes to be handledautomatically in many different areas, such as automated system monitoringand error notification, the collection of technical data, and report summariesbased on SAP EarlyWatch Alert (EWA) and Service Level Reporting (SLR). Ittherefore allows you to react swiftly and appropriately, and to identify trendsearly and take action before errors occur. Current know-how, as well as task andworkflow documentation, is also integrated in many areas with administrativeresponsibilities and other tasks (Central System Administration, SolutionReporting, Business Process Monitoring).

The solution operations tasks are spread out clearly across the following processes:

• Technical Operations• Business Process Operations• Incident and Problem Management• IT Reporting

The personalized user interface, ability to work centrally, automation, and efficienttransfer of knowledge give experts the time they need to concentrate on their corecompetencies. This, in turn, allows small teams to monitor and manage complex



system landscapes, while making the services they offer transparent to the enduser. SAP Solution Manager therefore makes it possible to keep IT know-howinside companies or outsource it and monitor the services provided.

Figure 13: Example – Business Process Monitoring

Figure 14: Optimize Phase



During the optimize phase, you can act on key figures and data collected from thelive solution, to curb expenditure or boost performance. The important thingis that you can trace any changes made in the solution. This phase comprisesthe functions of Change Request Management, quality gate management ofupgrade support, the concept of global rollouts, and the maintenance of SAPsolutions. The optimize phase is a time for ensuring that software changes areplanned and implemented consistently, once your software is in operation. SAPSolution Manager supports you in this task with its functions for managing changerequests. Quality gate management provides an additional quality inspection forthe projects and ensures that changes are transported correctly to the productionsystems. The Maintenance Optimizer supports the maintenance of your solutionlandscape. If you need to make radical changes, for instance upgrading a softwarecomponent in your solution, the tool lets you take a professional approach, usingtried and tested procedures. Another challenge you may face during the optimizephase is distributing a template defined at the head office, to your organization’ssubsidiaries. SAP Solution Manager’s answer to this challenge is the globalrollout function.

Figure 15: Example Change Request Management Supporting UrgentCorrections



Figure 16: ALM Processes Covered in this Course

Note: Only the following ALM processes are covered, or mentioned, inthis course:

• Solution Documentation• Innovation Management• Template Management• Test Management

Solution Documentation - The goal of solution documentation is to centrallydocument business processes and technical information about SAP and non-SAPsolutions, to ensure transparency, efficiency and collaboration. The properdocumentation of your business processes, and the technical information onsystems upon which these processes run as part of an implementation project,are prerequisites for later verification and re-documentation of theses pieces ofinformation, e.g. using the Solution Documentation Assistant. This aspect willalso be covered as a sideline of this course.

Innovation Management - Innovation Management helps you to identify, adapt,and implement new and enhanced business and technical scenarios. To do so,you leverage, among others, the implementation capabilities of SAP SolutionManager, such as project administration, business blueprint, configuration, andproject reporting. These capabilities are the main subject of this course.

Template Management - Template Management allows customers withmulti-site SAP installations to efficiently manage their business processesacross geographical distances – from initial template definition to templateimplementation and template optimization. SAP Solution Manager supports suchan approach with dedicated functionality, e.g., template projects, which have asimilar but extended functional scope compared to implementation projects. Howtemplate projects and local site implementation projects work together as part of aholistic template management approach, is touched as sideline in this course.



Test Management - The goal of test management is to thoroughly test yourimplemented solution, using test capabilities fully embedded in SAP SolutionManager or, alternatively, third party tools. You are supported in all your testingactivities – from test planning to test execution and test reporting. A dedicatedunit in this course will make you familiar with the testing capabilities in SAPSolution Manager. As a sideline, you will also learn about the Business ProcessChange Analyzer to analyze the impact on operative business processes to betested, based on deployed software changes.

Change Control Management - Workflow-based management of business-and technology-driven solution improvement changes, with integrated projectmanagement, quality management, and synchronized deployment capabilities, tobest manage the risks associated with the implementation of the solution, ensuringtechnical and functional robustness.

Application Incident Management - Enables centralized and common incidentand issue message processing, on multiple organizational levels, and offers acommunication channel between all relevant stakeholders in an incident. Theprocess includes follow-up activities such as knowledge research, root causeanalysis, and change management.

Technical Operations - All capabilities for monitoring, alerting, analysis, andadministration of SAP solutions, and allows customers to reduce TCO bypredefined content and centralized tools, for all aspects of SAP Solution Manageroperations. It provides end-to-end reporting functionality either out-of-the-box,or individually created by customers.

Business Process Operations - Comprises the most important application-relatedoperations topics to ensure the smooth and reliable flow of the core businessprocesses, to meet a company's business requirements: Business Process &Interface Monitoring, Job Scheduling Management, Data Volume Management,and Data Consistency Management.

Maintenance Management - Covers software correction packages: fromdiscovery and retrieval to test scope optimization, optionally including automaticdeployment into the production environment.

Upgrade Management - The identification, adaptation, and implementationof new and enhanced business and technical scenarios, and uses SAP SolutionManager to holistically and effectively manage the upgrade project, end-to-end.



Digression: From ASAP to SAP Solution Manager

Figure 17: Digression: From ASAP to SAP Solution Manager

SAP Solution Manager has travelled an evolutionary path to reached itscurrent stage - a holistic platform supporting major aspects of the applicationlifecycle management. The evolution of SAP Solution Manager started withAcceleratedSAP (ASAP), which comprised an offline CD set, providing customerswith functionality, content, and methodologies to support implementationprojects. This notion was enhanced to ValueSAP, which supported evaluationand continuous improvement aspect as well as implementation activities. SAPSolution Manager incorporates the concepts of ASAP and ValuesSAP into astand-alone product, covering the entire lifecycle of applications and solutions,including implementation, operations, and optimization.



Lesson Summary

You should now be able to:• Define the drivers for new implementation projects• Describe the use of SAP Solution Manager in implementation projects• Outline the key benefits of SAP Solution Manager in implementation projects• Extend the notion of implementation support to a holistic application



SMI310 Unit Summary

Unit SummaryYou should now be able to:• Define the drivers for new implementation projects• Describe the use of SAP Solution Manager in implementation projects• Outline the key benefits of SAP Solution Manager in implementation projects• Extend the notion of implementation support to a holistic application



Unit Summary SMI310


Unit 2Prerequisites for Implementation

Projects

Unit OverviewThis unit provides you with the basic concepts of system-related aspects of SAPSolution Manager, that you need to know to work with implementation projects


• Explain the role of SAP Solution Manager as a central store of systemlandscape information

• Explain how SAP Solution Manager is populated with system-relatedinformation, and where this information is used

• Explain what a logical component is, and how you use this entity inimplementation projects to navigate into managed systems and to attributeyour business processes

Unit ContentsLesson: Technical Prerequisites for Implementation Projects .. . . . . . . . . . . . 24


Unit 2: Prerequisites for Implementation Projects SMI310

Lesson: Technical Prerequisites for ImplementationProjects

Lesson OverviewThis lesson provides you with the basic concepts of system-related aspects of SAPSolution Manager, that you need to know to work with implementation projects.


• Explain the role of SAP Solution Manager as a central store of systemlandscape information

• Explain how SAP Solution Manager is populated with system-relatedinformation, and where this information is used

• Explain what a logical component is, and how you use this entity inimplementation projects to navigate into managed systems and to attributeyour business processes

Business ExampleYour are a project manager or an application consultant of a dedicated SAPSolution Manager implementation project. You need to understand the relevanttechnical concepts to provide input to your system administrator for system-relatedaspects.


SMI310 Lesson: Technical Prerequisites for Implementation Projects

Central Administration of Managed Systems

Figure 18: Central Storage of System Landscape Information

All information on managed systems with which you work in the implementationproject and in other ALM (application lifecycle management) processes, such asduring system monitoring, is stored centrally in SAP Solution Manager. This isalso true for other system-related information, such as servers and databases, or forthird-party (non-SAP) systems Not all systems that you work with are installed andconfigured at the beginning of the implementation project. The system landscapemanagement of SAP Solution Manager (transaction SMSY) is populated withsystem information, as you work along the project phases. You need to agree atime schedule for IT to make the required physical systems available, before thestart of each project stage, e.g. blueprinting, development, and testing.



Figure 19: Distributing and Using System Landscape Information

Systems managed by SAP Solution Manager can be configured so that they reporttheir data to the SLD (System Landscape Directory) continuously (automaticregistration and update). This is configured

• For ABAP systems via RZ70• In JAVA systems via Visual Administrator

SAP Solution Manager collects the system landscape data from SLD in a periodicjob, and stores it in the Solution Manager system landscape (transaction SMSY).A properly maintained system landscape is a prerequisite for working withdedicated Solution Manager capabilities, such as business blueprint, configuration,test management or system monitoring, where the system-related data is re-used indifferent contexts.



Figure 20: Logical Components as an Attribute of Business Processes

Logical components are created as part of a properly maintained system landscape.A logical component is a system-related entity that describes an instance of an SAPproduct. It is specifies on which SAP or non-SAP product a dedicated businessprocess runs (or more precisely, a process step). Typically business determinestogether with IT which logical components are required by a project. A logicalcomponent can be defined for a combination of SAP product and main instance.It can also be defined for non-SAP, or third-party products, as well as SAP ones.This helps you to describe your entire software solution in SAP Solution Manager,regardless of whether SAP or non-SAP software is implemented.



Figure 21: Logical Components Hosting Managed Systems

As well as specifying on which software product your business processes run,logical components also store information about the physical systems managed bySAP Solution Manager.

A logical component thus:

• identifies a system landscape with physical systems

– of an identical product version/main instance type (e.g., SAP ERP 6.0- ECC Server)

– which are typically connected in one transport route and– support one productive system

• hosts physical systems of different system roles, e.g., DEV, QAS, PRD

To actually navigate into the physical systems, they must be connected (e.g. RFCconnections to ABAP systems).

Legend of system roles in the graphics:

• DEVw/c – development system for workbench object/customizing• QASu/i – quality assurance systems for unit/integration testing• PRD – production system



Figure 22: Connecting Managed Systems to SAP Solution Manager

Your IT/system administration department has to make the settings to allow youto navigate into managed systems during your project. This is done initially inthe Solution Manager Configuration (SOLMAN_SETUP) transaction. As wellas performing the initial and basic configuration of the SAP Solution Managersystem itself, this transaction helps the system administrator to connect allmanaged systems to SAP Solution Manager, by establishing the required RFCs(Remote Function Calls).

Having set up the requested connections, you can navigate into and work in:

• the evaluation system during business blueprinting (system role evaluation)• the development system during business blueprinting/configuration (system

role development)• the test system to perform test activities (system role quality assurance).



Lesson Summary

You should now be able to:• Explain the role of SAP Solution Manager as a central store of system

landscape information• Explain how SAP Solution Manager is populated with system-related

information, and where this information is used• Explain what a logical component is, and how you use this entity in

implementation projects to navigate into managed systems and to attributeyour business processes


SMI310 Unit Summary

Unit SummaryYou should now be able to:• Explain the role of SAP Solution Manager as a central store of system

landscape information• Explain how SAP Solution Manager is populated with system-related

information, and where this information is used• Explain what a logical component is, and how you use this entity in

implementation projects to navigate into managed systems and to attributeyour business processes


Unit Summary SMI310


Unit 3Project Preparation

Unit OverviewThis unit will enable you to define a project, determine project scope, and makedecisions about project standards. You will also make decisions concerning thesystems landscapes to be used in your solution


• Describe the main project preparation work packages and activities• Explain the use and functionality of a central project administration tool• Define a project in the SAP Solution Manager• Define a project system landscape

Unit ContentsLesson: Project Administration... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Exercise 1: Project Administration ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53


Unit 3: Project Preparation SMI310

Lesson: Project Administration

Lesson OverviewThis unit will enable you to define a project, determine project scope, and makedecisions about project standards. You will also make decisions concerning thesystems landscapes to be used in your solution.


• Describe the main project preparation work packages and activities• Explain the use and functionality of a central project administration tool• Define a project in the SAP Solution Manager• Define a project system landscape

Business ExampleYou are ready to proceed with the implementation project using the SAP SolutionManager:

• You begin by defining the project and the system landscape.• In Business Blueprint, the project team defines and documents all the

business process requirements, both functional and technical. StandardSAP business scenarios will be employed because they are delivered withpredefined implementation content. Using this can significantly reduceproject implementation costs. At the end of this phase, a Business Blueprintdocument should be generated for approval.

• After the Blueprint is signed-off Realization proceeds with configuring therelated system landscape and performing development work to meet thedefined requirements.

• After completion, a rigorous testing process should be organized, executed,and documented to validate system performance.

• For all key implementation activities, the project management team andsteering committee will request regular status reports that are availablethrough the reporting function.


SMI310 Lesson: Project Administration

Project Administration Overview

Figure 23: Project Preparation Phase

The purpose of this phase is to provide initial planning and preparation for the SAPproject. Each SAP project has its own unique objectives, scope, and priorities, butthe steps in the Project Preparation help identify and plan the primary focus areas.

All the central administrative tasks relevant for the project are performed in theproject administration transaction of the SAP Solution Manager, such as:

• Creating projects• Determining general data• Defining the project language• Defining the system landscape• Assigning project team members• Defining project standards (status values, documentation types, keywords)• Specifying transport request information (based on the project type)

Access the project administration function over the Implementation and Upgradeworkcenter or using directly transaction SOLAR_PROJECT_ADMIN.



Work centers are central work environments that provide access to role-specificfunctions. The structure of a work center depends on your role. You have accessto relevant work items, such as project and solutions, messages and alerts, as wellas documents and reports for which your role is authorized. The number of workcenters assigned to you depends on your tasks.

Note: General information on how to use work centers, you find in theSAP Help Portal. http://help.sap.com –> SAP Solution Manager

Note: On the SAP Service Marketplace you will find a documentdescribing the workcenter concept and its use and adapt it. Please goto http://service.sap.com/solutionmanager–>Media Library –> How toDocuments –> How to Adapt a Workcenter View.

Figure 24: Define Project – General Functions

Existing projects are displayed in the project overview of the Solution Manager.

Additional functions are available to administer the project administration dataof a project.


http://help.sap.com

http://service.sap.com/solutionmanager


Project Types

Figure 25: Project Types

The project types delivered with the SAP Solution Manager enable you todifferentiate between various types of projects. You can use the SAP SolutionManager to create the following projects:

Implementation Project:

• The Implementation project type is considered for single-siteimplementations.

• If you create an implementation project, you can select predefined scenariosfrom template projects.

Template Project:

• The Template project type is considered for multi-site implementations. Itcan also serve as an authoring environment to develop Best Practices such ascreated by implementation partners.

• If you create a template project, you can select predefined scenarios fromtemplate projects.

• You can transport template projects to other SAP Solution Manager systems.

Optimization Project:

• A project to emphasize the flow of business processes, or the use of asoftware solution.

• For use in SAP Services



Safeguarding Project:

• A project to resolve a critical situation in the implementation or use of anSAP solution.

• Safeguarding projects show the reasons for a critical situation and coordinatethe steps required to resolve the problems.

• Maintenance Project:• A project to maintain a solution in change request management and quality

gate management.

Upgrade Project:

• Helps you to prepare, structure, and plan for your upgrades. Functionalupgrade projects are very similar to implementation projects. In additionto implementation project functionality they offer the generation of aupgrade/delta view in the project administration. Upgrade/delta-relevantIMG activities can be highlighted in the configuration if the comparisonagainst the upgrade/delta view is triggered.

The project type you select for your project directly influences the edit optionsavailable in the individual project phases (Business Blueprint and Realization).

Template projects differ from Implementation projects in the following ways:

• Reuse of the structure in other projects, independent of the template projectin which it was created

• Project structure, with its assigned objects (General Documentation, testcases, IMG activities), is available to other projects

• Structure can be completely or partially locked against changes when theyare used in other projects

• To use templates in other systems, transport them

Template projects are ideal for SAP partner solutions or for large enterprisesperforming a global rollout.



Building the Project

Figure 26: Define Project – General Data

You can enter the following data in the General Data tab:

Project Lead:The responsible persons should exist in the project administrationof the SAP System. You can use the possible entries help to change theseassignments. You can have both a Customer and Consultant responsible personslisted here.

Project language:

• When you choose a project language, all language-dependent informationfor this language (project documentation and status information) is madeavailable to project members. This is independent of the logon language ofthe project member.

• The project structure is created in the specified project language.• All content is stored in the selected project language.• After the project language has been selected and saved, it cannot be changed.

Description: You can either create a new document which describes the project orlink to an existing document.

Status: The default values for the status are set in the Project Standards tab.

Plan Data: This area enables you to enter the dates for the planned project startand finish and the work required in man days (MD).



Actual Data: This area enables you to enter the dates of the actual project start andfinish and the actual work performed in person days (PD).

Note: You cannot change the project language later!

• The planned and the actual data represent the time plan for the entire project.Dates entered for individual process tasks in the Business Blueprint orRealization phases should lie within the time frame set in the General Datatab.

Defining the Project Scope

Figure 27: Defining the Project Scope

You define the structure of the project by specifying the project scope. You can setthe project scope in various ways in an implementation project.

Selecting Templates

Select Templates from SAP and/or partners or customer templates created in atemplate project. If no template is selected, you must build the project structureusing elements from the Business Process Repository in the Business Blueprint.

All SAP scenarios that are transferred and saved to the project are copies. Theoriginal scenarios remain unchanged when the project structure is changed.

Selecting Roadmaps



Select Roadmaps from the range of supplied SAP or own created roadmaps.

When using Roadmaps, select a Roadmap flavor with which your project teammembers will work. The system displays this Roadmap flavor by default when theRoadmap for your project is called later.

Note: Only one roadmap should be assigned for each project.

Selecting Industries and Countries

By choosing the Country Selection tab, the scope may be limited by selectingwhich countries are valid in the project. The default is all countries.

With the Industry Selection tab it is possible to define what industries will beconsidered as part of the project scope. By default, all industries are included.

Locking the Business Blueprint

The Scope tab also includes locking functions for the Business Blueprint. You canrestrict the extent to which project members can work on the Business Blueprint inthe Scope tab, as shown below:

• Edit structure – By selecting the respective locking option you cannot placeproject structure elements in and out of the scope or enhance the projectstructure.

• Edit structures, Change documents, and in the Administration tab – Youcannot edit project structure elements and modify documentation andadministrative data.

• For project documentation: All documents with flag Blueprint-relevant areprotected in Business Blueprint as well as in Configuration.



Assigning Project Team Members

Figure 28: Define Project – Project Team Members

You use this tab to create and update the list of team members for your project.You can assign any number of project team members in each project. The projectlead makes this assignment in the project administration transaction.

You can use users defined in user administration and generic users (users notcreated in the user administration) for your user assignments. To check if theproject members listed on this tab are already present in the user administrationof your SAP System, click the Check against user master record button. Teammembers who are not SAP users are highlighted in the list.

Members of staff assigned to the project on this tab are displayed in a selectionlist when you enter task-specific administrative data in the Administration tab inthe Business Blueprint or Configuration transactions.

You can enter a description of the project member in the Name/Description field.This field is available only for internal project use. You can use it, for example, todocument the assignment of a team member to a subproject or a project group. Ifthe user is recognized in the SAP System, the user name appears here by default.

You can also specify the names and details of the SAP partners who are involvedin the project.



Defining Project Milestones

Figure 29: Defining Project Milestones

You can monitor the project progress according to the milestones defined in theRoadmap and in the project.

If you have selected a Roadmap for your project in the Roadmap tab, the systemlists the milestones in the selected Roadmap in the Milestones tab.

You can add to the milestones in the Roadmap, but not change them.



Defining Organizational Units Affected by the Project

Figure 30: Defining Organizational Units Affected by the Project

You can enter data about the organizational units you will use in your project. Thiscan include function, country, time zone.

Note: You cannot analyze this data in the project analysis tool. It is forinformation purposes only.



Defining Project Standards

Figure 31: Defining Project Standards

The Project Standards tab contains three tabs such as:

• Status Values: Provides information about the status of your project. A statusvalue has a ten-character status ID and a description of the status. Status IDsshould be meaningful. Note that status values used in roadmaps cannot bechanged or adapted to project-specific needs.

• Keywords: You can define keywords to flexibly categorize documents, forexample, to facilitate search and reporting in the Project Analysis transaction.Keywords should be concise.

• Documentation Types: Various documentation types are available for alltypes of projects.

Standard values for status, keywords, and documentation types for your projectare all set similarly in the project administration transaction. If values have not yetbeen assigned to a project, the project administrator can use the project template,which contains project-independent status values, keywords, and documentationtypes.

The values in the project template are available to all projects. The projectadministrator decides which values should be used and assigns values to theproject from the project template.



At the time of delivery, each project type is assigned to a template that contains anumber of values for statuses, priorities, and documentation types. You can adaptthe project template to suit project requirements.

The values set in the Project Standards tab are available as default values in theBusiness Blueprint and Configuration transactions.

Figure 32: Project Standards – Documentation Types

Various documentation types are available for all types of projects. You canuse documentation types to document all purposes during the implementationproject. You can use the various documentation types delivered by SAP astemplates to structure your project documentation. You can also create your owndocumentation types.

Each documentation type has a unique ID. There are two types of projectdocumentation:

• Project-specific documentation

– This documentation type is valid only for the project to which it isassigned.

• Cross-project documentation

– You can identify this documentation type by the Global Documentationindicator. This indicator is available for all projects and appearsautomatically in the Project Documentation Types list in theDocumentation Types tab. Document types indicated as "global" donot need to be explicitly assigned to a project.

You can create project documentation templates for each documentation type.



You can analyze documentation types for the Business Blueprint in the ProjectAnalysis transaction.

Documentation templates are stored in a content repository of the SAP SolutionManager.

Figure 33: Sample of Documentation Types

You can create a template for project documentation in the Documentation Typestab. The template enables you to define the appearance and format of yourdocumentation. You can use this template to create new documents during theBusiness Blueprint and Realization phases.

You can define further attributes for the documentation type if required, as shownbelow:

• Global doc: Set this indicator if you want to reuse a documentation typein other projects.

• Several documents allowed: Set this indicator to enable multiple assignmentof a documentation type to structure items in your project structure. Thisenables you to add, for example, several documents of the Microsoft Worddocumentation type to one structure item.

• File extension: If you want to use an editor other than the text editor to createor change the document template, enter the corresponding file extension, forexample, PPT for Microsoft PowerPoint. The text editor opens by defaultwhen there is no file extension.

• Blueprint-Relevant: Set this indicator when the document type should appearin the Business Blueprint.



To import a template from your local directory, choose Import and select thedocument. Set the status of the document template to released.

Defining the Project System Landscape

Figure 34: Define a Project System Landscape (1)

You need to define the system landscape for your implementation project beforeyou can access the managed systems in subsequent project phases.

You can centrally manage all the landscapes you require for your project using theSAP Solution Manager.



Figure 35: Define a Project System Landscape (2)

Transaction –> SOLAR_PROJECT_ADMIN or Implementation and UpgradeWorkcenter –> Plan –> Create or Maintain Project

You define the system landscape for an implementation project in this tab.

A system landscape for the project contains the following information:

• Logical component• Product version• Logical systems for dedicated system roles

– In the Business Blueprint, the system role Evaluation may bemaintained to test-drive related transactions of process tasks.

– You cannot maintain the logical system information for non-SAPproducts.

Prior to the definition of a project system landscape, the products, systems, logicalcomponents and related RFC destinations should be managed in the SystemLandscape Maintenance transaction (SMSY). This has already been outlined inthe previous units on prerequisites for implementation projects.

The following functions are available based on the system landscape:

• Navigation to business content in managed systems• Generation of IMG (Implementation Guide) projects in managed systems

and distribute central project data• Using the RFC connection to call directly objects in the managed system



Figure 36: Define a Project System Landscape – Create Project IMGs

If you selected logical components for the project and defined at least adevelopment system, all customizing subprojects are displayed in this tab. Youcan generate the corresponding Project IMGs and distribute the central projectdata (general data, project members, project standards, country selection) for theseCustomizing projects.

When the Project IMGs are generated in the managed systems, everything isinitially set in scope.

The green and red traffic lights indicate if Project IMGs have already beengenerated and the corresponding data distributed.

• Red: Project has not been generated.• Green: Project exists in the specified logical components and the assigned

logical systems.

Project IMG in application component is assigned the same name as the projectin the Solution Manager system. Project IMG corresponds to Reference IMG(default). Customizing projects with other names can also be assigned.

Prerequisite for Project IMG generation: System role “Development” ismaintained in the System Landscape tab for the related logical component.



Feature List Project Administration



Figure 37: Feature List Project Administration

• Assign status scheme to documentation types.

– You can define status values and arrange them in a status schema. Astatus schema can then be assigned to one or more document types.This assures that the document status values are reduced to the subsetapplicable to your project, e.g., status value in processing followedby review followed by released.

– In project administration (transaction SOLAR_PROJECT_ADMIN):Project standards Documentation types → Project templates → Assignstatus schema to documentation type

– Requires customizing: SAP Solution Manager Implementation Guide→ SAP Solution Manager → Cross-Scenario Settings → DocumentManagement → Document Status

• Activate access concept per structure node.

– Only users who are assigned to a dedicated structure node, e.g., abusiness process, are allowed to change such nodes in the businessblueprint and configuration phase.

– Requires customizing: SOLAR_PROJECT_ADMIN → <Project>→ Project Team Member → Restrict changes to nodes in project toassigned team members

– Check F1 Help to get additional info for authorization

• Use of quality gates.

– Quality Gate Management gives you an overview of the status of thesoftware distribution of your projects, that is, of the implementation ofchanges to your SAP software solution, for all operational units of thevarious organizations in a company. This increases the transparencyof the software change process.

– Further information on the functional scope: http://help.sap.com SAPSolution Manager → <documentation of current release> → searchfor: search for: Quality Gate Management

• Save dedicated objects centrally in SAP Solution Manager system.

– Central test objects, eCATTs and manual test cases, can be centrallystored in the SAP Solution Manager system.

– Requires customizing: SOLAR_PROJECT_ADMIN → <Projects> →System Landscape → Central Objects


http://help.sap.com


Exercise 1: Project Administration

Exercise ObjectivesAfter completing this exercise, you will be able to:• Define basic project information such as project language, project team

members, and project standards• Assign a roadmap as the guiding methodology for your project• Assign logical components and related system landscape information for

your project

Business ExampleYou are ready to proceed with the implementation project using SAP SolutionManager. As a project lead, you initially define basic project information anddecide on the methodology to support your implementation project. With thehelp of the technical project lead, you will subsequently define the related systemlandscape for your project.

Task 1:Create your own project and maintain basic data.

→ Login to the assigned system/client/user for your exercises

→ Open the <User menu>in the SAP System (TT4)

→ SAP Solution Manager Work Center; T-Code:<SOLMAN_WORKCENTER>

→ Open the tab for Implementation/Upgrade

→ Open in the panel the menue entry Plan (on the left-hand side)

→ Click on the link Create or Maintain Project (on the right-hand side)

1. Create a new Project:

Field Name Values

Project SOLT200_##, where <##> is your groupnumber.

Project Type Implementation Project

Solution Do not select a solution.

2. Maintain the basic data:

Continued on next page



Field Name Values

Title <Enter a Name>

Project language English

3. Save your settings. Upon save, confirm the default enhancement fordocuments.

Task 2:Select a roadmap as part of your project scope.

1. Select the roadmap version ASAP Methodology for Implementation 7.0 asthe guiding methodology for your project.

Task 3:1. Assign the following users as project team members:

Values

SMI310-00

SMI310-##

Task 4:Define your project system landscape.

1. Determine relevant logical components for your project and select thefollowing components:

Logical Component

Z_SMI310_CRM

Z_SMI310_ERP

Z_NONSAP

Task 5:1. Check the assignment of the following values as part of your project

standards. They should be listed in the Project Status Values.

Note: Please do not remove the other assigned project standards!




Data Type Value Name

Status ZSMIST01 andZSMIST02

doneto be checked

Keywords ZSMIKW01 Administrative

Docu type ZSMI Meeting Minutes

2. Now all project values are defined. Save the project.

3. (Optional) Upload a customer-specific template into your template directory.



Solution 1: Project AdministrationTask 1:Create your own project and maintain basic data.






→ Click on the link Create or Maintain Project (on the right-hand side)

1. Create a new Project:

Field Name Values

Project SOLT200_##, where <##> is your groupnumber.

Project Type Implementation Project

Solution Do not select a solution.

a) Click the Create Project (F5) button.

b) Enter SOLT200_## as the project name and choose ImplementationProject as the project type.

c) Choose a Solution if directed by your instructor, otherwise leave blank.

d) Click Continue.

2. Maintain the basic data:

Field Name Values

Title <Enter a Name>

Project language English

a) Enter a project description to field Title.

b) Select the General Data tab and select English as the project language.

3. Save your settings. Upon save, confirm the default enhancement fordocuments.

a)




Task 2:Select a roadmap as part of your project scope.

1. Select the roadmap version ASAP Methodology for Implementation 7.0 asthe guiding methodology for your project.

a) Select the Scope tab.

b) Select the Roadmap Select tab.

c) Select the roadmap flavour for Core ASAP from the ASAP Methodologyfor Implementation 7.0.

Task 3:1. Assign the following users as project team members:

Values

SMI310-00

SMI310-##

a) Select the Proj. Team Member tab.

b) Choose possible entry help (F4) to select the project team membersas shown above.

Task 4:Define your project system landscape.

1. Determine relevant logical components for your project and select thefollowing components:




Logical Component

Z_SMI310_CRM

Z_SMI310_ERP

Z_NONSAP

a) Select the System Landscape tab.

b) Select the Systems tab.

c) In the Logical Component column, choose logical components for yourproject using possible entry help (F4).

d) Select SAPCRM→CRMApplication Server ABAP→Z_SMI310_CRM

e) Select SAP ERP → SAP ECC Server → Z_SMI310_ERP

f) Select NON-SAP-APPLICATION → Z_NONSAP

Task 5:1. Check the assignment of the following values as part of your project

standards. They should be listed in the Project Status Values.

Note: Please do not remove the other assigned project standards!

Data Type Value Name

Status ZSMIST01 andZSMIST02

doneto be checked

Keywords ZSMIKW01 Administrative

Docu type ZSMI Meeting Minutes

a) Select the Project Standards tab.

Note: If there are other items already chosen for this project,you may leave them in the project column, just make sure theZSMI* choices are included.

b) choose sub tab Status Values, select the status values and use the assignicons to select values (<< and >>).

c) choose sub tab Keywords select the keywords and use the assign iconsto select values (<< and >>).

d) choose sub tab Documentation Types select the documentation typesand use the assign icons to select values (<< and >>).




2. Now all project values are defined. Save the project.

a) Click the Save button to save the project.

b) Confirm the enhancement and release enh. (/KWCUST/ and 620).

3. (Optional) Upload a customer-specific template into your template directory.

a) On the Documentation Types tab, choose the Project template button.

b) Create a new sample documentation type, e.g., ZFUN, and name it,such as Functional Specification.

c) Mark the line of the newly created documentation type.

d) Choose the Document Template button, drop down menu Import andconfirm the default document enhancement.

e) Upload an existing document template from your local hard drive.

f) Confirm the document template status switch to Released.

g) Close the document template.

Additionally, you may edit the document template via DocumentTemplate -> Change or even create a new document template withDocument Template -> Create Using Editor.



Lesson Summary

You should now be able to:• Describe the main project preparation work packages and activities• Explain the use and functionality of a central project administration tool• Define a project in the SAP Solution Manager• Define a project system landscape


SMI310 Unit Summary

Unit SummaryYou should now be able to:• Describe the main project preparation work packages and activities• Explain the use and functionality of a central project administration tool• Define a project in the SAP Solution Manager• Define a project system landscape


Unit Summary SMI310


Unit 4Use of Roadmaps

Unit OverviewThis unit will introduce you to the various roadmaps and the use of roadmapsin the context of the SAP Solution Manager for implementation. You willlearn how to navigate the roadmap structure and access the features of theroadmaps. You will also learn how roadmaps are associated with projects and theproject-independent use of roadmaps.


• Explain how SAP Solution Manager uses roadmaps to guide implementationand operation activities

• Use roadmaps in the context of the SAP Solution Manager forImplementation

• Activate ASAP Business Add-ons in SAP Solution Manager• Navigate through the structure and content of roadmaps• Describe the project-independent use of roadmaps• Explain the features of roadmaps

Unit ContentsLesson: Working with the Roadmap Methodology ... . . . . . . . . . . . . . . . . . . . . . . . 64

Exercise 2: Working with the Roadmap Methodology ... . . . . . . . . . . . . . . . 81


Unit 4: Use of Roadmaps SMI310

Lesson: Working with the Roadmap Methodology

Lesson OverviewThis lesson will introduce you to the various roadmaps and the use of roadmapsin the context of the SAP Solution Manager for implementation. You willlearn how to navigate the roadmap structure and access the features of theroadmaps. You will also learn how roadmaps are associated with projects and theproject-independent use of roadmaps.


• Explain how SAP Solution Manager uses roadmaps to guide implementationand operation activities

• Use roadmaps in the context of the SAP Solution Manager forImplementation

• Activate ASAP Business Add-ons in SAP Solution Manager• Navigate through the structure and content of roadmaps• Describe the project-independent use of roadmaps• Explain the features of roadmaps

Business ExampleAs the project manager of the implementation team, you need to introduceyour team to the ASAP Methodology for Implementation 7.0 and the BusinessAdd-on framework you will be using to guide your project. This is the standardSAP implementation methodology which utilizes a roadmap and businesscontent to help you cover the most important aspects and phases of an SAPimplementation based on SAP Best Practice, own practices (SOA [ServiceOriented Architecture]/composite solutions), and which provides best insight(technology to analyze). Your team uses the roadmap concept and the businesscontent to perform several tasks in a project, such as navigate through the roadmapstructure, display and assign documents to this structure, define the processstructure or build and test the solution.


SMI310 Lesson: Working with the Roadmap Methodology

Introducing the Roadmap Concept

Figure 38: ASAP Methodology for Implementation 7.0

Roadmaps are available as HTML offline versions on SAP Service Marketplace.Additionally, these roadmaps are delivered with the SAP Solution Manager.They contain standard SAP implementation methodology and include the mostimportant aspects and phases of an SAP implementation.

A fundamental component of Roadmaps is links to accelerators and tools toperform project tasks.

Roadmaps enable you to:

• Navigate through the structure• Filter structure items by role or subject area• Display and assign documents• Create keywords to search more efficiently for documents• Print individual documents or structures with assigned documents• Search for specific items in the structure and accelerators• Track/Set the status and create notes for each structure item• Create messages• Assign team members to tasks



Figure 39: ASAP Roadmap Benefits

The following benefits result from using the ASAP methodology:

• Reduced total cost of implementation by embedding Integrated ServiceDelivery (ISD) principles into a streamlined and modular ASAPimplementation roadmap

• ASAP delivers content rich implementation accelerators, templates andguides for implementation projects from Strategy to Support (E2E -end-to-end)

• • ASAP Business Add-ons provide proven implementation content forimplementation of various industry solutions, solution packages, andother related areas such as Agile Methodology, BPM (Business ProcessManagement), SOA (Service Oriented Architecture), MDM (Master DataManagement) and EA (Enterprise Architecture) Governance and Strategyframeworks

• Ensure transparency of value delivery through consistent business casereflection

• Enables efficient project governance and quality management• Efficient guidance for SOA, BPM and traditional implementation projects• Drive combined Business Process and IT Architecture approach (E2E)• Covers entire process, application, value, and project life-cycle• Delivers revised content in all traditional ASAP areas – Project Management,

Solution Manager, Organizational Change Management, Training,Blueprinting, Realization, Cutover planning and execution, and others



Introducing the ASAP Methodology for ImplementationThe new ASAP Methodology for Implementation adresses two centralcomponents: a) the ASAP core implementation roadmap and b) thecontent-enriched ASAP business add-ons.

ASAP Core Implementation Roadmap (“ASAP core”)

The ASAP core describes how to organize and run an implementation projectfrom a functional perspective. It provides the methodological framework for thetasks involved in the implementation of an SAP solution. It includes, among otheraspects, required project management, configuration of business processes, andtechnical aspects, test procedures, and training concepts.

The ASAP core divides the implementation process in six phases. The phasesfocus on specific subject areas and objectives and logically follow one another.The phases are as follows:

Figure 40: Phases of the ASAP Core Implementation Roadmap

Phase 1: Project Preparation - During this phase the team goes through initialplanning and preparation for SAP project.

Phase 2: Business Blueprint The purpose of this phase is to achieve a commonunderstanding of how the company intends to run SAP to support their business.

Phase 3: Realization - The purpose of this phase is to implement all the businessprocess requirements based on the Business Blueprint.



Phase 4: Final Preparation - The purpose of this phase is to complete the finalpreparation (including testing, end user training, system management and cutoveractivities) to finalize your readiness to go live.

Phase 5: Go Live & Support - The purpose of this phase is to move from aproject-oriented, pre-production environment to live production operation.

Phase 6: Run - The primary goal of this phase is to ensure the operability of thesolution.

Each phase has a set of deliverables that are produced during the duration of thephase and serve as the input to follow-up phases.

The six phases span four different levels (phase, work stream, deliverable,sub-deliverable), which are explained later on.

The ASAP core can be selected during the creation of a project in the ProjectAdministration (transaction SOLAR_PROJECT_ADMIN), Scope tab, RoadmapSelection tab.

ASAP Business Add-ons

Figure 41: Selecting a ASAP Business Add-on Template



The ASAP Business Add-ons provide proven implementation content forimplementation of various industry solutions, solution packages, and other relatedareas such as Agile Methodology, BPM, SOA, MDM and EA Governance andStrategy frameworks, etc. The ASAP Business Add-ons cover:

• The additional flavour project management methodology and accelerators• Solution or industry specific business content: Business process structure,

transactions, solution documentation, links to IMG objects, BC Sets,enhancements, SOA services, composite applications, test cases, trainingmaterial, etc.

• Relevant services and training

An important addition to the content stack provided by ASAP Business Add-onsare services. The intent of having services within the ASAP Business Add-ons is toensure that SAP delivers world-class services and keeps its value DNA at the coreof its priorities - ultimately maximizing customer success. The Business Add-onsare provided via the Solution Manager ST-ICO content packages and are selectablein the Project Administration (transaction SOLAR_PROJECT_ADMIN) astemplates and as an additional flavour next to the ASAP core implementationroadmap flavour.

You can find more information about the Business Add-ons on:

• SAP Service Marketplace: http://service.sap.com/roadmaps• SDN/ BPX Community: http://www.sdn.sap.com/irj/bpx/asap



Types of RoadmapsMethodology Provided Through Roadmaps

• ASAP Implementation Roadmap

– Target Group: Project Managers, Functional Implementation Team(Application Consultants)

– Provides a proven implementation methodology for SAPimplementations and addresses business add-ons to accelerate theimplemenation of dedicated application areas

• Upgrade Roadmap

– Target Group: Project Lead, Functional and Technical Team members,Power Users

– Provides SAP's latest upgrade methodologies to plan and execute anSAP upgrade project

• RunSAP Roadmap

– Target Group: Technical Implementation Team (Technical Consultants)and Support Team

– Provides guidance on how to implement and standardize solutionoperations end-to-end, focusing on application management.

• Global ASAP Methodology

– Consists of 2 roadmaps

– Global ASAP Template Roadmap– Global ASAP Rollout Roadmap

– Target Group: Program/Project Managers, Template and RolloutProject Team members, Customer Center for Excellence (CCE) Team

– Designed to help program teams develop business system template thatis then rolled-out to multiple sites

– Enables global team to define standard processes and also allow forlocal configuration and localization



Navigation Within Roadmaps

Figure 42: Graphical Entry Screen vs. Roadmap Structure View

The Roadmap can be accessed through a graphical entry screen. Choose a linkto a structure element in the initial screen to go to the Roadmap Structure view.Back returns you to the graphical screen.

To specify if the system shows the structure view or the initial screen next timeyou call the Roadmap, choose Settings → User-Specific and set or reset Entervia Structure.

Structure of the Graphical Entry screen:

• Phases – Roadmap phases.• Work area – Links to nodes in the Roadmap structure view. If you select

a link, you go to the structure view of the Roadmap in the same session.You can display the Roadmap and documents. Back takes you back to thegraphical view.



Roadmap structure view:

• Project area (structure on the left screen area) – This area contains thestructure of the Roadmap with attributes.

• Viewing area (text in the top right of the screen) – When you select a structureitem in the project area, a description of the item is displayed in this area.

• Attachment area (objects in the lower right-hand screen area)

– The Accelerators tab contains links to accelerators.– The Status/Notices tab is used to create and display notes about

structure elements and set a visible status icon on the structurecomponent (Open, In Process, Complete, Error).

– The Issues/Messages tab is used to create, display, and edit problemmessages for the selected structure element.

– In the Project Team Members tab you can assign structure elementsto the Project Team Members which you have put in your project, inthe Project Administration.

– The Project Documentation tab has the same functionality as the ProjectDocumentation tab in the Business Blueprint. You can use all generalproject documents and document types which you have assigned toyour project in the Project Administration

– You can assign project-specific keywords (which you assigned to yourproject in the Keywords sub-tab of the Project Standards tab in ProjectAdministration) to each structure step, in the Keywords tab. Thesekeywords help you to find structure elements during Project analysis.

Figure 43: Navigation Within Roadmaps - Navigation Structure Concept



The ASAP Implementation Roadmap divides the implementation process in sixphases. The content is structured according to four levels: Below the phase, youfind workstreams, delliverables and sub-deliverables assigned as substructures toeach phase . The structured roadmap contents focuses on specific subject areasand objectives and logically follow one another.

The following items are used to structure the ASAP Implementation Roadmap:

• Phase (Level 1)

– The Implementation Roadmap is divided in different phases. Eachphase represents a major milestone in the implementation project.

• Deliverable Group (Level 2)

– Each phase of the Implementation Roadmap is made up of severallogical groups of work streams.

• Deliverable (Level 3)

– In each phase the project team produces several deliverables. Thedeliverables represent the main objects within a workstream.

• Sub-deliverable (Level 4)

– Each deliverable comprises several outputs. Outputs are documents ortangible items that are results of a process. The output supports thecompletion of a desired deliverable as a standalone component.

Figure 44: Navigation Within Roadmaps - Business Blueprint andAccelerators



Displaying Implementation Project/Accelerator Documentation

To display the documentation for tasks in your implementation project, choose thecorresponding entry in the roadmap structure. The documentation is displayed onthe right of the screen.

Available Accelerators are listed on the lower right of the screen area in theAccelerator tab. Accelerators can be, for example, Word documents, PowerPointpresentations, or transactions. Double-click the accelerator to call it.

You can display a list of accelerators assigned to each structure step. ChooseGoto → Accelerators.

Project-independent Use of Roadmaps

Figure 45: Project-independent Use of Roadmaps



Accessing the Implementation Roadmap

1. Choose the transaction RMMAIN in the SAP Solution Manager or theImplementation/Upgrade workcenter –> Plan –> Show Roadmaps. If aroadmap has been assigned in Project Administration for the project, youaccess it directly at the Implementation Roadmap Entry Screen.

2. If the selected project does not have a roadmap assigned, the project selectorscreen enables you to choose another project or access a roadmap with noproject assignment (button: No Project).

3. You go to the structure view of the Roadmap.4. Choose a link to a structure element in the initial screen to go to the structure

view of the Roadmap. Back takes you back to the initial screen.5. To specify if the system shows the structure view or the initial screen next

time you call the Roadmap, choose Settings → User-Specific and set or resetEnter via Structure.

Figure 46: Filter Options for Roadmaps

Roadmap User Settings

To specify if the system shows the structure view or the initial screen next timeyou call the Roadmap, choose Settings → User-Specific and set or reset Entervia Structure.

Filter Options



The Filter function enables you to filter structure items in the initial and structureviews based on the following criteria:

• Subject Areas: You can select one or more subject areas. The structure itemsto which the selected subject areas are assigned are displayed in the initialand structure views.

• Role: You can select one or more roles. The structure items to which theselected roles are assigned are displayed in the initial and structure views.Role descriptions can be displayed here.

• Flavors: You can select one or more flavors, such as ASAP core and one toseveral business add-onsThe structure items to which the selected flavors areassigned are displayed in the initial and structure views.

• Keywords: You can select one or more keywords. The structure items towhich the selected keywords are assigned are displayed in the initial andstructure views.

• Scope: Filtering by Scope shows only those elements that belong to theroadmaps selected.

Download into HTML

You can create a download (HTML) version of the roadmaps and read themoffline on your laptop.

Procedure:

1. Select Roadmap → Download → HTML Version.2. Enter the path where you want to store the offline version in the Directory

field.3. Choose Continue to generate the offline version.



Project-specific Use of Roadmaps

Figure 47: Project-Specific Use of Roadmaps - Overview

Note: Simultaneous access to multiple roadmaps is possible only whenworking in multiple sessions.



Figure 48: Setting Status and Attaching Notes

Set Status

The status of a structure step is displayed as an icon in the structure and in theRoadmap initial screen. To set the status of a structure item, you need to:

• Click the Status icon beside the structure item. The initial status of allstructure elements is Open.

• Choose a structure step in the reference structure and set the status using thepush-buttons in the Status/Notices tab.

Make Notes

• You can make notes about structure elements in the Status/Notices tab. Todo this, you need to:

– Go to the structure element for which you want to make a note.– Select the Status/Notices tab in the creation area.– Choose Enter and write the note in the creation window. The system

saves your entries automatically when you leave the tab.

Note:

• Status settings cannot be inherited along the roadmap structure.• Reporting on roadmap status values is not possible.



Figure 49: Roadmap Features: Project Documentation

Attach documentation, transactions, links:

You can assign project-specific documents/accelerators and other objects to aroadmap structure element:

• Insert and execute transactions• Insert/upload, display, and change project documents, for example,

project-specific accelerators• Insert and display URLs

To assign documentation, transactions, links proceed as follows:

1. Go to the structure element to which you want to assign information.2. Enter documents, transactions, and URL links with push-buttons in the

Project Documentation tab.3. Double-click the assigned elements to view or run them.

Note:

• Assigned transactions can only run in the local SAP SolutionManager system.



Figure 50: Searching in and Reporting on the Roadmap Structure

There are context-specific search/reporting capabilities provided in the Gotomenu:

• Depending on position of the cursor in the roadmap structure, accelerators,notes, or messages can be listed

• Double-click an item to directly navigate to the related roadmap structure

Note: Searching for project-specific documents/accelerators or otherassignments is NOT yet supported.

Feature List Roadmaps

Figure 51: Feature List Roadmaps



Exercise 2: Working with the RoadmapMethodology

Exercise ObjectivesAfter completing this exercise, you will be able to:• Understand the ASAP Methodology for Implementation Roadmap• Navigate through the roadmaps and search for accelerators• Download accelerators and upload project documentation• Set status/notes to track project progress, add project members, and set

keywords• Use other roadmap features, such as filter options and reporting

Business ExampleWhether you are a project manager or a technical/business process team leader,you leverage SAP's implementation methodology as guide to defining standardsand procedures for your implementation project. The Implementation Roadmapserves as a key information source/repository providing templates and proceduresto effectively manage your activities from a project management, functional andtechnical perspective.

Task 1:Check, whether the roadmap ASAP Methodology for Implementation 7.0 isassigned to your project.





→ Open in the panel the menu entry Plan (on the left-hand side)

→ Click on the link Show Roadmaps (on the right-hand side)

Choose your project (SOLT200_##) with an assigned roadmap and access theroadmap structure.

1. Your roadmap structure contains different entities structured according to theitems phase, work stream, deliverable, and sub-deliverable.

2. Find out about the milestone set for phase 1.




Task 2:Explore the contents delivered with SAP’s implementation methodology.

1. Access and read the following accelerators:

Structure area Accelerator

ASAP Implementation (rootnode)

ASAP for Implementation 7.0 Overview

Business Blueprint (root node) Blueprint Phase Description andDeliverables by Workstream - Guide

Run (root node) SAP Enterprise Support

2. In the ASAP Methodology for Implementation Roadmap (V7.0), go to thestructure item Business Process Modeling Standards and launch the WebLink SAP Business Process Modeling Handbook.

Note: From the roadmap, you can launch other SAP SolutionManager documents and transaction, when available.

Note: You need to login into the SAP Service Marketplace with anappropriate user and password to access the document.

3. Explore filter options by subject areas.

4. Explore filter options by roles and understand the role concept.

Read the descriptions of several roles, such as Project Manager/SeniorProject Manager, Business Consultant, and Technology Consultant.

5. Search for other accelerators related to the use of project-supporting SAPSolution Manager functions, e.g., the accelerator Solution Manager -Operational Guide for Project Administration.

Note: The list of accelerators relates to the context (cursor position)in the roadmap structure.

If there is no accelerator available, the corresponding information isdisplayed in the status bar.

Task 3:Work with your project-specific roadmap.

1. Go to the structure item Business Process Unit and String Test Cases.

2. Download the accelerator Business Process Unit and String Test Cases andmodify and upload it as a project document.




3. Set the status of the structure item Business Solution Design to In Processand write a short note.

4. Add a project team member to this roadmap node.

5. Add keywords to this roadmap node.

6. (Optional) Report on your roadmap, e.g., on the status or completition ofyour project documentation.



Solution 2: Working with the RoadmapMethodologyTask 1:Check, whether the roadmap ASAP Methodology for Implementation 7.0 isassigned to your project.





→ Open in the panel the menu entry Plan (on the left-hand side)

→ Click on the link Show Roadmaps (on the right-hand side)

Choose your project (SOLT200_##) with an assigned roadmap and access theroadmap structure.

1. Your roadmap structure contains different entities structured according to theitems phase, work stream, deliverable, and sub-deliverable.

a) If your project name does not appear in the title bar above the roadmapstructure, click on the Other Project (Shift + F5) button and chooseyour project name from the Project Selection list.

b) Expand the roadmap structure for phase 1 and view the differentstructure items.

2. Find out about the milestone set for phase 1.

a) Scroll down until you see the grey milestone icon.

b) Check the milestone description by clicking on the milestone in thestructure.

The milestone description is launched in the upper right frame.

Task 2:Explore the contents delivered with SAP’s implementation methodology.

1. Access and read the following accelerators:




Structure area Accelerator

ASAP Implementation (rootnode)

ASAP for Implementation 7.0 Overview

Business Blueprint (root node) Blueprint Phase Description andDeliverables by Workstream - Guide

Run (root node) SAP Enterprise Support

a) Go to the structure items listed in the exercise table.

b) Select the Accelerator tab on the lower right-screen.

c) Double-click the accelerator and choose Continue.

d) Read the document and choose File → Exit to close the document.

2. In the ASAP Methodology for Implementation Roadmap (V7.0), go to thestructure item Business Process Modeling Standards and launch the WebLink SAP Business Process Modeling Handbook.

Note: From the roadmap, you can launch other SAP SolutionManager documents and transaction, when available.

Note: You need to login into the SAP Service Marketplace with anappropriate user and password to access the document.

a) Find the structure item Business Process Modeling Standards usingthe Find button.

b) Select the Accelerator tab on the lower right.

c) Double-click the accelerator SAP Business Process ModelingHandbook.

d) Close the web browser when done.

3. Explore filter options by subject areas.

a) In the menu Settings → Filter → Subject Areas, select one or multiplevalues, e.g., Training.

b) Verify filter settings by navigating through the roadmap structure andchecking the accelerator attributes.

c) Undo the filter settings by setting the Subject Areas filter back toinactive.

4. Explore filter options by roles and understand the role concept.




Read the descriptions of several roles, such as Project Manager/SeniorProject Manager, Business Consultant, and Technology Consultant.

a) In the menu Settings → Filter → Roles, double-click the descriptionicon aligned to a role.

b) Read the description for the roles as outlined above.

c) Select one or multiple values, e.g., roles as stated above.

d) Verify filter settings by navigating through the roadmap structure.

e) Undo the filter settings by setting the Roles filter back to inactive.

f) (Optional) Explore other filter options, e.g., for flavors, keywords, andthe scope. Afterwards, change back the filter options to its original state(inactive, except for the flavors) so that the complete roadmap structureis available for further exercises.

5. Search for other accelerators related to the use of project-supporting SAPSolution Manager functions, e.g., the accelerator Solution Manager -Operational Guide for Project Administration.

Note: The list of accelerators relates to the context (cursor position)in the roadmap structure.

If there is no accelerator available, the corresponding information isdisplayed in the status bar.

a) Place the cursor on the root node of the roadmap structure and launchthe menu Goto → Accelerator.

b) Click the Find button to search for a specific accelerator displayed onthe Accelerator Overview screen, e.g., Solution Manager Usage Outline

c) Double-click on the accelerator found.

d) Move to the Accelerators tab.

e) Double-click on the accelerator to launch the documentation.

f) Read and close the document.

Task 3:Work with your project-specific roadmap.

1. Go to the structure item Business Process Unit and String Test Cases.

a) Launch the find dialogue.

b) Enter Business Process Unit and String Test Cases and continue.




2. Download the accelerator Business Process Unit and String Test Cases andmodify and upload it as a project document.

a) Select the Accelerator tab on the lower-right of the screen.

b) Double-click the Business Process Unit and String Test Casesaccelerator.

c) Save the document to the local drive. Close the document.

d) In the Project Documentation tab, upload the modified accelerator usingthe button Assign Project Documentation –> Create Document ( ).

e) Enter a document title, select a Documentation Type, select UploadFile and click OK (Enter).

f) The document will open. Modify the document.

Note: Please note that you have to remove the write protectionin the document before modifying.

g) Save and Close.

3. Set the status of the structure item Business Solution Design to In Processand write a short note.

a) Find or directly go to the structure item Business Solution Design.

•

b) Select the Status/Notices tab on the lower-right screen.

c) Click the In Process button to set the status.

d) Enter a text in the comment field.

4. Add a project team member to this roadmap node.

a) Select the Project Team Member tab on the lower-right screen.

b) Add a project team member by pressing the Add Entry button .

c) Choose one to several users from the list of team members.

Note: Notice that this list is restricted to those project teammembers chosen when the project was defined.




5. Add keywords to this roadmap node.

a) Select the Keywords tab on the lower-right screen.

b) Add one or more keywords from the list by pressing the Add Entrybutton .

c) Assign the proposed keyword from the list.

Note: Notice that the list of keywords is restricted to thosechosen during the project definition.

6. (Optional) Report on your roadmap, e.g., on the status or completition ofyour project documentation.

a) Launch the requested report selecting Environment -> Status Reportfrom the menu.

b) In the Roadmap Status - SAP Solution Manager screen, select the statusvalue In Process.

c) Execute the report.

d) Expand the structure and view the results.



Lesson Summary

You should now be able to:• Explain how SAP Solution Manager uses roadmaps to guide implementation

and operation activities• Use roadmaps in the context of the SAP Solution Manager for

Implementation• Activate ASAP Business Add-ons in SAP Solution Manager• Navigate through the structure and content of roadmaps• Describe the project-independent use of roadmaps• Explain the features of roadmaps


Unit Summary SMI310

Unit SummaryYou should now be able to:• Explain how SAP Solution Manager uses roadmaps to guide implementation

and operation activities• Use roadmaps in the context of the SAP Solution Manager for

Implementation• Activate ASAP Business Add-ons in SAP Solution Manager• Navigate through the structure and content of roadmaps• Describe the project-independent use of roadmaps• Explain the features of roadmaps


Unit 5Business Blueprint

Unit OverviewThis unit describes the activities in the Business Blueprint phase.


• Explain the Business Blueprint phase• Create the Business Blueprint structure, preferably based on SAP predefined

implementation content• Use the message handling functions• Create the Business Blueprint documentation• Generate the Business Blueprint document• Execute standard reports for all facets of the implementation project• Identify other useful Solution Manager tools

Unit ContentsLesson: Business Blueprint. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Exercise 3: Business Blueprint Part 1- Defining the Business BlueprintStructure .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .117

Lesson: Document Management .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128Exercise 4: Business Blueprint Part 2 - Document Management .. . .139

Lesson: Reporting ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .152


Unit 5: Business Blueprint SMI310

Lesson: Business Blueprint

Lesson OverviewThis lesson describes the activities in the Business Blueprint phase.


• Explain the Business Blueprint phase• Create the Business Blueprint structure, preferably based on SAP predefined

implementation content• Use the message handling functions

Business ExampleNow that you have created a project and introduced your team to theimplementation roadmap, you need to create a business blueprint which will bethe plan for the your team to follow in the Realization Phase.

Introducing the Business Blueprint Concept

Figure 52: Activities and Functions by Phase – Business Blueprint


SMI310 Lesson: Business Blueprint

The purpose of this phase is to create the Business Blueprint, which is detaileddocumentation of the business process requirements of the company.

The Business Blueprint provides a general understanding of how an enterprise'sbusiness processe should be mapped in one or more SAP Systems. The purpose ofthe Business Blueprint is to document in detail the scope of business scenarios,business processes, process steps, and the requirements of an SAP implementation.

You continue to use the Business Blueprint in the Solution Manager during theRealization phase (configuration and testing). You reuse the project structure youcreated in the Business Blueprint phase to configure and generate test plans.

Creation of the Business Blueprint

Defining the Business Blueprint enables you to document the business processesthat you want to use in your SAP System. You create a project structure in whichrelevant business scenarios, business processes, and process steps are organized ina hierarchical structure. You can also create project documentation to assign toindividual scenarios, processes, or process steps. To define how business processesshould run in SAP Systems, you need to assign transactions to each process step.

The definition of the Business Blueprint provides a detailed description ofbusiness processes and system requirements. You can also print out the BusinessBlueprint document. The project documentation and the project structure thatyou use during the Business Blueprint phase can be used during configurationand test organization.

Use of Business Blueprint project structure during Realization

• When you configure business processes, the system displays the projectstructure you created for the Business Blueprint. You can use the BusinessBlueprint project structure as a point of orientation during configuration.

• You can also display and edit the project documentation created in theBusiness Blueprint phase during configuration.

• The project structure from the Business Blueprint forms the basis for all testplans that you create during test organization.

The transactions that you assign to process steps in the Business Blueprintare placed in test plans during test plan generation.

The transactions can be processed as function tests to test the transactions.



Figure 53: Business Blueprint Work Center

Business processes do not have to be created from scratch in SAP SolutionManager. SAP offers some support tools and options that are presented in thefollowing lessons.

• Business Process Repository• A Business Process Modeling Tool• Solution Documentation Assistant• Other Solution Manager Project or Solution

Figure 54: Starting points for SAP Solution Manager Business Blueprint



Exploring the Business Blueprint StructureA Business Blueprint consists of the following structure items that are organizedin a hierarchical structure:

• Organizational units• Master data• Business scenarios• Business processes• Process steps• Interfaces

You assign content, for example, project documentation, Business ConfigurationSets, or transactions, to individual structure items in the SAP Solution Manager.

You can also create structure items for organizational units and master data belowa business scenario. You use these structure items only if the organizational unitsand master data are relevant exclusively for the business process above them inthe structure.

All the levels of this structure can be modified to represent the entirecustomer-specific solution.

The Business Blueprint structure in the left-hand pane can be filtered by attributessuch as Scope, Status, Team Member, Keyword, End-User Role or GlobalAttribute.

Figure 55: Structure of a Standard Scenario

A Business Scenario is a set of processes that define a business task in acomprehensive and self-contained manner on a macro level.

A Business Process is a set of logically related activities performed to achievea defined business outcome.



A Process Step is an elementary activity performed to accomplish a process.

You can use the Structure tab to create or change the project structure in whichorganizational units, master data, business scenarios, processes, and process stepsare listed.

Note: The predefined folders for organizational units and master datacannot be deleted.

Figure 56: Working with different levels

Note: The number of three business process levels (Business Scenario,Business Process, Process Step) is restricted cannot be extended.

You can create interfaces for the processes in a solution or a project, centrally,and reuse them in various processes. You then only have to maintain the requiredinformation, e.g. sending and receiving logical components, technology andinterface type used, once. When maintaining interfaces, you define a threefoldstructure consisting of interface scenarios, interfaces, and interface steps. Youneed interfaces for business process and interface monitoring.

The Structure tab enables you to:

• Add new scenarios, business processes, process steps and interface elements(interface scenarios, interfaces, interface steps)

• Adapt names for scenarios, business processes, and process steps andinterface elements to suit individual enterprises

• Remove scenarios, business processes, and process steps from the projectstructure



For organizational units, master data, process steps and interface steps, you needto specify the component in the system landscape to which the structure itembelongs. You cannot specify a component for business processes, because afew business processes run across components. Assignment of components isperformed at the process step level.

Defining the Business Blueprint based on theBusiness Process RepositoryThe SAP Solution Manager provides central access to the SAP reference businessprocesses as a starting point for the project scope.

When creating the business blueprint, customers select the pre-configuredbusiness processes they want to evaluate or implement. Customers can also createtheir own business processes. Based on the scenarios selected in the scope, thecorresponding Business Process Repository content is made available.

The Business Process Repository is a package of reusable, predefined businessprocess content that is comprised of:

• Scenario and process documentation• Transaction assignments• IMG assignments• Configuration guides• Predefined test cases, delivered for selected areas

Note: The available Business Process Repository content may vary fordifferent scenarios. Some BPR areas may cover only parts of the contentassignment listed above.



Figure 57: Building up a customer solution based on SAP referenceprocesses

The SAP Solution Manager provides with the Business Process Repository centralaccess to the list of business scenarios that serve as a starting point to identifythe project scope to be implemented.

If you chose a predefined structure item from the Business Process Repository,the system specifies the components for the system.

When creating the detailed business blueprint, customers select additionalpredefined business processes to complement the project scope. SAP stronglyrecommends to start an implementation project based on SAP reference content.You can also amend these predefined processes to suit your business needs.

You can also include additional sections, graphics, demonstrations, procedures,and/or simulations.

When creating the business blueprint, customers select the pre-configured businessprocesses they want to implement. Based on the scenarios selected in the scope,the corresponding Business Process Repository content is made available.

Note: Latest available content for the business processrepository can be downloaded from SAP Service Marketplaceat http://service.sap.com/solutionmanager or be accessed onhttps://implementationcontent.sap.com/bpr.


http://service.sap.com/solutionmanager

https://implementationcontent.sap.com/bpr


Figure 58: Using BPR content in your project

General documentation:

• All the documentation delivered by SAP is in the form of generaldocumentation, which cannot be changed by the customer. These documentstake, i.e. the form of scenario descriptions or installation guides.

• The documents delivered by SAP are stored in the Knowledge Warehouse,which is available after installing and setting up the SAP Solution Manageror they are links pointing to the SAP Help Portal at http://help.sap.com.

Transaction documentation:

• In implementation projects, the documentation of relevant standardtransactions is displayed at the process step level. However, you need toinstall the SAP Library, which enables access to application help for thetransaction in corresponding managed systems.



Figure 59: Search Function and Preview in Business Process Repository

Note:

• Structure items in grey can be selected, but require an additionallogical component that have to be assigned to your project systemlandscape.

• Context-specific search is restricted to specific structure level suchas scenarios.



Maintaining the Business Blueprint Structure

Figure 60: Define Project Scope – Adjust Structure

You can Copy and Paste an existing structure element. The copied element hasthe prefix “Copy of” and copied sub-items do not have a designation. This can beuseful when two or more elements share the same process or business requirement.For example, in Supply Chain Planning where the manufacturing process forMake-to-Stock product may be different from the Make-to-Order process butthe Shipping and Billing business requirements may be the same regardless ofthe product involved.

The Copy function allows both the copy of general documentation and projectdocumentation.

The Copy and Paste functionality within the structure allows the option to:

• Refer to original document(s)• Copy existing document(s)• Ignore documents while copying structure

Assignments of administrative data and issues are not copied.



Figure 61: Copy/Paste Function

Figure 62: Shortcuts in Blueprint Structure

Shortcuts are used when a structure element (i.e. a process step or master data) isused more than once and multiple data maintenance should be avoided. A shortcutlinks to another element in the process structure. The changes are always donein the original object.

Note: Use the Where-Used-List to display all occurrences of a structureelement.



Graphical Representation of Business Processes• You can display a process graphic.• You can create and change the connections between graphic elements to

indicate the message flow.

Prerequisites:

• Local availability of Internet Explorer (5.5 or higher)• ActiveX controls are active in your browser

Figure 63: Graphical View of Project Structure

The graphic in the Graphic tab at process level visually addresses the followingquestions:

• Which process steps does the process contain?• In which logical components do the process steps run?• What dependencies exist between process steps (predecessor-successor

relationships)?

Maintaining User-specific SettingsBy choosing Settings → User Specific, you can specify if you want to display thedocumentation on the Project Documentation tab or in a new window.



You can also specify when data should be saved.

• If you choose the Save Automatically option, the data will be savedautomatically when you change the structure element.

• If you do not select the Save Automatically option, the data is savedprovisionally but is saved only to the database when you choose to Save.

Assigning Administrative Data to Business BlueprintStructure

Figure 64: Administration of Structure Elements

For all structure elements administrative data can be assigned.

In a project important data are the start and end date for the editing of a structureelement. For reporting purposes the status value can be set.

Most projects assign responsible persons (e.g. process owners) to a structureelement.

Note: The values for the administrative data (team members, keywords,status) must be maintained in the project administration before they can beassigned in the business blueprint or configuration structure.



Assigning Transactions to Business BlueprintStructure

Figure 65: Working with Transactions

At the process step level, run the transaction marked as “default” and evaluate howthe process-related transaction fits project-specific requirements.

Transactions and reports that do not yet exist in the component systems, can alsobe assigned, so long as the component system itself exists.

Tests are executed to check if the transaction exists in the satellite system. Duringcustomer development, there should be a transaction defined in the Blueprint,even if the transaction is not yet running.

Figure 66: Test drive Business Scenarios in Evaluation System



Working with Issues/MessagesYou can create, change, and display issues and messages on the Issues/Messagestab. Create a message if problems in project documentation, configuration, orprocessing of test cases arise.

You can do the following:

• Create new issues/messages• Display or change issues/messages – You can change existing messages by

clicking Display in the Issue/Message tab and switching to Change mode inthe dialog box that appears

• Attach documents to issues/messages

The issue/message is forwarded to your message system and processed. Allissues/messages are stored and processed in a single system. Both the SAPSolution Manager and the Global Service and Support Backbone have accessto this system. Problem messages are created by default in the local SolutionManager system. You can also navigate to a system other than the SolutionManager system to create problem messages (customizable through IMG).

Prerequisites for message handling:

• To be able to create messages, you must set up the Service Desk functionalityand specify a system to store the messages, typically the Solution Managersystem.

• You can change message system settings, create number ranges and maintainmessage system roles in the SAP Solution Manager customizing.



Figure 67: Message Creation

The Incident Management Workcenter can be used for central problem messagehandling.

You can process messages for which you are the processor with this transaction.

You can search for problem messages in the SAP Solution Manager projectanalysis.

Assigning End User RolesTo facilitate the flow of information to users and/or groups of users, the End UserRolestab can be configured. This tab uses the HR Organizational structure of theSAP Solution Manager system. By default, a standard Org. Structure exists withinSolution Manager. The structure can be modified and enhanced to fit the needsof the project. The End User Roles tab is available from transactions SOLAR01and SOLAR02.

Three types of roles are available:

• Organizational Unit (OU)• Job• User



In the E-Learning Scenario, which will be discussed later in the course, eachBusiness Process and/or process step can be assigned multiple types. By assigningrole types, when learning materials are assigned to that Business Process or processstep, all users assigned via OU, Job or User can receive a link to the materials.

Using Filter Options for Business Blueprint StructureThe following filter options are worth mentioning due to their potential timesaving features.

Figure 68: Using Filter Options for Business Blueprint Structure

To help locate elements in the Business Blueprint Structure in transactionsSOLAR01 and SOLAR02, the structure filter is available, providing the user tosee only those elements desired, based on:

• Scope• Status• Team Member• Keywords• End User Roles



From transaction SOLAR01 or SOLAR02:

1. Select the filter icon in the top left corner of the Business Blueprint Structurewindow

2. Select the desired filter attribute3. Select the value of the attribute to filter on

As a result, only those elements which match the filter inputs will appear in theBusiness Blueprint Structure window.

Feature List Business Blueprint

Figure 69: Feature List Business Blueprint

• Lock dedicated objects in business blueprint and configuration

– You can lock dedicated objects, e.g., structure nodes, single tabs incl.documentation, to restrict phase-based changes your project work.

– Example: As a process owner, you lock a dedicated business processto prevent any structure scope changes; you lock the documentationattached to it, and the application scope (e.g. transactions to beassigned), later.

– For structure nodes and tabs, no customizing is required– Requires customizing: you have to use a status scheme for

documentation: SAP Solution Manager Implementation Guide –>SAP Solution Manager –> Cross-Scenario Settings –> DocumentManagement –> Status for Documents

• Combine locks with signature strategy

– All locks can be combined with a signature strategy– Requires customizing: Define a signature strategy: SAP Solution

Manager Implementation Guide –> SAP Solution Manager –>Cross-Scenario Settings –> Digital Signature –> Signature Strategy



– Customizing: Assign signature strategy to structure nodes and tabs:SAP Solution Manager Implementation Guide –> SAP SolutionManager –> Scenario-Specific Settings –> Implementation/Upgrade –>Object Attributes –>Assignment of a signature strategy when locking aproject structure

• Assign customer attributes to classify application scope of processes andreference objects

– Customer attributes give you the flexibility to define and use freelydefinable attributes to categorize/classify your project structure(structure nodes) and additional objects (e.g. documentation,transaction, IMG, function module).

– Customer attributes are applicable to all projects (not project-specific).– Customer attributes values are copied when copying a

project/template/solution.– Multi-value attributes can be assigned, that is, one attribute can be

assigned several times to a structure item but with different attributevalues.

– Attribute can be mandatory– Attribute values can be checked to ease reporting– Reporting capabilities are available for all assignment reports (except

for documents and links) and for admin (General Status Analysis)– Example 1: Categorize the business criticality of a process– Example 2: Specify the region in which the process runs– Requires customizing: SAP Solution Manager Implementation

Guide –> SAP Solution Manager –> Scenario-Specific Settings –>Implementation/Upgrade –> Object Attributes

• Enhance and restrict object types on Transaction tab

– You can enhance or restrict the object types available on the Transactiontab.

– Customizing: SAP Solution Manager Implementation Guide–> SAP Solution Manager –> Scenario-Specific SettingsImplementation/Upgrade –> Blueprint and Configuration –> TabExtension



Figure 70: Feature List Business Blueprint Documentation

• Assign documentation to referenced objects

– You can assign a document to a content object in the context of alogical component. For example, you can assign notes documented inthe integrated KW, to an IMG activity, as an object attribute.

– To use this functionality: mark reference object on tab and selectAttributes icon –> Links

• Assign technical objects to test document

– You can assign technical objects attached to the structure node, e.g.IMG activities, transactions, eCATT, as an attribute, to a test casedocument.

– To use this functionality: mark reference object on tab and selectAttributes icon -> Test objects

• Use bi-directional links when creating/assigning documents

– All documents can be marked as bi-directional. This means that a linkto a document works: a) from the document to the linked document andb) from the linked document back to the document.

– Example 1: A test requirement document is attached to a process, andrelated test case descriptions are attached as (bi-directional) documentlinks. When assigning the test case descriptions to process steps, thetest requirement document is automatically displayed as a referenceddocument, on the Links tab.

– Example 2: risk document and activity descriptions on how to tacklethe risk

– To use this functionality: mark reference object on tab and selectAttributes icon -> Links



• Display all old documentation versions via history with notification“obsolete”

– When trying to open previous document versions on the Historytab, you are notified with “The displayed version of the document isobsolete”.

– To use this functionality: mark the document and select Attributes icon-> History tab -> select older than the current entry and Display icon.

• Assign signature strategy to status in status schema

– You can assure the authenticity and integrity of documents, e.g. byhaving authorized persons sign documents with specified status values,e.g. to comply with FDA 21 CFR Part 11 .

– Customizing 1: SAP Solution Manager Implementation Guide –> SAPSolution Manager –> Cross-Scenario Settings –> Digital Signature –>Signature Strategy

– Customizing 2: Assign signature strategy to status schema: SAPSolution Manager Implementation Guide –> SAP Solution Manager–> Cross-Scenario Settings –> Document Management –> Status forDocuments –> Define Document Status Schemes

• Display current signatures

– You can display which user, in which role, has signed a document when.– To use this functionality: mark the document and select the Display icon

• Print out current signatures (by whom, in which role, when)

– To use this functionality: use SAP print icon for printout. An additionalpage will be printed, with all signature information

• Check-In/Check-Out documents for offline work.

– You can check out a document to work offline on your local PC. Duringthe checkout, the document is locked for online editing in SAP KW(Knowledge Warehouse).

– To use this functionality: mark the document and select the Checkdocument in/out icon

• Move/store documents to folder (group).

– Documents can be stored in other than the default (project) folders, torestrict access to these documents by folder level.

– To use this functionality: mark the document and select Attributes icon–> General tab –> Folder

– Use the authorization object S_IWB-IWB_FLDGRP to restrict folderaccess

• Read/display option for accessing documents

– read: only versions with specific status can be read



– display: all versions can be displayed, but not changed– Requires Customizing: SAP Solution Manager Implementation Guide

–> SAP Solution Manager –> Cross-Scenario Settings –> DocumentManagement –> Status for Documents –> Assign Status Values forRead Authorization

• Create URL to provide read access from external sources withoutpersonalized user

– You can generate a URL for every KW document. This URL can beembedded and launched from external sources, e.g. from the intranetor a learning map. This makes documents available to project staffwithout users in SAP Solution Manager.

– Requires customizing: SAP Solution Manager Implementation Guide–> SAP Solution Manager –> Cross-Scenario Settings –> DocumentManagement –> Display Solution Manager Documents from ExternalApplication –> Configure Solution Manager Document Display viaURL

• Adapt Business Blueprint Document Template

– You can configure the business blueprint document template to yourbusiness needs, e.g. by changing the header or footer, or inserting yourcompany logo.

– Requires customizing: SAP Solution Manager Implementation Guide–> SAP Solution Manager –> Cross-Scenario Settings –> DocumentManagement –> Generation of Documents –> Adjust Template Filesfor Generation of Business Blueprint Document

ARIS and SAP Solution Manager SynchronisationARIS for SAP NetWeaver and SAP Solution Manager can be used for SAPimplementation, template and upgrade projects. ARIS is a modelling tool forbusiness processes. SAP Solution Manager is an application lifecycle managementtool that supports the implementation, operation, and ongoing use of SAP andnon-SAP solutions. Both tools offer the modelling of business processes. Theseoverlapping, but different focuses and functionalities explain why it makessense to synchronize both tools. The strengths of ARIS lie, in the modelingof complex business processes, graphical modelling and support of recognizedprocess standards (i.e. event driven process chains). The process models can beenriched with any necessary information. Moreover, the underlying database hasto be mentioned. SAP Solution Manager strengths came up when the design phaseis finished and implementations, operations and optimizations phase starts. Forinstance, this includes the connected systems for blueprint, configuration andtesting, as well as solution monitoring (business process monitoring) and changemanagement functionality.



Figure 71: ARIS Solution Manager Process Level

The levels of process modeling in ARIS can be chosen freely. In contrast,SAP Solution Manager supports only four modeling levels (Scenario, Process,Process Step and Transactions). That means that the levels of SAP SolutionManager have to be mapped to the levels that are available in ARIS. In additionto the synchronization of process levels the exchange of implementations links,documentation links and system landscape information and organizational unitsis supported.

Figure 72: Comparing ARIS and SAP Solution Manager Modeling



For the synchronization the modeling in ARIS has to be done in value added chaindiagrams, event-driven process chains and function allocation diagrams. Whereasthe models in ARIS on each level are stored in own diagrams, the modeling inSAP Solution Manager is done in one big model, the business blueprint structure.





Exercise 3: Business Blueprint Part 1-Defining the Business Blueprint Structure

Exercise ObjectivesAfter completing this exercise, you will be able to:• Use the pre-defined SAP implementation content• Define the project scope by creating a project-specific solution structure• Assign responsible team members and administrative data

Business ExampleDuring Phase 2, Business Blueprint, the project team will define and documentall business process requirements, both functional and technical. When possible,standard SAP business scenarios will be employed because they are deliveredwith predefined implementation content such as process documentation, IMGassignments, and test cases. Using these scenarios, you can significantly reduceproject implementation costs. At the end of Phase 2, a Business Blueprintdocument should be generated for approval. That will be done in the next exerciseBusiness Blueprint Part 2.

Task 1:In phase 1 (project preparation) you created your own project SOLT200_##. Nowin phase 2, the Business Blueprint phase, you will define your business processstructure with all the related requirements for this project. Open your projectwith the following steps:


→ Open the <User menu> in the SAP System (TT4)

→SAP SolutionManagerWork Center; T-Code: <SOLMAN_WORKCENTER>



→ Click on the link Define Business Blueprint (on the right-hand side)

1. Select your recently created project SOLT200_##.

2. In the Structure tab, create your own business scenario and businessprocesses:




Go to Structure area Add Name

<Group Project Description> →Business Scenarios

Sales <##>

Save the new entry. Navigate to your new business scenario and insert thefollowing business process:


<Group Project Description> →Business Scenarios → BusinessProcesses

Sales Process <##>

Save the new business process.

Note: If you want to save your changes automatically, the SAPSolution Manager can be configured accordingly ( User Settings.Settings → User-Specific you can select Save Assignments withoutPrompt.)

3. In the Structure tab, add process steps from the Business Process Repositorythat are part of the project-specific solution structure. Use the followingstructure areas and process steps :

Structure area Process Steps

Sales → Order Processing (CRM)• Create Order• Process Order

Sales→Sales OrderManagement(SAP R/3 4.6C) • Create Sales Order

• Create delivery• Send/Print Delivery Documents• Create Customer Invoice• Send/Print Billing Documents

4.

In the Structure tab, sort the process steps in the sequence specified above.

5. In the Structure tab, rename the following process steps:




Original name (Description inBusiness Process Repository)

New Name (Process Step)

Create Order Create Order in CRM

Create Sales Order Create Order in ERP

6. Create the following NONSAP-specific process steps for the businessprocess Sales Process ##:

Logical Component Process step

Z_NONSAP Check Order Consistency

Z_NONSAP Pricing

7. Create a shortcut for the NONSAP-specific process step Check OrderConsistency and assign it to the same business process.

Note: Now you can see in front of the step name a shortcut icon (likea chain link). The relation between linked element and original canbe seen by using the connection icon.

8. In the Structure tab order the process steps for Sales Process ## in thefollowing process flow and save your changes:

Process Steps

• Create Order in CRM• Check Order Consistency (Original)• Process Order• Pricing• Check Order Consistency (Shortcut)• Create Order in ERP• Create delivery• Send / Print Delivery Documents• Create Customer Invoice• Send / Print Billing Documents

9. In the Graphic tab, display the related business process graphic for SalesProcess ##.




10. Run the transaction assigned to the business process step Create Order inERP to evaluate the related SAP application.

Hint: You can change the system role, for example, Evaluation andDevelopment, through the Business Blueprint → System Role menu.

In the Transactions tab, you can run other transactions related tothe process task or designate another transaction as the default(standard).

Click the Back (F3) button to return to the SAP Solution Manager system.

11. (Optional) Navigate to the structure area <Group Project Description> →Business Scenarios → Sales <##> → Business Processes.

12. (Optional) Add another business process and try to build a realcustomer-specific process.

Task 2:Maintain administrative data to track the progress of the project.

1. For the Sales Process <##> maintain the Administration tab. Enter and savethe following data at the minimum:

Data Type Value

Status In Process

Assigned Project Member SMI310-## and SMI310-00

Plan Data <optional>

Actual Data <optional>

Keyword Administrative

2. In the Administration tab, copy the administrative data to subitems andchange the status In Process in several process steps to another status value.

Note: The available status values depend on the assignments to theproject in Project Administration <SOLAR_PROJECT_ADMIN>.

3. In the Administration tab of the Sales Process ##, copy the team members toall your process step items as part of a mass change. Check this change andsave the complete project at the end.



Solution 3: Business Blueprint Part 1-Defining the Business Blueprint StructureTask 1:In phase 1 (project preparation) you created your own project SOLT200_##. Nowin phase 2, the Business Blueprint phase, you will define your business processstructure with all the related requirements for this project. Open your projectwith the following steps:







1. Select your recently created project SOLT200_##.

a)

2. In the Structure tab, create your own business scenario and businessprocesses:


<Group Project Description> →Business Scenarios

Sales <##>

Save the new entry. Navigate to your new business scenario and insert thefollowing business process:


<Group Project Description> →Business Scenarios → BusinessProcesses

Sales Process <##>




Save the new business process.

Note: If you want to save your changes automatically, the SAPSolution Manager can be configured accordingly ( User Settings.Settings → User-Specific you can select Save Assignments withoutPrompt.)

a) Navigate to <Group Project Description> → Business Scenarios.Select the Structure tab. Create a new Scenario called Sales <##>.Click the Save button.

b) Navigate to <Group Project Description> → Business Scenarios →Sales <##> → Business Processes. Select the Structure tab. In theBusiness Process Name column, enter a new item using the namingconvention Sales Process <##>. Click the Save button.

3. In the Structure tab, add process steps from the Business Process Repositorythat are part of the project-specific solution structure. Use the followingstructure areas and process steps :

Structure area Process Steps

Sales → Order Processing (CRM)• Create Order• Process Order

Sales→Sales OrderManagement(SAP R/3 4.6C) • Create Sales Order

• Create delivery• Send/Print Delivery Documents• Create Customer Invoice• Send/Print Billing Documents

a) Navigate to the business process <Group Project Description> →Business Scenarios → Sales <##> → Business Processes → SalesProcess <##>.

b) Select the Structure tab.

c) In the Step Name column, use possible entry help (F4).

d) Navigate to the structure areas as shown above and select the relatedprocess steps.

e) Click the Save button to transfer structure items to the project structureand save.

4.




In the Structure tab, sort the process steps in the sequence specified above.

a) Select the process step(s), click the Move Up/Move down buttons tosort the process steps, and Save.

5. In the Structure tab, rename the following process steps:

Original name (Description inBusiness Process Repository)

New Name (Process Step)

Create Order Create Order in CRM

Create Sales Order Create Order in ERP

a) In the Process Step column, overwrite the structure items with the newnames and Save.

6. Create the following NONSAP-specific process steps for the businessprocess Sales Process ##:

Logical Component Process step

Z_NONSAP Check Order Consistency

Z_NONSAP Pricing

a) In the Process Step column, enter a name for the new structure item.

b) In the Logical component column, select ZNONSAP.

7. Create a shortcut for the NONSAP-specific process step Check OrderConsistency and assign it to the same business process.

Note: Now you can see in front of the step name a shortcut icon (likea chain link). The relation between linked element and original canbe seen by using the connection icon.

a) Select the process step Check Order Consistency in the BusinessBlueprint Structure (left-hand side).

b) Open the context menue with the right mouse button

c) Choose Copy.

d) Choose again with the right mouse button the context menue and usethe function Insert Shortcut.

e) Confirm the popup Data has been changed with Yes.

8. In the Structure tab order the process steps for Sales Process ## in thefollowing process flow and save your changes:




Process Steps

• Create Order in CRM• Check Order Consistency (Original)• Process Order• Pricing• Check Order Consistency (Shortcut)• Create Order in ERP• Create delivery• Send / Print Delivery Documents• Create Customer Invoice• Send / Print Billing Documents

a) Use the Move Up/Move down buttons to place the structure itemcorrectly and Save.

9. In the Graphic tab, display the related business process graphic for SalesProcess ##.

a)

Hint: If prompted enter your username, SMI310-##, andpassword.

10. Run the transaction assigned to the business process step Create Order inERP to evaluate the related SAP application.

Hint: You can change the system role, for example, Evaluation andDevelopment, through the Business Blueprint → System Role menu.

In the Transactions tab, you can run other transactions related tothe process task or designate another transaction as the default(standard).

Click the Back (F3) button to return to the SAP Solution Manager system.

a) Click on the Execute-Symbol in the Business Blueprint Structure(left-hand side).

11. (Optional) Navigate to the structure area <Group Project Description> →Business Scenarios → Sales <##> → Business Processes.

a)




12. (Optional) Add another business process and try to build a realcustomer-specific process.

a)

Task 2:Maintain administrative data to track the progress of the project.

1. For the Sales Process <##> maintain the Administration tab. Enter and savethe following data at the minimum:

Data Type Value

Status In Process

Assigned Project Member SMI310-## and SMI310-00

Plan Data <optional>

Actual Data <optional>


a) Navigate to the business process <Group Project Description> →Business Scenarios → Sales <##> → Business Processes → SalesProcess <##>.

b) Select the Administration tab.

c) In the Status field, use possible entry help (F4) and select the statusvalue In Process.

d) In the Assigned Project Member column, use possible entry help (F4)and select users as indicated above.

e) Populate the Plan Data and Actual Data fields as required.

2. In the Administration tab, copy the administrative data to subitems andchange the status In Process in several process steps to another status value.

Note: The available status values depend on the assignments to theproject in Project Administration <SOLAR_PROJECT_ADMIN>.

a) Click the Copy Data to Subitems button to copy the values for Status(and Plan Data) to process steps and Continue (Enter).

b) Navigate to several process steps under the business process SalesProcess ## and change the copied status value In Process using possibleentry help (F4) and Save.




3. In the Administration tab of the Sales Process ##, copy the team members toall your process step items as part of a mass change. Check this change andsave the complete project at the end.

a) Click on the Sales Process ## and select the Administration tab.

b) Navigate to the tab Team Member and select the icon Make MassChanges.

c) Use the entry Add from the drop-down-list.

d) Choose the team members with the checkbox in the first column.

e) Accept the selection with the green checkmark (Copy Selection).

f) Check if your changes are available on process step level.

g) Now all is done. Save the project.



Lesson Summary

You should now be able to:• Explain the Business Blueprint phase• Create the Business Blueprint structure, preferably based on SAP predefined

implementation content• Use the message handling functions



Lesson: Document Management

Lesson OverviewSAP Solution Manager offers enhanced features for working with documents thatare needed for working with documents in projects. Especially when multipleusers work with documents a document management tool is needed.


• Create the Business Blueprint documentation• Generate the Business Blueprint document

Business ExampleAs project team member you have to create documents.

Document Management with the Integrated KnowledgeWarehouseDocuments are saved in the Knowledge Warehouse and are available whenworking with the SAP Solution Manager.

Figure 73: Blueprint Structure - Knowledge Warehouse Dependencies


SMI310 Lesson: Document Management

Documentation is centrally stored in the Knowledge Warehouse embedded andconfigured in SAP Solution Manager. One dedicated document may be reused inseveral projects.

SAP Solution Manager with integrated SAP Knowledge Warehouse provides thefollowing functionality:

• Central storage of all project documentation in SAP Knowledge Warehousewith the main focus on Business Blueprint and Configuration

• Provides functions to create, edit, store, upload, and download documentation• Predefined templates/document types are shipped with SAP Solution

Manager:

– Templates for scenario descriptions, diagrams, and installation guides– Customer Input Templates (CITs)– Templates for interfaces, forms, and reports

• Creation of project-specific documentation types (templates)• Reporting features• Locking features for documents if multiple user work in Solution Manager.

You assign a document type to all the documents you create. Based on thedocument type, a document template is called up. You can use only documenttypes that either have a document template or a file name extension supportedby the SAP Solution Manager. If a document type has no template or file nameextension, the text editor is launched.

Working with Project DocumentationCreating Documentation

You can use the Project Documentation tab to create, add, display, or delete specificproject documentation on individual structure items for the implementationproject. You can also display the document attributes or export documents.



By clicking the icon Insert Document, you can:

• Create new documents.• Link to documents whose originals are assigned to other structure elements

in Solution Manager.• Copy documents whose originals are assigned to other structure elements

in the SAP Solution Manager and that you can change independently ofthe original document.

• Upload a file.

Ensure that you enter the title in the dialog box. If not, “new document” isautomatically selected as the default type. You can change titles by clickingthe Attribute icon.

• Create a link to a Web site.

To determine which other structure items a document is assigned to, click theWhere-Used List icon.

Note: n the project all documentation types are available as previouslydefined and assigned to the project in the project administration(SOLAR_PROJECT_ADMIN). In most cases naming conventions forthese documents are useful.

Figure 74: Add Project Documentation

Note: Consider the differences between linking and copying



Document copy:

• A new document is created which does not contain any reference to thedocument from which it was copied.

• Document history is not copied.• The copied document does not receive any updates from the initial document

from which it was copied.

Document reference/link:

• If a document that is referenced is changed, all occurrences of thisdocument immediately reflect the changes (e.g., in an implementationproject, productive solution, and upgrade project - if the option to referencedocumentation was chosen).

• Document history is kept.

Using the “Link to SAP Solution Manager Document” or “Copy of SAP SolutionManager Document” function to add a document provides a flexible search featureto locate an existing document in the knowledge warehouse.

It is not possible to link to external documents (KW constraint) unless they areaccessible from an URL. It is recommended that you check in those documentsthat you wish to link to the structure element.

Figure 75: Link or Copy Project Documentation



You assign a document type to all the documents you create. Based on thedocument type, a document template is called up. You can use only documenttypes that either have a document template or a file name extension supportedby the SAP Solution Manager. If a document type has no template or file nameextension, the text editor is launched.

User-specific settings enable you to open documents in a new window.

Figure 76: Create Project Documentation

Maintaining Document Attributes



You can enter the following attributes in the General tab (mandatory attributes aredefined in bold letters):

• Title: You can change the title.• Technical Name: You can choose the technical name for the document.• Documentation Type: You can change the document type.• Status: Choose the current edit status of the document from the list.• Priority: Select the document priority from the list.• Person Responsible: You can determine an owner (author) for the document.

You can use the entries to do so.• Folder: You can use folders to group documents and to govern authorizations

for documents.• Business Blueprint-Relevant: Select this check-box if you want the document

to be included in the printout of the Business Blueprint document.• Keywords: Enter relevant keywords by which your document can be

classified or identified.• Generate: You can generate an URL for a document stored in the Knowledge

Warehouse. That enables other persons to open the document directly withoutsearching it in the SAP Solution Manager or in the Knowledge Warehouse.

Note: Remember that documents not marked “BusinessBlueprint-Relevant” will not be included in the Business Blueprintdocument.

Displaying Document Details

The History tab displays technical details such as who created or changed thedocument, when it was created, when it was last changed, and the originallanguage of the document.

Displaying Document Versions

Current and older document versions can be displayed via the History tab. Marka respective line and select the Display icon to display the selected documentversion.



Figure 77: Edit Project Documentation/Documentation Attributes

Working with General DocumentationFor template project types, the General Documentation tab provides the samefunctions as the Project Documentation tab. For implementation projects, theGeneral Documentation tab has limited functions to display, export, and sortdocuments.

To copy general documents for further processing and use in projectdocumentation, you need to click the Copy Documents to Project Documentationicon. Any changes made to copied documents will not affect the original texts.

To copy a document from the General Documentation to the ProjectDocumentation tab:

1. Choose one or more documents by selecting the corresponding row(s).2. Click the Copy Documents to Project Documentation icon.3. Enter a documentation type for the document.4. Click Copy to transfer your entries to the structure. The documents are copied

to the Project Documentation tab, where you can access and edit them.



Figure 78: Copy to Project Documentation

Creation of a Business Blueprint DocumentAfter creating the Business Blueprint (project structure, project documentation,and transaction assignments), you can generate the Business Blueprint documentfor approval and use.

The Business Blueprint Document typically reflects a consolidated big pictureof all the work you have done in the Blueprint phase and includes the definedprocess structure with documented business processes as well as their graphicalrepresentation. It also contains all other kinds of documentation, such as functionalrequirements. The goal is to portray a the process and functional scope to beimplemented in the subsequent "Realization" phase. This document may also beused for sign-off by the different application or functional implementation teams.



Procedure:

1. Start the Business Blueprint transaction, SOLAR01 or Implementation andUpgrade Workcenter –> Plan –> Define Business Blueprint

2. Select Business Blueprint → Generate Blueprint Document...3. Flag which graphics to include in the generated document (Scenarios and/or

Business Processes) under the General Tab.

You can specify a shared repository or drive for the generated blueprintdocument, under Directory, to make the blueprint document available toother project team members.

4. Specify what Structure Elements and Documents to consider in the BusinessBlueprint generation in the Scope Tab. You can, for example, filter bydocument type or status, or select from the project structure by choosingStructure.

5. In the Display Options Tab which Structure Elements and DocumentAttributes to include in the Business Blueprint can be selected. If a documentoccurs several times in the blueprint, you can either include the entiredocument several times, or set a link to where the document is included once.Select or deselect Insert Link under Documents Used Several Times.

Enter the required data and choose Execute. All required documents aredownloaded to the destination chosen and a dialog appears. Select Continue.Your text-processing (Word) program starts. A dialog box gives youinformation concerning a macro that should be run in Microsoft Word.

6. Choose the menu Tools → Macro → Macros. Then select the macroSAP_BUSINESS_BLUEPRINT from the list and choose run.

The Blueprint document will now appear.

You can use the upload function on the Project Documentation tab to edit theBusiness Blueprint document further or publish it for users in the SolutionManager.

To print the document, use the print function in the text-processing program. Tosave the document to a local directory, use the save function. If you want to editthe Business Blueprint document or make it available to users in the SolutionManager, use the upload function in the Project Documentation tab to uploadthe document. Deselect the FlagBusiness Blueprint-Relevant to ensure that thedocument is not included in the next Business Blueprint document.



Figure 79: Generate Business Blueprint Document

Note:

• Blueprint generation will download all relevant documents to yourlocal hard disk first. Select criteria to minimize generation time

• Not all documents linked in the Solution Manager will be embeddedin the Business Blueprint Document.

• Only those documents with the docu attribute “Business Blueprintrelevant” set will be included in the Business Blueprint Document.

• Freeze scope and locking of documents can be set inSOLAR_PROJECT_ADMIN on the Scope tab.





Exercise 4: Business Blueprint Part 2 -Document Management

Exercise ObjectivesAfter completing this exercise, you will be able to:• Document business and technical requirements along the project scope• Create a blueprint-specific issue using message-handling features• Generate a Business Blueprint document

Business ExampleDuring Phase 2, Business Blueprint, the project team will define and documentall business process requirements, both functional and technical. When possible,standard SAP business scenarios will be employed because they are deliveredwith predefined implementation content such as process documentation, IMGassignments, and test cases. Using these scenarios, you can significantly reduceproject implementation costs. At the end of Phase 2, a Business Blueprintdocument should be generated for approval.

Task 1:1. Choose the predefined training project (SMI310_200).



→ SAP Solution Manager Work Center; T-Code: <SOLMAN_WORK-CENTER>




Task 2:Review the available implementation content along the business process LeadAnalysis (Business Scenario: Lead and Opportunity Management).

1. Read the scenario documentation Business Scenario Lead and OpportunityManagement for the business process Lead Analysis.




Task 3:Change the project and choose your own project SOLT200_##.

In the Project Documentation tab, document the business and technicalrequirements (Business Blueprint) along the project-specific solution structure.

1. At the process step Create Order in CRM, create a Customer Input (CI)template on the Proj. Documentation tab and describe with your own wordsthe business requirements for this process step.

Document attribute: Possible Entries:

Title CRM Business Requirements

Documentation Type Customer Input Template

Status In Processing

Radio Button Create New Document

Note: If you want to display/edit the document in a separateapplication window, you can change the settings over the menueSettings → User-Specific → General Settings.

2. At the process step Create Order in CRM, create an Interface Form anddescribe the technical requirements on the interface to the NONSAP processstep Pricing.


Title Interface CRM - Pricing

Documentation Type Interface Form



3. At the process step Create Order in ERP, link the CI template described atthe process step Create Order in CRM.

4. Now the name of the document is obsolete. The CRM business requirementsdocument will be used for CRM and ERP requirements. Change the title ofthe document to CRM-ERP Business Requirements by using the Attributeicon.

5. At the process step Create Order in ERP, create Meeting Minutes andmaintain the following document attributes:





Title Meeting Minutes <date>

Documentation Type Meeting Minutes



6. Change the following attributes of the document Meeting Minutes <date>by using the attribute icon.

Data Type Value

Priority High

Status Released


Business Blueprint Relevant <select>

7. (Optional) At other process steps, use other options (Upload File, Copyof a SAP Solution Manager Document, Web Link, etc.) and add projectdocumentation to specify additional business and technical requirements.

8. (Optional) Maintain the document attributes for other project documents.

Task 4:Create a Business Blueprint-specific message for the process step Create Orderin CRM.

1. In the Issues/Messages tab, create a message about the interface specificationusing the following data and save.

Data Type Value

Priority 4 (Low)

System/IBase IBase component: 74

Component CRM-BE

Reported by <your user>

Short text Interface message ##

Long text Connection not possible

2. In the Issues/Messages tab, process the created message, as shown below:




Data Type Value

Pers. Resp. (MessageProcessor)

SMI310-00

Status Put In Process (In Process)

Task 5:Generate a Business Blueprint document.

Caution: Close all other Word applications before you generate theBusiness Blueprint document.

1. Create a Business Blueprint document. Restrict the selection to the structurearea Sales Process <##>.

2. Upload the generated Business Blueprint document to your business processSales Process ##.

Note: Deselect the document Business Blueprint-Relevant attributeand set the status to Released.



Solution 4: Business Blueprint Part 2 -Document ManagementTask 1:1. Choose the predefined training project (SMI310_200).



→ SAP Solution Manager Work Center; T-Code: <SOLMAN_WORK-CENTER>




a) If the correct project is not showing, choose the Other Project button,then select the (SMI310_200) project.

Task 2:Review the available implementation content along the business process LeadAnalysis (Business Scenario: Lead and Opportunity Management).

1. Read the scenario documentation Business Scenario Lead and OpportunityManagement for the business process Lead Analysis.

a)

• In the Documentation (Gen.) tab, choose Lead Analysis and openit by clicking the Display button.

• Read the document to understand the general structure and contentof scenario documentation.

• Click the Close Document button and return to the overviewscreen.

Task 3:Change the project and choose your own project SOLT200_##.

In the Project Documentation tab, document the business and technicalrequirements (Business Blueprint) along the project-specific solution structure.

1. At the process step Create Order in CRM, create a Customer Input (CI)template on the Proj. Documentation tab and describe with your own wordsthe business requirements for this process step.





Title CRM Business Requirements

Documentation Type Customer Input Template



Note: If you want to display/edit the document in a separateapplication window, you can change the settings over the menueSettings → User-Specific → General Settings.

a) If the correct project is not showing, choose the Other Project button,then select the (SOLT200_##) project.

Navigate to the business process <Group Project Description> →Business Scenarios → Sales <##> → Business Processes → SalesProcess <##> → Create Order in CRM.

b) Select the Project Documentation tab.

c) Click the Insert Document button and select the Create New Documentoption.

d) Insert all the required information (see above). Close the Add Documentwindow with Ok.

e) Enter sample data in the various sections of the template and save thedocument.

f) Click the Close Document button to return to the overview screen andconfirm by saving again.

2. At the process step Create Order in CRM, create an Interface Form anddescribe the technical requirements on the interface to the NONSAP processstep Pricing.





Title Interface CRM - Pricing

Documentation Type Interface Form



a) Click the Insert Document button and insert all the required information(see above). Close the Add Document window with Ok.

b) Enter sample data in the form and save the document.

c) Click the Close Document button to return to the overview screen andconfirm by saving again.

3. At the process step Create Order in ERP, link the CI template described atthe process step Create Order in CRM.

a) Navigate to the business process <Group Project Description> →Business Scenarios → Sales <##> → Business Processes → SalesProcess <##> → Create Order in ERP.

b) Select the Project Documentation tab.

c) Click the Insert Document button and select the Link to SAP SolutionManager Document option and press Enter.

d) The next popup ask you for the creation of a search index. Confirmwith Yes.

e) In the Find Document screen, choose your own project SOLT200_##and documentation type CIT as the search criteria and execute.

f) Select the created CI template from the list and continue with F2.

4. Now the name of the document is obsolete. The CRM business requirementsdocument will be used for CRM and ERP requirements. Change the title ofthe document to CRM-ERP Business Requirements by using the Attributeicon.

a) Select the document row of the document CRM Business Requirements.

b) Click on the Attribute icon.

c) Change the title to CRM-ERP Business Requirements.

5. At the process step Create Order in ERP, create Meeting Minutes andmaintain the following document attributes:





Title Meeting Minutes <date>

Documentation Type Meeting Minutes



a) Click the Insert Document button and insert all the required information(see above). Close the Add Document window with Ok.

b) Enter sample data in the form and save the document.

c) Click the Close Document button to return to the overview screen andconfirm by saving again.

d) Select the row for the project document Meeting Minutes.

e) Click the Attribute button, modify the values as indicated above, andcontinue.

Note: The Business Blueprint Relevant attribute is referencedwhile generating the Business Blueprint document.

6. Change the following attributes of the document Meeting Minutes <date>by using the attribute icon.

Data Type Value

Priority High

Status Released


Business Blueprint Relevant <select>

a) Select the document row of the document Meeting Minutes <date>.

b) Click on the Attribute-Icon.

c) Change the values of Meeting Minutes <date> with the values fromthe table above.

7. (Optional) At other process steps, use other options (Upload File, Copyof a SAP Solution Manager Document, Web Link, etc.) and add projectdocumentation to specify additional business and technical requirements.

a)




8. (Optional) Maintain the document attributes for other project documents.

a)

Note: The locking function in Project Administration<SOLAR_PROJECT_ADMIN, Scope tab enables you tofreeze the process scope and protect changes to the projectdocumentation.

Task 4:Create a Business Blueprint-specific message for the process step Create Orderin CRM.

1. In the Issues/Messages tab, create a message about the interface specificationusing the following data and save.

Data Type Value

Priority 4 (Low)


Component CRM-BE


Short text Interface message ##

Long text Connection not possible

a) Select the Issues/Messages tab.

b) Click the Create Message line on the Create button and insert all therequired information (see above). Close the Message window withSave (F6).

c) Optional: In the Attachmt tab, upload an attachment using the Importbutton.

2. In the Issues/Messages tab, process the created message, as shown below:




Data Type Value

Pers. Resp. (MessageProcessor)

SMI310-00

Status Put In Process (In Process)

a) Select the created message row.

b) Click the Display button to launch the message.

c) Change to the edit mode using the Display/Change Trans. button.

d) Assign user SMI310-00 as Resp. Person (Message Processor) andchange the status to In Process.

e) Save and return to the overview screen using the Back button (F3) andconfirm by saving again.

f) Save.




Task 5:Generate a Business Blueprint document.

Caution: Close all other Word applications before you generate theBusiness Blueprint document.

1. Create a Business Blueprint document. Restrict the selection to the structurearea Sales Process <##>.

a) Go to the menu at the top of the screen. Choose Business Blueprint→ Generate Blueprint Document. A selection screen with three tabswill pop up.

b) In the General tab, select the check-boxes beside which Graphicsshould be included in the Blueprint.

You can leave the default directory location for storing the document.

c) In the Scope tab, decide how much you want to include in the blueprint.

To do this, press the Structure button and drill down to your businessprocess Sales Process <##>.

Make sure to include only those structure items below Sales Process##, otherwise you will generate a very large blueprint!

d) In the Display Options tab, accept the defaults.

e) Next, choose the Execute button. A window will appeartelling you the file has been downloaded to the subdirectoryindicated and that you should open Word and run a macro called“SAP_BUSINESS_BLUEPRINT”.

• In MS Word 2003, go to the menu Tools → Macro → Macros,select the macro SAP_BUSINESS_BLUEPRINT, then choose Run.

• In MS Word 2007, go to the menu View → Macros → ViewMacros, select the macro SAP_BUSINESS_BLUEPRINT, thenchoose Run.

The blueprint document will open.




2. Upload the generated Business Blueprint document to your business processSales Process ##.

Note: Deselect the document Business Blueprint-Relevant attributeand set the status to Released.

a) Choose File →Save Copy as… to store the Business Blueprintdocument on the hard drive.

b) Click the Back button (F3) to return to the Business Blueprinttransaction.

c) Navigate to the business process SAP Solution Manager - TrainingProject → Business Scenarios → Sales-<##> → Business Processes→ Sales Process.

d) Select the Proj. Documentation tab.

e) Click the Insert Document button.

f) Enter the document title and select BB - Business Blueprint as thedocumentation type.

g) Choose the Upload File option and click OK (Enter).

h) Select the saved Blueprint file from the local directory.

i) Select the row with the Business Blueprint document and click theAttribute button.

j) Deselect the document attribute Business Blueprint-Relevant and setthe status to Released.

k) Save.



Lesson Summary

You should now be able to:• Create the Business Blueprint documentation• Generate the Business Blueprint document



Lesson: Reporting

Lesson OverviewThis lesson explains how to execute standard reports for all facets of theimplementation project.


• Execute standard reports for all facets of the implementation project• Identify other useful Solution Manager tools

Business ExampleThe project team will need to understand other features available in SolutionManager, such as reporting tools to use for various reasons throughout the project.

General Information on Reporting Capabilities

Figure 80: Reporting at a Glance


SMI310 Lesson: Reporting

You can save information about a project by phase or project activity, for example,status, deadlines, and team members. Project analysis is based on this information.The more details you record, the more project analysis options there are. Youcan analyze a project, a project view (only for customizing projects), or severalprojects simultaneously, based on the selected project type.

Reporting is an important topic in every project that enables project managersto keep track on the progress of the project. Project analysis can be doneproject-specific or cross projects.

SAP offers a collection of useful reports in one transaction. The reportingcan be accessed directly via transaction SOLAR_EVAL or from theImplementation/Upgrade work center navigation area Reports. Moreover, theproject phase specific transactions (e.g. SOLAR01 for the Business Blueprint)allow to jump into the reporting transaction (Environment –> Project Analysis).All assignments that are done in the business blueprint or in the realization phaseof a project can be evaluated.

The project analysis and analysis results display options are very flexible. Youcan use selection criteria to restrict the scope of the analysis. You can also specifythe presentation of the analysis results. You can create standard analyses and savethem as selection variants. You can call the displayed elements of the projectstructure or IMG activities directly from the output.

You can use the following analyses in project analysis based on the selectioncriteria you chose:

• Project information: Status information and documentation type analyses• Progress monitoring: For example, by linking various status information,

such as project team members and a given status, or by aggregating projectinformation

• General analyses: For example, daily analyses• You can restrict analyses to one or more projects (based on the project type).

Figure 81: Reporting Recommendations



Selected Business Blueprint Reports• Administration: Analysis of administrative information structured by general

status analysis and worklists, which can be assigned to one or more projectmembers. In analysis by worklists, you can focus the analysis on specificdata, such as the status and planned end.

• Assignments: Analysis of assignments in the project structure, i.e.documentation, transactions or issues/messages that were added during theproject.

– Example: Report on all documentation that has not yet been set tostatus "released".

– Example: Report on all assignments that are assigned to your user oryour project team.

During the generation of report variants, all selection criteria except structuralinformation can be selected.

Figure 82: Reporting – Search for Messages

You can run a report about the problem messages created and monitor their status.For example, you can cover the following use scenarios:

• Analysis of problem messages with status as Open• Analysis of problem messages created by a specific User• Check the processing status of all messages with priority as Very High


SMI310 Lesson: Reporting

Lesson Summary

You should now be able to:• Execute standard reports for all facets of the implementation project• Identify other useful Solution Manager tools


Unit Summary SMI310

Unit SummaryYou should now be able to:• Explain the Business Blueprint phase• Create the Business Blueprint structure, preferably based on SAP predefined

implementation content• Use the message handling functions• Create the Business Blueprint documentation• Generate the Business Blueprint document• Execute standard reports for all facets of the implementation project• Identify other useful Solution Manager tools


Unit 6Realization

Unit OverviewThis unit explains how to use the SAP Solution Manager in the Realization phase.The purpose of this phase is to implement business process requirements basedon the Business Blueprint. The objectives of the Realization Phase are the finalconfiguration of the system, robust functional and system testing, and the releaseof the system for production (live) operation.


• Use Solution Manger to configure the system based upon the BlueprintRequirements.

• Plan and prepare testing• Understand the concept of Business Configuration (BC) Sets• Conduct basic testing with SAP Solution Manager.

Unit ContentsLesson: Configuration and Development .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .158

Exercise 5: Configuration and Development.. . . . . . . . . . . . . . . . . . . . . . . . . . .175Lesson: Testing ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .185

Exercise 6: Testing ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .207


Unit 6: Realization SMI310

Lesson: Configuration and Development

Lesson OverviewThis lesson explains how to use the SAP Solution Manager in the Realizationphase. The purpose of this phase is to implement business process requirementsbased on the Business Blueprint. The objectives of the Realization Phase are thefinal configuration of the system, robust functional and system testing, and therelease of the system for production (live) operation.

In this phase, settings are made and tested for master data, organizational units,and business processes placed into scope in the Business Blueprint phase.


• Use Solution Manger to configure the system based upon the BlueprintRequirements.

• Plan and prepare testing• Understand the concept of Business Configuration (BC) Sets

Business ExampleYour project team has completed the Blueprint Phase of the project and a completeand signed-off Business Blueprint is available to all teams to guide the processof customizing (configuration) the system. You will use Solution Manager toaccomplish this.


SMI310 Lesson: Configuration and Development

Introducing the Realization Concept

Figure 83: Activities and Functions by Phase – Realization

You can launch configuration activities via the Implementation and Upgradeworkcenter subview “Plan”.

The objective of the Realization Phase is to implement business processrequirements based on the Business Blueprint. Activities are focused onconfiguring the solution and testing the implemented solution.



Figure 84: Realization Phase Work Center

Prerequisites:

• The Business Blueprint has been created and approved.• The development system is available.

The Business Process Configuration transaction SOLAR02 bases on the BusinessBlueprint (SOLAR01).

It differs from SOLAR01 in the following:

• The Blueprint structure that has been defined in SOLAR01 under the tabStructure cannot be changed any more.

• Per default, SOLAR02 offers new tabs like Configuration, Development,Test Cases and Training Materials. Nevertheless, these tabs canalready be switched on for the Business Blueprint Phase if needed(SOLAR_PROJECT_ADMIN, Project Standards tab).

• Data that has been registered in the Blueprint tabs (General Documentation,Project Documentation, Administration, Transactions, Issues/Messages,Graphic, End User Roles) can be enhanced with further configurationinformation.

Note: Status values maintained tab Administration differ if they aremaintained in the Business Blueprint (SOLAR01) or in the Configuration(SOLAR02) phase.



In order to assign and perform configuration and development objects and toassign test cases you go to the Implementation and Upgrade Workcenter, select thesubview “Build” and click on “Got to Business Process Configuration”. Anotheroption is to open directly your project with the transaction code SOLAR02.

Figure 85: Working in the Realization Phase

Performing Business Process ConfigurationYou can access the various Customizing tools using the SOLAR02 transaction. Itis the central point of access to configure system settings for the implementationproject. You create and assign configuration of different object types that help youto configure your business processes, e.g., Business Configuration Sets (BC-Sets),Implementation Guide objects (IMG objects), extended Computer Aided Test Tool(eCATT) and Add-on transport requests.



Figure 86: Tracking Customizing on the Configuration Tab

Use of Business Process Configuration During Realization:

• You can create new BC Sets, assign them to a structure, view the content ofassigned BC Sets, and delete the assignments of BC Sets that are no longerrequired from the project in application systems.

• You can activate one or more assigned BC Sets.• You can view the settings configured by BC Sets in the Implementation

Guide and edit the system settings that could not be configured by BC Sets.• You can assign CATTs and eCATTs to process steps and call them to

configure system settings or store pre-configuration.• You can store documentation for individual configuration steps. You can

assign existing documentation and create new documentation.

A configuration document is used to describe configuration processes thatdo not take place in the SAP world or non-ABAP customizing. It does notcontain any descriptions of IMG settings.

• You can also import Customizing contained in Add-On transports to yoursystem.

• You can specify the processing status and the person responsible for eachobject you assigned.

Note: All entries with a logical component are maintained in the managedsystem. The entries in SAP Solution Manager are only links to theseobjects in managed systems. Exception: As for eCATTs and manual testcases, this data can be stored centrally in SAP Solution Manager.



Figure 87: Performing configuration using IMG

You can specify the processing status and the person responsible for each objectassigned.

Note:

• Documentation of customizing can take place at the IMG level orthrough project documentation on process/process step level

• There is no automated replication of IMG status and responsiblefrom the Project IMG in the managed system and the Configurationtab in SAP Solution Manager.

Performing Technical ConfigurationBusiness Process Configuration with relation to a structure item (Scenario,Business Process, Process Step) is done in the blueprint structure. Configurationsettings that are valid for various structure items can be maintained in theconfiguration folder which is placed on the top left side of the business processstructure. These settings are often basic system settings that have to be done inthe systems before you can start to define the configuration for your scenarios andbusiness processes. An example includes setting up connectivity between an SAPCRM and an SAP ERP system. Moreover, you document settings in this overallconfiguration folder that cannot be assigned to a structure object (i.e. authorizationinformation).

To sum it up, these settings can be seen as a prerequisite to business processconfiguration.



Figure 88: Technical Configuration

Note: The number of levels in the technical configuration folder is notrestricted.

Configuration structures are deliverd by SAP together with SAP pre-definedreference scenarios and processes (BPR content or templates). In SOLAR02, thereis also the ability to restrict the configuration structure scope to your businessscenarios and industries. When doing so, there is a useful filter to help you duringthe process.



Figure 89: Scenario and Industry-Specific Filters for selecting configurationstructures

When making changes to the configuration, the Scenario-specific filter for theBusiness Process Repository allows one to see only those configuration structureelements which are part of the scenario configured for the selected project. Atthe same time, the Industry-specific filter allows one to choose which elementsto display based on selected industries

To use configuration structures and embedded filter functionality,, go to transactionSOLAR02:

• In the Configuration Structure window, select the Configuration structureelement of the project

• On the right side of the screen, select the Structure tab and click on theChange Configuration Structure button

• Confirm that the Source field is set to Business Process Repository• Select the Configuration Element field and press the F4 key

The resulting window is the Business Process Repository Selection Help. At thebottom of this window are the filter buttons. One for Scenarios, one for Industries.If it displays Scenarios: Active then the filter is active and only those elementsrelated to the Scenario configured for the Project will be shown. Clicking on the



button will toggle the filter to Inactive and all elements of the Scenario will bevisible. The Industries filter works the same way as the scenario filter, except that,when activating the filter, the industries to use for the filter must be selected.

Note: In the Change Configuration Structure you edit the structure of theconfiguration folder. The assignment of configuration objects is donedirectly in SOLAR02.

Working with Business Configuration (BC) Sets

Figure 90: Definition of a BC Set

A BC Set is a collection of customizing settings:

• Grouped according to logical, business management criteria of a unit• For documentation, quality assurance and reuse purposes• Independent of the original Customizing tables/views• Accessible across the system landscape

The idea is to capture customizing for reuse at different systems, to documentthe customizing at a certain state of time, e.g. for FDA (U.S. Food and DrugAdministration) purposes.



Figure 91: Advantages of BC Sets

Figure 92: Realization: Creating and Assigning Customizing Objects

Figure 93: BC Set Types



Figure 94: BC Set Transactions for Editing, Activating and Viewing BC Sets

They can be used for a group rollout, where the customizing settings, for example,are bundled by the group headquarters and passed on in a structured way to itssubsidiaries.

BC Sets are provided by SAP for selected industry sectors, and customers can alsocreate their own. When a BC Set is created, values and combinations of values arecopied from the original Customizing tables into the BC Set and can be copiedinto the tables, views and view clusters in the customer system. The BC Sets arealways transported into the customer system in which Customizing is performed.

The loading of BC Sets is logged by the system, i.e. which BC Set was copiedwhen into the system, and any errors which occurred. This information issignificant for Continuous Change and Upgrade.

Only customizing data can be captured in a BC Set. Master Data, TransactionData and Repository Objects are not valid for BC Sets.



Figure 95: Customizing Setting Attributes in BC Sets

When creating BC Sets the customizing settings may be configured with one ofthe following values:

• Default• Fixed• Variable

Default copies the existing values of the table fields in the source system (in thiscase, Solution Manager) into the BC Set, overwrites the value in the activationsystem without confirmation, once the BC Set is activated, and allows manualchanges.

Fixed copies a set value into the BC Set, which cannot be changed in theactivation system.

Variable allows the attribute value to be set upon activation. All values whichcannot be set at the time the BC Set is created must have this attribute.

There are two primary types of BC Sets:

• Simple BC Set• Hierarchical BC Set

The Simple BC Set is the most common, being built from customizing datacreated in the IMG activities.

A Hierarchical BC Set is a BC Set comprised of other BC Sets. The BC Setsincluded can be Simple BC Sets or other Hierarchical BC Sets. There is no limitto the depth of the nesting when including Hierarchical BC Sets in a HierarchicalBC Set.



A third type of BC Set which is sometimes mentioned is the BC Set from transportrequest. However, this is really only another example of a Simple BC Set where atransport request is used as the customizing template.

To find out more about BC Sets go to http://service.sap.com/rkt-solman and selectSAP BC-Sets E-Learning from the available OKPS session.

Creating a Configuration GuideYou can generate a Configuration Guide out of your project. You can selectwhich parts of the structure and which document types with which status, personresponsible and keywords should be included to the guide. Then the documents aredownloaded to the specified directory. Afterwards you start Microsoft Word andstart the macro SAP_CONFIGURATION_GUIDE, then the guide will be created.

Figure 96: Creating a Configuration Guide

Performing Customer-Specific DevelopmentsSolution Manager supports the implementation of other activities which includeenhancements and customer development.


http://service.sap.com/rkt-solman


Figure 97: Performing customer-specific developments

You can put your own developments and modifications in your implementationproject for central access, in the Development tab. You specify the developmentsand modifications which you have made in your implementation project.

The developers assign all workbench objects, they create for the development inthe development system to the proper structure element at the development tab.Due to restrictions at the development tab not all workbench object types, e.g. database tables/structures, domains, data types etc. can be assigned to. In this casecollect the additional ones in a document at top of the development tab.



In case of end-to-end scenarios, development specification documents exist atseveral places in the business process structure. The document exists only oncein the Knowledge Warehouse and is linked to the different processes for whichthey are relevant.

• For instance, you can assign documents, packages, programs, transactions,function modules, classes and transport requests to the structure elements.

• You can navigate to development objects in the managed systems.• You can assign transport requests to the structure elements in the

Development tab, for example to put the modifications in a transport requestinto your implementation project.

• You can specify the processing status and the person responsible for anassignment.

Example: You have modified a customizing object so that current settingsare possible in your system, and written this change into a transport request.You assign this transport request in the Development tab, to document themodification. If this modification is overwritten by importing a SupportPackage, repeat the modification with the assigned transport request.

Note:

• Transactions cannot be executed on the development tab.• BADI_SA_OBJECT_TYPE_ACTIVATION and

BADI_SA_HIDE_TYPES_ON_TABS allow the extensionor limitation respectively of the entries on the Transactions" ,"Development" and "Configuration" tab. See note 1027579.

Assigning Test CasesIn the Configuration transaction, SOLAR02, you also have the possibilityto assign automated and manual test cases to your process-oriented blueprintstructure. This material is used in later project stages for test management and testexecution. You will find more detailed information in the chapter "Realization -Test Management".

Assigning Training MaterialIn the Configuration transaction, SOLAR02, you also have the possibility to assignlearning material to your process-oriented blueprint structure. This material isused in later project stages as a starting point to create role-specific learning maps.

Reporting for ConfigurationThe reporting capabilities for configuration are analogous to those in the BusinessBlueprint phase. They focus, however, more on administration-related issues andassignments in the configuration phase.



Figure 98: Reporting for Configuration

• Analysis is analogous to the Business Blueprint phase, where you can alsoanalyze configuration objects (such as BC Sets, CATTs, IMG activities),development objects, test cases, and messages/issues with assignments.

• You can also perform cross-system project IMG analyses locally incomponent systems.





Exercise 5: Configuration andDevelopment

Exercise ObjectivesAfter completing this exercise, you will be able to:• From the SAP Solution Manager, access the IMG in the ERP development

system and perform configuration for a selected IMG activity.• Create a BC Set to cluster customizing in a process-specific context.• Usage of the development tab in the realization phase.

Business ExampleOnce the Business Blueprint is signed off, the Realization proceeds withconfiguring the related system landscape and performing development work tomeet the defined business process requirements.

Task 1:Perform the system configuration for the process step Create Order in ERP.





→ Open in the panel the menue entry Build (on the left-hand side)

→ Click on the link Goto Business Process Configuration (on the right-handside)

1. Navigate to <Group Project Description> → Business Scenarios → Sales<##>→ Business Processes → Sales Process <##>→Create Order in ERP.

In the Configuration tab assign the IMG activity below:




User IMG Activity

• SMI310-01• SMI310-11• SMI310-21

Logistics - General → Material Master →Settings for Key Fields → Data Relevant to Salesand Distribution → Define Commission Groups(SIMG_CFMENUOLSDOVFVX)

• SMI310-02• SMI310-12• SMI310-22

Sales and Distribution → Master Data → BusinessPartners → Contact Person → Define Authority(SIMG_CFMENUOLSDOVSR)

• SMI310-03• SMI310-13• SMI310-23

Sales and Distribution → Basic Functions →Pricing → Pricing Control → Define And AssignPricing Procedures (SIMG_CFMENUOLSDFP4)

• SMI310-04• SMI310-14• SMI310-24

Sales and Distribution → Master Data → BusinessPartners → Customers → Sales → DefineCustomer Groups (SIMG_CFMENUOLSDOVS9)

• SMI310-05• SMI310-15• SMI310-25

Logistics General → Material Master →Settings for Key Fields → Data relevant to Salesand Distribution → Define Material Groups(SIMG_CFMENUOLSDMATGR)

• SMI310-06• SMI310-16• SMI310-26

Logistics Execution → Shipping → Deliveries→ Define Reasons for Blocking in Shipping(SIMG_CFMENUOLSDOVLS)

• SMI310-07• SMI310-17• SMI310-27

Logistics Execution → Shipping → Basic ShippingFunctions → Partners → Master Data → DefineDelivery Priorities (SIMG_CFMENUOLSDOVSD)




• SMI310-08• SMI310-18• SMI310-28

Sales and Distribution→ Sales → SalesDocuments → Define And Assign Status Profile(SIMG_CFMENUOLSDBS02)

• SMI310-09• SMI310-19• SMI310-29

Enterprise Structure → Definition → Salesand Distribution → Define copy, delete, checkdistribution channel → Define distribution channel(SIMG_CFMENUSAPCOVXI)

• SMI310-00• SMI310-10• SMI310-20

Enterprise Structure → Definition → Logistics -General → Define, copy, delete, check division(SIMG_CFMENUSAPCOVXB)

Caution: Users working on the same activity may lock each othertemporarily since only one user can make changes to an object.

Task 2:Leverage Business Configuration (BC) Set technology to cluster and standardizecustomizing for process steps Create Order in ERP to be re-used in otherdevelopment systems.

1. Under the configuration tab assign the existing BC Set ZSMI to process stepCreate Order in ERP .

2. Display the content of the BC-Set and navigate to the assigned IMG activityDefine Order Reasons.

3. Create a new BC Set for process step Create Order in ERP.

Choose the create option IMG hierarchy and enter the following:

Field Name Values

BC Set ZBC_##

Short Description BC Set ##

Software Component SAP_APPL

4. Include the customizing entry that you created for the IMG activity in task1 in the BC Set




Task 3:A preselection screen for the process step Create Order in CRM has beendeveloped. Document this development object on the development tab.

1. Create a document on the development tab for this own development. Writesome sample text in the document.

Field Name Values

Title Preselection Screen Order Creation

Documentation Type Program Development Form

2. Assign the program Z_PRESELECTION_ORDER_CREATION from theCRM system to the same tab.



Solution 5: Configuration andDevelopmentTask 1:Perform the system configuration for the process step Create Order in ERP.





→ Open in the panel the menue entry Build (on the left-hand side)


1. Navigate to <Group Project Description> → Business Scenarios → Sales<##>→ Business Processes → Sales Process <##>→Create Order in ERP.

In the Configuration tab assign the IMG activity below:

User IMG Activity

• SMI310-01• SMI310-11• SMI310-21

Logistics - General → Material Master →Settings for Key Fields → Data Relevant to Salesand Distribution → Define Commission Groups(SIMG_CFMENUOLSDOVFVX)

• SMI310-02• SMI310-12• SMI310-22

Sales and Distribution → Master Data → BusinessPartners → Contact Person → Define Authority(SIMG_CFMENUOLSDOVSR)

• SMI310-03• SMI310-13• SMI310-23

Sales and Distribution → Basic Functions →Pricing → Pricing Control → Define And AssignPricing Procedures (SIMG_CFMENUOLSDFP4)

• SMI310-04• SMI310-14• SMI310-24

Sales and Distribution → Master Data → BusinessPartners → Customers → Sales → DefineCustomer Groups (SIMG_CFMENUOLSDOVS9)




• SMI310-05• SMI310-15• SMI310-25

Logistics General → Material Master →Settings for Key Fields → Data relevant to Salesand Distribution → Define Material Groups(SIMG_CFMENUOLSDMATGR)

• SMI310-06• SMI310-16• SMI310-26

Logistics Execution → Shipping → Deliveries→ Define Reasons for Blocking in Shipping(SIMG_CFMENUOLSDOVLS)

• SMI310-07• SMI310-17• SMI310-27

Logistics Execution → Shipping → Basic ShippingFunctions → Partners → Master Data → DefineDelivery Priorities (SIMG_CFMENUOLSDOVSD)

• SMI310-08• SMI310-18• SMI310-28

Sales and Distribution→ Sales → SalesDocuments → Define And Assign Status Profile(SIMG_CFMENUOLSDBS02)

• SMI310-09• SMI310-19• SMI310-29

Enterprise Structure → Definition → Salesand Distribution → Define copy, delete, checkdistribution channel → Define distribution channel(SIMG_CFMENUSAPCOVXI)

• SMI310-00• SMI310-10• SMI310-20

Enterprise Structure → Definition → Logistics -General → Define, copy, delete, check division(SIMG_CFMENUSAPCOVXB)

Caution: Users working on the same activity may lock each othertemporarily since only one user can make changes to an object.

a) Open the Configuration for process step Create Order in ERP

b) In column Type choose entry IMG object.

c) In column Logical Component choose Z_SMI310_ERP.

d) In column Object, use possible entry help (F4) and launch IMG.

e) Go to the IMG activity in the table.

f) Select/Mark IMG activity (see table above).




g) Choose Select/Deselect button to select the IMG activity and continue(Transfer selected nodes button). The IMG activity will be assigned toprocess step Create Order in ERP in the Configuration tab.

h) Save.

Task 2:Leverage Business Configuration (BC) Set technology to cluster and standardizecustomizing for process steps Create Order in ERP to be re-used in otherdevelopment systems.

1. Under the configuration tab assign the existing BC Set ZSMI to process stepCreate Order in ERP .

a) Navigate to<Group Project Description> → Training Project →Business Scenarios → Sales <##> → Business Processes → SalesProcess <##> → Create Order in ERP.

b) Choose the Configuration tab.

c) Choose type BC Set and use possible entry help (F4) in column Object.

d) In search screen, enter Z* in field BC Set and continue (Start searchbutton).

e) Select BC Set ZSMI in the list, assign via Copy button and Save.

f) Select the row with the BC Set.

g) Choose Display button to view BC Set content.

2. Display the content of the BC-Set and navigate to the assigned IMG activityDefine Order Reasons.

a) In the Business Configuration Set - Display screen, double-click on theIMG activity with the name Define Order Reasons

3. Create a new BC Set for process step Create Order in ERP.

Choose the create option IMG hierarchy and enter the following:




Field Name Values

BC Set ZBC_##

Short Description BC Set ##

Software Component SAP_APPL

a) Go back to the Configuration tab of your project.

b) Select an empty row and choose type BC Set.

c) Select the new row and choose the Create button.

d) Enter the data from the table and Continue.

4. Include the customizing entry that you created for the IMG activity in task1 in the BC Set

a) Navigate to the IMG activity as used in Task 1.

b) Choose the Execute button to load the customizing data in the rightscreen.

c) Double-click on an entry in the Data Records table, column Table/View.

d) Mark several rows/values in the Data Records table and Save as localobject ($tmp).

e) Go back to the overview screen with the Back button (F3).

f) Save.

Task 3:A preselection screen for the process step Create Order in CRM has beendeveloped. Document this development object on the development tab.

1. Create a document on the development tab for this own development. Writesome sample text in the document.




Field Name Values

Title Preselection Screen Order Creation

Documentation Type Program Development Form

a) In the Configuration transaction (SOLAR02), go to the process stepCreate Order in CRM.

b) Select the tab Development.

c) Create a document (object type: Document) with the data from thetable above.

d) Fill in a description of the selection screen.

e) Save and close the document.

2. Assign the program Z_PRESELECTION_ORDER_CREATION from theCRM system to the same tab.

a) In the Configuration transaction (SOLAR02), go to the process stepCreate Order in CRM.

b) Select the tab Development.

c) Select as type Program. The logical component will be selectedautomatically. It should be Z_SMI310_CRM.

d) In the column Object choose for the program Z_PRESELECTION_OR-DER_CREATION and execute your selection.

e) Save your settings.



Lesson Summary

You should now be able to:• Use Solution Manger to configure the system based upon the Blueprint

Requirements.• Plan and prepare testing• Understand the concept of Business Configuration (BC) Sets


SMI310 Lesson: Testing

Lesson: Testing

Lesson OverviewTest Management with SAP Solution Manager


• Conduct basic testing with SAP Solution Manager.

Business ExampleThe configuration and development objects have been created in an implementationproject. Before deploying them on the productive systems they have to be tested.



Testing Overview

Figure 99: End-to-End testing strategy

• Test Option 1

– Almost all of the functions and tools are provided by SAP SolutionManager without further Licenses needed, except SAP Test DataMigration Server (SAP TDMS) and 3rd party test automation tools

• Test Option 2

– For customers who have already Hewlett Packard (HP) testmanagement products in use

– Usage of SAP Test Acceleration and Optimization (SAP TAO) possible



Figure 100: End-to-End testing strategy - 2 options

From the many tools available for testing SAP-centric business processes, twooptions have emerged. In option 1, almost all the test tools are provided by SAPSolution Manager, while option 2 relies on a combination of SAP SolutionManager, SAP Quality Center by HP, SAP TDMS and SAP TAO. Both of theseoptions support the entire testing process.

Figure 101: Business process-oriented testing



Figure 102: Test Management Workcenter

Note: There are two ways to perform testing with Workcenters. Youwill see that there is a dedicated work center for test management andthe possibility to perform testing with the Implementation and UpgradeWorkcenter. Which workcenter you will use, depends on your role inyour implementation project.

You organize tests after

• you create a Business Blueprint Structure• and perform initial configurations, such as assignment of test objects in the

Realization phase (e.g. SAP transactions on tab “Transactions”).

The first task of test organization is to create a test plan. In the Business Blueprintphase, you created a project structure containing business scenarios, processes,and process tasks. You then assigned transactions and test cases to process tasks.When you create a test plan, the system offers this project structure as the basis fortest plans. The system also provides all manual and automated test cases that youassigned to processes or process tasks. You can select these cases for the test plan.



Testing Procedure

• Creating and assigning test cases to process elements in transactionConfiguration (SOLAR02 or via Test Management Work Center -> TestPreparation -> Goto -> Configuration)

– Systematic storage of test cases to test business processes– Administration of manual and automated tests

• Test Organization/Test Plan Management (STWB_2 or via Test ManagementWork Center -> Test Plan Management)

– Generation of project-specific test plans and test packages according tothe test goal (e.g. module test plan or integration test plan)

Note: Provides filtering of Test Case Type by Test Case Type,Search Terms and Priority as well as structure filtering byassigned Status, Project Team Member and Keyword.

Generation of project-specific test plans and test packagesaccording to test goal (e.g. module test plan or integration test)

– Assignment of testers to test packages– Optional: (available with SAP Solution Manager Enterprise Edition):– Test case assignment on tester level– Test sequence definition– Notification workflows

• Test execution (STWB_WORK or via the Test Management Work Center ->Tester Worklist)

– Accessing tester-specific work list– Reading test cases and executing tests in satellite systems– Tracking results in individual tester notes and creating Service Desk

messages, if required– Maintaining the status of test cases in Solution Manager

• Test monitoring & reporting (STWB_2, STWB_INFO or via TestManagement Work Center -> Test Evaluation)

– Detailed views of test progress and test results– Graphics and reports for all test plans in a project– Monitoring of error messages

• Handling problem messages (with SAP Service Desk)

– Maintaining error messages during testing– Detailed analysis and prioritization of problems



The Test Workbench feature is reused in the Solution Manager Test Organization.For more information about the Test Workbench, refer to the documentation onthe Test Workbench in the SAP Help Portal.

Test PreparationThe Business Blueprint Structure and configuration is the starting point for the testpreparation. Based on the defined business process structure the test cases can beassigned (SOLAR02, tab “Test Cases”).

Figure 103: Assigning Test Cases

You can assign various types of test cases on this tab (e.g. manual test cases andautomated eCATT test configurations). When using the test type 'TWTD', alltest case descriptions are stored in the integrated Knowledge Warehouse whatprovides advanced test case functionality:

• Creation of test cases (specific template can be assigned)• Link to existing SAP Solution Manager document / test case• Upload of a file• Definition of a web link• Check-out / Check-in of documents• Usage of document status schemes, e.g. for approval procedures• Usage of digital signature to sign documents

Moreover, it is possible to run automated test configurations from the test cases tab.



Figure 104: eCATT for automated testing

The basic concept of eCATT is to separate the application flow (eCATT script),Test Data (Test Data Container and Test Data Variants) and information aboutsystem to be tested (System Data Container). This allows to reuse the samescript for several test activities with different data on different systems. Thecombination of the script, data variants and system data is stored in the eCATTTest Configuration.

The usage of test case attributes for better traceability and to prepare massprocessing is recommended:

• Priority• Status• Keywords• Responsible Person• Link: Connect test case to business process description/requirement



Strengths of test automation using eCATT:

• Testing of complex business process scenarios like Order-to-Cash andProcure-to-Pay

• Advanced functionality to test backend business logic (function modules,eSOA services, test result verification at SAP table / database level, resultcomparison with previous runs, …)

• Central definition via SAP Test Workbench combined with execution indistributed systems

• Central repository for test data

Test PlanningThe test cases assigned here can be used as the default test organization valueswhen you create test plans:

Figure 105: Test Case Repository and Test Plan Generation

In order to provide a test phase related test scope it is possible to create test plans.All test cases that are defined in the central repository can be reused for differenttest phases. Thus test plans are used to collect test cases to be processed during aspecific test phase with a specific scope.

The following test plan attributes must be defined:

• Test plan title• Select relevant SAP Solution Manager project• Select correct system role for testing



During test plan generation the following test plan attributes can be assigned:

• Test Set: grouping criteria for test reporting• Release status profile: Status scheme for test plans• Test note: documentation type for test notes• Test status weighting profile: to assign weighting factors for different test

case status• Test plan consistency profile: to filter test cases

The test case attributes (e.g. priority, key words, etc.) can be used to set a filterfor test plan definition.

Figure 106: Options to generate test plans



The following test plan functionality can be used:

• Copy test plans

Note: With the option to include test packages, test sequences andassigned testers and related messages. Test Status and Test Noteswill be initialized in new Test Plan.

• Change/modify test plans

Note: Delete test cases form test plans causes deletion of test casestatus for test case to be deleted.

• Delete test plans

Note: Test status values will be also deleted

• Search test plan structure for update test case versions• Assign updated version of test cases to test plan

Note: Status values for previous version will not be transferred

After test plan creation user-specific test packages must be defined. Test cases arecollected for the tester in test packages. A test package is based on a test plan. Testcases are chosen from the test plan for the test package. The new test package isdisplayed in the test plan hierarchy. A test package is usually assigned to a tester.The assigned and released test packages is in the form of a work list. You can lockor delete a test package for a tester. Test package assignment is client-specific.

Release Status Schema

In order to control the test process properly and more transparency it is possible touse a release status scheme on test plan level:

• better control and managing options in test plan management• automated email notifications (test plan released, test plan locked, ...) over

workflow automatically• usage of digital signature for test plan sign-off is possible



Figure 107: Release Status Schema

Figure 108: Creating Test Package and assign Test Package to Tester



The following functionality for test packages can be used:

• Copy test packages• Change/Modify test packages

Note: Deletion of test cases from test packages causes deletion oftest case status

• Delete test packages

Note: Test status values will be deleted as well.

• Start/Stop worklist for testers• Multiple assignments of packages to testers are possible (and vice versa)

Test Sequences

Figure 109: Test sequences and workflow support

New approach allows

• to define cross area, process oriented end-to-end integration test scenarioswhere testers with different skills will test in the right sequence which meansless coordination effort during test phase and reliable results

• automated email notifications (e.g. test plan released, test case can beexecuted, test phase has finished, …) over workflow functionality

Test planning (STWB_2 or via Test Management Work Center -> Test PlanManagement)



The access to test sequence functionality can be carried out within test planmanagement functionality of SAP Solution Manager (STWB_2 or via TestManagement Work Center -> Test Plan Management) in test package section:

Figure 110: Test Sequence functionality

Figure 111: Test execution with sequences

An example for the test workflow with test sequences: tester 1 executes a test casein his worklist and sets the status to “OK”. This status triggers an automatede-mail notification to tester 2 who can now execute his test case.



Test ExecutionA tester calls the tester worklist and obtains an overview of the assigned test cases.

Figure 112: Perform Testing

Testers can access their testing work list using the transaction STWB_WORK orvia the Test Management Work Center -> Tester Worklist)

Testers can:

• Display/Print test case description• Perform test in test system• Set processing/test status• Create Tester notes to provide details on result• Create error messages (with SAP Service Desk functionality) when a test

cannot be executed successfully.



Figure 113: Test Note providing details on result

Defect Handling

The SAP Service Desk functionality can be used for the administration of errormessages resulting in a test scenario:

• Integration of Test Management and Incident Management allows to use thesame support process that has been already established for other support areas

• Allows to report on test related messages with test workbench• Enhanced traceability regarding test errors and easy follow-up

The process starts directly with the creation of an error message from the tester'swork list. Test case attributes will be automatically handed over to the messagelong text section. After the creation of the message, the message number isautomatically assigned to the tester's work list.



Figure 114: Support Message creation

A test manager can monitor all test related support messages using

• the message overview functionality within the status information system(STWB_INFO or via Test Management Work Center -> Test Evaluation);overall messages, messages per specific test plan

• the Incident Management Work Center

Test ReportingThere are two possibilities for reporting on test results and progress:

• Using the status info systems and / or• Using Business Intelligence (BI) reporting

The status information system provides detailed information about the testprogress. It is a real time snapshot of current test status and related messages. Youget a context related view, e.g. you navigate either within a test plan or a testa test package. BI offers you in addition visualized reports on test status, testprogress and related messages. It offers sophisticated , flexible filter and drilldownnavigation. You can get aggregated and detailed views down to test cases.



Figure 115: Status info system

The status info system provides the following functionality:

• Analysis of single and multiple test plans• Status overview per test packages• Status analysis on test plan level• Error message overview• Grouping of test plans using test set functionality• General list functions to further analyze the list (pass data to spreadsheet

program or export the data to a text processing program)

The status of a test plan is usually the result of a particular test. Test planindependent status analyses combine the results of several test plans and can beconsidered as the overall result of a complex test that comprises several testplans. You obtain an up-to-date status analysis of all the test packages in theselected test plan.



Figure 116: BI Reporting

Benefit of BI reporting: It provides efficient and flexible way to a visualize dayto day test status and progress as well as messages.

Note: BI offers visualized reports on test status, test progress andrelated messages, sophisticated, flexible filter and drill-down navigation(aggregated and detailed view down to test cases), daily data extraction(delayed view) and additional reports like progress reports. The statusinfo system offers a real time snapshot of the current test status and relatedmessages and only a context related view, e.g., navigation either withina test plan or test package.

Figure 117: BI Reporting - Motivation



Figure 118: BI Reporting - Target Group and Use Cases

Figure 119: Test Report

The test report functionality can be used when test plan has finished. It uses apredefined Microsoft Word Template. The information can be defined individuallyby predefined selection criteria.

You generate a test report to document the status of the test plans or test packagesat a specified time. For example, the test coordinator can generate a test report fora test plan, at the beginning and end of a test phase, to document the test progress.If you protect the test plan against changes, you can use the test report for yourinternal quality assurance, or for audits.



Summary Test Management Benefits• Coverage of complete test process

– From change events and change impact analysis– via test planning and test execution– to deployment of changes in production system

• Central access to all test capabilities

– SAP Solution Manager acts as central point of access to SAP and 3rdparty test capabilities

– ... as well as additional capabilities like E2E integration validation anddefect management

• Risk-based Test Planning

– Identification of business processes affected by SAP solution changes• Provide choices to SAP customers

– Customers can use SAP capabilities and 3rd party test suites incombination

– All required interfaces will be provided over time

Feature List Test Management

Figure 120: Feature List Test Management

• SAP Solution Manager Adapter for SAP Quality Center

– The SAP Solution Manager adapter for SAP Quality Center by HPsupports role-specific testing, and covers the complete testing processfrom requirements gathering to test case definitions and reporting. Theadapter allows you to transfer information about business requirementsand Test Objects seamlessly to Quality Center, which is the maintesting environment for the customer’s quality teams. After testcompletion, the test results are transferred out of SAP Quality Centerby HP, directly into SAP Solution Manager, automatically displayingthe results of the test of the business requirements transferred. This willhelp project leads to see their business processes and trace them frombusiness requirements to test results, and allow customers to re-usethis information during later application management phases, such asupgrades or continuous business improvement projects.



– For more information on this price list product, refer to:http://service.sap.com/solutionmanager -> SAP Solution ManagerAdapter for SAP Quality Center

• SAP Test Data Migration Server (TDMS)

– SAP Test Data Migration Server (TDMS) helps you to create small,easy-to-maintain non-production environments, with consistent,relevant extracts of business data for testing. It helps you to set-up leantest systems, selectively refresh clients in the test systems, and extractdata by business objects, organizational units and time slices. You canalso scramble sensitive data.

– For more information on this product, refer to: http://ser-vice.sap.com/tdms http://service.sap.com/alm -> Process: TestManagement

• SAP Test Acceleration and Optimization (TAO)

– SAP Test Acceleration and Optimization (SAP TAO) is an SAPtesting tool that accelerates the creation and update of automatic (SAPGUI-based) test case components for business processes, lowering yourtest and maintenance efforts. In combination with SAP Quality Centerby HP and Quick Test Professional, the customer can inspect selectedtransactions and create test cases based on test components, which canbe executed to test business processes in SAP systems. As soon thereare plans to change running SAP systems, there is the risk that someof the test cases might not run anymore. To find out which test casesmight be affected, the Business Process Change analyzer can identifyrelated Transactions, which could then be re-examined with SAP TAO.The re- examination allows you to update the test components, so therelated test cases are repaired automatically.

– For more information on this price list product, refer to:http://service.sap.com/saptao





Exercise 6: Testing

Exercise ObjectivesAfter completing this exercise, you will be able to:• Prepare for testing by creating test cases• Prepare and organize integration test by creating test plans, test packages and

assigning responsible testers.• Perform tests in your assigned test package using the prepared test cases;

track the status and document the test results.• Monitor testing progress

Business ExampleUpon completion, a rigorous testing process must be organized, executed anddocumented.

Task 1:Creation of Test Cases:





→ Open in the panel the menue entry Test (on the left-hand side)

→ Click on the link Create Test Cases (on the right-hand side)

1. In the Test Cases tab, create a new test document “ZTC_##_Create_Or-der_in_CRM” to process step Create Order in CRM with the status “InProcessing”. Fill in sample data for the test case description for the createdtest case.

Assign transaction CRMD_ORDER in the column Test Object.

2. In the Test Cases tab, create a test document “ZTC_##_Create_Or-der_in_ERP” to process step Create Order in ERP with the status “CopyEditing”. Fill in sample data for the test case description for the createdtest case

Assign transaction VA01 in the column Test Object.

3. In the Test Cases tab, assign the existing eCATT ZDISPLAYORDER to CRMprocess step Process Order. Do not assign a Logical Component.




Task 2:Prepare for Integration Testing:






→ Click on the link Create Test Plan and Test Packages (on the right-hand side)

1. Create for your project SOLT200_## a test plan that includes the businessprocess Sales Process <##> as scope for your integration test I1. Considerthe following data / naming conventions while creating the integration test:

Field Name or Data Type Values

Template Project SOLT200_<##>

Title I1 Test_SalesProcess_<##>

Test Set I1 (Integration Test 1)

Person Responsible SMI310-##

Only Released Test Documents <deselect>

With Transactions <select>

2. Assign the attributes scheme DEFAULTS to your new created test plan.

3. Build a test package (for your generated testplan I1 Test_SalesProcess_<##>)that reflects the area of responsibility of a typical end-user Sales Clerk.Consider the following data / naming conventions while creating the testpackage:


Process Steps• Create Order in CRM• Process Order• Create Order in ERP

Title TestPack_SalesClerk_<##>

4. Assign the responsible testers to test package TestPack_SalesClerk_<##>using the following values:




User

SMI310-##

SMI310-00

5. Assign the testers to the test cases as part of a test sequence:

Process Step Test Case Tester

“Description”:ZTC_##_Create_Order_in_CRM,Create Order in CRM

SMI310-##

“Description”:ZDISPLAYORDER,Process Order

SMI310-##

“Description”:ZTC_##_Create_Order_in_ERP,Create Order in ERP

SMI310-00

6. Create a test sequence by defining the sequence ID 01 and the sequencenumbers 1–3.

Description SequenceID No.Sequence

ZTC_##_Create_Order_in_CRM 01 1

ZDISPLAYORDER 01 2

ZTC_##_Create_Order_in_ERP 01 3

7. Release your complete test plan I1 Test_SalesProcess_##.

Task 3:Perform tests related to your integration test set I1.





→ Open in the panel the menu entry Test (on the left-hand side)

→ Click on the link Access Test Work List (on the right-hand side)

1. Launch test package TestPack_SalesClerk_<##>.




2. Read the test case description available for the test caseZTC_01_Create_order_in_CRM.

3. Run the related transaction to simulate the testing for CRM_ORDER.

4. Track status of the last test case and set it to Errors. Retest Required.

5. Document the test results in a Test Note.

Document Data Values

Title ZTC_##_Create_Order_in_CRM

Documentation Type Test Note for Test Case


Radio Button Create new document

6. Create a message for the test case.

Data Type Value

Priority 3 (Medium)


Component CRM-BE-BD


Short text Order problem ##

Long text Process failure

7. Assume that the test case ZTC_Create_Order_in_CRM ended successfully.Set status of the first test case to OK, save, and return to the tester worklist.

8. Now start to test the test case ZDISPLAYORDER automatically.

Read the log of the eCATT. Afterwards return to the test workbench andcheck the status result.

9. Try to test the last test case ZTC_Create_Order_in_ERP.




Task 4:Monitor test progress via Status Information System:




→ Open the tab for Test Management (on the right-hand side)

→ Open in the panel the menue entry Test Evaluation (on the left-hand side)

1. Show the status for your test plan I1Test_SalesProcess_<##>.

2. Create a test report for your integration test I1. Follow the steps in the popup(To create the test report, run the macro "SAP_CREATE_TESTREPORT").

3. List all testing related messages for the test plan I1Test-SalesProcess_<##>

4. Visualize graphically the status of all test plans using bars as the chart type.

5. For the test plan I1Test_SalesProcess_<##>, display all test cases with statusTest_Error..



Solution 6: TestingTask 1:Creation of Test Cases:






→ Click on the link Create Test Cases (on the right-hand side)

1. In the Test Cases tab, create a new test document “ZTC_##_Create_Or-der_in_CRM” to process step Create Order in CRM with the status “InProcessing”. Fill in sample data for the test case description for the createdtest case.




Assign transaction CRMD_ORDER in the column Test Object.

a) Navigate to <Group Project Description> → Business Scenarios →Sales <##> → Business Processes → Sales Process <##> → CreateOrder in CRM (on the left-hand side).

b) Go to the Test Cases tab (on the right-hand side).

c) Choose the small icon at the end of a empty column Test Case Typeto get the dropdown list. Select

Test Case Type Test Document

d) Enter the following data in the next popup:


Title ZTC_##_Create_Or-der_in_CRM

Documentation Type [TD1] Test CaseDescription



e) Confirm the settings with OK (Enter).

f) Fill in a proper Description for this test case.

g) Leave the text editor with Save Document. Then Close the documentand confirm the popup with YES.

h) On the Test Cases tab, go to the column Test Object.

i) Enter transaction CRMD_ORDER followed by enter.

Hint: Only transactions can be assigned which are inserted inthe Transaction tab first.

j) Save your settings (Ctrl-S).

2. In the Test Cases tab, create a test document “ZTC_##_Create_Or-der_in_ERP” to process step Create Order in ERP with the status “CopyEditing”. Fill in sample data for the test case description for the createdtest case




Assign transaction VA01 in the column Test Object.

a) Navigate to<Group Project Description> → Business Scenarios →Sales <##> → Business Processes → Sales Process <##> → CreateOrder in ERP.

b) Choose the Test Cases tab.

c) Choose the small icon at the end of a empty column Test Case Typeto get the dropdown list. Select

Test Case Type Test Document

d) Enter the following data in the next popup:


Title ZTC_##_Create_Or-der_in_ERP

Documentation Type [TD1] Test CaseDescription

Status Copy Editing


e) Confirm the settings with OK (Enter).

f) Fill in a proper description for this test case.

g) Leave the text editor with Save. Then Close the document and confirmthe popup.

h) On the Test Cases tab, go to the column Test Object.

i) Enter transaction VA01.

j) Save your settings (Ctrl-S).

3. In the Test Cases tab, assign the existing eCATT ZDISPLAYORDER to CRMprocess step Process Order. Do not assign a Logical Component.

a) Navigate to<Group Project Description> → Business Scenarios →Sales <##> → Business Processes → Sales Process <##> → ProcessOrder.

b) Choose the Test Cases tab.

c) In column Test Case Type, choose eCATT Test Configuration.

d) In the column Test Case, assign the Test ConfigurationZDISPLAYORDER and execute your selection (Enter).




Task 2:Prepare for Integration Testing:






→ Click on the link Create Test Plan and Test Packages (on the right-hand side)

1. Create for your project SOLT200_## a test plan that includes the businessprocess Sales Process <##> as scope for your integration test I1. Considerthe following data / naming conventions while creating the integration test:


Template Project SOLT200_<##>

Title I1 Test_SalesProcess_<##>

Test Set I1 (Integration Test 1)

Person Responsible SMI310-##

Only Released Test Documents <deselect>

With Transactions <select>

a) From the Test Plan Management - Test Organizer screen (transactionSTWB_2), choose the button Create (F5) to generate a new Test Plan.

b) Fill in the field with the data from the table above.

c) Use possible entry help (F4) to assign test set I1 (Integration Test 1)and continue.

d) In the Test Plan: - Project SOLT200_## - Create Structure, deselectvia the check-box all the scenarios that only the scenario/process<Group Project Description> → Business Scenarios → Sales <##> →Business Processes → Sales Process <##> will be remain.

e) Choose the Test Plan button (F8) to generate the test plan.

f) Save the new test plan under the Package “Local Object” ($tmp) ->(F7).




2. Assign the attributes scheme DEFAULTS to your new created test plan.

a) In the Test Plan Management environment (transaction STWB_2),select the row of the test plan you have just created.

b) Select the Attributes button (Ctrl+F3).

c) Switch to the Change mode (F6).

d) On the General Data tab, assign under the topic Release in the StatusProfile field the profile Defaults (not Default).

Hint: If the status profile is entered into the field, the initialstatus New (Test in Preperation ) is automatic linked to a testingexecution lock. Testing activities cannot be started until thetest plan is set to Released (You will do so in the course ofthis exercise).

e) Save your settings and return to the Test Plan Management - TestOrganizer environment using Back (F3).

3. Build a test package (for your generated testplan I1 Test_SalesProcess_<##>)that reflects the area of responsibility of a typical end-user Sales Clerk.Consider the following data / naming conventions while creating the testpackage:


Process Steps• Create Order in CRM• Process Order• Create Order in ERP

Title TestPack_SalesClerk_<##>

a) Select created test plan in the list and choose Test Packages button(Ctrl+F4) to open the Test Package Management.

b) Choose the icon Create Test Package to create the related test case.

c) Go to the Sales Process <##> and select via check-box all test casesand related transactions of the process steps listed above.

d) Choose the Generate button (F8), enter title from the last table andContinue (Enter).

e) Save the new test package under “Local Object” ($tmp) -> (F7).

4. Assign the responsible testers to test package TestPack_SalesClerk_<##>using the following values:




User

SMI310-##

SMI310-00

a) Select the test package TestPack_SalesClerk_<##> in the list.

b) With the icon Assign Tester it's not possible to link a user direkt to thistest package. This icon will open a search dialog to generate a Hit List.(use in the field user the search string SMI310* and Continue).

c) Copy the SMI310-00 and SMI310-## user via the hit list to the testpackage.

5. Assign the testers to the test cases as part of a test sequence:

Process Step Test Case Tester

“Description”:ZTC_##_Create_Order_in_CRM,Create Order in CRM

SMI310-##

“Description”:ZDISPLAYORDER,Process Order

SMI310-##

“Description”:ZTC_##_Create_Order_in_ERP,Create Order in ERP

SMI310-00

a) Select the test package TestPack_SalesClerk_<##>.

b) Click on the Button Sequences.

c) Log on with your login data. Confirm the security alert if required.

d) Select the test package TestPack_SalesClerk_<##> with double click(on the left-hand side).

e) Select the button Change (on the right-hand side) .

f) Assign tester SMI310-## to test case description ZTC_##_Create_Or-der_in_CRM.

g) Assign tester SMI310-## to test case description ZDISPLAYORDER.

h) Assign tester SMI310-00 to test case description ZTC_##_Create_Or-der_in_ERP.

i) Save all your entries (on the top of the right-hand side)




6. Create a test sequence by defining the sequence ID 01 and the sequencenumbers 1–3.

Description SequenceID No.Sequence

ZTC_##_Create_Order_in_CRM 01 1

ZDISPLAYORDER 01 2

ZTC_##_Create_Order_in_ERP 01 3

a) Mark all three test cases.

b) Select the Sequence button, context menu Create Sequence.

c) Enter sequence ID 01 and confirm your entry with OK.

The sequence ID and with it the respective sequence numbers areautomatically assigned in order of appearance of the test cases.Alternatively you could manually assign the sequence order.

d) Save all your entries (on the top of the right-hand side)

and close the browser.

7. Release your complete test plan I1 Test_SalesProcess_##.

a) In the Test Plan Management environment (transaction STWB_2),select your test plan.

b) Choose the Attributes button (Ctrl+F3).

c) Switch from display to the change mode.

d) On the General Data tab, change the status from New to Released.

e) Save your settings and leave the transaction (STWB_2). Navigate backto the WorkCenter main entry screen.

Testing activities can now start.




Task 3:Perform tests related to your integration test set I1.





→ Open in the panel the menu entry Test (on the left-hand side)

→ Click on the link Access Test Work List (on the right-hand side)

1. Launch test package TestPack_SalesClerk_<##>.

a) Click in theTest Package column to access the test case.

2. Read the test case description available for the test caseZTC_01_Create_order_in_CRM.

a) Go to the test case ZTC_##_Create_order_in_CRM.

b) In Test Case Description column, open the related test case descriptionvia click on the test document icon.

c) Read the test case description and, after having done that, close thedocument.

3. Run the related transaction to simulate the testing for CRM_ORDER.

a) Go to the test case ZTC_##_Create_order_in_CRM.

b) Choose and click on the text CRMD_ORDER in the column Test Objectto run the related transaction.

Hint: In the background (over a RFC connection into thesattelite system) the transaction will be startet in a separatewindow (new session).

c) Simulate the transaction test and return via Back (F3) and Exit sessionbutton (Shift+F3) to the test package overview




4. Track status of the last test case and set it to Errors. Retest Required.

a) In the row of the test case ZTC_01_Create_order_in_CRM, click onthe traffic light in the column Status to launch the status maintenancescreen.

b) In the Status tab, use possible entry help (F4) to set status to Errors.Retest Required.

c) Save your settings (Ctrl+S).

5. Document the test results in a Test Note.

Document Data Values

Title ZTC_##_Create_Order_in_CRM

Documentation Type Test Note for Test Case


Radio Button Create new document

a) Choose button Create Test Note to describe the results of the test.This button is on the left corner under the line with the text Statusmaintenance.

b) Save your feedback and return via Back button (F3) to the statusmaintenance screen.

6. Create a message for the test case.

Data Type Value

Priority 3 (Medium)


Component CRM-BE-BD


Short text Order problem ##

Long text Process failure

a) In the Messages tab, create a message.

Note: Use the Create Message Button in the RegisterMessages. Do not use the Button Send Message next to theButton Create Test Note.

b) Enter some mandatory sample data (see table above) and save yourmessage.




7. Assume that the test case ZTC_Create_Order_in_CRM ended successfully.Set status of the first test case to OK, save, and return to the tester worklist.

a) In the row of the test case ZTC_01_Create_order_in_CRM, click onthe traffic light in the column Status to launch the status maintenancescreen.

b) In the Status tab, use possible entry help (F4) to set status to OK.

c) Save your settings (Ctrl+S).

8. Now start to test the test case ZDISPLAYORDER automatically.

Read the log of the eCATT. Afterwards return to the test workbench andcheck the status result.

a) In column Run Test Case click on the icon Test Automatically.

b) On the next screen, click on the Execute Button (F8).

c) Confirm the SAP GUI message that a script tries to connect twice withOK.

d) Read the log of the eCATT. Afterwards return to the test workbench.

e) Check the result in the column Status. The status is set automatically.

9. Try to test the last test case ZTC_Create_Order_in_ERP.

a) The test case is locked due to the previously arranged setup of testsequence and tester. It can only be tested by the assigned testerSMI310-00.

Task 4:Monitor test progress via Status Information System:




→ Open the tab for Test Management (on the right-hand side)

→ Open in the panel the menue entry Test Evaluation (on the left-hand side)

1. Show the status for your test plan I1Test_SalesProcess_<##>.

a) Select the Button Status Infosystem (in the center of the window).Choose in the drop down menu the entry For Selected Test Plans.

b) In the field Test Plan Title enter I1Test_SalesProcess_<##> and execute(F8). You know see the test results (errors, not result, OK) for yourdedicated test plan.




2. Create a test report for your integration test I1. Follow the steps in the popup(To create the test report, run the macro "SAP_CREATE_TESTREPORT").

a) Select I1Test-SalesProcess_<##>.

b) Click on the icon Status overview.

c) Generate with the button Test Report a document.

d) Don't change any attribute for the Test Report Display Options.

e) Execute the report.

f) Confirm Download Test Report with Continue.

g) Enable Marcos in Microsoft Word.

• If you use MS Word 2003: Select Tools –> Macro –> Macros andrun macro SAP_CREATE_TESTREPORT.

• If you use MS Word 2007: Select View –> Macros –> ViewMacros and run macro SAP_CREATE_TESTREPORT

h) Reaqd the documents and save it on the frontend.

i) Close and return to the Status Overview - Test Organizer.

3. List all testing related messages for the test plan I1Test-SalesProcess_<##>

a) Select I1Test-SalesProcess_<##>.

b) Launch the Message Overview icon. Here you find the message youcreated during testing the first test case.

c) Close the Message Overview window and return to theStatus InfoSystem (F3).

4. Visualize graphically the status of all test plans using bars as the chart type.

a) Return to the Status Info System screen.

b) Select all test packages, then choose display Graphic button.

c) With an right mouse click on the ALV Grafic you can change the charttype.




5. For the test plan I1Test_SalesProcess_<##>, display all test cases with statusTest_Error..

a) In Status Info System, select the row of the test planI1Test_SalesProcess_<##>.

b) Select Status Analysis View button and switch with Tabular Displaybutton to the table view.

c) Choose Set Filter button (Ctrl+F11) to access the filter menu.

d) If not already available, move value Status from right to left columnwith Add filter criterion button and continue (Transfer button).

e) In the same popup Define Filter Criteria -> Determine Values for FilterCriterias in the 2. step.

f) Choose the status with F4 and execute the search criteria.

g) Or select in the Tabular Display direct in the column Status (rightmouse click on column header) the entry Test_Error (red traffic light,F4) for the search criteria.



Lesson Summary

You should now be able to:• Conduct basic testing with SAP Solution Manager.


SMI310 Unit Summary

Unit SummaryYou should now be able to:• Use Solution Manger to configure the system based upon the Blueprint

Requirements.• Plan and prepare testing• Understand the concept of Business Configuration (BC) Sets• Conduct basic testing with SAP Solution Manager.


Unit Summary SMI310


Unit 7Final Preparation

Unit OverviewThis unit introduces you to the concept of E-Learning Management in SAPSolution Manager.


• Explain the motivation for updating material• explain the concept of e-Learning Management• explain the selected steps/examples of the e-learning management process in

more details

Unit ContentsLesson: E-Learning... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .228


Unit 7: Final Preparation SMI310

Lesson: E-Learning

Lesson OverviewThis lesson introduces you to the concept of E-Learning Management in SAPSolution Manager.


• Explain the motivation for updating material• explain the concept of e-Learning Management• explain the selected steps/examples of the e-learning management process in

more details

Business ExampleAs an application consultant, you have been assigned as the person responsiblefor the training material creation and delivery process. In the configuration phase,training materials have already been developed for end-user training. Your taskis now to assemble the material in a format digestible by the end-users, that is,(role-specific) learning maps. The material assembled can also be used in veryearly project stages to for educate project team members, e.g., by rolling outproject standards, use cases for project documentation etc.

Triggers for Creating and Updating Learning Material

Figure 121: Triggers for Creating and Updating Learning Material

As an alternative to classroom training and training on the job, this session focuseson the creation of learning material with the SAP Solution Manager embeddede-Learning functionality.


SMI310 Lesson: E-Learning

Figure 122: Goals and Functional Scope

E-Learning in SAP Solution Manager

Figure 123: Assigning Learning Material to Training Material



To create E-Learning material in SAP Solution Manager, as a prerequisite forbuilding role-specific learning maps, you proceed as follows:

1. In the Solution Manager Implementation/Upgrade Workcenter (Navigationlevel Build select the link Goto Business Process Configuration.

Alternatively call directly transaction SOLAR02.

2. Select process steps in the Process Structure and add training materials3. Add or change attributes of the training material, such as Title, Owner and

Length of Duration.4. Add relevant jobs or organizational units to the process steps, using the End

User Roles tab

SAP Tutor allows the recording, editing, playback and reporting of interactivesimulations in the SAP environment. Simulations can be created (such as forcreating a sales order) and then edited to include other information, such as textand hyperlinks.

• SAP Tutor Recorder allows the recording of any Windows application.During the recording automatically default text is added.

• SAP Tutor Editor enables the user to create, import, remove or modify therecorded session.

• SAP Tutor Player runs the tutorial.• SAP Tutor Reporter allows reporting and determines, i.e. who has completed

particular training activities.

The tool comes free with Solution Manager with a 5-user license for authoring.Additional licences cannot be purchased. SAP Tutor development has endedwith version 2.2.

Figure 124: SAP Tutor Player



Further information on SAP Tutor use for SAP Solution Manager customers canbe obtained in SAP Service Marketplace: http://service.sap.com/saptutor -> SAPTutor for SAP Solution Manager customers.

Figure 125: From Learning Material to Learning Maps

You reuse the learning materials and role information maintained in theconfiguration phase (transaction SOLAR02) as follows, to compile learning maps:

1. Go to the the Implementation/Upgrade Workcenter (Navigation levelBuild and select the link Create Role-Specific Learning Maps andcreate a new Learning Map for the project. Otherwise you can calltransactionSOLAR_LEARNING_MAP

2. Create a Learning Map Header3. Assign Roles to the Learning Map to link users to the materials4. Create the Learning Map structure5. Filter learning material for selection according to roles as defined in the

configuration phase6. Test display of the Learning Map7. Distribute to Users

To the end-users an HTML version of the learning maps is distributed via URL.The URL always points to the most up-to-date material embedded in the learningmap. This means, there is no need to redistribute a learning map upon update –changes are automatically depicted in the existing URL.



With each Learning Map, users have the ability to leave feedback. This feedbackcan be viewed from SOLAR_LEARNING_MAP. Select a Learning Map andclick the Analysis button.

Feature List E-Learning

Figure 126: Feature List E-Learning

SAP ProductivityPak by RWD adapter for SAP Solution Manager:

SAP ProductivityPak by RWD is a comprehensive performance support solutionfor the collaborative creation, storage, and management of e-learning material,application simulations and procedural documentation. The adapter launches theSAP ProductivityPak by RWD client for recording, from SAP Solution Manager.The actual recording, editing and storage of the recorded documents is handledby SAP ProductivityPack by RWD; you can seamlessly access and view thesedocuments from SAP Solution Manager. For more information on this price listproduct, refer to: http://service.sap.com/solutionmanager -> Integration of SAPProductivity Pak by RWD

SAP sells RWD software like the SAP Productivity Composer or the SAPProductivity Pak which offer rich E-Learning functions. The tools are validatedand supported by SAP and allow professional recording and editing options. SAPProductivity Pak offers more features than Productivity Composer.

In contrast to SAP Tutor the SAP Productivity Composer or the SAP ProductivityPak by RWD creates an XML-file that can be edited after the recording. TheXML-file is basis for other documents like the Adobe Flash based animation,customizing documentation, test protocol, PDF based training materials andexercises. Moreover, SAP Productivity Composer offers some additional featureslike ReRecording, context sensitive help, definition management.



Lesson Summary

You should now be able to:• Explain the motivation for updating material• explain the concept of e-Learning Management• explain the selected steps/examples of the e-learning management process in

more details


Unit Summary SMI310

Unit SummaryYou should now be able to:• Explain the motivation for updating material• explain the concept of e-Learning Management• explain the selected steps/examples of the e-learning management process in

more details


Unit 8From Implementation to Operations

Unit OverviewThis unit tells you how the information gained in implementation projects ishanded over to production, reused and maintained in the form of solutions.


• Understand the concept of solutions• Know the main components of solutions• Know the differences between projects and solutions• Maintain solutions• Name selected usage scenarios requiring solutions

Unit ContentsLesson: From Implementations to Operations ... . . . . . . . . . . . . . . . . . . . . . . . . . . .236


Unit 8: From Implementation to Operations SMI310

Lesson: From Implementations to Operations

Lesson OverviewThis lesson tells you how the information gained in implementation projects ishanded over to production, reused and maintained in the form of solutions.


• Understand the concept of solutions• Know the main components of solutions• Know the differences between projects and solutions• Maintain solutions• Name selected usage scenarios requiring solutions

Business ExampleYour are a solution team member or administrator of a dedicated SAP solution.You need to understand the relevant technical concept to keep the documentedbusiness processes and dedicated technical objects up-to date, and providecontrolled access for changes.

Transition from Project to Solution

Figure 127: From Projects to Solutions


SMI310 Lesson: From Implementations to Operations

This slide shows the application life-cycle along which business scenariosand business processes are defined and changed in different life-cyclestages. Alternative paths are supported by SAP Solution Manager. OneSAP-recommended walk-through is as follows:

• Create an implementation project based on SAP implementation contentstored in the Business Process Repository (BPR). Alternatively, create andexecute a template project with templates containing standardized businessprocesses, e.g., for use in global rollouts. The template project may also bebased on SAP pre-defined implementation content.

• Implement the solution in the implementation project• Transfer the implemented solution into a productive solution by copying

the project content into the solution• Perform ongoing changes/corrections to the solution in a maintenance

project (ideally using check-in/out functionality)

Figure 128: Goals, Scope, and Benefits of Solutions

Benefits:

• Up-to-date, central solution documentation• Reliable solution documentation through controlled maintenance• Basis for many other SAP Solution Manager capabilities like business

process and interface monitoring, upgrade projects, knowledge transfer,issue management



Transparency of business processes:

• All business process and related system information are centrally availableand can be analyzed

• Increased awareness of business process and system information reduces riskwhen problems occur

Reuse of project information:

• Business process documentation of projects is reused, combined withtechnical documentation, and does not have to be maintained twice

• Combined business, landscape and technical view enables internal businessand IT alignment

Controlled changes of documentation:

• Check-in/check-out functionality allows controlled changes of the currentbusiness process documentation, keeping it up-to-date and reliable

Basis for other capabilities

• Enriches solution manager capabilities: business process and interfacemonitoring, upgrade projects, knowledge transfer, issue management

Figure 129: Components of a Solution



Solutions are accessed via the Solution Directory. They contain information, data,and documentation that is structured similarly to projects. The highlighted areasshow the main differences from projects.

1. The last entry in the navigation structure is folders listing system and serverinformation supporting the business scenarios and processes above

2. The Configuration tab is display only, because productive systems must notbe changed without controlled access. This controlled access and changeis provided by the check-in/check-out mechanism (see Check-Out Status[change requests]).

To transfer documents from projects, the Business Process Repository or othersolutions, into your current solution, you can:

• copy or reference documents• transfer documents of selected document types only, e.g., specifications,

requirement or customer-defined document types



Figure 130: Functional Comparison of Projects and Solution

Note:

• The information located at the Administration tab of an SAPSolution Manager project, for example keywords, are not transferredto a solution. Therefore it is recommended that you do not usekeywords to attribute process-relevant data (like location, risk level)to processes; instead, use customer attributes in the process structure.

• Maintenance and implementation projects provide different functionsin Change Request Management. For detailed explanations, refer tocourse SM200 - Change Request Management and Service Desk –Configuration.



Figure 131: Maintaining Solutions

1. Option 1: See the following slide for details of the process flow2. Option 2: is based on option 1, but would lead too far in this context, and is

the subject of training course SM2003. Option 3: This option is not recommended because it does not allow you to

change your productive solution in a controlled fashion.

Figure 132: Option 1: Check-In/Check-Out Process Flow and Roles



Check-in/Check-out procedure

• Changes to the sub-structures "Organizational Units", "Master Data" and"Business Scenarios" are made in the maintenance project assigned to thesolution on the ‘Solution Settings’ tab

• To change an object, a “change request” is sent to the solution administratorwho has approval authority

• If approved, the object is checked out into maintenance project formodification

• Once all changes have been made, the checked out sub-structure is set to “Ready for check-in” in the maintenance project, and can be checked backin to the solution directory

Note:

• A history function is available on the tabs, to document changesto the solution

• The check-in/check-out process can be combined with the completechange request management functionality.

Figure 133: Usage Scenarios Requiring Solutions



Figure 134: Example: Business Process Monitoring

Adequate solution documentation is the foundation of, and provides the scope for,Business Process Monitoring.

Business Process Monitoring in SAP Solution Manager is highly integrated withmany different other SAP tools and allows monitoring, notification and reportingin the following areas:

• Application monitoring• Background job monitoring• Cross-application monitoring• Data consistency monitoring• Dialog performance monitoring• Interface monitoring



Lesson Summary

You should now be able to:• Understand the concept of solutions• Know the main components of solutions• Know the differences between projects and solutions• Maintain solutions• Name selected usage scenarios requiring solutions

Related InformationEducation Trainings:

• SM200: Change Request Management and Service Desk - Configuration• SM300: Business Process & Interface Monitoring


SMI310 Unit Summary

Unit SummaryYou should now be able to:• Understand the concept of solutions• Know the main components of solutions• Know the differences between projects and solutions• Maintain solutions• Name selected usage scenarios requiring solutions


Unit Summary SMI310


Unit 9Service Desk

Unit OverviewThis unit will help you understand the functions of the SAP Solution ManagerService Desk.


• Understand the fundamentals of the SAP Solution Manager Service Deskconcept

• Know how to use the Service Desk in different project phases and in theproductive environment

Unit ContentsLesson: Working with the Service Desk ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .248


Unit 9: Service Desk SMI310

Lesson: Working with the Service Desk

Lesson OverviewThis lesson will help you understand the functions of the SAP Solution ManagerService Desk.


• Understand the fundamentals of the SAP Solution Manager Service Deskconcept

• Know how to use the Service Desk in different project phases and in theproductive environment

Business ExampleDuring an implementation as well as during testing and operative usage, differentkinds of issues and errors arise that need to be handled professionally andefficiently. The SAP Solution Manager embedded Service Desk functionality helpsyou to perform this task – up to an integration into change request management.

Introducing the Service Desk

Figure 135: The Central Capability of Incident Management


SMI310 Lesson: Working with the Service Desk

SAP Solution Manager Service Desk is the central capability to manage incidents.In different project phases, your staff can create messages which you can managecentrally in the Service Desk. A major benefit comparing to other Help Deskapplications is that end users can create support messages from any transactionin SAP system that is connected to SAP Solution Manager. An internal supportteam will then process these support messages centrally in the SAP SolutionManager Service Desk.

The Service Desk functionality is fully integrated into other SAP Solution Managercapabilities, like test management, change management, projects or many more.Service Desk messages for example could be used for creating a Change Request.

SAP Solution Manager Service Desk has also a integration to the SAP GlobalSupport backbone and the partner ecosystem. Customer messages can beforwarded with the message history to the SAP Global Support. Remoteconnection and SAP Notes Search are also integrated in Service Desk.

Since a lot of SAP customers have already other Help Desk tools in place tomanage incidents, SAP Solution Manager offers a Service Desk interface whichcan be used for an integration to third-party applications, as well as to otherSolution Manager systems or the IT Service Management processes in SAP CRM.

Figure 136: Process Overview: Message Creation and Message Handling



Using the Service Desk

Figure 137: Documenting Project Issues

In the build phase business blueprint and configuration is done by business processexperts in SAP Solution Manager. SAP Solution Manager service desk can beused to create issue messages out of the business blueprint structure elements.Open issues are documented this way in relation to a business scenario, businessprocess or process step. A responsible project member can be assigned to thisissue and will be responsible to solve it. With reporting functionalities the statusof issue processing can be evaluated.



Figure 138: Documenting Test-related Issues

During the test phase of a project, the service desk is used for test error resolution.In case of an error during testing, the SAP Service Desk functionality can be usedfor the administration of error messages resulting in a test scenario. Integrationof Test Management and Incident Management allows to use the same supportprocess that has been already established for other support areas and it allowsto report on test-related messages with the SAP Test workbench. It offers anenhanced traceability regarding test errors and easy follow-up.

The process starts directly with the creation of an error message from the tester’swork list. Test case attributes will be automatically handed over to the messagelong text section. After the creation of the message, the message number isautomatically assigned to the tester’s work list.

The test manager can monitor all test related support messages using the messageoverview functionality within the status information system to get an overview ofoverall messages or to select messages per specific test plan.

Tracking your messages in the testing phase is important too from a viewpoint ofexternal revision.



Figure 139: From Service Desk Message to Change Request

A Service Desk message can serve as a trigger for creating change requestmessages. This is, for example, the case when it is necessary to implement anSAP note or to correct coding, to solve an incident or problem. The change isthan deployed via Change Control Management and the deployment status canbe tracked in the Service Desk message. You see, that the Service Desk could beused as the input channel for business to request a change, in all SAP Netweaverapplications.



Figure 140: Using Service Desk in Productive Environments

Application Incident Management allows end- or keyusers to create incidentmessages directly from a transaction, web application or the Incident ManagementWork Center. The reporter can contact their service desk easily in this way. Ifan internal solution database is installed, the support staff member can entersymptoms in it, to process the problem, and search for solutions. The support staffmember can collaborate with the SAP Service & Support and search for SAPnotes in the SAP Service Marketplace. If the support staff member does not find aproblem solution, he can forward the support message to subsequent support unitsor to SAP Support, and monitor the progress of processing in the Service Desk.

Even the Business Process Monitoring functionality interacts with the SAPSolution Manager Service Desk. Business Process Monitoring focuses onbusiness-critical processes and generates alerts warnings in case of problems orto escalate to further processes. Alerts can automatically create Service Deskmessages, which are routed to escalation managers to resolve the cause of thealert as soon as possible.

You see that the Solution Manager Service Desk plays a vital role during theOperation of your SAP solution. For the support of non-SAP applications you cancontinue using an external service desk of a third party provider in connectionwith the 3rd party interface or you can even use the Service Desk and extendit to your needs.



Figure 141: Incident Management Work Center

The process of message creation and processing is fully supported by a web-UIbased (browser-enabled) Incident Management Work Center.

Figure 142: Incident Management Work Center



Lesson Summary

You should now be able to:• Understand the fundamentals of the SAP Solution Manager Service Desk

concept• Know how to use the Service Desk in different project phases and in the

productive environment


Unit Summary SMI310

Unit SummaryYou should now be able to:• Understand the fundamentals of the SAP Solution Manager Service Desk

concept• Know how to use the Service Desk in different project phases and in the

productive environment


Unit 10Managing Projects - Beyond

Implementation

Unit OverviewThe preceding units gave you all the information you need to carry outimplementation projects, by introducing you to the portfolio of tools, content, andmethodologies offered with SAP Solution Manager. But a solution’s lifecycle doesnot stop with the end of the implementation project. There are other situationswhere your knowledge as a project manager, application consultant, businessprocess expert, test organizer or tester is required, when the solution is to beupdated or is deployed company-wide. This unit will therefore introduce you tothe further implementation-related topics mentioned in the unit objectives.


Unit 10: Managing Projects - Beyond Implementation SMI310

After completing the unit, you will be able to explain:

• How SAP Solution Manager is used to create and use templates in globalrollout. If your company is a global player, or if you have subsidiariesin various countries, you may want to standardize and harmonize yourbusiness processes throughout your company. SAP Solution Manageroffers a template management approach, which allows customers withmulti-site SAP installations to manage their business processes efficiently,across geographical distances – from initial template definition to templateimplementation and template optimization. This approach facilitates theconsistent design, re-use and uniform deployment of your business processesacross your company.

• How to analyze your productive solution. The Solution DocumentationAssistant function gives you clarity and transparency about the us of yourmanaged systems. It enables you to verify your documented business processstructure and to check the completeness of your business process structuredocumentation. For example, an analysis can be performed on a regularbasis to evaluate which parts of an originally implemented solution are usedproductively, by analyzing SAP and customer-specific transactions, reports,and SQL statements. Such an analysis facilitates both continuous businessimprovements and upgrade preparation.

• How to identify business processes affected by software changes that requirere-testing. Solution updates may occur frequently - from minor configurationchanges through support package installation, to a major release upgrade.The challenge is to find out which business processes are affected by plannedchanges. Based on a technical comparison, the resulting BPCA analysisindicates which changes to the system might impact your business processes– in other words, the analysis highlights on what you should focus yourtesting efforts and gives risk-based test recommendations.


• How to create and update templates• How to implement templates• How to roll back template requirements and roll out updated templates• How to compare and adjust template changes from an update template to a

local implementation project.• Explain the purpose of Solution Documentation Assistant• Use the Solution Documentation Assistant• Explain why TBOMs are necessary• Run a change analysis


SMI310 Unit 10: Managing Projects - Beyond Implementation

Unit ContentsLesson: Template Management .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .260Lesson: Solution Documentation Assistant .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .278Lesson: Business Process Change Analyzer .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .293

Exercise 7: Business Process Change Analyzer.. . . . . . . . . . . . . . . . . . . . . .301



Lesson: Template Management

Lesson OverviewThis lesson describes the template management approach as it can be used inglobal rollouts. It explains the concepts of how SAP Solution Manager supportsefficient and effective management of global implementations.


• How to create and update templates• How to implement templates• How to roll back template requirements and roll out updated templates• How to compare and adjust template changes from an update template to a

local implementation project.

Business ExampleImagine that the company you work in is a globally-operating consumer productscompany, with subsidiaries in Europe, North America, and Asia-Pacific. Over theyears, the system landscape has grown, and reached a dimension which is nolonger feasible and supportable by the organization. Additionally, financial andeconomic constraints drive the need for cost savings, and ultimately the need forconsolidated and standardized business processes and system landscape.

The company’s top management has recognized the importance of such a globalapproach. With full board commitment, your company starts a global templateinitiative, which envisages a global business process setup, running on two globalSAP ERP instances (there were previously 10), one for Europe and North America(region 1) and the second one for the Asia-Pacific region (region 2), with someleeway for localization. The template management approach was to use SAPSolution Manager to document the global processes in the global templates, in atemplate project, and roll them out to both regions, at different times.


SMI310 Lesson: Template Management

Introducing the Template Management Concept

Figure 143: Introducing the Template Management Concept

The template management approach allows customers with multi-site SAPinstallations to efficiently manage their business processes across geographicaldistances – from initial template definition to template implementation andtemplate optimization, such as in a global rollout.

The template management approach comprises the following activities:

• The template is created by the global template team, in a template projectwhich serves as a container for your template definition.

• The template is rolled out to the local sites, e.g., dedicated subsidiaries orregions, and implemented by the local rollout teams using implementationprojects.

• Over the course of time, requirements for changes (e.g., functionalenhancements, increased productivity, business process merge or split) mayresult in the creation of an updated template. The updated template is to berolled out once more to local sites, who now transfer the delta changes via acomparison and adjustment mechanism, into their project.



Creating Templates

Figure 144: Creating Templates - Process in Detail

The template creation process involves the following activities:

• Internal and external drivers, e.g., requirements for enhanced functionality,as well as, constraints, e.g., the need to harmonize business processes andunderlying IT, drive the need for template management approaches.

• Once senior management or board approval has been obtained, you – nowas a member of the global template team - get started with your templateproject by defining the project framework, e.g., project standards and projectstaffing, and the template “shells”.

• In the template blueprint phase, you define the scope of the global processeswhich must be implemented by the local sites.

• In the template configuration phase, you assign pre-configuration and testmaterial, to speed up configuration and test activities in the local rolloutprojects.

• Having completed the template, you package it, and roll it out to the localsites. If the local rollout projects are performed on another SAP SolutionManager system, you would have to transport the template to this SAPSolution Manager system first.



Figure 145: Defining the Template Project

We are now going to focus on the steps that you perform when you createa template via SAP Solution Manager. When you create a new project inSAP Solution Manager, you select the project type Template Projects. Whendefining the project framework, you assign project team members, roles, andresponsibilities. This is the same as in implementation projects. In templateprojects, there is an additional tab, Template, in the project administrationtransaction, where you define the templates required in your project. Templatesserve as containers for global, standardized and harmonized business processesand the underlying system landscape in which they Operate. Template projectsprovide the environment to managed one or more templates.

For each of these templates, you can control the visibility by switching betweenthe statuses Closed and Open. A closed template is still being worked on by thetemplate application team and, therefore, can currently not be transferred to anyother rollout project. Only templates that are open for public use can be used byother rollout projects to jump-start template implementation.

To be able to control the use of global attributes, you need to activate the GlobalRollout Functionality on this tab. These attributes define the global coverageof a business scenario or process, and allow you to control the extent to whicha dedicated business scenario or process can be changed in an implementationproject.



Figure 146: Working with Global Attributes

The global attribute defines the scope of changes allowed to business scenarios inprocesses in local rollout projects. You can lock the process structure elementsagainst changes in the rollout project, or allow subsidiaries to change them



partially or completely, by giving their global attribute appropriate values. Thereare global and local elements and three different kinds for harmonized elements,standard complete, standard partial and harmonized.

• A process is global when it is integrated throughout the enterprise, that is,it is cross-functional or cross-organizational. An element that is flagged asglobal cannot be changed or deleted in a Local Rollout, i.e. the structureelement and all associated business content is pre-determined.

• A process is standardized if it must be executed in the same way inthe entire enterprise, in all relevant organizational units. A standardizedcomplete element and its business content can be seen as a suggestion fromthe Global Template that should be used as delivered. However the localteam may extend the structure element with additional substructures and withadditional business content.

• A standardized partial element and its business content can be seen as asuggestion from the Global Template that should be used as delivered, butthe process consists of sub-processes that are locally regulated, by legalrequirement, and these need to be defined locally. The local team can designown process, if agreed by the parent company. The local team may extendthe structure element with additional substructures and additional businesscontent. Template business content may even be changed or deleted bythe local team. Whenever a template object is deleted, there is a warningmessage.

• It is recommended that the local rollout uses the harmonized structureelements for Business Process, Master Data or Organizational Units that willbe standardized in the future. A process is harmonized if it is recommendedto execute the process in a specific way. Harmonization is a first step towardsstandardization, but without mandatory elements. One reason can be fororganizational readiness, or legal requirements preventing standardization.For the local team the same activities are allowed and forbidden as forStandard Partial.

• A process is local if it is not possible, or it makes no sense, to define it asglobal, standardized, or harmonized. Local units must design this process fortheir needs. These processes are necessary to obtain an executable systemfor testing. For the local team the same activities are allowed and forbiddenas for Standard Partial.



Figure 147: Defining the Business Blueprint Template

In the business blueprint phase of your template creation process, you define yourglobal business processes and related functional requirements. The easiest way tojump-start your global process design is to use SAP predefined implementationcontent from the Business Process Repository. Along your global business processstructure, you assign your templates to the process structure, so that all businessprocess-related content is stored in the desired template for later rollout and/orshipment. This is done in the Template column, where you assign one or moretemplates to business scenarios. You can set the global attribute for each businessscenario, process or process step, to determine the scope of process changes inlocal roll-out projects.



Figure 148: Defining Template Configuration

After finishing the business blueprint template, you enter the configuration phaseof the template and prepare the reference template by pre-configuring it. Youdo so by:

• Creating and assigning BC Sets (Business Configuration Sets) to yourprocess structure

• Assigning related IMG (SAP Implementation Guide) activities, to fine-tuneyour configuration

• Assigning global customer-specific developments like programs,transactions, etc.

• Creating standard test cases (manual or automatic) and assigning them toyour process structure as well.

All these different pieces of pre-configuration can be launched in the rolloutprojects to accelerate local template implementation. The pre-configuration can beapplied either 1:1, such as for BC Sets, or can be used as a copy reference, uponwhich local material can be built, e.g. for test cases.



Figure 149: Packaging and Rolling Out Templates

When you have finished building your templates, you can start to package them.Ensure that you have assigned all relevant scenarios to the template. Then releasethe template, by changing the visibility to public use, in the project administration.The template is only then visible, and thus usable by the rollout projects. If youare not using the same SAP Solution Manager for your rollout projects, collectthe templates into transport requests and transport them to the other SAP SolutionManager System.

Figure 150: Global Rollout in Stages



A template can be distributed as part of a global rollout. To minimize effortand maximize investment, it is recommended to roll out the template in stages.Typically you start the template rollout with a first pilot. You enhance the templateto reflect the changes requested in the pilot’s feedback. The template should onlythen be rolled out into the subsidiaries of your organization.

The process of template creation and template implementation in stagesis supported by the GlobalASAP methodology.GlobalASAP delivers aprocess-oriented, clear, and concise methodology, the GlobalASAP Roadmap,to provide step by-step direction throughout your global or multi-site SAPimplementation.

GlobalASAP provides two roadmaps:

• GlobalASAP Template Roadmap for template creation and pilot rollout• GlobalASAP Rollout Roadmap for template implementation

These roadmaps are fully embedded in SAP SolutionManager. Further informationon roadmaps in general can be found under: http://service.sap.com/roadmaps

Implementing Templates

Figure 151: Process in Detail



The template implementation process involves the following activities:

• You – now as a member of the local rollout team - started your local siteimplementation project by defining the project framework. This alsoinvolves the selection of the targeted template for implementation

• In the local business blueprint phase, you refine the local business blueprint,based on the blueprint delivered with the template.

• In the local configuration phase, you execute the pre-configuration deliveredwith the template and adapt the test material to suit your local test activities.

• You may optionally use the SAP Solution Manager embedded e-learningmanagement capabilities, to create and distribute your own e-learning maps.

• Finally, the implemented local solution is deployed into an operativeenvironment.

Tthe template implementation is not uni-directional. It is a sub-step withinan iterative cycle, consisting of updating the initial template and rolling outthe updated template to the local sites again. The difference in the second andsubsequent iterations of template implementation, is that only the parts that havebeen changed, not the entire template, need to be implemented again.

Figure 152: Copying Templates into an Implementation Project

The template is copied into an implementation project, the template, with allits pre-configuration, documentation, and test material, is the basis for the localconfiguration. Nevertheless, the copied content always keeps the reference to theoriginal template. Comparison, and update mechanisms can retrieve and transfer



changes from an updated template, into the local implementation projects, at laterproject stages, based upon this reference information. Further information willbe provided at the end of this chapter.

Figure 153: Local Project Preparation

Having rolled out the template, you now create a local roll-out project (SAPSolution Manager project type implementation project). This is where youassign your project team members, roles and responsibilities, and define theimplementation standards. On the Template tab, you select one or more templatesas well as related scenarios, for you implementation. This will copy the globalprocesses from your template into your local implementation project.

During your local business blueprint, you can then enhance the global processes,adapt harmonized and local processes to local requirements, and document localrequirements of harmonized and local processes. Additionally, you may addfurther local processes if required, and document them accordingly. The scopeof processes to be implemented should be documented in a formal fashion bysigning off the business blueprint.

Figure 154: Local Blueprint, Configuration and Test Management



You perform the local configuration by applying preconfigured customizingshipped with the global template processes, and by performing the finalconfiguration via IMG activities, based on local requirements. You also deployglobal customer-specific developments, such as reports, and you enhance yourprocesses with local customer-specific developments. Test cases delivered withthe template are used as a reference to create local test cases.

All global and local requirements will then be tested using the regular testmanagement capabilities provided in SAP Solution Manager, with the sub-stepsto be performed as listed above. Further information on how to plan and executeyour test activities can be found in the unit on Test Management.

Figure 155: E-Learning and Solution Transfer

As you do with regular implementation projects, you can then set up end-usertraining using the e-learning functionality in SAP Solution Manager, as you havealready seen in the previous unit on e-learning management.

Locally implemented solutions are treated like all other solutions within theapplication lifecycle path. They have to be prepared for productive use bytransferring them to the Solution Directory, which serves as a central storage ofall your productive processes, including the technical information upon whichthese processes are operated. This information in turn saves as a starting pointfor other ALM processes, e.g.

• Technical Operations: System Monitoring requires an operative solutionwith productive systems to be monitored.

• Business Process Operations: Business Process Monitoring requires theinformation on operative business processes to be monitored.

• Maintenance Management: The maintenance optimizer requires a solutionwith operative system information, upon which the latest support packageswill be calculated for download.



Rolling Back Template Requirements and Rolling OutUpdated Templates

Figure 156: Rolling Back Template Requirements and Rolling Out UpdatedTemplates

The rollback and template update process can be divided into three phases.

Firstly, you roll in additional template requirements, like improvements orcorrections of the template. Currently, this process has to be organized manually.In the future, tool support for the template rollback and template update processis expected, using compare and adjust functionality.

Secondly, you update the template and implement the feedback from local sites, oradapt it to new or updated SAP solutions or enhancements.

Thirdly, you rollout the updated template to local implementation projects usingthe compare and adjust functionality.



Comparing and Adjusting Implemented Templates

Figure 157: Updating Implemented Templates

The goal of the compare and adjust functionality is to retrieve and transfer processand pre-configuration difference from an updated template, into the currentimplementation project. It is a two-step approach:

• In a first step, SAP Solution Manager helps you to compare theimplementation project with the updated template, and highlights all changesin the process structure of your implementation project. This functionality islaunched using transaction SA_PROJECT_UPGRADE.

• In the next step, you decide which changes should be transferred into yourproject.This is done using the Compare and Adjust functionality in theimplementation project; it is started using the Adjust to Original button (seenext slide).



The scope of the comparison and adjustment includes the following entities ofyour project:

• All tabs as per selection, e.g., Transaction, Configuration, Development• Attributes of structure elements (if selected)• Name changes of structure elements• Structure tab: global attribute• Tab-based update of contents assigned to structure elements

– Adjustment process („Complete“ function) is applicable to individualTransaction, Documentation etc. tabs attached to the structure elements,not to structure elements

– This allows scheduling the comparison and adjustment job daily

Figure 158: Updating Implemented Templates

Having compared the implementation project with the updated template,differences (e.g., deleted and new assignments) are highlighted – here with ayellow exclamation mark - but not yet transferred into the Blueprint and/orConfiguration environment. If the changes are not visible, switch on thecomparison mode in the user-specific settings. Changes from the template can betransferred into the current implementation project, in this case a BC Set [BusinessConfiguration Set], by selectively choosing them for transfer.



During the transfer or adjustment step, initiated via the Adjust to Original button,you should consider the following:

• The Complete button completes the comparison, regardless of whether allchanged objects have been transferred into the implementation project ornot. This will make the yellow exclamation mark disappear. A new archiveversion will be created. After completing the comparison, the compareand adjust dialogue will no longer show differences in the New Version ofOriginal section (left pane). The compare and adjust dialogue will only flagnew changes that come with the next template update.

• Via the Copy button you simply transfer the changed objects into yourimplementation project. The yellow exclamation mark does not disappearuntil you have set the comparison to complete.

Changes in the actual content objects, e.g., changes within a captured BC Set,updates of an eCATT, or changes within a document text, are not discovered andhighlighted. Instead it is recommended to delete the previous version of thecontent object, e.g., the “old” BC Set, and replace it with a new one.

After the transfer into the project, the configuration will still need to be appliedto the locally managed systems, documented and tested, as demonstrated in theprevious rollout cycle.



Lesson Summary

You should now be able to:• How to create and update templates• How to implement templates• How to roll back template requirements and roll out updated templates• How to compare and adjust template changes from an update template to a

local implementation project.



Lesson: Solution Documentation Assistant

Lesson OverviewUnderstand how to use the Solution Documentation Assistant.


• Explain the purpose of Solution Documentation Assistant• Use the Solution Documentation Assistant

Business ExampleThere two scenarios for the Solution Documentation Assistant:

1. Companies want to check on a regular basis if the documentation initiallymaintained in SAP Solution Manager, e.g., as part of an implementationproject, is still up to date (Use case 1: verification of the solution content).

2. Companies want to model their business processes and the appropriatesystem landscape in SAP Solution Manager. The business process couldhave already been modeled with other modeling tools. Moreover, thecompanies can use SAP systems and want to use a reverse engineeringapproach as basis for the modeling in Solution Manager (Use case 2: startingpoint for maintaining business content).


SMI310 Lesson: Solution Documentation Assistant

Introducing the Solution Documentation Assistant

Figure 159: Introducing the Solution Documentation Assistant

First, we explain the data and system infrastructure required to run the SolutionDocumentation Assistant in SAP Solution Manager. Second, we will dive deeperinto customer pain points, and how Solution Documentation Assistant cansupport them. Third, we will focus on the key Solution Documentation Assistantfunctions. And finally we will wrap up with a summary.

Figure 160: Identify, verify and create business processes



Today’s IT solutions get more from support! Why? Here are four aspects of thisquestion.

• Firstly, your business is one part of your IT organization. Business arerepresented by business process champions, key users, end users and programmanagement which manages your projects. The business are focusedon business improvements and innovations. Managing improvementsand innovations will result in IT changes. Changing IT usually has therequirement that all technical objects which are in use must still run afterchanges have been made.

• Secondly, to reduce cost of operations, business organizations are migrated,and related IT systems are increasingly consolidated. Before you canconsolidate business and IT, you need to know how your business processrun, and how your system landscape is set-up. All this information isnecessary to compare and discuss business processes at different sites forstandardization potential.

• Thirdly, the increasing complexity of software and solutions requires holisticmanagement of your IT landscape over the life-cycle of your applications.This includes all types of development: standard SAP software, customdevelopment (including that delivered by SAP), and partner solutions.Clarity of your IT solution, and knowledge transfer to the employeesinvolved, provides the basis of smooth support.

• Fourthly, you can use the Solution Documentation Assistant as an acceleratorfor your project and solution documentation, from a business perspective.The existing SAP Solution Manager infrastructure, including connectedsystems, is used to analyze satellite systems.

The Solution Documentation Assistant function in SAP Solution Manager takesthe lead in addressing these challenges.



Figure 161: Maintain your data transfer from the managed systems to SAPSolution Manager

Because Solution Documentation Assistant is a function of SAP SolutionManager, we can use the data provided by the existing infrastructure. The basicfunctionality of Solution Documentation Assistant is available from SAP SolutionManager 7.0 Support Package 16; enhanced functionality is shipped in SAPSolution Manager 7.0 EhP 1.

Customers need to check the technical requirements and RFC connections. TheEarly Watch Alert, which already delivers data from managed systems to SAPSolution Manager, has been enhanced to provide the data required by SolutionDocumentation Assistant. The data transferred is workload statistics data fortransactions and reports which are executed in the managed systems. If the EarlyWatch Alert data has red or yellow alerts, you need to double-check the datatransfer. Correct data transfer has the status green, and the system is ready fora jump-start analysis.

Early Watch Alert must deliver data for a minimum of one month before the firstanalysis run starts. The Solution Documentation Assistant takes the data for a fullmonth into account, so the latest month available for a current analysis is the lastmonth. The data which can be transferred depends on the customizing storage inthe managed systems. Because of the large data volume, customers customizethree months by default.

The customer system landscape environment provides a service infrastructure.Customer managed systems are connected with the customer’s SAP SolutionManager. The managed systems must have release 4.6C or higher.



The data transfer is managed by the Early Watch Alert service session, whichis already part of our SAP support engagement. The SAP software componentST-PI has been enhanced to collect the workload statistics data, so SAP softwarecomponent ST-PI release 2008_1_* SP00 is a technical prerequisite. Thisenhanced service has to be activated via the SAP Solution Manager customizingIMG. After activation, the workload statistics data is transferred via the EarlyWatch Alert.

The Solution Documentation Assistant work center is the central access point, andprovides several views to manage the analysis projects, to create analyses, towork with analysis results, and to manage check rules in the rule database. It isan SAP Solution Manager work center. Activation and related user authorizationhave to be set-up via the Implementation Guide (IMG) and role maintenance viatransaction PFCG user roles.

The Solution Documentation Assistant manages information about implementationprojects and information from productive solutions.

Use Cases for Solution Documentation Assistant

Figure 162: Use Cases for Solution Documentation Assistant

Customers need clarity and transparency about their current situation. It isimportant to identify which data exists, and which processes are alreadydocumented, to find the right starting point. Information about planned andscheduled activities also helps to identify the use cases for Solution DocumentationAssistant in these plans.



To establish the customer functionality, SAP and SAP customers have defined aset of typical customer pain points which describe where Solution DocumentationAssistant can support customers, partners and consultants.

Typical pain points are reflected by the following questions:

• Is my solution content still valid? How can I use SAP’s implementationcontent to validate my business content in SAP Solution Manager? Is myexternal maintained business content still up to date?

• How can I use Solution Documentation Assistant to start maintaining mybusiness content in SAP Solution Manager?

Figure 163: Use Case 1

Validation of business content in solutions means content which is alreadydocumented in the SAP Solution Manager solution. To validate the solution,customers need to create an analysis project in Solution Documentation Assistantand run the analyses based on it. The analysis results are highlighted in SolutionDocumentation Assistant. The results can be used to create or update animplementation project. The changes can also be maintained manually in thesolution.



To operate this use case, you perform the following individual activities:

• Generate an analysis project in Solution Documentation Assistant• Optional: Generate partner content in Solution Documentation Assistant via

the external interface• Run the analyses based on the analysis project• Verify analysis results• Enhance analysis project check rules• Run additional analyses• Use analysis results to update the implementation project or create a new one• Copy generated implementation project structure to solution

Figure 164: Use Case 2

To identify the mission-critical top score processes which are running on thecustomer’s systems, a dummy business scenario and business process needto be created into an implementation project in SAP Solution Manager. Thisdummy structure is the starting point to generate an analysis project in SolutionDocumentation Assistant and to run the analyses based on it. The analysis result ishighlighted in Solution Documentation Assistant and the starting point to maintainthe dummy nodes and/or to create a new implementation project from scratch.

•



To operate this use case, you perform the following individual activities:

• Create a dummy business scenario and business process in SAP SolutionManager implementation project

• Generate an analysis project in Solution Documentation Assistant• Run the analyses based on the analysis project• Verify analysis results• Use top score processes which are running on the customer’s system to

identify the mission-critical technical objects• Based on the analysis results, create the business structure in SAP Solution

Manager

If a customer or partner plan to reuse already created analysis projects or checkrules as a ‘template’, an external interface supports the data exchange.

• Example 1: A customer or partner want to reuse an analysis project thatthey use in a reference Solution Manager system in another SolutionManager system with a similar system landscape. You download the datafrom the reference system and upload it to the second Solution Managersystem. On the second Solution Manager system you make adjustments andenhancements. You then upload the adjustments to your reference systemand thus continually optimize your analysis project in the reference system.

• Example 2: A customer or partner want to reuse maintained check rules foranalyses. You download the data from the reference system and upload itto the second Solution Manager system. The data are used to verify theanalysis project.



Solution Documentation Assistant Work Center

Figure 165: Solution Documentation Assistant Work Center

The Solution Documentation Assistant work center is the central access point.The work center presents several views to enable you to manage analysis projects,manage process analyses and their results, and create and edit check steps in therule database.

Figure 166: Creating an Analysis Project



This view of an analysis project shows the analysis structure and the check rulesassigned to the analysis structure nodes.

Analysis Project – The Solution Documentation Assistant offers you a viewshowing the structure and details of an individual analysis project. The screen isdivided into two related parts. On the left-hand side, analysis structure mirrorsthe structure to be analyzed and matches the structure source, which can beimplementation projects, solutions or an uploaded partner project structure. Theright-hand side contains check items, check steps and threshold values, which arelisted in a hierarchical order and related to the selected structure node.

The

• process structure - mirrors the business processes to be analyzed• Check items - link to a structure item that is to be analyzed• Check steps - to be run through for that structure item

Check Steps which are supported by Solution Documentation Assistant are

• Transactions• Reports• Business Add-In (BAdI)• Database table (SQL)

For check steps for database tables you can create subtypes of SQL check stepsthat check the following cases:

• Whether a specified database table is present• Whether a specified field of a database table is present• Whether specified values occur in fields of a database table• How often certain values occur in fields of a database table

Threshold value- is used for check steps in the analysis, to identify the usagerate as true or false.



Figure 167: Overview on usage per structure item

The Solution Documentation Assistant provides a detailed view of the resultsof an analysis.

The Solution Documentation Assistant compiles the analysis results by thefollowing criteria and displays them on the corresponding tabs:

• Structure Results Overview• Summary of Analysis Results• Graphical Overview• Analysis Settings• Error Statistics



Figure 168: Overview on usage analysis for technical objects

The Solution Documentation Assistant provides a summary of the analysis resultsby analysis success and object use, for example, of SAP or customer-specifictransactions and reports. Depending on the type of check steps used, the analysisresults are summarized under different aspects, for example:

• All transactions and reports• SAP transactions and reports• Customer-specific transactions and reports

It is possible that the origin of some objects cannot be identified unambiguously(either as SAP or customer-specific transactions and reports). In this case, thespecified number of all transactions and reports is larger than the total of SAP andcustomer-specific transactions and reports. The possible deviation is due to thefact that only information for used objects is transferred. Objects in managedsystems that exist there but are not used in the analyzed period, are not transferredand therefore have no designated origin. Information about customer objects thatare not used is only displayed if you have selected the Get All Customer Objectsoption when you created the analysis.



Figure 169: Transferring Analysis Results into Project

Analysis Results can be transferred back into projects

Solution Documentation Assistant Benefits

Figure 170: Customer situations which the Solution DocumentationAssistant can support



You can:

• Verify the business processes maintained in your implementation andupgrade project managed systems

• Verify your mission critical processes maintained in your solution• Discover your AS-IS processes on your managed systems and create your

starting point for solution documentation or upgrade• Bring your business processes into SAP Solution Manager by comparing

your AS-IS processes in your managed systems with SAP’s implementationcontent

• Bring your business processes into SAP Solution Manager by identifyingyour mission-critical activities.



Lesson Summary

You should now be able to:• Explain the purpose of Solution Documentation Assistant• Use the Solution Documentation Assistant


SMI310 Lesson: Business Process Change Analyzer

Lesson: Business Process Change Analyzer

Lesson OverviewThis lesson covers how to create a technical bill of material (TBOM), which formsthe basis for Business Process Change Analysis.


• Explain why TBOMs are necessary• Run a change analysis

Business ExampleYou are working on an upgrade project and want to use Business Process ChangeAnalysis to identify changes to your core business processes.

Assessing The Impact of Change

Figure 171: What Will Be The Impact Of These Support Packages?

Changes to your system are a fact of life - from seemingly minor configurationchanges through support package installations up to a major release upgrade.To avoid nasty surprises, you need to test your system after any such changes.



However, as time and resources are often short, you must prioritize your testingactivities. This is, of course, hard if you are not sure what impact the changes willhave on which of your business processes.

The Business Process Change Analyzer is a tool that helps you to identify areasof your system that have been impacted by changes that are imported from yourdevelopment system. It works by comparing the technical objects contained in atransport with the technical objects used by your business transactions. The resultsof the analysis show the points at which changes to the system might impactyour business processes - in other words, the analysis highlights areas on whichyou should focus your testing efforts.

A further feature of the Business Process Change Analyzer is that it can evengenerate a new test plan based on the test cases assigned to your Solution Managerproject. As you will recall, in your project you assign test cases to particularprocesses or transactions. The Business Process Change Analyzer can thereforeidentify the test cases that should be repeated in order to ensure that your system isstill working as required.

Figure 172: Changes To Technical Objects Affect Business Transactions

The above graphic shows how your system can be affected by support packages,upgrades, or configuration changes. The programs, Customizing settings, andother technical objects that are changed as part of the new development orcorrection are all used by applications in the system. It has always been possibleto tell which objects are included in a support package, as every transport requesthas its own object list. However, it has never been easy to identify whichapplications use these objects without the need for specialized configuration oreven development knowledge.



The impact analysis works by comparing the object list of one or more transportrequests with a list of objects used by your business applications. However, beforeyou can perform the analysis, you first need to generate this list as a TechnicalBill of Materials (TBOM).

Figure 173: Technical Structure Of A Transaction

Technically speaking, the transactions that you use in an SAP system are madeup of a chain of screens. Each of these screens contains elements, which arethemselves subject to change, but they also call blocks of source code, whichcan be realized in different ways. As well as processing the input and outputfrom the screens, the source code is responsible for reading and writing data toand from the database. The database contents include master data, transactionaldata, and Customizing settings. Put simply, therefore, any changes to the userinterface of a transaction, the programs used by it, or the database tables andCustomizing settings on which it relies could have an impact on the way thatthe transaction works.

In order to know whether a transaction is affected by the contents of a particulartransport, we need a list of the technical objects used by the transaction itself - aTechnical Bill of Materials (TBOM).



Creating a Technical Bill of Materials

Figure 174: Creating a Technical Bill of Materials

You create TBOMs from the Configuration of your Solution Manager project.Each TBOM relates to a transaction. To create a TBOM, open the Transactionstab in the Configuration, select the relevant transaction, then choose Attributes .In the subsequent dialog box, switch to the TBOM tab.

Next, choose Create to create a new TBOM. A dialog box appears in which youhave to decide whether to create the TBOM dynamically or statically.

Method ofTBOM Creation

Description

Dynamic You run the transaction. The system logs all technicalobjects that are accessed as you do so.

Static up to nbranching levels

The system analyzes the source code without you havingto run the transaction. Dynamic coding cannot be takeninto account. The analysis stops after the given number ofbranching levels.

If you create the TBOM dynamically, you run the transaction as normal and allof the technical objects that are accessed by the system are added to the TBOM.You can also opt to create the TBOM on the basis of a static analysis. In thiscase, the system analyzes the source code and adds all of the technical objectsthat it can identify to the TBOM. This option may be less efficient as it analyzesall coding branches, even those that are not normally executed. There is also a



danger that some objects will be missed out if they are invoked dynamically orif the transaction has a branching depth greater than that which you set whenyou started the analysis.

The result of the TBOM creation is an extensive list of objects accessed during thetransaction. From the TBOM dialog box, you can display this list, either in fullor as a set of statistics. You can also determine which kinds of object are mostcritical using the Criticalities option.

Running the Business Process Change AnalysisHaving generated TBOMs for the relevant transactions in your project, you mustcompare them with the contents of one or more transport requests to establish theimpact of the transports on your business process.

Figure 175: Running the Business Process Change Analysis

You start the Business Process Change Analysis from the Test Management workcenter. Enter a description for the change analysis, then specify the scope of theanalysis. This has two parts - on the left-hand side of the screen, you specify themanaged system and the transport requests that have been imported and whoseimpact you want to assess. On the right-hand side, choose a project - for whichTBOMs must already exist - with which the contents of the transport should becompared.

If you have defined criticality rules for your TBOMs, you can use the TBOM ItemCriticality option to set a filter for the analysis results. If you do not do this, allchanges will be highlighted.

To start the analysis, choose Run. The analysis starts in the background. To checkthe progress, choose the Refresh option at the bottom of the list of analyses.



Figure 176: Business Process Change Analysis: Results

When the analysis is finished, you can click on the corresponding line of the list.In the grid below, you will see an entry for each project covered by the analysis.If you select one of these lines and choose Display Details, the system displaysall of the processes and transactions affected by the transports requests that youincluded in the analysis. If you now choose Display Intersection, you can see theindividual objects that caused the impact.



Creating a New Test Plan

Figure 177: From Analysis To A New Test Plan

The Business Process Change Analysis highlights the business processes andtransactions that have been affected by changes in the managed system. In yourconfiguration, you may well have assigned test cases to these project nodes. Inorder to ensure that your system is still running properly, you must re-test these testcases. However, it is also possible that the changes to the system have invalidatedthe test cases (for example, because the layout of the application has changed orbecause configuration changes have altered the data that users must enter in thetransaction). You will therefore have to review the tests as well as re-testing.

The Business Process Change Analyzer allows you to create a new Test Planbased on the results of the analysis. To do this, select the relevant analysis in thelist of all of the BPCA runs and then, in the grid below the overview, choose theCreate Test Plan option. This creates a new test plan with precisely the scope ofthe changes identified by the Business Process Change Analyzer, allowing you totarget your testing activities more precisely.





Exercise 7: Business Process ChangeAnalyzer

Exercise ObjectivesAfter completing this exercise, you will be able to:• Create a Technical Bill Of Materials for a transaction• Run a Business Process Change Analysis and generate a new test plan to

re-test the impacted test cases.

Business ExampleYou are working on an upgrade project and need to assess the impact of thechanges on your business processes. TBOMs will help you to do this bycomparing the technical contents of your transactions with the contents of thetransport requests that you are going to import.

Task 1:In this exercise you will create a TBOM for transaction VA01.





→ In the navigation panel, open the menu entry Build (on the left-hand side)


1. In your SAP Solution Manager project SOLT200_## drill down in theproject structure to the node Create Order in ERP. Find and select transactionVA01.

2. Select the TBOM as an attribute to the previously marked transaction.

3. Create a new dynamic TBOM for transaction VA01 using the following data:

Screen Field Value

Initial Screen Order Type OR

Initial Screen Sales Organization 1000

Initial Screen Distribution Channel 10

Initial Screen Division 00




Data Entry Screen Sold-To Party 1234

Data Entry Screen Material P-103

Data Entry Screen Quantity 1

4. Examine the contents and summary of the TBOM.

Task 2:In this exercise you will compare the TBOM that you created in the last exercisewith the transport request provided by your trainer.




→ Open the tab for Test Management

→ In the navigation panel, open the menu entry BP Change Analyzer

1. Prepare the change impact analysis by setting the parameters as follows:

Field Value

Analysis Description BPCA ## for VA01 changes

Change Event Scope From Transport Requests

System TT5

Client 800

Transport requests Your instructor will tell you whichrequest to use

BP Hierarchy Node Scope Project

Project ID SOLT200_##

Leave all other default values as they are

2. Run the analysis. To see the progress of the analysis, refresh the display.

3. Open the contents of the analysis to see the impact of the changes on yourproject.

4. Generate a new test plan based on the results of the analysis.

5. View the newly generated test plan in the Test Plan Managementenvironment.



Solution 7: Business Process ChangeAnalyzerTask 1:In this exercise you will create a TBOM for transaction VA01.





→ In the navigation panel, open the menu entry Build (on the left-hand side)


1. In your SAP Solution Manager project SOLT200_## drill down in theproject structure to the node Create Order in ERP. Find and select transactionVA01.

a) Navigate to <Group Project Description> -> Business Scenarios ->Sales ## -> Business Processes -> Sales PRocess ## -> Create Orderin ERP.

b) Switch to the Transactions tab.

c) Mark the row for transaction VA01.

2. Select the TBOM as an attribute to the previously marked transaction.

a) Choose Attributes tab.

b) Choose the tab TBOM.

3. Create a new dynamic TBOM for transaction VA01 using the following data:

Screen Field Value

Initial Screen Order Type OR

Initial Screen Sales Organization 1000

Initial Screen Distribution Channel 10

Initial Screen Division 00




Data Entry Screen Sold-To Party 1234

Data Entry Screen Material P-103

Data Entry Screen Quantity 1

a) On the TBOM tab, click Create.

b) A dialog box appears containing the settings for the TBOM. Ensure thatthe Dynamic checkbox is set and choose Continue.

c) Complete the transaction using the following data:

Screen Field Value

Create Sales Order -Initial Screen

Order Type OR


Sales Organization 1000


Distribution Channel 10


Division 00

d) Hit Enter. In the upcoming screen, enter the following data:

Screen Field Value

Create StandardOrder - Overview

Sold-To Party 1234

Create StandardOrder - Overview,Sales tab

Material P-103

Create StandardOrder - Overview,Sales tab

Quantity 1

e) Save your settings.

f) Wait until you are informed that your TBOM has been createdsuccessfully.

4. Examine the contents and summary of the TBOM.

a) In the TBOM tab, choose Display TBOM Content and TBOM ContentStatistics to display information about your new TBOM.




Task 2:In this exercise you will compare the TBOM that you created in the last exercisewith the transport request provided by your trainer.




→ Open the tab for Test Management

→ In the navigation panel, open the menu entry BP Change Analyzer

1. Prepare the change impact analysis by setting the parameters as follows:

Field Value

Analysis Description BPCA ## for VA01 changes

Change Event Scope From Transport Requests

System TT5

Client 800

Transport requests Your instructor will tell you whichrequest to use

BP Hierarchy Node Scope Project

Project ID SOLT200_##

Leave all other default values as they are

a) Make the following entries as listed in the above mentioned table.

2. Run the analysis. To see the progress of the analysis, refresh the display.

a) Choose Run.

b) To get the analysis populated on the UI, you have to refresh the display:Click Refresh below the bottom right-hand corner of the list of analyses.




3. Open the contents of the analysis to see the impact of the changes on yourproject.

a) Once the analysis is finished, select it in the results grid. A moredetailed results view appears in a grid below.

b) Select your project from this detailed results list and choose the DisplayDetails button.

c) To see the exact point of impact, select your project in the bottom gridand choose the Display Intersection button.

You can see that the process step Create Order in ERP is affected viachanges occurring within transaction VA01.

4. Generate a new test plan based on the results of the analysis.

a) In the second of the tree grids, select the project and choose the CreateTest Plan button.

b) Enter the following data:

Field Value

Project SOLT200_##

Title Retest SOLT200_##

Responsible SMI310-##

Settings Deselect both, Only ReleasedDocuments and WithTransactions

Release Status Schema Defaults

Documentation Type for TestNote

Test Note for TestCase

c) Generate and save the new test plan. When prompted for a package,chose Local Object or enter package $TMP.

5. View the newly generated test plan in the Test Plan Managementenvironment.

a) In the Test ManagementWork Center, select Test Plan Managementfrom the navigation panel.

b) To get your newly created test plan populated into the list, click Refreshbelow the bottom right-hand corner of the list of test plans.

c) Select your test plan and choose Test Plan button, Display Test Plan.

d) Expand the test plan structure.



As you can see, the test plan has been generated for the process stepCreate Order in ERP .



Lesson Summary

You should now be able to:• Explain why TBOMs are necessary• Run a change analysis


SMI310 Unit Summary

Unit SummaryYou should now be able to:• How to create and update templates• How to implement templates• How to roll back template requirements and roll out updated templates• How to compare and adjust template changes from an update template to a

local implementation project.• Explain the purpose of Solution Documentation Assistant• Use the Solution Documentation Assistant• Explain why TBOMs are necessary• Run a change analysis


Unit Summary SMI310


Unit 11Authorization and Roles

Unit OverviewThis unit describes the various implementation roles in the SAP Solution Manager.The lesson also explains the authorization of roles in the SAP Solution Manager.


• Utilize the different roles delivered with SAP Solution Manager• Describe the underlying authorization concept for SAP Solution Manager

Unit ContentsLesson: Working with Authorizations and Roles... . . . . . . . . . . . . . . . . . . . . . . . . .312


Unit 11: Authorization and Roles SMI310

Lesson: Working with Authorizations and Roles

Lesson OverviewThis lesson describes the various implementation roles in the SAP SolutionManager. The lesson also explains the authorization of roles in the SAP SolutionManager.


• Utilize the different roles delivered with SAP Solution Manager• Describe the underlying authorization concept for SAP Solution Manager

Business ExampleWhile trying to understand the toolset, your team discovers that the SAP SolutionManager ships with various implementation roles. These roles can be used byproject managers to log on to the implementation project by using the roles andauthorizations assigned to them and work through their specific project tasks. Youdecide to implement the SAP Solution Manager for the Project Manager role.You need to grant full authorization to Project Managers for their functions ortransactions.

Introducing the Roles and Authorization Concept

Figure 178: Roles and Authorizations in Implementation Projects


SMI310 Lesson: Working with Authorizations and Roles

Figure 179: Working with end-user oriented composite roles

Authorizations are assigned to project roles during the project implementationphase in the SAP Solution Manager. Authorizations determine the degree ofaccess project members have to functions and transactions in the project.

Various implementation roles are delivered with the SAP Solution Manager.Project members can log on to the implementation project using the roles andauthorizations assigned to them and work through their specific project tasks.The authorization concept for the SAP Solution Manager is predefined for thefollowing roles:

Exploring Composite Roles in Detail• Project Manager• Application Consultant• Development Consultant• Technical Consultant• Read-Only User• Read User by Status• Tester

SAP delivers predefined composite roles (SAP_SOL_*_COMP) asrecommendations. Each role comprises various implementation project taskstypical to the role.



Project Manager

Project Managers are responsible for the realization of desired project results anddaily project management. They anticipate deviations from the project directionand promptly take necessary corrective measures. Project managers should alsounderstand the integration of business processes within the enterprise.

Role: SAP_SOL_PM_COMP

The main responsibilities of a project manager include:

• Organizing the entire project• Developing and maintaining the time schedule for the implementation project• Assigning and managing resources• Developing strategies and procedures for an efficient SAP implementation• Representing the project internally and externally• Monitoring project progress on a weekly basis• Carrying out evaluations and analyses• Carrying out a formal review at the end of each phase• Reporting regularly to the review committee on the progress and status of

the project• Giving status updates to the whole project team• Clarifying open issues in good time• Finalizing and managing the project scope, budget and deadlines in

accordance with the approved plans

Authorizations for: Project Administration, Define System Landscape,Define Business Blueprint Perform Configuration Organize/Perform Testing,Reporting/Project Monitoring, Roadmaps

Application Consultant

Application consultants are responsible for making sure that the BusinessBlueprint and software configuration are tailored to the business processes and thatanalysis and report requirements are fulfilled. They use their knowledge of provenbusiness procedures to support them in these tasks. Application consultants alsofunction as advisers and work closely with the rest of the project team. They alsowork in close cooperation with legacy system experts, when extraction of legacydata is necessary.

Role: SAP_SOL_AC_COMP



An application consultant has several important responsibilities, such as:

• Supporting definition and modeling of business processes• Checking how the business model works with the SAP products• Configuring the software to suit the required business processes and to meet

analysis and report requirements• Determining the global and local standardization requirements• Determining requirements for organizational change in the enterprise• Supporting knowledge transfer to other project team members• Defining requirements for authorization profiles and access authorizations• Analyzing statistical performance and passing on recommendations for

improvement to support• Creating and developing data solutions and strategies to meet the

requirements of the corresponding SAP component (for example, SCM,BW, CRM)

• Creating end user training materials for the new functions• Supporting organization and performance of tests

Authorizations for: Define Business Blueprint, Perform Configuration,Synchronize and Monitor Customizing, Organize and Perform Testing, Roadmaps

Technical Consultant

Technical consultants plan the technical requirements for a project with the projectmanager and the manager of the technical team and then carry out the requiredtechnical tasks in the system. Depending on the scope and complexity of theimplementation, technical consultants may work in several areas, for example,system administration, database administration, network administration, operatingsystem administration, development of cross-application components, or ABAPdevelopment.

Role: SAP_SOL_TC_COMP

The main responsibilities of the technical consultant include:

• Setting up and installing the system landscape• Managing the system landscape and the corresponding transport landscape• Providing support and advice for technical queries and issues during an

implementation project• Giving daily updates on the technical direction of the project including

communicating deviations in the project• Developing and realizing the Cut-over Plan before going live• Communicating effectively with the business process team• Transferring knowledge effectively to employees in system administration



Authorizations for: Define System Landscape, Synchronize/Monitor Customizing,Roadmaps

Development Consultant

Development consultants work with the project manager and the applicationconsultant on the planning and organization of the authorization concept. Theyalso perform developmental tasks and customer-specific developments.

Role: SAP_SOL_BC_COMP

A development consultant has several important responsibilities, such as:

• Organizing authorizations• Developing ABAP programs, for example, interfaces, forms, or modifications• Working with the ABAP Workbench

Authorizations for: Define Business Blueprint, Synchronize/Monitor Customizing,Organize/Perform Testing, Roadmaps

The Read-only role SAP_SOL_RO_COMP enables project team members todisplay relevant information, but not make changes.

The Read-User by Status role SAP_SOL_RE_COMP only allows versionsof a document with specified status values to be displayed (restricted displayauthorization or read authorization).

Note: The explanations about systems roles only refer to the SAPSolution Manager roles. Authorizations in the managed systems have tobe maintained additionally.

For the creation of roles and authorizations use transactions SU01 and PFCG.

Authorizations are assigned to project roles during the project implementationphase in the SAP Solution Manager. Authorizations determine the degree of accessproject members have to functions and transactions in the project. Authorizationprofiles can be modified to meet project-specific requirements. Use the SAP tool,Profile Generator, to copy and modify existing roles.

Note: It is recommended to copy existing composite roles and adaptthe authorizations according to your project needs. Ensure that allauthorization objects are maintained.



Exploring Single Roles

Figure 180: Getting additional functionality with single roles

In addition to the composite roles, single roles have to be added for specificfunctionalities that are not included in the composite roles.

Implementations

The creation and change authorizations of roadmaps in SAP Solution Managerhave to be added by additional authorizations.

Test Management

For using the Business Process Change Analyzer a user needs dedicatedauthorizations for the BPCA (SAP_SM_BPCA_*), like the authorization forBPCA execution (display) and TBOM execution (display). You can add thesesingle roles to your users that already have the implementation or test managementcomposite roles.

Test Management Reporting for BW is based on the Extractor Framework anddepends on how BW concept is developed. You can use it in the same clientor/and system as SAP Solution Manager or you can use it in an external system. Ifyou use it in an external system,, the role for BW must be downloaded from theSolution Manager system and uploaded in your BW-System.

The workflow functionality can specify and start actions at specified events in thetest management process or during testing. Sending an E-mail is the default value.This bases on CRM functionality and needs additional authorizations.



Document Management

You can control the access rights to documents in the project by assigningauthorizations for groups of documents, for instance you can specify that only theproject management can change documentation templates. The system savesSolution Manager documents in folders.

Service Desk

Service Desk bases on CRM. As admin you can create Business Partners, canrestrict Service Desk creation, restrict processing of Service Desk messages ormessage handling in general (SAP_SUPPDESK_*).

Workcenter Concept and Related Roles

Figure 181: Workcenter Concept and Related Roles

Important work center for Implementation and Upgrade projects:

• SAP_SMWORK_BASIC: Basic Authorization Objects• SAP_SMWORK_MYHOME: My Home Page• SAP_SMWORK_IMPL: Implementation and Upgrade• SAP_SMWORK_ITEST: Test Management• SAP_SMWORK_SDA: Solution Documentation Assistant• SAP_SMWORK_SETUP: SAP Solution Manager Administration



Work centers are central work environments that provide access to role-specificfunctions. The structure of a work center depends on your role. In contrastto authorization roles which contain a number of authorization objects, workcenter roles only contain authorization object S_TCODE for transactionSOLMAN_WORKCENTER. The main focus lies on the menu tab as it defines thenavigation for the user in the work center.

They need to be assigned to the user in addition to the authorization roles forthe individual scenarios (e.g. SAP_SMWORK_IMPL) in addition to single roleSAP_SMWORK_BASIC.

You can specify which work centers and assigned links to transactions or furtherfunctions are offered to your users in the work centers. By default, all areaswith assigned transactions and further links are shown in the lists. You can hidetransactions, etc. parts of areas, or entire areas, if you do not need them.

• SAP_SMWORK_BASIC offers the basic settings to open a work center as itcontains all necessary authorization objects for it. Therefore, it is needed inaddition to all other work centers.

• Implementation and Upgrade: It comprises views in which you can describe,configure, and test business processes and scenarios within a project.Includes Custom Development Management Cockpit.

• Test Management: This work center is the central access to all functions forpreparing, creating, managing, and evaluating test plans. Includes BusinessProcess Change Analyzer.

• Solution Documentation Assistant: The Solution Documentation Assistantevaluates SAP Solution Manager business processes automatically.

• SAP Solution Manager Administration comprises views in which you canset up and manage solutions, projects and systems, and execute user-specificfunctions. You can also perform common tasks that you need often inadministration.

Prerequisites for Using Implementation Functionalities

Figure 182: Creation of RFCs to Managed Systems as Prerequisite



The creation of RFC connections between SAP Solution Manager and themanaged systems is the prerequisite for lots of implementation functionalities,such as the creation of an IMG project in the managed system, using testmanagement efficiently, TBOM creation, etc. In case of a Trusted RFC connectionany user that will be performing functions via this connection, must also havethe authorization object S_RFCACL assigned. This authorization object is notincluded in the profile SAP_ALL for security reasons. The user name has to bethe same in each of the systems. For conducting his business task, the user needsin addition appropriate authorizations in the managed system. Some functionsrequire roles or profiles in the managed systems, like Customizing Distributionand Comparison, Customizing Scout and BC Sets.

Information for Roles and Authorizations

Figure 183: Up to date information for Roles and Authorizations

For additional Roles and Profiles used in the managed systems, please see the SAPSolution Manager Security Guide and SAP Note 834534.

The above matrix shows various authorization profiles of Project Managersand Application Consultants with regards to their authorization in the ProjectAdministration transaction.



The following authorizations are available for your project:

• A – A user with the project role has full authorization for the function ortransaction.

• D – A user with the project role can call the function or transaction in thedisplay mode.

• N – A user with the project role has no authorization. This function ortransaction is not in the project role menu.

Note: The SAP Security Guide can be downloaded fromhttp://service.sap.com/solutionmanager –> Getting Started with EHP 1 –>Planning, Installation, Upgrade Guides –> Operations –> Security GuideSAP Solution Manager 7.0 EHP 1, or at: http://service.sap.com/instguides–> SAP Components –> SAP Solution Manager (current release).



Lesson Summary

You should now be able to:• Utilize the different roles delivered with SAP Solution Manager• Describe the underlying authorization concept for SAP Solution Manager

Related Information

• SAP Solution Manager Security Guide• SAP Note 834534


SMI310 Unit Summary

Unit SummaryYou should now be able to:• Utilize the different roles delivered with SAP Solution Manager• Describe the underlying authorization concept for SAP Solution Manager


Unit Summary SMI310


Unit 12Additional Information

Unit OverviewThis unit shows you where you can find further information on SAP SolutionManager in implementation projects.


• You know the important sources for further information.

Unit ContentsLesson: Further Information ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .326


Unit 12: Additional Information SMI310

Lesson: Further Information

Lesson OverviewYou attended the training course SMI310 and want to know where can find furtherinformation.


• You know the important sources for further information.

Business ExampleYou are back home from your SMI310 implementation course and want to deepenyour knowledge.

Further Information on SAP Solution Manager

Figure 184: Further Information


SMI310 Lesson: Further Information

Figure 185: Further Information

Figure 186: Books related to SAP Solution Manager


Unit 12: Additional Information SMI310

Lesson Summary

You should now be able to:• You know the important sources for further information.


SMI310 Unit Summary

Unit SummaryYou should now be able to:• You know the important sources for further information.


Unit Summary SMI310


SMI310 Course Summary

Course SummaryYou should now be able to:

• Explore the key concepts of SAP Solution Manager in the context ofimplementation projects

• Understand the concepts of application lifecycle management (ALM) andhow SAP Solution Manager supports ALM

• Define a project and document the system landscape for the solution to beimplemented

• Design and document the project scope, including its business requirements• Configure the project scope• Organize, perform and document all project-related test activities• Use roadmaps as the underlying project methodology• Explore reports to support project management activities• Learn about handling problem messages in implementation projects• Get an impression of how SAP Solution Manager supports the maintenance

of your productive environment• Learn about implementation-related topics, such as template management,

Solution Documentation Assistant and Business Process Change Analyzer• Get technical background information as required for your project role• Locate additional information about the SAP Solution Manager


Course Summary SMI310


IndexAAdjust Structure, 96ASAP ImplementationRoadmap, 70

BBusiness Blueprint, 93GGeneral documentation, 99Global ASAP Methodology,70

RRoadmap, 71

RunSAP Roadmap, 70SSolution Manager, 36TTransaction documentation,99

UUpgrade Roadmap, 70


Index SMI310


FeedbackSAP AG has made every effort in the preparation of this course to ensure theaccuracy and completeness of the materials. If you have any corrections orsuggestions for improvement, please record them in the appropriate place in thecourse evaluation.
