Smi310 en Col84

Full text

(1)SMI310 SAP Solution Manager: Implementation Projects with SAP Solution Manager SAP Solution Manager. Date Training Center Instructors Education Website. Participant Handbook Course Version: 84 Course Duration: 3 Day(s) Material Number: 50095974. An SAP course - use it to learn, reference it for work.

(2) Copyright Copyright © 2010 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.. Trademarks •. Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered 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 trademarks of Citrix Systems, Inc.. •. HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide 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.com are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other products mentioned are trademarks or registered trademarks of their respective companies.. Disclaimer THESE MATERIALS ARE PROVIDED BY SAP ON AN "AS IS" BASIS, AND SAP EXPRESSLY DISCLAIMS ANY AND ALL WARRANTIES, EXPRESS OR APPLIED, INCLUDING WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THESE MATERIALS AND THE SERVICE, INFORMATION, TEXT, GRAPHICS, LINKS, OR ANY OTHER MATERIALS AND PRODUCTS CONTAINED HEREIN. IN NO EVENT SHALL SAP BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES OF ANY KIND WHATSOEVER, INCLUDING WITHOUT LIMITATION LOST REVENUES OR LOST PROFITS, WHICH MAY RESULT FROM THE USE OF THESE MATERIALS OR INCLUDED SOFTWARE COMPONENTS.. g2010029103157.

(3) About This Handbook This handbook is intended to complement the instructor-led presentation of this course, and serve as a source of reference. It is not suitable for self-study.. Typographic Conventions American English is the standard used in this handbook. The following typographic conventions are also used. Type Style. Description. Example text. Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths, and options. Also used for cross-references to other documentation both internal and external.. 2010/Q1. Example text. Emphasized words or phrases in body text, titles of graphics, and tables. EXAMPLE TEXT. Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example SELECT and INCLUDE.. Example text. Screen output. This includes file and directory names and their paths, messages, names of variables and parameters, and passages of the source text of a program.. Example text. Exact user entry. These are words and characters that you enter in the system exactly as they appear in the documentation.. <Example text>. Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.. © 2010 SAP AG. All rights reserved.. iii.

(4) About This Handbook. SMI310. Icons in Body Text The following icons are used in this handbook. Icon. Meaning For more information, tips, or background. Note or further explanation of previous point Exception or caution Procedures. Indicates that the item is displayed in the instructor's presentation.. iv. © 2010 SAP AG. All rights reserved.. 2010/Q1.

(5) Contents Course Overview ......................................................... vii Course Goals ...........................................................vii Course Objectives .................................................... viii. Unit 1: Introduction to SAP Solution Manager Implementation. 1 SAP Solution Manager Supporting Implementations ..............2. Unit 2: Prerequisites for Implementation Projects ............... 23 Technical Prerequisites for Implementation Projects ............. 24. Unit 3: Project Preparation ............................................ 33 Project Administration ................................................ 34. Unit 4: Use of Roadmaps .............................................. 63 Working with the Roadmap Methodology.......................... 64. Unit 5: Business Blueprint............................................. 91 Business Blueprint .................................................... 92 Document Management ............................................128 Reporting..............................................................152. Unit 6: Realization ...................................................... 157 Configuration and Development ...................................158 Testing .................................................................185. Unit 7: Final Preparation .............................................. 227 E-Learning ............................................................228. Unit 8: From Implementation to Operations ...................... 235 From Implementations to Operations .............................236. Unit 9: Service Desk.................................................... 247 Working with the Service Desk.....................................248. Unit 10: Managing Projects - Beyond Implementation ......... 257 Template Management ..............................................260 Solution Documentation Assistant .................................278. 2010/Q1. © 2010 SAP AG. All rights reserved.. v.

(6) Contents. SMI310. Business Process Change Analyzer ..............................293. Unit 11: Authorization and Roles.................................... 311 Working with Authorizations and Roles ...........................312. Unit 12: Additional Information ...................................... 325 Further Information ..................................................326. Index ....................................................................... 333. vi. © 2010 SAP AG. All rights reserved.. 2010/Q1.

(7) Course Overview The SAP Solution Manager is an integrated, customer platform that provides the procedures, tools and content needed to successfully and efficiently implement, operate and optimize their SAP and non-SAP solutions, regardless of the complexity of the system landscape. The purpose of this course is to introduce you to the SAP Solution Manager and is focused on the implementation portfolio delivered with this lifecycle platform. The information in this course pertains to the following SAP Software Components and releases: • • •. SAP Solution Manager 7.0 EhP1 SAP CRM 5.0 SAP ERP 6.0. Target Audience This course is intended for the following audiences: •. Project managers/leaders, project team members (application consultants/business process experts), test organizers and testers responsible for managing, documenting, configuring and testing SAP solutions. Course Prerequisites Required Knowledge • •. SAP01 – SAP Overview SM100 – Introduction to SAP Solution Manager. Recommended Knowledge • • • •. 2010/Q1. 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 SAP AG. All rights reserved.. vii.

(8) Course Overview. SMI310. Course Goals This course will prepare you to: • • •. Understand the concept of SAP Solution Manager with the focus on supporting implementation (and upgrade) projects Explore tools, contents, and methods in detail to successfully and efficiently implement complete software solutions and new enhancements Use the tools, content, and methods, provided to successfully and efficiently implement your SAP/non-SAP solution. Course Objectives After completing this course, you will be able to: • • • • • • • • • • • • •. viii. Explore the key concepts of SAP Solution Manager in the context of implementation projects Understand the concepts of application lifecycle management (ALM) and how SAP Solution Manager supports ALM Define a project and document the system landscape for the solution to be implemented 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. © 2010 SAP AG. All rights reserved.. 2010/Q1.

(9) Unit 1 Introduction to SAP Solution Manager Implementation Unit Overview SAP Solution Manager is SAP's service and support platform to help you implement and operate your SAP solution efficiently. Together with the SAP Service Marketplace, SAP Solution Manager represents SAP's strategic service infrastructure that guides our customers through all stages of their SAP solution life cycle.. Unit Objectives After 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 Contents Lesson: SAP Solution Manager Supporting Implementations ...............2. 2010/Q1. © 2010 SAP AG. All rights reserved.. 1.

(10) Unit 1: Introduction to SAP Solution Manager Implementation. SMI310. Lesson: SAP Solution Manager Supporting Implementations Lesson Overview This lesson introduces SAP Solution Manager as a platform to support implementation projects. This concept is extended to the idea of application lifecycle management, which SAP Solution Manager supports with a dedicated portfolio of tools, services and methods.. Lesson Objectives After 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 lifecycle management approach. Business Example The SAP Solution Manager is a platform that provides the integrated content, tools, and methodologies that you need to implement, support, operate and monitor your enterprise's solutions from SAP and non SAP. With SAP Solution Manager, 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 to the 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 of an SAP CRM and SAP ERP solution, with the SAP Solution Manager. During this course, you will explore the different roles and tasks involved in such an implementation procedure. •. •. • •. 2. As a project manager, you will establish a project framework, including defining the project, introducing project team members to the project, and setting project-specific standards. As a business process expert or application consultant, you will be responsible for the central business process design, and the documentation to be implemented in the later configuration phase. As a test coordinator, you will familiarize yourself with all the necessary steps from test planning to test execution and test reporting. As a tester, you will learn how to test the implemented solution and provide feedback about problem resolution.. © 2010 SAP AG. All rights reserved.. 2010/Q1.

(11) SMI310. Lesson: SAP Solution Manager Supporting Implementations. As a central lifecycle management platform, SAP Solution Manager provides access to all connected (managed) systems.Typically it is the task of a system administrator or technical expert to provide the underlying IT infrastructure for the project. Since this course focuses on business-oriented implementations, the technical 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 to the preparation and execution of implementation projects: • • • • •. Internal business needs, e.g., functional enhancements required to increase user productivity Requirements collectively generated through user groups & events, such as through DSAG and ASUG Market-driven needs, e.g., the need to comply with financial and environmental legislation Increased competitiveness, such as fulfilling sustainability criteria to increase the corporate image End of maintenance of a software release. This may ultimately lead to the implementation of a new solution, or innovation via new enhancements.. 2010/Q1. © 2010 SAP AG. All rights reserved.. 3.

(12) Unit 1: Introduction to SAP Solution Manager Implementation. SMI310. 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 the implementation of SAP solutions. Phase 1 – Project Preparation In the project preparation phase, you define the framework for your implementation project. This includes setting project goals and objectives, determining the implementation scope, defining the implementation strategy and plan, and determining the implementation tasks. SAP Solution Manager supports this phase with the following functions: • • • • •. 4. 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. © 2010 SAP AG. All rights reserved.. 2010/Q1.

(13) SMI310. Lesson: SAP Solution Manager Supporting Implementations. Primary roles involved: Project Manager, System Administrator Phase 2 – Business Blueprint In the business blueprint phase, you determine the detailed project scope for implementation. The business blueprint portrays your business process, including the functional requirements to be implemented. SAP Solution Manager supports this phase with the following functions: • •. Evaluation of SAP predefined implementation content Creation of the business blueprint, including: –. • •. Editing and scoping of the process structure to reflect your business processes – 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 the business blueprint phase. Additionally, you document all your customer-specific developments and prepare concepts for end-user documentation and training. SAP Solution Manager supports this phase with the following functions: • • • • •. Performing technical configuration, e.g. establishing connectivity between systems 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, Test Organizer, Tester Phase 4 – Final Preparation In the final preparation phase, you prepare and conduct end-user training and perform final testing on the application and managed systems, before going live. You also finish preparing and perform data conversion from legacy systems to the production system. You should also resolve all open issues. SAP Solution Manager supports this phase with the following functions: • •. 2010/Q1. Performing final test activities Creation and distribution of learning material. © 2010 SAP AG. All rights reserved.. 5.

(14) Unit 1: Introduction to SAP Solution Manager Implementation. SMI310. 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 a productive environment, establish a support organization for end users, and optimize the system performance and technical environment, as far as possible. SAP Solution Manager supports this phase with the following functions: • •. 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 project and support organizations Phase 6 – Run The primary goal of this phase is to ensure the operability of the solution. It includes the concepts of the Run SAP Roadmap but goes beyond it. This phase is not explicitly covered in this course. The following capabilities are cross-functions because they can be accessed throughout the implementation project: • •. •. Issue tracking and project reporting, to track and monitor open issues and the project 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 entire implementation project. The ASAP phases can be mapped onto the phases of the application lifecycle management (ALM), an SAP approach that provides support along the lifecycle of both SAP and non-SAP solutions, by offering tools, methods, and services and an organizational model.In this sense, the ALM approach is more holistic than the ASAP approach, because it also covers aspects of deploying and optimizing your solution. More details on the application lifecycle management is provided in the following chapter.. 6. © 2010 SAP AG. All rights reserved.. 2010/Q1.

(15) SMI310. Lesson: SAP Solution Manager Supporting Implementations. 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 maintain and store all business-process-related information and technical data to operate dedicated application lifecycle management (ALM) processes. In implementations, this includes: • • • • •. 2010/Q1. 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. © 2010 SAP AG. All rights reserved.. 7.

(16) Unit 1: Introduction to SAP Solution Manager Implementation. SMI310. By doing so, you maximize transparency and collaboration within your project team. The investments made in the implementation project can be transferred to other supporting processes of the application lifecycle, e.g. process information and system data can be used later, in technical system monitoring and business process monitoring.. Beyond Implementing Solutions - Application Lifecycle Management. 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 and solutions (Business Configuration and Business Continuity) throughout the entire life cycle, which consists of phases The required functionality is delivered by capabilities of SAP Solution Manager and other integrated tools SAP provides service and support offerings that help customers to use all these features The experience of SAP in ALM of how to best manage the application life-cycle, are summarized in best-practice methodologies, organizational models, and standards. To sum up, SAP Solution Manager is the platform to support ALM.. 8. © 2010 SAP AG. All rights reserved.. 2010/Q1.

(17) SMI310. Lesson: SAP Solution Manager Supporting Implementations. In the following, you will learn more about all phases of the ALM cycle according to ITIL. • • • • • •. Requirements: Gather requirements for new/adapted applications, based on your business needs Design: Translate requirements into feature specifications (business blueprint) 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 evaluate all functional and non-functional requirements during the requirements phase. SAP supports this phase with content and tools. At this stage, your primary concern is to evaluate scenarios and their respective business processes and check their viability for your project. In the SAP Solution Manager environment, you can use SAP Business Maps for knowledge transfer and more detailed process analysis. Their content is stored in the Business Process Repository (BPR), SAP’s process library. This includes content designed specifically for implementations that you can use in your projects. In many projects, however, you need first to analyze which transactions and processes are currently in use so that you can define the project scope. For this purpose, SAP Solution Manager Enterprise. 2010/Q1. © 2010 SAP AG. All rights reserved.. 9.

(18) Unit 1: Introduction to SAP Solution Manager Implementation. SMI310. Edition includes the Solution Documentation Assistant, which performs automatic analyses to enable you to detail your core business processes in a Business Blueprint, quickly and efficiently.. Figure 7: Design Phase. In the design phase, you use the findings from the requirements phase to specify precisely how your application or IT operation processes are to function, and which IT applications should be used to map the processes. A 2004 university study on project management found that only 43% of all projects reflect their clients’ strategies, and only 13% boost the value of the IT solution. One quarter of all projects begin with insufficient resources. To enable you to deal with impending bottlenecks quickly and efficiently, it is essential that you have professional, transparent project management procedures and a clearly-defined project scope. With these in place, you will be able to safeguard your company’s investments, deploy resources for specific objectives, set priorities, and ensure that everyone involved in a project communicates well. During this phase, application life-cycle management provides you with roadmaps (proven procedures for project management) and project management activities, using tools such as project administration functions. The standardized processes also help you draw up a well-defined, transparent conceptual design (Business Blueprint) for your project.. 10. © 2010 SAP AG. All rights reserved.. 2010/Q1.

(19) SMI310. Lesson: SAP Solution Manager Supporting Implementations. 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 defined in the design phase, in accordance with your requirements. You set up a system landscape for configuring and testing the planned scenarios and processes. You use the build and test phase to set up the system landscape that will run your scenarios and business processes, to realize the scenarios and processes you defined in the requirements phase. You adopt the structure used in the Business Blueprint, which helps you configure your solution around your business processes and during subsequent testing activities.. 2010/Q1. © 2010 SAP AG. All rights reserved.. 11.

(20) Unit 1: Introduction to SAP Solution Manager Implementation. SMI310. Implementation comprises the following steps: • • • • •. Continuous monitoring of project targets, especially costs, deadlines, and resources 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 your processes. You can navigate directly to the SAP Implementation Guide (IMG) in the different development systems being managed, and set up the systems centrally from SAP Solution Manager. You can also document the configuration settings centrally. Furthermore, by integrating existing testing tools, SAP Solution Manager supports you in organizing and documenting the results of a range of testing activities, from unit testing through to integration testing.. Figure 10: Example - Central Test Management and Execution in SAP Solution Manager. 12. © 2010 SAP AG. All rights reserved.. 2010/Q1.

(21) SMI310. Lesson: SAP Solution Manager Supporting Implementations. Figure 11: Deploy Phase. In the deploy phase, the application goes into live operation. Communication channels are critical during this phase, because they enable the smooth transfer of information to end users. Final preparation transfers the results of the realization phase into the live solution. All open issues concerning the final steps for going live are clarified. Once this phase has been completed, the production business processes of your solution can run. As in the build and test phase, the Test Management capabilities of SAP Solution Manager provide valuable support; the same utilities and tools can be used to test various aspects of the system, such as performance, load, and interfaces. At this stage, the Learning Maps created in SAP Solution Manager are distributed to the relevant end users, who can then use them for self-study, to tailor content to their working environment and provide feedback on individual units, or the Learning Map as a whole. Feedback can be evaluated and used to improve the training materials. This phase facilitates the transition from 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 days after going live, but in the long-term as well. SAP Solution Manager’s integrated Service Desk can do this. Before production can go live, the cutover plans must be implemented, which involves transferring data verified in the realization phase from the legacy system to the production system. Tested configuration settings as well as modifications and customer developments are also transported to the production system. Controlled and quality-assured change management is a key element in highly integrated solution landscapes, to ensure that SAP applications are highly available and operate reliably. Throughout the entire life cycle of an SAP solution, most changes and enhancements are made at the application level. They involve transferring custom software developments or Customizing settings made within the scope of projects or customer defined shipment cycles, to production operation. Such changes require a traceable, standardized IT process. 2010/Q1. © 2010 SAP AG. All rights reserved.. 13.

(22) Unit 1: Introduction to SAP Solution Manager Implementation. SMI310. that covers planning, approval, development, testing, and finally deployment to production. Using such a standardized process minimizes the risk of adversely affecting productive business processes.. Figure 12: Operate Phase. The operate phase groups tasks that are performed after system start-up. Most of these 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 handled automatically in many different areas, such as automated system monitoring and error notification, the collection of technical data, and report summaries based on SAP EarlyWatch Alert (EWA) and Service Level Reporting (SLR). It therefore allows you to react swiftly and appropriately, and to identify trends early and take action before errors occur. Current know-how, as well as task and workflow documentation, is also integrated in many areas with administrative responsibilities and other tasks (Central System Administration, Solution Reporting, 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 efficient transfer of knowledge give experts the time they need to concentrate on their core competencies. This, in turn, allows small teams to monitor and manage complex. 14. © 2010 SAP AG. All rights reserved.. 2010/Q1.

(23) SMI310. Lesson: SAP Solution Manager Supporting Implementations. system landscapes, while making the services they offer transparent to the end user. SAP Solution Manager therefore makes it possible to keep IT know-how inside companies or outsource it and monitor the services provided.. Figure 13: Example – Business Process Monitoring. Figure 14: Optimize Phase. 2010/Q1. © 2010 SAP AG. All rights reserved.. 15.

(24) Unit 1: Introduction to SAP Solution Manager Implementation. SMI310. During the optimize phase, you can act on key figures and data collected from the live solution, to curb expenditure or boost performance. The important thing is that you can trace any changes made in the solution. This phase comprises the functions of Change Request Management, quality gate management of upgrade support, the concept of global rollouts, and the maintenance of SAP solutions. The optimize phase is a time for ensuring that software changes are planned and implemented consistently, once your software is in operation. SAP Solution Manager supports you in this task with its functions for managing change requests. Quality gate management provides an additional quality inspection for the projects and ensures that changes are transported correctly to the production systems. The Maintenance Optimizer supports the maintenance of your solution landscape. If you need to make radical changes, for instance upgrading a software component in your solution, the tool lets you take a professional approach, using tried and tested procedures. Another challenge you may face during the optimize phase is distributing a template defined at the head office, to your organization’s subsidiaries. SAP Solution Manager’s answer to this challenge is the global rollout function.. Figure 15: Example Change Request Management Supporting Urgent Corrections. 16. © 2010 SAP AG. All rights reserved.. 2010/Q1.

(25) SMI310. Lesson: SAP Solution Manager Supporting Implementations. Figure 16: ALM Processes Covered in this Course. Note: Only the following ALM processes are covered, or mentioned, in this course: • • • •. Solution Documentation Innovation Management Template Management Test Management. Solution Documentation - The goal of solution documentation is to centrally document business processes and technical information about SAP and non-SAP solutions, to ensure transparency, efficiency and collaboration. The proper documentation of your business processes, and the technical information on systems upon which these processes run as part of an implementation project, are prerequisites for later verification and re-documentation of theses pieces of information, e.g. using the Solution Documentation Assistant. This aspect will also 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 Solution Manager, such as project administration, business blueprint, configuration, and project reporting. These capabilities are the main subject of this course. Template Management - Template Management allows customers with multi-site SAP installations to efficiently manage their business processes across geographical distances – from initial template definition to template implementation and template optimization. SAP Solution Manager supports such an approach with dedicated functionality, e.g., template projects, which have a similar but extended functional scope compared to implementation projects. How template projects and local site implementation projects work together as part of a holistic template management approach, is touched as sideline in this course.. 2010/Q1. © 2010 SAP AG. All rights reserved.. 17.

(26) Unit 1: Introduction to SAP Solution Manager Implementation. SMI310. Test Management - The goal of test management is to thoroughly test your implemented solution, using test capabilities fully embedded in SAP Solution Manager or, alternatively, third party tools. You are supported in all your testing activities – from test planning to test execution and test reporting. A dedicated unit in this course will make you familiar with the testing capabilities in SAP Solution Manager. As a sideline, you will also learn about the Business Process Change Analyzer to analyze the impact on operative business processes to be tested, based on deployed software changes. Change Control Management - Workflow-based management of businessand technology-driven solution improvement changes, with integrated project management, quality management, and synchronized deployment capabilities, to best manage the risks associated with the implementation of the solution, ensuring technical and functional robustness. Application Incident Management - Enables centralized and common incident and issue message processing, on multiple organizational levels, and offers a communication channel between all relevant stakeholders in an incident. The process includes follow-up activities such as knowledge research, root cause analysis, and change management. Technical Operations - All capabilities for monitoring, alerting, analysis, and administration of SAP solutions, and allows customers to reduce TCO by predefined content and centralized tools, for all aspects of SAP Solution Manager operations. It provides end-to-end reporting functionality either out-of-the-box, or individually created by customers. Business Process Operations - Comprises the most important application-related operations topics to ensure the smooth and reliable flow of the core business processes, 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: from discovery and retrieval to test scope optimization, optionally including automatic deployment into the production environment. Upgrade Management - The identification, adaptation, and implementation of new and enhanced business and technical scenarios, and uses SAP Solution Manager to holistically and effectively manage the upgrade project, end-to-end.. 18. © 2010 SAP AG. All rights reserved.. 2010/Q1.

(27) SMI310. Lesson: SAP Solution Manager Supporting Implementations. 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 its current stage - a holistic platform supporting major aspects of the application lifecycle management. The evolution of SAP Solution Manager started with AcceleratedSAP (ASAP), which comprised an offline CD set, providing customers with functionality, content, and methodologies to support implementation projects. This notion was enhanced to ValueSAP, which supported evaluation and continuous improvement aspect as well as implementation activities. SAP Solution Manager incorporates the concepts of ASAP and ValuesSAP into a stand-alone product, covering the entire lifecycle of applications and solutions, including implementation, operations, and optimization.. 2010/Q1. © 2010 SAP AG. All rights reserved.. 19.

(28) Unit 1: Introduction to SAP Solution Manager Implementation. SMI310. 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 lifecycle management approach. 20. © 2010 SAP AG. All rights reserved.. 2010/Q1.

(29) SMI310. Unit Summary. Unit 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 lifecycle management approach. 2010/Q1. © 2010 SAP AG. All rights reserved.. 21.

(30) Unit Summary. 22. SMI310. © 2010 SAP AG. All rights reserved.. 2010/Q1.

(31)

(32)

(33) Unit 2 Prerequisites for Implementation Projects Unit Overview This unit provides you with the basic concepts of system-related aspects of SAP Solution Manager, that you need to know to work with implementation projects. Unit Objectives After completing this unit, you will 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 attribute your business processes. Unit Contents Lesson: Technical Prerequisites for Implementation Projects ............. 24. 2010/Q1. © 2010 SAP AG. All rights reserved.. 23.

(34) Unit 2: Prerequisites for Implementation Projects. SMI310. Lesson: Technical Prerequisites for Implementation Projects Lesson Overview This lesson provides you with the basic concepts of system-related aspects of SAP Solution Manager, that you need to know to work with implementation projects.. Lesson Objectives After completing this lesson, you will 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 attribute your business processes. Business Example Your are a project manager or an application consultant of a dedicated SAP Solution Manager implementation project. You need to understand the relevant technical concepts to provide input to your system administrator for system-related aspects.. 24. © 2010 SAP AG. All rights reserved.. 2010/Q1.

(35) 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 implementation project and in other ALM (application lifecycle management) processes, such as during system monitoring, is stored centrally in SAP Solution Manager. This is also true for other system-related information, such as servers and databases, or for third-party (non-SAP) systems Not all systems that you work with are installed and configured at the beginning of the implementation project. The system landscape management of SAP Solution Manager (transaction SMSY) is populated with system information, as you work along the project phases. You need to agree a time schedule for IT to make the required physical systems available, before the start of each project stage, e.g. blueprinting, development, and testing.. 2010/Q1. © 2010 SAP AG. All rights reserved.. 25.

(36) Unit 2: Prerequisites for Implementation Projects. SMI310. Figure 19: Distributing and Using System Landscape Information. Systems managed by SAP Solution Manager can be configured so that they report their data to the SLD (System Landscape Directory) continuously (automatic registration 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 periodic job, and stores it in the Solution Manager system landscape (transaction SMSY). A properly maintained system landscape is a prerequisite for working with dedicated Solution Manager capabilities, such as business blueprint, configuration, test management or system monitoring, where the system-related data is re-used in different contexts.. 26. © 2010 SAP AG. All rights reserved.. 2010/Q1.

(37) SMI310. Lesson: Technical Prerequisites for Implementation Projects. 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 SAP product. It is specifies on which SAP or non-SAP product a dedicated business process runs (or more precisely, a process step). Typically business determines together with IT which logical components are required by a project. A logical component 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.. 2010/Q1. © 2010 SAP AG. All rights reserved.. 27.

(38) Unit 2: Prerequisites for Implementation Projects. SMI310. 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 by SAP 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. RFC connections to ABAP systems). Legend of system roles in the graphics: • • •. 28. DEVw/c – development system for workbench object/customizing QASu/i – quality assurance systems for unit/integration testing PRD – production system. © 2010 SAP AG. All rights reserved.. 2010/Q1.

(39) SMI310. Lesson: Technical Prerequisites for Implementation Projects. Figure 22: Connecting Managed Systems to SAP Solution Manager. Your IT/system administration department has to make the settings to allow you to navigate into managed systems during your project. This is done initially in the Solution Manager Configuration (SOLMAN_SETUP) transaction. As well as performing the initial and basic configuration of the SAP Solution Manager system itself, this transaction helps the system administrator to connect all managed 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: • • •. 2010/Q1. 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).. © 2010 SAP AG. All rights reserved.. 29.

(40) Unit 2: Prerequisites for Implementation Projects. SMI310. 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 attribute your business processes. 30. © 2010 SAP AG. All rights reserved.. 2010/Q1.

(41) SMI310. Unit Summary. Unit 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 attribute your business processes. 2010/Q1. © 2010 SAP AG. All rights reserved.. 31.

(42) Unit Summary. 32. SMI310. © 2010 SAP AG. All rights reserved.. 2010/Q1.

(43)

(44)

(45) Unit 3 Project Preparation Unit Overview This unit will enable you to define a project, determine project scope, and make decisions about project standards. You will also make decisions concerning the systems landscapes to be used in your solution. Unit Objectives After completing this unit, you will 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 Contents Lesson: Project Administration................................................. 34 Exercise 1: Project Administration ........................................ 53. 2010/Q1. © 2010 SAP AG. All rights reserved.. 33.

(46) Unit 3: Project Preparation. SMI310. Lesson: Project Administration Lesson Overview This unit will enable you to define a project, determine project scope, and make decisions about project standards. You will also make decisions concerning the systems landscapes to be used in your solution.. Lesson Objectives After completing this lesson, you will 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. Business Example You are ready to proceed with the implementation project using the SAP Solution Manager: • •. •. • •. 34. 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. Standard SAP business scenarios will be employed because they are delivered with predefined implementation content. Using this can significantly reduce project implementation costs. At the end of this phase, a Business Blueprint document should be generated for approval. After the Blueprint is signed-off Realization proceeds with configuring the related system landscape and performing development work to meet the defined 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 and steering committee will request regular status reports that are available through the reporting function.. © 2010 SAP AG. All rights reserved.. 2010/Q1.

(47) 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 SAP project. Each SAP project has its own unique objectives, scope, and priorities, but the 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 the project 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 Upgrade workcenter or using directly transaction SOLAR_PROJECT_ADMIN.. 2010/Q1. © 2010 SAP AG. All rights reserved.. 35.

(48) Unit 3: Project Preparation. SMI310. Work centers are central work environments that provide access to role-specific functions. The structure of a work center depends on your role. You have access to relevant work items, such as project and solutions, messages and alerts, as well as documents and reports for which your role is authorized. The number of work centers assigned to you depends on your tasks. Note: General information on how to use work centers, you find in the SAP Help Portal. http://help.sap.com –> SAP Solution Manager Note: On the SAP Service Marketplace you will find a document describing the workcenter concept and its use and adapt it. Please go to http://service.sap.com/solutionmanager–>Media Library –> How to Documents –> 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 data of a project.. 36. © 2010 SAP AG. All rights reserved.. 2010/Q1.

(49) SMI310. Lesson: Project Administration. Project Types. Figure 25: Project Types. The project types delivered with the SAP Solution Manager enable you to differentiate between various types of projects. You can use the SAP Solution Manager to create the following projects: Implementation Project: • •. The Implementation project type is considered for single-site implementations. If you create an implementation project, you can select predefined scenarios from template projects.. Template Project: •. • •. The Template project type is considered for multi-site implementations. It can also serve as an authoring environment to develop Best Practices such as created by implementation partners. If you create a template project, you can select predefined scenarios from template projects. You can transport template projects to other SAP Solution Manager systems.. Optimization Project: • •. 2010/Q1. A project to emphasize the flow of business processes, or the use of a software solution. For use in SAP Services. © 2010 SAP AG. All rights reserved.. 37.

(50) Unit 3: Project Preparation. SMI310. Safeguarding Project: • • • •. A project to resolve a critical situation in the implementation or use of an SAP solution. Safeguarding projects show the reasons for a critical situation and coordinate the 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. Functional upgrade projects are very similar to implementation projects. In addition to implementation project functionality they offer the generation of a upgrade/delta view in the project administration. Upgrade/delta-relevant IMG activities can be highlighted in the configuration if the comparison against the upgrade/delta view is triggered.. The project type you select for your project directly influences the edit options available 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 project in which it was created Project structure, with its assigned objects (General Documentation, test cases, IMG activities), is available to other projects Structure can be completely or partially locked against changes when they are used in other projects To use templates in other systems, transport them. Template projects are ideal for SAP partner solutions or for large enterprises performing a global rollout.. 38. © 2010 SAP AG. All rights reserved.. 2010/Q1.

(51) SMI310. Lesson: Project Administration. 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 administration of the SAP System. You can use the possible entries help to change these assignments. You can have both a Customer and Consultant responsible persons listed here. Project language: •. • • •. When you choose a project language, all language-dependent information for this language (project documentation and status information) is made available to project members. This is independent of the logon language of the project member. The project structure is created in the specified project language. All content 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 or link 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 start and finish and the work required in man days (MD).. 2010/Q1. © 2010 SAP AG. All rights reserved.. 39.

(52) Unit 3: Project Preparation. SMI310. Actual Data: This area enables you to enter the dates of the actual project start and finish 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 or Realization phases should lie within the time frame set in the General Data tab.. Defining the Project Scope. Figure 27: Defining the Project Scope. You define the structure of the project by specifying the project scope. You can set the project scope in various ways in an implementation project. Selecting Templates Select Templates from SAP and/or partners or customer templates created in a template project. If no template is selected, you must build the project structure using elements from the Business Process Repository in the Business Blueprint. All SAP scenarios that are transferred and saved to the project are copies. The original scenarios remain unchanged when the project structure is changed. Selecting Roadmaps. 40. © 2010 SAP AG. All rights reserved.. 2010/Q1.

(53) SMI310. Lesson: Project Administration. Select Roadmaps from the range of supplied SAP or own created roadmaps. When using Roadmaps, select a Roadmap flavor with which your project team members will work. The system displays this Roadmap flavor by default when the Roadmap 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 selecting which countries are valid in the project. The default is all countries. With the Industry Selection tab it is possible to define what industries will be considered 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 can restrict the extent to which project members can work on the Business Blueprint in the Scope tab, as shown below: •. •. •. 2010/Q1. Edit structure – By selecting the respective locking option you cannot place project structure elements in and out of the scope or enhance the project structure. Edit structures, Change documents, and in the Administration tab – You cannot edit project structure elements and modify documentation and administrative data. For project documentation: All documents with flag Blueprint-relevant are protected in Business Blueprint as well as in Configuration.. © 2010 SAP AG. All rights reserved.. 41.

(54) Unit 3: Project Preparation. SMI310. 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 project lead makes this assignment in the project administration transaction. You can use users defined in user administration and generic users (users not created in the user administration) for your user assignments. To check if the project members listed on this tab are already present in the user administration of your SAP System, click the Check against user master record button. Team members who are not SAP users are highlighted in the list. Members of staff assigned to the project on this tab are displayed in a selection list when you enter task-specific administrative data in the Administration tab in the 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, to document the assignment of a team member to a subproject or a project group. If the 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 involved in the project.. 42. © 2010 SAP AG. All rights reserved.. 2010/Q1.

(55) SMI310. Lesson: Project Administration. Defining Project Milestones. Figure 29: Defining Project Milestones. You can monitor the project progress according to the milestones defined in the Roadmap and in the project. If you have selected a Roadmap for your project in the Roadmap tab, the system lists the milestones in the selected Roadmap in the Milestones tab. You can add to the milestones in the Roadmap, but not change them.. 2010/Q1. © 2010 SAP AG. All rights reserved.. 43.

(56) Unit 3: Project Preparation. SMI310. 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. This can include function, country, time zone. Note: You cannot analyze this data in the project analysis tool. It is for information purposes only.. 44. © 2010 SAP AG. All rights reserved.. 2010/Q1.

(57) SMI310. Lesson: Project Administration. 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 status value has a ten-character status ID and a description of the status. Status IDs should be meaningful. Note that status values used in roadmaps cannot be changed or adapted to project-specific needs. Keywords: You can define keywords to flexibly categorize documents, for example, to facilitate search and reporting in the Project Analysis transaction. Keywords should be concise. Documentation Types: Various documentation types are available for all types of projects.. Standard values for status, keywords, and documentation types for your project are all set similarly in the project administration transaction. If values have not yet been assigned to a project, the project administrator can use the project template, which contains project-independent status values, keywords, and documentation types. The values in the project template are available to all projects. The project administrator decides which values should be used and assigns values to the project from the project template.. 2010/Q1. © 2010 SAP AG. All rights reserved.. 45.

(58) Unit 3: Project Preparation. SMI310. At the time of delivery, each project type is assigned to a template that contains a number of values for statuses, priorities, and documentation types. You can adapt the project template to suit project requirements. The values set in the Project Standards tab are available as default values in the Business Blueprint and Configuration transactions.. Figure 32: Project Standards – Documentation Types. Various documentation types are available for all types of projects. You can use documentation types to document all purposes during the implementation project. You can use the various documentation types delivered by SAP as templates to structure your project documentation. You can also create your own documentation types. Each documentation type has a unique ID. There are two types of project documentation: •. Project-specific documentation –. •. This documentation type is valid only for the project to which it is assigned. Cross-project documentation –. You can identify this documentation type by the Global Documentation indicator. This indicator is available for all projects and appears automatically in the Project Documentation Types list in the Documentation Types tab. Document types indicated as "global" do not need to be explicitly assigned to a project.. You can create project documentation templates for each documentation type.. 46. © 2010 SAP AG. All rights reserved.. 2010/Q1.

(59) SMI310. Lesson: Project Administration. You can analyze documentation types for the Business Blueprint in the Project Analysis transaction. Documentation templates are stored in a content repository of the SAP Solution Manager.. Figure 33: Sample of Documentation Types. You can create a template for project documentation in the Documentation Types tab. The template enables you to define the appearance and format of your documentation. You can use this template to create new documents during the Business Blueprint and Realization phases. You can define further attributes for the documentation type if required, as shown below: • •. •. •. 2010/Q1. Global doc: Set this indicator if you want to reuse a documentation type in other projects. Several documents allowed: Set this indicator to enable multiple assignment of a documentation type to structure items in your project structure. This enables you to add, for example, several documents of the Microsoft Word documentation type to one structure item. File extension: If you want to use an editor other than the text editor to create or change the document template, enter the corresponding file extension, for example, PPT for Microsoft PowerPoint. The text editor opens by default when there is no file extension. Blueprint-Relevant: Set this indicator when the document type should appear in the Business Blueprint.. © 2010 SAP AG. All rights reserved.. 47.

(60) Unit 3: Project Preparation. SMI310. To import a template from your local directory, choose Import and select the document. 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 before you can access the managed systems in subsequent project phases. You can centrally manage all the landscapes you require for your project using the SAP Solution Manager.. 48. © 2010 SAP AG. All rights reserved.. 2010/Q1.

(61) SMI310. Lesson: Project Administration. Figure 35: Define a Project System Landscape (2). Transaction –> SOLAR_PROJECT_ADMIN or Implementation and Upgrade Workcenter –> 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 be maintained to test-drive related transactions of process tasks. You cannot maintain the logical system information for non-SAP products.. Prior to the definition of a project system landscape, the products, systems, logical components and related RFC destinations should be managed in the System Landscape Maintenance transaction (SMSY). This has already been outlined in the previous units on prerequisites for implementation projects. The following functions are available based on the system landscape: • • •. 2010/Q1. 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. © 2010 SAP AG. All rights reserved.. 49.

(62) Unit 3: Project Preparation. SMI310. Figure 36: Define a Project System Landscape – Create Project IMGs. If you selected logical components for the project and defined at least a development system, all customizing subprojects are displayed in this tab. You can generate the corresponding Project IMGs and distribute the central project data (general data, project members, project standards, country selection) for these Customizing projects. When the Project IMGs are generated in the managed systems, everything is initially set in scope. The green and red traffic lights indicate if Project IMGs have already been generated 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 project in 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” is maintained in the System Landscape tab for the related logical component.. 50. © 2010 SAP AG. All rights reserved.. 2010/Q1.

(63) SMI310. Lesson: Project Administration. Feature List Project Administration. 2010/Q1. © 2010 SAP AG. All rights reserved.. 51.

(64) Unit 3: Project Preparation. SMI310. Figure 37: Feature List Project Administration. •. Assign status scheme to documentation types. –. •. You can define status values and arrange them in a status schema. A status schema can then be assigned to one or more document types. This assures that the document status values are reduced to the subset applicable to your project, e.g., status value in processing followed by review followed by released. – In project administration (transaction SOLAR_PROJECT_ADMIN): Project standards Documentation types → Project templates → Assign status schema to documentation type – Requires customizing: SAP Solution Manager Implementation Guide → SAP Solution Manager → Cross-Scenario Settings → Document Management → Document Status Activate access concept per structure node. –. –. – •. Only users who are assigned to a dedicated structure node, e.g., a business process, are allowed to change such nodes in the business blueprint and configuration phase. Requires customizing: SOLAR_PROJECT_ADMIN → <Project> → Project Team Member → Restrict changes to nodes in project to assigned 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 the software distribution of your projects, that is, of the implementation of changes to your SAP software solution, for all operational units of the various organizations in a company. This increases the transparency of the software change process. – Further information on the functional scope: http://help.sap.com SAP Solution Manager → <documentation of current release> → search for: search for: Quality Gate Management Save dedicated objects centrally in SAP Solution Manager system. – –. 52. Central test objects, eCATTs and manual test cases, can be centrally stored in the SAP Solution Manager system. Requires customizing: SOLAR_PROJECT_ADMIN → <Projects> → System Landscape → Central Objects. © 2010 SAP AG. All rights reserved.. 2010/Q1.

(65) SMI310. Lesson: Project Administration. Exercise 1: Project Administration Exercise Objectives After 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 Example You are ready to proceed with the implementation project using SAP Solution Manager. As a project lead, you initially define basic project information and decide on the methodology to support your implementation project. With the help of the technical project lead, you will subsequently define the related system landscape 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.. 2.. Create a new Project: Field Name. Values. Project. SOLT200_##, where <##> is your group number.. Project Type. Implementation Project. Solution. Do not select a solution.. Maintain the basic data:. Continued on next page. 2010/Q1. © 2010 SAP AG. All rights reserved.. 53.

(66) Unit 3: Project Preparation. 3.. SMI310. Field Name. Values. Title. <Enter a Name>. Project language. English. Save your settings. Upon save, confirm the default enhancement for documents.. Task 2: Select a roadmap as part of your project scope. 1.. Select the roadmap version ASAP Methodology for Implementation 7.0 as the 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 the following 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!. Continued on next page. 54. © 2010 SAP AG. All rights reserved.. 2010/Q1.

(67) SMI310. 2010/Q1. Lesson: Project Administration. Data Type. Value. Name. Status. ZSMIST01 and ZSMIST02. done to 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.. © 2010 SAP AG. All rights reserved.. 55.

(68) Unit 3: Project Preparation. SMI310. Solution 1: Project Administration 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.. 2.. 3.. Create a new Project: Field Name. Values. Project. SOLT200_##, where <##> is your group number.. 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 Implementation Project as the project type.. c). Choose a Solution if directed by your instructor, otherwise leave blank.. d). Click Continue.. 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.. Save your settings. Upon save, confirm the default enhancement for documents. a) Continued on next page. 56. © 2010 SAP AG. All rights reserved.. 2010/Q1.

No results found