Expert Guided Implementation Change Request Management Day 3

Jose M Seren Rodriguez

Expert Guided Implementation

Review

Review Day 2 General Configuration

Standard Configuration Extended Configuration Master Data Authorization

Expert Guided Implementation

Agenda

Expert Guided Implementation Methodology Introduction Check of Prerequisites Execution of Implementation Steps Scenario Usage

SAP 2008 / Page 3

Expert Guided Implementation

Implementation Steps in detail
Day 3 Processes
Processes Project and Release Management Configuration Check Urgent Correction Normal Correction Test Message Administration Message Completing Project Cycle

Project and Release Management

Change Request Management is able to manage different types of software changes. Therefore SAP Solution Manager projects and cycles allow an individual control:

SAP Solution Manager Projects:

Implementation / Upgrade / Template Projects: Different (e.g. development) projects with specific periods of time. Those projects are divided in project cycles.

Maintenance Projects: Continuous support of the Productive-System, e.g. Notes, Corrections, Release cycles . Maintenance Projects are divided in maintenance cycles.

SAP 2010 / Page 5

Project and Release Management

SAP 2010 / Page 6

Project and Release Management

Solution Manager Project

SAP Solution Manager projects defines the project types & systems participating in these projects. Project landscapes are defined through one or more Logical Components. Logical Components incorporate Logical Systems that have defined system role types. Only one active cycle can exist simultaneously for each project. IMG and CTS Projects collect changes: An IMG project represents a SAP Solution Manager project in one development system. A CTS Project represents an IMG project in one client.

Assign a Logical Component

SAP 2010 / Page 7

Types of Projects used in Change Request Management

Physical (Development) Systems Logical Systems (Clients) Transport Request

Project Cycle

Project cycle Task List

CTS Project

IMG Project SAP Solution Manager Project

CTS Project

CTS Project

CTS Project

IMG Project
CTS Project

CTS Project

SAP 2010 / Page 8

Project and Release Management

Maintenance Project: Definition

The maintenance project is prerequisite for production support. A maintenance project manages maintenance cycles as long as defined by the project lifecycle. The maintenance cycle distributes consistently any maintenance or urgent correction change to any system of the project landscape. One maintenance project can have multiple maintenance systems assigned to it, including the corresponding transport routes. A maintenance cycle belongs to exactly one maintenance project.

SAP 2010 / Page 9

Project and Release Management

Create a Solution Manager Project
Transaction: SOLAR_PROJECT_ADMIN

Create a Solution Manager Project:

Solution Manager Project

SAP 2010 / Page 10

Solution Manager Project is enhanced by the Project Cycle

Solution Manager Project

Logical Components: DEV QAS PRD Project Documentation (Business Processes, Documentation, Test cases, )

Project Cycle
Maintenance Cycle / Project Cycle

Development without release

Development with release

Test

Preparation for Go-Live

Go-Live

SAP 2010 / Page 11

Project and Release Management

Representatives of the Project Cycle

SAP Solution Manager

Change Request Management

Cycle Transaction

Change Manager

PRD

controlled transports

Project Cycle QAS

Cycle Task List

controlled transports

DEV

Recommendation: Perform all

activities in the Cycle Transaction, e.g. switch between phases.
SAP 2010 / Page 12

Project and Release Management

Cycle Transaction
Transaction: SCMA

In the Cycle Transaction you can switch the project phase.

SAP 2010 / Page 13

Project and Release Management

Maintenance Cycle: Definition

A Maintenance Cycle is the period of time in which you: make changes in maintenance systems include these changes in new transport requests import these requests into follow-up systems for testing At the end of a maintenance cycle, all transport requests are imported into the production system at the same time. Subsequently, the maintenance cycle can be closed manually and a new one can be created, if necessary (but only in compliance with the rules of the change requests that belong to the maintenance cycle).

SAP 2010 / Page 14

Phases of a Maintenance Cycle:

What can be done in which phase?

Maintenance / Project Cycle

Development without release Development with release Preparation for Go-Live

Test

Go-Live

Transport requests and transport tasks can be created. Exports are not permitted (except in the case of urgent corrections). Export of urgent corrections are permitted in every phase except for the Go-Live phase. When using the new regular correction (SDMJ), this phase is not recommended because transport of copies can not be exported.
SAP 2010 / Page 15

Transport requests can be released from within a regular correction. For regular corrections, the administrator has to use the task list to import all released corrections into the test systems or he has to schedule regular import batch jobs in the satellite systems.

Release of regular corrections is not possible anymore (code freeze) Errors can be fixed with test messages Urgent corrections can be used as in the previous phases Unfinished developments will not be included in the actual test and golive, they can be included in the next test phase.

If changes still have to be made after the test phase has been completed, transport requests and tasks can be created and released as part of the Preparation for Go-Live phase, but only by using the task list of the schedule manager.

Importing the entire project buffer into the production system. No type of correction can be released during this phase.

Project and Release Management

Differences between Project Cycle and Maintenance Cycle

Project Cycle
For Implementation, Upgrade and Template Projects

Maintenance Cycle
Only for Maintenance Projects

Usually the phases of the cycle were passed only once. A new cycle has to be created after completing. For these project types no urgent corrections are possible. This is not necessary, because the new functionality is not yet life in production.

Phases of the cycle can be reset after completing the cycle.

Urgent corrections can be released in all phases except Go Live.

SAP 2010 / Page 16

Project and Release Management

Implementation Projects

SAP Solution Manager Project (Implementation Project)

Development without release

Development with release

Test

Preparation for Go-Live

Go-Live

Project Cycle

Normal Corrections

Test Messages
(during integration test)

SAP 2010 / Page 17

Project and Release Management

Maintenance Projects

SAP Solution Manager Project (Maintenance Project)

Development without release

Development with release

Test

Preparation for Go-Live

Go-Live

Maintenance Cycle

Normal Corrections

Test Messages
(during integration test)

Urgent Corrections

SAP 2010 / Page 18

Project and Release Management

Projects & Cycles

Demo: Creation of a Solution Manager Project

Expert Guided Implementation

Implementation Steps in detail
Day 3 Processes Processes
Project and Release Management Configuration Check Urgent Correction Normal Correction Test Message Administration Message Completing Project Cycle

Configuration Check
Transaction: SOLAR_PROJECT_ADMIN

Check for correct ChaRM settings

Check your Project for correct settings before you generate a Task List.

SAP 2010 / Page 21

Expert Guided Implementation

Agenda

Expert Guided Implementation Methodology Motivation Check of Pre-requisites Execution of Implementation Steps Scenario Usage

SAP 2008 / Page 22

Expert Guided Implementation

Implementation Steps in detail
Day 3 Processes Processes
Project and Release Management Configuration Check Urgent Correction Normal Correction Test Message Administration Message Completing Project Cycle

Processes

Urgent Correction
SAP Solution Manager Project (Maintenance Project)

Development without release

Development with release

Test

Preparation for Go-Live

Go-Live

Maintenance Cycle

Normal Corrections

Test Messages
(during integration test)

Urgent Corrections

SAP 2010 / Page 24

Processes

Urgent Correction

SAP Solution Manager

Service Desk
Feedback

Service Desk Employee

Service Message

Requester

Change Request Management

Developer

Change Request

Change Manager

PRD

Controlled transports

Tester

Change Document
e.g. Urgent Correction

Task List

QAS

Controlled transports

IT Operator

Maintenance Cycle DEV

SAP 2010 / Page 25

Processes

Urgent Correction

Demo: Standard Process Urgent Correction

Expert Guided Implementation

Implementation Steps in detail
Day 3 Processes Processes
Project and Release Management Configuration Check Urgent Correction Normal Correction Test Message Administration Message Completing Project Cycle

Processes

Normal Correction
SAP Solution Manager Project (Maintenance Project)

Development without release

Development with release

Test

Preparation for Go-Live

Go-Live

Maintenance Cycle

Normal Corrections

Test Messages
(during integration test)

Urgent Corrections

SAP 2010 / Page 28

Processes

Normal Correction

SAP Solution Manager

Service Desk
Feedback

Service Desk Employee

Service Message

Requester

Change Request Management

Developer

Change Request

Change Manager

PRD

Controlled transports

Tester

Change Document
e.g. Normal Correction

Maintenance Cycle QAS

Controlled transports

IT Operator DEV

SAP 2010 / Page 29

Processes

Normal Correction
The Normal Correction relates to the life cycle of the project Each project can have as many Normal Corrections as required A Normal Correction can be shared by multiple developers, and multiple transport requests and transport tasks can be created A Normal Correction phase depends on the phase of the project cycle Normal Corrections can only be distributed by import project Transport requests/tasks can be created and exported from within the service request Project exports and imports can be managed by the maintenance task-list

SAP 2010 / Page 30

Processes

Normal Corrections & Test Transports

Legend: Normal Correction

Test Transport

Test Transport (Transport of Copies)

Transport buffer

Transport buffer

DEV

QAS

PRD

Original Workbench or Customizing transport

Test Transport and original transport reach QAS

Only original transport follows the transport routes to PRD

SAP 2010 / Page 31

Processes

Consolidated Transport
Legend:

Urgent Correction

Normal Correction Urgent Correction Consolidated Transport

Transport buffer

Transport buffer

DEV

QAS

PRD

Normal Correction(s)

Test of all Correction(s)

Import in correct order to ensure consolidated system state

The Consistency of Urgent Corrections and Maintenance Activities remains protected!

SAP 2010 / Page 32

Processes

Normal Correction

Demo: Standard Process Normal Correction

Differences between Normal and Urgent Corrections

Normal Correction
Transport requests have to be created manually using actions of the change transaction. Test transports are used during the phase Development with Release. Transports are exported and imported in concordance with the phases of the maintenance cycle. A violation against the separation of functions is only a warning. No individual task list but the task list of the maintenance cycle is used.
SAP 2010 / Page 34

Urgent Correction
Transport requests are generated automatically Test transport functionality is not available. Transports can be propagated directly into the follow-on systems but remain in the transport buffer. Developer and tester must be different persons. An individual task list is used.

Expert Guided Implementation

Implementation Steps in detail
Day 3 Processes Processes
Project and Release Management Configuration Check Urgent Correction Normal Correction Test Message Administration Message Completing Project Cycle

Processes

Test Message
SAP Solution Manager Project (Maintenance Project)

Development without release

Development with release

Test

Preparation for Go-Live

Go-Live

Maintenance Cycle

Normal Corrections

Test Messages
(during integration test)

Urgent Corrections

SAP 2010 / Page 36

Processes

Test Message
SAP Solution Manager

Change Request Management

Developer

Cycle Transaction

Change Manager

PRD

Controlled transports

Tester

Test Message

Task List

QAS

Controlled transports

Project Phases DEV

SAP 2010 / Page 37

Processes

Test Message: Summary

Test messages can only be used in the Test phase. Test messages do not require an approval. Test messages allow inserting any system of the system landscape as a reference, supposedly a test system. Test messages must be released before status preparation for go-live is set. Test messages allow creating and releasing transport requests.

SAP 2010 / Page 38

Processes

Test Message

Demo: Standard Process Test Message

Expert Guided Implementation

Implementation Steps in detail
Day 3 Processes Processes
Project and Release Management Configuration Check Urgent Correction Normal Correction Test Message Administration Message Completing Project Cycle

Processes

Administration Messages
SAP Solution Manager Project (Maintenance Project)

Development without release

Development with release

Test

Preparation for Go-Live

Go-Live

Maintenance Cycle

Administration Messages
(during all project phases)

SAP 2010 / Page 41

Processes

Administration Message

SAP Solution Manager

Service Desk
Feedback

Service Desk Employee

Service Message

Requester

Change Request Management

Change Request

Change Manager

PRD

Controlled transports

Admin. Message

Cycle Tasklist

QAS

Controlled transports

IT Operator

Project Phases DEV

SAP 2010 / Page 42

Processes

Administration Messages: Summary

Administration messages allow performing any action including actions where no transport request is needed (including logon system that can be performed within one particular system): server switching, browser update etc.

An administration message can be created during all phases of a project and allows logon any system that is part of the project.

Access to the task list is provided.

SAP 2010 / Page 43

Expert Guided Implementation

Implementation Steps in detail
Day 3 Processes Processes
Project and Release Management Configuration Check Urgent Correction Normal Correction Test Message Admin Message Completing Project Cycle

Processes

Completing Project Cycles

Start the completion process for the cycle i.e. by switching the cycle phase from Being Completed to Completed.

You will see an overview of all checks which will be performed for completing the cycle, and information about the importance of the checks. Some checks may be ignored, some must not be ignored (marked with ).

SAP 2010 / Page 45

Processes

Completing Project Cycles

Still opened transactions and transport requests will be assigned automatically to the next cycle.

Open Transactions in Service Desk:

Non-Released Transport Requests:

SAP 2010 / Page 46

Processes

Completing Project Cycles New Assignments

When you create a new cycle in the SAP Solution Manager, the saved business transactions and transport requests are assigned to the new cycle. You see messages about the new assignments in the Application Log: Go to transaction SOLAR_PROJECT_ADMIN and select Appl. Log on the tab strip System Landscape Change Requests

SAP 2010 / Page 47

Expert Guided Implementation

Forecast

Day 4 Advanced Functions Work Center

Administrative Functions Reporting Monitoring

To avoid problems with the next steps it is important that all points from today were implemented carefully in your system.

Expert Guided Implementation

How to get help

How to get help

Customer

+353 1 467 4482 jose.maria.seren.rodriguez@sap.com

SAP Expert

During the execution part you have direct access to the Expert via telephone number +353 1 467 4482 to solve questions quickly. Please ensure that the R/3 support connection is open that we can logon to your system.

SAP 2010 / Page 49

Disclaimer

"This presentation is part of the SAP Expert Guided Implementation service and cannot be used separately, as lacking elementary empowerment parts. It may only be used by participants of the SAP Expert Guided Implementation Service and affiliated SAP users of registered participants. Unauthorized copying, extraction, alternation and distribution is not permitted. Support and further details on this document will only be provided during the SAP Expert Guided Implementation service."

SAP 2010 / Page 50

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. SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, SAP Business ByDesign, ByDesign, PartnerEdge and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned and associated logos displayed are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence. The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.

Weitergabe und Vervielfltigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrckliche schriftliche Genehmigung durch SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen knnen ohne vorherige Ankndigung gendert werden. Einige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte knnen Softwarekomponenten umfassen, die Eigentum anderer Softwarehersteller sind. SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, SAP Business ByDesign, ByDesign, PartnerEdge und andere in diesem Dokument erwhnte SAP-Produkte und Services sowie die dazugehrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Lndern weltweit. Alle anderen in diesem Dokument erwhnten Namen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich und dienen lediglich zu Informationszwecken. Produkte knnen lnderspezifische Unterschiede aufweisen. Die in dieser Publikation enthaltene Information ist Eigentum der SAP. Weitergabe und Vervielfltigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, nur mit ausdrcklicher schriftlicher Genehmigung durch SAP AG gestattet. Bei dieser Publikation handelt es sich um eine vorlufige Version, die nicht Ihrem gltigen Lizenzvertrag oder anderen Vereinbarungen mit SAP unterliegt. Diese Publikation enthlt nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP-Produkts. SAP entsteht aus dieser Publikation keine Verpflichtung zu einer bestimmten Geschfts- oder Produktstrategie und/oder bestimmten Entwicklungen. Diese Publikation kann von SAP jederzeit ohne vorherige Ankndigung gendert werden. SAP bernimmt keine Haftung fr Fehler oder Auslassungen in dieser Publikation. Des Weiteren bernimmt SAP keine Garantie fr die Exaktheit oder Vollstndigkeit der Informationen, Texte, Grafiken, Links und sonstigen in dieser Publikation enthaltenen Elementen. Diese Publikation wird ohne jegliche Gewhr, weder ausdrcklich noch stillschweigend, bereitgestellt. Dies gilt u. a., aber nicht ausschlielich, hinsichtlich der Gewhrleistung der Marktgngigkeit und der Eignung fr einen bestimmten Zweck sowie fr die Gewhrleistung der Nichtverletzung geltenden Rechts. SAP haftet nicht fr entstandene Schden. Dies gilt u. a. und uneingeschrnkt fr konkrete, besondere und mittelbare Schden oder Folgeschden, die aus der Nutzung dieser Materialien entstehen knnen. Diese Einschrnkung gilt nicht bei Vorsatz oder grober Fahrlssigkeit. Die gesetzliche Haftung bei Personenschden oder Produkthaftung bleibt unberhrt. Die Informationen, auf die Sie mglicherweise ber die in diesem Material enthaltenen Hotlinks zugreifen, unterliegen nicht dem Einfluss von SAP, und SAP untersttzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewhrleistungen oder Zusagen ber Internetseiten Dritter ab. Alle Rechte vorbehalten.