Sie sind auf Seite 1von 10

SMI310 Lesson: Global Template/Rollout Approach

Figure 105: Global Features Reuse in Rollout Project (1)

Project Preparation
Create a local rollout project (usual type: implementation)
Select one or multiple templates and related scenarios in the Scope tabbed
page. You can restrict your selection and do not have to re-use all scenarios
in a chosen template. You can only choose from templates which have been
made available for public visibility in the 'master' project.

Figure 106: Global Features Reuse in Rollout Project (2)

2006/Q2 2007 SAP AG. All rights reserved. 201


Unit 4: Managing Projects Beyond Implementation SMI310

Business Blueprint
Adapt harmonized and local processes to local-specific requirements (such
as enhance process scope)
Document local-specific requirements of harmonized/local processes
Documentation in the General Documentation tab of a rollout project has been
inherited as part of the template. This type of documentation may be adopted for
use within the rollout project, where it will appear as Project Documentation.
Realization
Use the local-specific installation guide to facilitate system set up
Apply template-specific customizing (related BC Sets) for standard processes
Perform final configuration (delta customizing) based on local-specific
requirements
Reuse master data samples recorded in the template context
Consider global customer developments (reports, ...) assigned in the
Transaction tabbed page
Reuse standard test cases (manual test cases or CATTs ) to test standard
processes and use as template to create test cases for local-specific
requirements

Figure 107: Locking Concept at a Glance

The value you give to the global attribute of a structure element can lock it against
changes in the rollout project, or allow it to be changed wholly or in part.
For the most recent information, please refer to the online help documentation for
your release of SAP Solution Manager.

202 2007 SAP AG. All rights reserved. 2006/Q2


SMI310 Lesson: Global Template/Rollout Approach

Lesson Summary
You should now be able to:
Describe the global template/rollout approach
Use the SAP Solution Manager in a local rollout project
Explain the global features of templates

2006/Q2 2007 SAP AG. All rights reserved. 203


Unit 4: Managing Projects Beyond Implementation SMI310

Lesson: Use In Upgrade Projects

Lesson Overview
This lesson will discuss how Solution Manager can be used to plan for and carry
out an Upgrade Project

Lesson Objectives
After completing this lesson, you will be able to:
Explain the phases of an upgrade project
Explain how the SAP Solution Manager can support the different phases
Which content is available for upgrade projects

Business Example
Your company's productive SAP landscape will reach its end of maintenance in
the near future. The company needs to begin planning for the upgrade.

Upgrades with Solution Manager

Figure 108: Upgrade Cost Drivers

In every upgrade project, costs and unknowns are issues. Using SAP Solution
Manager in the upgrade project can help control those costs and limit the
unknowns.

204 2007 SAP AG. All rights reserved. 2006/Q2


SMI310 Lesson: Use In Upgrade Projects

Figure 109: Process In Detail

The Upgrade phases will be discussed in detail later in the lesson

Upgrade Support Upgrade Roadmap

Figure 110: SAP Upgrade Roadmap at a Glance (1)

2006/Q2 2007 SAP AG. All rights reserved. 205


Unit 4: Managing Projects Beyond Implementation SMI310

Figure 111: SAP Upgrade Roadmap at a Glance (2)

Figure 112: When to Use Which Upgrade Roadmap

As with an Implementation Projects, it is possible to use predefined templates for


the Upgrade Roadmap.

206 2007 SAP AG. All rights reserved. 2006/Q2


SMI310 Lesson: Use In Upgrade Projects

All functionality and features available during Implementation Projects are also
available in the Upgrade Projects, such as:
Filter and user-specific setings
Flexible search and print features
Download of project plan template in HTML or MS project format
Central status and issue trancking
Assign and monitor activites of responsible project team members
Storage of project documents and flexible keyword search

Figure 113: SAP Upgrade Roadmap Top 10 Accelerators

Figure 114: SAP Upgrade Roadmap Benefits in Detail

2006/Q2 2007 SAP AG. All rights reserved. 207


Unit 4: Managing Projects Beyond Implementation SMI310

Figure 115: SAP Upgrade Roadmap Version 2.0

Upgrade Support Tools

Figure 116: Upgrade Project Project Preparation

As with Implementation Projects, Upgrade projects follow the ASAP methodology,


but with unique tasks designed to deal with the issues of upgrades, such as:
Current technical status of the system
System release
Database version and patch
Add-Ons and Support Package Levels
Identifying core business processes
Identifying customer development and interfaces

208 2007 SAP AG. All rights reserved. 2006/Q2


SMI310 Lesson: Use In Upgrade Projects

Figure 117: Upgrade Project Blueprint

Figure 118: Upgrade Features Blueprint

Figure 119: Upgrade Project Realization

2006/Q2 2007 SAP AG. All rights reserved. 209


Unit 4: Managing Projects Beyond Implementation SMI310

Figure 120: Upgrade Features Realization

Figure 121: Upgrade Features Testing

210 2007 SAP AG. All rights reserved. 2006/Q2

Das könnte Ihnen auch gefallen