expert charm+ +day 3

Expert Guided ImplementationChange Request Management

Day 3

Jose M Seren Rodriguez

Expert Guided ImplementationReview

Review Day 2

General Configuration• Standard Configuration

• Extended Configuration

• Master Data

• Authorization

© SAP 2008 /

Expert Guided Implementation Methodology

Introduction

Check of Prerequisites

Execution of Implementation Steps

Scenario Usage

Expert Guided ImplementationAgenda

Expert Guided ImplementationImplementation 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

© SAP 2010 /

SAP Solution Manager Projects:

Change Request Management is able to manage different types of softwarechanges. Therefore SAP Solution Manager projects and cycles allow an individualcontrol:

Maintenance Projects:

Continuous support of the Productive-System, e.g. Notes, Corrections, Release cycles . Maintenance

Projects are divided in maintenance cycles.

Implementation / Upgrade / Template Projects:

Different (e.g. development) projects with specific periods of time. Those projects are divided in project

cycles.

Project and Release Management

© SAP 2010 /

Project and Release ManagementSolution 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.

© SAP 2010 /

Assign a Logical Component

Types of Projects used inChange Request Management

SAP Solution ManagerProject

Projectcycle

Task List

Physical(Development)

Systems

Logical Systems(Clients)

IMG Project

IMG Project

TransportRequest

CTS Project

CTS Project

CTS Project

CTS Project

CTS Project

CTS Project

Project Cycle

© SAP 2010 /

Project and Release ManagementMaintenance 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 /

Project and Release ManagementCreate a Solution Manager Project

© SAP 2010 /

Create a SolutionManager Project:

Solution Manager Project

Transaction: SOLAR_PROJECT_ADMIN

Solution Manager Project is enhanced by theProject Cycle

Solution Manager ProjectLogical Components: DEV QAS PRDProject Documentation (Business Processes, Documentation, Test cases, …)

Project CycleMaintenance Cycle / Project Cycle

Developmentwithoutrelease

Developmentwith release Test Preparation

for Go-Live Go-Live

© SAP 2010 /

SAP Solution Manager

Project and Release ManagementRepresentatives of the Project Cycle

CycleTransaction

Cha

nge

Req

uest

Man

agem

ent

CycleTaskList

Project Cycle

ChangeManager

DEV

QAS

controlled transports

controlled transports

PRD

© SAP 2010 /

Recommendation: Perform allactivities in the Cycle Transaction,e.g. switch between phases.

Project and Release ManagementCycle Transaction

© SAP 2010 /

In the Cycle Transaction you canswitch the project phase.

Transaction: SCMA

Project and Release ManagementMaintenance Cycle: Definition

A Maintenance Cycle is the period of time in which you:

make changes in maintenance systemsinclude these changes in new transport requestsimport these requests into follow-up systems for testing

At the end of a maintenance cycle, all transport requests are imported into theproduction system at the same time.

Subsequently, the maintenance cycle can be closed manually and a new one can becreated, if necessary (but only in compliance with the rules of the change requeststhat belong to the maintenance cycle).

© SAP 2010 /

Phases of a Maintenance Cycle:What can be done in which phase?

Developmentwithoutrelease


for Go-Live Go-Live

Transport requestsand transport taskscan be created.

Exports are notpermitted (except inthe case of urgentcorrections).

Export of urgentcorrections arepermitted in everyphase except for theGo-Live phase.

When using the newregular correction(SDMJ), this phase isnot recommendedbecause transport ofcopies can not beexported.

Transport requestscan be released fromwithin a regularcorrection.

For regularcorrections, theadministrator has touse the task list toimport all releasedcorrections into thetest systems or hehas to scheduleregular import batchjobs in the satellitesystems.

Release of regularcorrections is notpossible anymore(code freeze)

Errors can be fixedwith test messages

Urgent correctionscan be used as in theprevious phases

Unfinisheddevelopments will notbe included in theactual test and go-live, they can beincluded in the nexttest phase.

If changes still haveto be made after thetest phase has beencompleted, transportrequests and taskscan be created andreleased as part ofthe Preparation forGo-Live phase, butonly by using thetask list of theschedule manager.

Importing the entireproject buffer into theproduction system.No type of correctioncan be releasedduring this phase.

© SAP 2010 /

Maintenance / Project Cycle

Project and Release ManagementDifferences between Project Cycle and Maintenance Cycle

Project Cycle Maintenance CycleFor Implementation, Upgrade andTemplate Projects

Only for Maintenance Projects

Usually the phases of the cycle werepassed only once. A new cycle hasto be created after completing.

Phases of the cycle can be resetafter completing the cycle.

For these project types no urgentcorrections are possible.This is not necessary, because thenew functionality is not yet life inproduction.

Urgent corrections can be releasedin all phases except ‘Go Live’.

© SAP 2010 /

Project and Release ManagementImplementation Projects

SAP Solution Manager Project (Implementation Project)

Developmentwithout release


for Go-Live Go-Live

Test Messages(during integration test)

NormalCorrections

Project Cycle

© SAP 2010 /

Project and Release ManagementMaintenance Projects

SAP Solution Manager Project (Maintenance Project)



for Go-Live Go-Live


NormalCorrections

UrgentCorrections

Maintenance Cycle

© SAP 2010 /

Project and Release ManagementProjects & Cycles

Demo: Creation of a Solution Manager Project


Day 3

Processes

• Processes





• Test Message



Configuration CheckCheck for correct ChaRM settings

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

© SAP 2010 /

Transaction: SOLAR_PROJECT_ADMIN

© SAP 2008 /

Expert Guided Implementation Methodology

Motivation

Check of Pre-requisites

Execution of Implementation Steps

Scenario Usage

Expert Guided ImplementationAgenda


Day 3

Processes

• Processes





• Test Message



ProcessesUrgent Correction




for Go-Live Go-Live


NormalCorrections

UrgentCorrections

Maintenance Cycle

© SAP 2010 /



DEV

QAS

Controlled transports


Serv

ice

Des

kC

hang

e R

eque

st M

anag

emen

t

RequesterService

DeskEmployee

Developer

Tester

IT Operator Maintenance Cycle

ServiceMessage

ChangeRequest

ChangeDocument

PRD

Feedback

ChangeManager

TaskList

© SAP 2010 /

e.g. UrgentCorrection


Demo: Standard Process Urgent Correction


Day 3

Processes

• Processes





• Test Message



ProcessesNormal Correction




for Go-Live Go-Live


NormalCorrections

UrgentCorrections

Maintenance Cycle

© SAP 2010 /


DEV

QAS



Serv

ice

Des

kC

hang

e R

eque

st M

anag

emen

t

RequesterService

DeskEmployee

Developer

Tester

IT Operator

Maintenance Cycle

ServiceMessage

ChangeRequest

ChangeDocument

PRD

Feedback

ChangeManager


© SAP 2010 /

e.g. NormalCorrection


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 multipletransport 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 withinthe service requestProject exports and imports can be managed by the maintenancetask-list

© SAP 2010 /

Transport buffer Transport buffer

ProcessesNormal Corrections & Test Transports

DEV QAS PRD

Legend:

Normal CorrectionTest Transport(Transport of Copies)

TestTransport and

originaltransport

reach QAS

Only originaltransport follows

the transportroutes to PRD

Original Workbench orCustomizing transport

Test Transport

© SAP 2010 /

ProcessesConsolidated Transport

Transport buffer Transport buffer

DEV QAS PRD

Legend:

Normal Correction

Test of allCorrection(s)

Import in correctorder to ensure

consolidatedsystem state

Urgent Correction

Normal Correction(s)

Consolidated TransportUrgent Correction

© SAP 2010 /

The Consistency of Urgent Corrections and Maintenance Activities remains protected!


Demo: Standard Process Normal Correction

Differences between Normal and UrgentCorrections

Normal Correction Urgent CorrectionTransport requests have to becreated manually using actionsof the change transaction.

Transport requests aregenerated automatically

Test transports are used duringthe phase “Development withRelease”.

Test transport functionality is notavailable.

Transports are exported andimported in concordance withthe phases of the maintenancecycle.

Transports can be propagateddirectly into the follow-onsystems but remain in thetransport buffer.

A violation against theseparation of functions is only awarning.

Developer and tester must bedifferent persons.

No individual task list but thetask list of the maintenancecycle is used.

An individual task list is used.

© SAP 2010 /


Day 3

Processes

• Processes





• Test Message





DEV

QAS



Cha

nge

Req

uest

Man

agem

ent

Developer

Tester

CycleTransaction

Test Message

PRDChangeManager

TaskList

Project Phases

© SAP 2010 /

ProcessesTest 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 /


Demo: Standard Process Test Message


Day 3

Processes

• Processes





• Test Message



ProcessesAdministration Messages




for Go-Live Go-Live

Maintenance Cycle

AdministrationMessages

(during all project phases)

© SAP 2010 /

ProcessesAdministration Message


DEV

QAS



Serv

ice

Des

kC

hang

e R

eque

st M

anag

emen

t

RequesterService

DeskEmployee

IT Operator

ServiceMessage

ChangeRequest

Admin.Message

PRD

Feedback

ChangeManager

CycleTasklist

Project Phases

© SAP 2010 /

ProcessesAdministration 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 /


Day 3

Processes

• Processes





• Test Message

• Admin Message


ProcessesCompleting Project Cycles

You will see an overview of all checkswhich will be performed for completingthe cycle, and information about theimportance of the checks. Somechecks may be ignored, some mustnot be ignored (marked with ).

© SAP 2010 /

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

ProcessesCompleting Project Cycles

© SAP 2010 /

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

Open Transactions in Service Desk: Non-Released Transport Requests:

ProcessesCompleting Project Cycles – New Assignments

When you create a new cycle in the SAP Solution Manager, the saved business transactions and transportrequests 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 SystemLandscape Change Requests

© SAP 2010 /

Expert Guided ImplementationForecast

To avoid problems with the next steps it isimportant that all points from today wereimplemented carefully in your system.

Day 4

Advanced Functions

• Work Center

• Administrative Functions

• Reporting

• Monitoring

Expert Guided Implementation –How to get help

How to get help

Customer SAP Expert+353 1 467 4482

[email protected]

During the execution part you have direct access to the Expert via telephonenumber +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 /

mailto:[email protected]

Disclaimer

© SAP 2010 /

"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."

Copyright 2010 SAP AGAll 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 changedwithout 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 aretrademarks 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 arethe 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 writtenpermission 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 thatthis 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 theaccuracy 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 orimplied, 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 limitationshall 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 thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.

Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durchSAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden.

Einige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte können 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 erwähnte SAP-Produkte und Services sowie diedazugehörigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Ländern weltweit. Alle anderen in diesem Dokument erwähnten Namen vonProdukten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken. Produkte können länderspezifische Unterschiede aufweisen.

Die in dieser Publikation enthaltene Information ist Eigentum der SAP. Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Formauch immer, nur mit ausdrücklicher schriftlicher Genehmigung durch SAP AG gestattet. Bei dieser Publikation handelt es sich um eine vorläufige Version, die nicht Ihrem gültigen Lizenzvertragoder anderen Vereinbarungen mit SAP unterliegt. Diese Publikation enthält nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP®-Produkts. SAP entsteht aus dieserPublikation keine Verpflichtung zu einer bestimmten Geschäfts- oder Produktstrategie und/oder bestimmten Entwicklungen. Diese Publikation kann von SAP jederzeit ohne vorherigeAnkündigung geändert werden.

SAP übernimmt keine Haftung für Fehler oder Auslassungen in dieser Publikation. Des Weiteren übernimmt SAP keine Garantie für die Exaktheit oder Vollständigkeit der Informationen, Texte,Grafiken, Links und sonstigen in dieser Publikation enthaltenen Elementen. Diese Publikation wird ohne jegliche Gewähr, weder ausdrücklich noch stillschweigend, bereitgestellt. Dies gilt u. a.,aber nicht ausschließlich, hinsichtlich der Gewährleistung der Marktgängigkeit und der Eignung für einen bestimmten Zweck sowie für die Gewährleistung der Nichtverletzung geltenden Rechts.SAP haftet nicht für entstandene Schäden. Dies gilt u. a. und uneingeschränkt für konkrete, besondere und mittelbare Schäden oder Folgeschäden, die aus der Nutzung dieser Materialienentstehen können. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit.

Die gesetzliche Haftung bei Personenschäden oder Produkthaftung bleibt unberührt. Die Informationen, auf die Sie möglicherweise über die in diesem Material enthaltenen Hotlinks zugreifen,unterliegen nicht dem Einfluss von SAP, und SAP unterstützt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewährleistungen oder Zusagen über InternetseitenDritter ab.

Alle Rechte vorbehalten.

expert charm+ +day 3

Documents